Anyone setup SCCM 2007 SP2?

m4cc45

m4cc45

m4cc45

Soldato
Joined
10 Mar 2003
Posts
6,790
Hi,

As topic really. Just looking for good guides. After a lot of messing about I finally got it installed, all fine and dandy, but I'm thinking there must be post install tasks (obviously creating boundaries, software distribution, windows deployment, etc.) that I would rather have a quick read about rather than attempting blindly, so to speak.

So if you have any useful links, etc. then please let me know.



M.
 
Yeah I'm chucking the DB onto a SQL cluster so that's no problem. I had a nightmare trying to get it to install on Windows 2008 because of Webdav problems (even though it was installed - ended up reinstalling it and IIS then it was fine).

We have an old SCCM server which is running really badly (hearbeat service isnt running) and the permissions have been setup incorrectly so rather than fix this I'd rather start again which means I have a problem of updating clients to new site code, etc.



M.
 
Yeah I'm looking forward to it - I would prefer to start with nothing but the clients out in the field pointing to the old server so when I change it over it's probably going to cause issues no doubt.

The setup is possibly the worst installer I've ever used and it's only by sheer persistence that I've gotten it actually to install - the guides on the net were a little flakey to say the least.

Hopefully R3 will address these issues. I'll report back with anything I notice whilst going through it.

The really 'hard' thing, if you like, is going to be configuring WDS via SCCM - it should be okay from what I've read but, again, it's something that will need thoroughly testing.


M.
 
Well the main reason is that it was put in by someone who didn't know what they were doing. No offence to the people involved but the permissions are all over the place and it simply doesn't work (heartbeat service doesn't run, etc.)

Rather than fix it I'd rather start again and make sure it's done properly.



M.
 
Sadly we can keep neither as the new server has to be put in parallel and then the clients migrated to the new server. I can't really work on the pxe side either as that needs to also be seemlessly migrated.

It's a little bit of a nightmare but good experience I guess once it's done.

I did find the installer bad mainly because it says that BITS / Webdav / etc. are not installed when they are and rather than it just getting on and installed the pre-reqs it just puts up an ambigious error message and then you're off to google!

Apart from that it's been fine - I'll report back with anything I find if anyones interested.



M.
 
Already have the Administrators Companion book - which is okay but not brilliant. Especially on the pre-req stuff which I thought was very important but it barely touches on.

I'll see how I go with this anyway!



M.
 
Having now gone through the install and initial client deployment to a couple of test clients I still think it's an evil installer. Had to edit DCOM settings just to get people to be able to access the console which I think is fairly poor. The initial collection scan is 1 day as well which didn't help with testing.

Just seems to have been put together quickly rather than with ease of use and quality in mind. My DB is on another server which seems fine at the moment (see how that goes later) I've had no speed issues, etc. Just issues which should have been sorted out in the installer and wasted around 4 hours of my time.

I'll update tomorrow when I have a lot more clients on there!
 
Ev0 said:
Yup they do



Obviously never had to setup and use old sms 2.0 stuff then :)

The product has gotten better with each version.

I really can't understand why you've had so many problems, I've never had an issue with any of my installations with all this kind of thing, it's always just worked.

Having worked with SMS then SCCM for the last 7 years or so, with a brief stint as an SMS+SCCM contractor, I've seen my fair share of naff installations!
Click to expand...

Have you ever deployed SCCM 2007 on Windows 2008? I had a lot of issues actually getting the remote admin consoles to connect (had to edit DCOM for remote execution).

I can't import the AD because we have an existing server out there which I can't replace until this is properly tested. It's a pain (and probably hindering the deployment) but that's life.

The permissions seem all over the place and doesn't seem to like groups (DCOM certainly doesn't). There's groups on the server, groups on SCCM and then the DCOM group.


M.

P.S. Never had to install SMS2 but certainly helped with the deploymetn - client deployment was a nightmare!
 
In the console we added groups (i.e. Domain\ServerTeam) if we copy the Admin role (which is created by default) they can't access it. If I give the individual, who is a member of the group, the rights he's fine yet the groups cant access it (and yes they are in the local SMS Admin groups).

Same with the DCOM issue.

It's only been up a day - need to look into it properly tomorrow (and yes I know it's Saturday - bah!)


M.
 
Finally got it all running (only manually deployed to one client but that's working well).

It really does not like x64 edition operating systems. Found another problem with reporting which was only fixed when converting the IIS app pools back to 32 bit mode.

Anyway I'm a lot happier than I was last week and I have learnt a lot about how ever it is! But at least it's working now!


M.
 
Well found another 'feature' that I need to fix on Monday with reagrds to the 64 bit giving HTTP 500 errors - thought I'd fixed it but obviously not.

It's a monster of a program so why it's anything than 64-bit is a bit strange.



M.
 
Well... now it's been in a few days and everythings green I'm happy to say it seems to be working. I have a minor problem whereby the deployment from the client management is very, very slow (believe this to be a BITS problem as BITS downloads it and then takes 2 hours to download and a couple of minutes to install - I've checked my settings in the console and they're all on 9999 Kbps transfer rate so it's something I need to look into).

It now seems rather stable. I still believe it's the worst way to install a program ever (you install it then fix it).




M.
 
You must log in or register to reply here.
Back
Top Bottom