I have added a new site to our 2007 hierarchy which I have made the new parent site and want the client on our deployed machines to have the client now point to the new parent. I've tried multiple different things like going to a machine and attempt running the uninstall switches, but the computer will not remove the client. How can I resolve this so I can get the new info onto the computers?

Moving a client in the hierarchy is as easy as re-assigning the client's site code. To make this effective for auto-assignment, you need to update your boundaries also. For existing clients, if you update the boundaries and restart the agent, they will see the new boundary and move themselves.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

When you say update the boundaries, could you explain more? On my new Parent I have the same boundary as the the old parent(new child) as DEFAULT-FIRST-SITE-NAME and the type as Active Directory Site. Do i have to change the boundaries for either the parent or the child?

When you say update the boundaries, could you explain more? On my new Parent I have the same boundary as the the old parent(new child) as DEFAULT-FIRST-SITE-NAME and the type as Active Directory Site. Do i have to change the boundaries for either the parent or the child?

Hi, If you would like to add the new site as the parent site while the old site to be its child site, and move the original clients to be the clients for the new parent site, you may refer to the procedure to reassign the client to new site: 1) Remove the boundaries from the old site 2) add the boundaries to the new site 3) Run a script or program to reassign the clients You can use this VB script: 'replace with your Site Code sSiteCode = "EnterNewSiteCode" sMachine = "." set oCCMNamespace = GetObject("winmgmts://" & sMachine & "/root/ccm") Set oInstance = oCCMNamespace.Get("SMS_Client") set oParams = oInstance.Methods_("SetAssignedSite").inParameters.SpawnInstance_() oParams.sSiteCode = sSiteCode oCCMNamespace.ExecMethod "SMS_Client", "SetAssignedSite", oParams reference: child-parent site relation Regards, Sabrina This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Ok that sounds good. Where do we run the vb script? On the computer to where the client goes or on the parent site?

On each client to be reassigned to the new site. Execute locally. Miguel Rodriguez

Ok i've changed the site code like you have said up above (made no other changes) and made a.vbs file out of it and put it onto one of my clients. When i try and run it from an elevated command prompt I get an Unspecified Error with code 80004005 Any suggestions?

Cannot say. For me the script (cscript.exe [scriptname]) executes just fine on Windows 7 machines. Does that workstation have the Configmgr client installed? You could also use the adm template to create a group policy for site assignment, depending on how much clients you need to migrate and if that can be done in one step. You can find the template on the Configmgr install media under tools.Miguel Rodriguez

Just a side note to using the GPO for (re-)assigning the clients: I'd prefer the vbs method, because the GPO method creates a regkey for site assignment that has to be removed manually if the GPO is removed.Torsten Meringer | http://www.mssccmfaq.de

Hey Miquel, Yeah the computer already has the client installed. I've also tried a couple of other machines to no avail with the same error code. There is no other changes that needs to be made to that script besides the site code? I checked with our admins and there is no GPO enforcing the original site onto the machines

Please try Roger Zanders collection commander to reassign a group of machines: http://sourceforge.net/projects/smscollctr/ After installation choose your testcollection and start client actions/agent actions/assign clients to the site You should be able to test reassignment this way for at least all machines that are currently online... See if that works. Miguel Rodriguez