yeah yeah Posted July 7, 2010 Report post Posted July 7, 2010 All, Majority of the workstations out here already have the SCCM agent installed. It's just that the agent is pointing to a non-existent server from a previously failed SCCM installation from a couple of years ago. I went to one of these machines, went START > Control Panel > Config. Manager > Advanced > Discover...and it automatically found the new SCCM server and was shortly updated within the ConfigMgr. Now, is there a way to do this remotely? I was told to push the agents out again with: ccmsetup.exe /mp:MPNAME SMSSITECODE=XXX but that doesnt seem to do anything at all. Is there another way of doing this via command line? Quote Share this post Link to post Share on other sites More sharing options...
BenjAdmin Posted July 7, 2010 Report post Posted July 7, 2010 You can push an adm template changing the sitecodes through group policy. Use the Group Policy administrative template named ConfigMgr2007Assignment.adm supplied in the folder TOOLS\ConfigMgrADMTemplates on the Configuration Manager 2007 installation media to apply the site assignment configuration to client computers. Afther a reboot of the clients, those should point to the correct site. If you assign or reassign the client to a site using Windows Group Policy, the site code is stored in a registry key on client computers. To reassign a client to another site, change the Group Policy setting to update the registry key. Please take notice of the fact that you cannot change the registry key directly! More information on this subject can be found on the Technet site: Technet Article Quote Share this post Link to post Share on other sites More sharing options...
BenjAdmin Posted July 7, 2010 Report post Posted July 7, 2010 Updated previous post with the location of the adm-templates. Quote Share this post Link to post Share on other sites More sharing options...
yeah yeah Posted July 7, 2010 Report post Posted July 7, 2010 Wow ! Of course I see this after I left the job. A reboot is required? Damn damn damn. Quote Share this post Link to post Share on other sites More sharing options...
BenjAdmin Posted July 8, 2010 Report post Posted July 8, 2010 Wow ! Of course I see this after I left the job. A reboot is required? Damn damn damn. I guess a reboot is required there it involves changes to the registry key which cannot be mannually applied. Better count on it as being the case, I haven't needed this solution yet so I'm not completely sure to be honest. When tried, please let us know if the reboot ectually is required and don't forget to force the gp before trying and rebooting ;-) (To do this, type "gpudate /force" in a commandbox on an infected client computer to speed up things) Quote Share this post Link to post Share on other sites More sharing options...
yeah yeah Posted July 8, 2010 Report post Posted July 8, 2010 Back in the office. Will apply the admin template and see what I can do. I'll let you know. Quote Share this post Link to post Share on other sites More sharing options...
