SCCM Software Distribution and Patching when client is reassigned
I have two SCCM site: Central in US and child Primary inIndia. SCCM clients are assigned to both sites. Each site has protected DPs. My central site went down.I added site boundaries of Central site to Child Primary at India. Machines are disocvered at India. 1. Do i need to install SCCM client again after clients are disocvered at child primary? 2. What all needs to be done so as to make S/W distibtuion, Inventory and Patch managemetn work after clinet is reassigned to child primary? Divya
November 11th, 2010 6:09am

Hi, 1) No, you don't need to reinstall the client. 2) Nothing has to be done. The client will automatically read the policies for the new site and start downloading the policies. Agent settings like HW agent will automatically be applied to the client.Kent Agerlund | http://scug.dk/ | The Danish community for System Center products
Free Windows Admin Tool Kit Click here and download it now
November 11th, 2010 6:19am

Thanks Kent. One more thing plz. If central site is up how can i reassign the clients from child primary back to central site?Divya
November 11th, 2010 7:17am

Simple , Change the site boundaries back to original :) that should automatically assign clients to central as Kent Said. //Eswar Koneti @ http://eskonr.wordpress.com/
Free Windows Admin Tool Kit Click here and download it now
November 11th, 2010 7:31am

Kent, how does it actaully work in background when we change site boundaries and client is reassigned to another site code? I have seen this not happening with SCCM 2007 SP1, has anything changed with SP2 or R2?Divya
November 11th, 2010 7:54am

The client will download policies from the "new" management point and start implementing the rules that are applied to the new site, Agent settings, packages etc. It will happen without any user interaction.Kent Agerlund | http://scug.dk/ | The Danish community for System Center products
Free Windows Admin Tool Kit Click here and download it now
November 11th, 2010 8:01am

1) No you don’t need to re-install the client but you do have to reassign them if you want them to do anything. The is a tool within the right-click tools to do this. 2) Nothing.http://www.enhansoft.com/
November 11th, 2010 8:07am

Adding the Boundaries back to the center site will NOT have the client automatically re-assigned selves. The client will stay assigned to child site but will be consider roaming. You will need to reassign them to have them report back to the central site. http://www.enhansoft.com/
Free Windows Admin Tool Kit Click here and download it now
November 11th, 2010 8:10am

Here is what i tested: I added specific system name in system discovery and its IP in site boundaries at child primary site. I ran discovery so that client assigned to central is doscovered at primary. Client was discovered at primary site with site as primary but client as NO. I have to re-install the client. Now I am testing the scenario to assign client from primary site back to central. How to reassign the client?Divya
November 12th, 2010 2:25am

Has any one tested the scenario? Please let me know if anyone has different findings from what I have?Divya
Free Windows Admin Tool Kit Click here and download it now
November 15th, 2010 2:43am

Hello All, If any has tested this scenario in lab then please share your findings.Divya
November 18th, 2010 5:17am

Garth already mentioned the key point: client will never be automatically reassigned (even if boundaries are changed). You discovered the client from a child site, that's why it is in that database. It says "client = no", because the client is not assigned to that site. Assign it to that site, run heartbeat and it will show up as "client = yes" then. You can reassign clients using one of the right click tools or using a GPO. SW dist won't work, because the site that they are assigned to is down and therefore they cannot retrieve policies from it.
Free Windows Admin Tool Kit Click here and download it now
November 18th, 2010 5:30am

I haved added IP address as boundary on primary site and discovered the machine to be assigned to primary site. It is showing Assigned site code as that of primary and client as No. I ran Discoverey Data collection cycle but sees follwoing error in CLientlocation.log at client. Unable to verify the sitecode 'NOI', AD schema is not extended or SLP is not present. Cannot continue site assignment. Note: Ad schem,a is extended and SLP was present at central site.Divya
November 18th, 2010 8:33am

Any thoughts on this?Divya
Free Windows Admin Tool Kit Click here and download it now
November 19th, 2010 12:39am

Client is not able to retrieve the site version from either AD or using the SLP. So make sure that the schema is extended and the primary site can publish information to AD or if the SLP is working.
November 19th, 2010 3:24am

Torsen, as I mentioned in note, AD schema is extended and SLP was present at central site which is now down.Divya
Free Windows Admin Tool Kit Click here and download it now
November 19th, 2010 4:23am

ANy help on this? I am still struggling...Divya
November 22nd, 2010 4:37am

You said that your SLP was installed on central site and now this site is down, so Install SLP on your primary site. Check that your primary site MP published its informations to AD.
Free Windows Admin Tool Kit Click here and download it now
November 22nd, 2010 5:21am

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

Other recent topics Other recent topics