SMS Site code issues.
Hi All, I have rebuild the SMS server, My previos site code was abc, after rebuild i have given new site code called 123. sms collections all clients are reflecting properly.. when i deploy any software..it is not receving. if i go and check the controlpanel->smsproperties. site code is showing prasent one i.e 123, if i click on discover button, automatic site code is showing abc. if close and reopen the properties, again site code will show 123, if i click on discover it is showing abc; remaining every thing is properly displayed. due to this if i deploy any softwares, it is not receiving. Could some one help me on this.
October 26th, 2010 7:18am

Hi, You need to reassign the clients to the new site. This can be done with a script or reinstalling the clients. A script could look like this: 'replace with your Site Code sSiteCode = "NewSiteCodeGoesHere" 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", oParamsKent Agerlund | http://scug.dk/ | The Danish community for System Center products
Free Windows Admin Tool Kit Click here and download it now
October 26th, 2010 7:33am

Check the system management container & verify that new site server has permission over this container & remove old entries referencing old site server and management point.
October 26th, 2010 7:33am

Hi, Manually i've reinstalled the SMS Client (first ccmclean and then reinstalled the client), still its showing same issue. if open control panel-sms properties->site code will show new site code. if we click on discover-again it will show old site code.
Free Windows Admin Tool Kit Click here and download it now
October 26th, 2010 8:05am

new site server has permissions..and we removed the old entries..
October 26th, 2010 8:07am

You also might run into issues with the trusted root key: http://technet.microsoft.com/en-us/library/bb680980.aspx (RESETKEYINFORMATION)
Free Windows Admin Tool Kit Click here and download it now
October 26th, 2010 8:08am

new site server has permissions..and we removed the old entries.. I'd double check that. If they are finding the old site code they are getting it from somewhere. Check the logs on a client and see if they are getting that old site code from AD. If so delete everything in the System Management container and let the new server put back what should be in there. That will happen automatically. John Marcum | http://myitforum.com/cs2/blogs/jmarcum |
October 26th, 2010 8:58am

Hi, Could you adapt this code to chance in a remote machine? I try to use this script bu the client show errors strRemoteComputer = "L0765XDZWVNNYEM" strSite = "L90" Set objLocator = CreateObject("WbemScripting.SWbemLocator") Set objServices = objLocator.ConnectServer(strRemoteComputer, "root\ccm") Set objSMSClient = objServices.Get("SMS_Client") objSMSClient.SetAssignedSite strSite LocationServices.log errors: Failed to resolve 'SMS_SLP' to IP address from WINS LocationServices 16/3/2011 16:22:51 1064 (0x0428) LSGetSLP : Failed to resolve SLP from WINS, is it published LocationServices 16/3/2011 16:22:51 1064 (0x0428) LSGetAssignmentSiteCodeForSiteFromSLP : Unable to get the list of SLPs LocationServices 16/3/2011 16:22:51 1064 (0x0428) LSGetAssignmentSiteCodeForSite: Failed to get Assigned Site Code from AD and SLP LocationServices 16/3/2011 16:22:51 1064 (0x0428) Any idea?
Free Windows Admin Tool Kit Click here and download it now
March 18th, 2011 7:18pm

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

Other recent topics Other recent topics