Well it appears I managed to get it working without the schema update. I agree the schema update makes things easier and I am expecting more issues until this update is done but I was personally kept from being able to run the update because our Change Control wouldn't allow it.
The major deviation from setting up SCCM (from here http://www.windows-noob.com/forums/index.php?/topic/1064-sccm-2007-guides/ ) is that I disabled updating AD. I did this because of all the errors I got with SCCM trying to update itself in AD and until we extend the schema it's not going to work anyway. This is in the properties of the site.
Then what I changed was the command line information for SCCM's client installation. I had to manually specify all the settings so the client knew where it was pointing to. This is a requirement when you have a server locator point instead of an extended schema.
This is the syntax I added CCMSETUP.EXE /noservice SMSMP=tstsccm SMSSITECODE=rg6 smslp=TSTSCCM
This was in the properties of the program
Now I also followed instructions for WSUS config and noticed the client inside the package said yes under WSUS but not under the Adobe pack. I decided to remove the query information all together to make it manually add itself and requery and then this showed the client was "yes". I did that because I had tried reinstalling the client a million times and never once did the actual client say it was "yes".
After this the software install and udpates started right up.
No comments:
Post a Comment