SCCM secondary site clients = No
We have a primary and a new secondary site. Any new machines being built within the boundaries of the second site are not registering correctly with SCCM. I know this because the clients do not recieve any packages and in the console it states that the clients are assigned to the secondary site (which you cant be). If I connect to one of the machines in the secondary site and do an auto site assignment it picks up the correct site code (that of the primary) but it never updates in the SCCM console to show the correct site assignment. It also never says client installed = Yes, it is always client = NO. I have tried forcing the client registration using initite hardware inventory scan but this makes no difference. I am sure that the issue is with the secondary as if I move a subnet boundary to the primary site the client registration will be successful. I will get a Client = Yes and the packages will start distributing. Can anyone advise how to troubleshoot this? Thanks
November 5th, 2010 11:02am

I assume you installed an MP at the secondary site? Test it using the MP troubleshooter from the SCCM v2 toolkit. John Marcum | http://myitforum.com/cs2/blogs/jmarcum |
Free Windows Admin Tool Kit Click here and download it now
November 5th, 2010 11:15am

Yes, installed MP at the secondary I will try the troubleshooter as advised! I have already manually checked using http:// for MPCert and MPlist and both the primary and secondary management points look OK. Will have a look to see what the troubleshooter says though
November 5th, 2010 11:18am

If MPList and MPCert work you are good to go. This may sound crazy but have you refreshed the All Systems collection in the console? You'd be suprised how many people miss that and think the clients are still "NO" John Marcum | http://myitforum.com/cs2/blogs/jmarcum |
Free Windows Admin Tool Kit Click here and download it now
November 5th, 2010 6:44pm

For client status NO eventhough it is installed on client machine, i'll delete the machine hostname from SCCM and do a discovery again. Then it will be listed as YES if the machine successfully registered the client. It works for me. (assuming you've tried Initiate Actions on Configuration Manager icon at Control Panel, update collection membership etc.)---Packie
November 7th, 2010 2:57am

I have tried the troubleshooter and everything looks to be in order. I get a warning about not being able to use RPC to check that the management point computer account has admin rights on the SQL server. There is a firewall in place but the documentation states that only port 1433 is required (which is in place) I have removed the client entirely from SCCM and rediscovered. It still is stating that the client is assigned to the secondary site in the console and that the client is not installed.
Free Windows Admin Tool Kit Click here and download it now
November 8th, 2010 8:42am

And the clients logs are indicating that it's working? It almost has to be a problem with the secondary site server. Can you zip the logs from both the server and client and email them to me? Make sure to get the MP logs too. john marcum at gmail dot com. John Marcum | http://myitforum.com/cs2/blogs/jmarcum |
November 8th, 2010 6:17pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics