Change Site Code after installing with DISABLESITEOPT=TRUE switch
SCCM R2 running on WIndows 2003 R2. All clients installed manually during O/S builds (not client push) using the following options per the IT policy: SMSSITECODE=YYY CCMENABLELOGGING=TRUE CCMLOGMAXSIZE=1000000 CCMLOGLEVEL=0 DISABLESITEOPT=TRUE DISABLECACHEOPT=TRUE SMSCACHESIZE=4000 SMSDIRECTORYLOOKUP=NOWINS A new Primary server was brought online and we need to change the existing site code of all clients from YYY (old primary server) to ZZZ (new primary server). The error indicates an access denied although all rights are open for the accounts used when attempting to change the site code. Would this be due to the DISABLESITEOPT=TRUE switch and if so, how do we get around this ? Thx ! ESP
October 19th, 2010 9:00pm

How did you try to change the sitecode? Script? Re-push? Which error were you getting and where?
Free Windows Admin Tool Kit Click here and download it now
October 19th, 2010 9:10pm

Note that you cannot simply re-assign a client from one primary site to another if they are not in the same hierarchy because of the trusted root key: http://blogs.technet.com/b/configmgrteam/archive/2009/04/09/reassigning-a-configuration-manager-client-across-hierarchies.aspx.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys
October 19th, 2010 9:52pm

Via VBS script under an acct that has admin rights on the client. Error: -2147467259 Description: Unspecified error
Free Windows Admin Tool Kit Click here and download it now
October 19th, 2010 10:19pm

A very good point. The new server ZZZ is the Parent of the old server YYY. The new server ZZZ started out as the Child of old server YYY in order to start the downward flow in the site, then they have switched roles to allow for the upward flow. Currently, ZZZ (new) is the Parent Primary above YYY (old) Child Primary. Thx
October 19th, 2010 10:21pm

That's not "access denied" ... the only way to tell details is by having a look at the script. I can tell you that changing the sitecode using a script does work when disablesiteopt=true is set.
Free Windows Admin Tool Kit Click here and download it now
October 19th, 2010 10:25pm

Interesting....thx ' Begin Code Const HKLM = &H80000002 strNewSiteCode = "C01" Set oCCMNamespace = GetObject("winmgmts://./root/ccm") Set oInstance = oCCMNamespace.Get("SMS_Client") Set oParams = oInstance.Methods_("SetAssignedSite").inParameters.SpawnInstance_() oParams.strNewSiteCode = strNewSiteCode oCCMNamespace.ExecMethod "SMS_Client", "SetAssignedSite", oParams
October 19th, 2010 11:03pm

This corrected the issue. Set smsClient = CreateObject("Microsoft.SMS.Client") smsClient.SetAssignedSite "ZZZ", 0
Free Windows Admin Tool Kit Click here and download it now
October 21st, 2010 12:20am

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

Other recent topics Other recent topics