SCCM Pushed client not setting site correctly
Hi, I was wondering if anybody could help me out with a problem i'm having with a new SCCM server that I am trying to deploy in our organisation.
I have installed SCCM on a brand new 2003 box running its own SQL 2005 database and have setup SCCM to perform an Active Discovery which appears to be working sucessfully as I can see all of our servers and workstations listed in 'All Systems'. I have also configured the server to perform a push of the client to the discovered systems which also appears to be working as all every system I check I can see the c:\windows\system32\CCM folder has been created and the 'Configuration Manager' icon has been created in control panel.
However my problem appears to be that the client does not assign itself to my site database. On all the clients I have checked the client has been asigned to a site named 001 but the site that I have configured is named something different. I have tried editing this from within the client manually but each time I recieve a message saying 'site asignment failed' also if I try an automatic discovery I recieve an error saying 'Automatic site code discovery was unsucessful'.
I think that this explains in full my problem but if I have missed anything then please let me know.
Many thanks for your help in advance
Andrew
Answers
One thing to consider is that Configuration Manager clients actually can't be assigned to an SMS 2003 site. I don't know how you'd get a SMS 2003 site code listed there on the SCCM client.
Correct, we'd overwrite the SMS 2003 schema extensions, but that will not get rid of any of the SMS 2003 data published to AD. You'd have to go into AD and delete those items.
Just go to Active Directory Users and Computers, and then on the View menu, click Advanced Features. Then expand the domain, expand System, and then click System Management.
Delete the site 001 entry, plus the management point and server locator point (if listed).
Then go and publish the Configuration Manager site stuff by selecting the "Publiish to AD" option on the Advanced tab of the Site Properties dialog box.
All Replies
Hi Andrew,
In order to assign a Configuration Manager client to a site, you either have to have the Configuration Manager site data published to Active Directory, which means the schema must have been extended for SCCM, OR you have to have a Configuration Manager Server Locator Point installed in the site, and the client told to use that SLP. Otherwise, the client not accept a manual assigned site, as we must validate that the site is indeed a Configuration Manager site, and not some other site.
If the clients are finding a site called 001, that means that there is a site in the environment that has that site code, and is either published to AD, or has an SLP publiished, AND the clients are within the Boundaries of that site.
If so, then the LocationServices.log on the client will tell you what management point they are using, and maybe you can use that to track down that site. Sounds like there are some overlapping boundaries, which is not a good thing in SMS or SCCM.
Hope that helps,
Wally
Hi Andrew
Have you extended your Active Directory ? Do you have any other SMS or Configuration Manager installations in your environment ?
What does the ClientLocation.log on the client say ?
Hi Andrew,
For site assignment to complete in SCCM, you must either extend the Active Directory schema for Configuration Manager or clients must be able to communicate with a server locator point in the hierarchy. Additionally, if you have extended Active Directory but have clients from a separate forest, or clients from workgroups, you will need a server locator point.
Also, ClientLocation.log can help you to troubleshoot scenarios where the client is not assigned to a SCCM site.
Kenneth
Thanks for the info Wally, I have not done the schema extensions as I was not sure how it would affect our domain in mixed-mode. I will do some research into this but hopefully I can make sure that I get that done within the next couple of days and hopefully that will sort the problems I have.
I know why the clients are finding site code 001, I think. Previous to my employment my predessor had installed SMS 2003 in our site and called the site 001. I'm guessing then that he had performed the schema extensions for SMS and that is why the clients are finding that site. SMS has now been removed from the original server but it is still on our domain as a file server. Am I correct in think that doing the SCCM schema extensions would over-write SMS extensions if this is the case?
Thanks for everybody who has replied but as all of your answers are along the same lines I am only replying to the first post.
Andrew
You will need to remove the entries that the previous server has done and enable your new server to publish to the Active Directory. Or remove the entries for the SLP in your WINS. depending on what the other guy did.
More info here.
http://technet.microsoft.com/en-us/library/bb633121.aspx
The clients will no reassign them selves they need to be reassigned.
One thing to consider is that Configuration Manager clients actually can't be assigned to an SMS 2003 site. I don't know how you'd get a SMS 2003 site code listed there on the SCCM client.
Correct, we'd overwrite the SMS 2003 schema extensions, but that will not get rid of any of the SMS 2003 data published to AD. You'd have to go into AD and delete those items.
Just go to Active Directory Users and Computers, and then on the View menu, click Advanced Features. Then expand the domain, expand System, and then click System Management.
Delete the site 001 entry, plus the management point and server locator point (if listed).
Then go and publish the Configuration Manager site stuff by selecting the "Publiish to AD" option on the Advanced tab of the Site Properties dialog box.
Once the Configuration Manager site is published to AD, or a Configuration Manager SLP is installed and publiished to WINS or manually to clients, you CAN reassign clients to the Configuration Manager site. You would NOT have to reinstall them.
Wally,
I too was having this same problem. We had a test SCCM 2007 server that was on the network and we have now purchased a larger server for our production SCCM 2007 server and the site name and code is different than test server and now I can't get it to publish to AD even though I've followed the steps you listed in this thread. Any suggestions?
If you can't get your site server to publish to AD, you need to ensure that the site server computer account has Full Control rights to the System (or System Management) container AND all child objects.
That's it, nothing harder than that.
