Hullo :) We have a three tier SCCM architecture (Central - Primary - Secondary) setup with Central and Primary servers set up as management points. Our MDT database (2010, SCCM integrated) etc. all come from the central server and packages are distributed from the Secondary server. When we perform a build using MDT, the site code is set to the code of the Central server. Performing a Discovery in the SCCM client finds the code of the Primary server without any problems. Would this be expected behaviour (in which case I guess I need to run a script to update the site code), or is there something I've missed. I have no installation properties configured in the Setup Windows and ConfigMgr task and the ClientLocation.log shows that only the Central site code is being referenced. <![LOG[Setting Assigned Site]LOG]!><time="17:22:38.601+-60" date="04-19-2011" component="ClientLocation" context="" type="1" thread="1712" file="smsclientclass.cpp:473"> <![LOG[Assigning client to site 'CEN']LOG]!><time="17:22:38.601+-60" date="04-19-2011" component="ClientLocation" context="" type="1" thread="1712" file="smsclientclass.cpp:485"> <![LOG[GetCurrentManagementPointEx]LOG]!><time="17:22:38.601+-60" date="04-19-2011" component="ClientLocation" context="" type="1" thread="1500" file="smsclientclass.cpp:1039"> <![LOG[GetCurrentManagementPointEx]LOG]!><time="17:22:38.616+-60" date="04-19-2011" component="ClientLocation" context="" type="1" thread="1500" file="smsclientclass.cpp:1039"> <![LOG[Getting Assigned Site]LOG]!><time="17:22:38.648+-60" date="04-19-2011" component="ClientLocation" context="" type="1" thread="1712" file="smsclientclass.cpp:922"> <![LOG[GetCurrentManagementPointEx]LOG]!><time="17:22:38.648+-60" date="04-19-2011" component="ClientLocation" context="" type="1" thread="1500" file="smsclientclass.cpp:1039"> <![LOG[Client is currently not assigned to any site]LOG]!><time="17:22:38.648+-60" date="04-19-2011" component="ClientLocation" context="" type="1" thread="1712" file="smsclientclass.cpp:587"> <![LOG[Removing client site assignments]LOG]!><time="17:22:38.648+-60" date="04-19-2011" component="ClientLocation" context="" type="1" thread="1712" file="smsclientclass.cpp:698"> <![LOG[Raising event: instance of CCM_RemoteClient_Reassigned { ClientID = "GUID:d58dc2ed-3405-4b3e-9270-8fa9aa33ec45"; DateTime = "20110419162238.710000+000"; LastAssignedSite = ""; NewAssignedSite = "CEN"; ProcessID = 2600; ThreadID = 1712; }; ]LOG]!><time="17:22:38.710+-60" date="04-19-2011" component="ClientLocation" context="" type="1" thread="1712" file="event.cpp:525"> <![LOG[Client assigned to site 'CEN']LOG]!><time="17:22:38.710+-60" date="04-19-2011" component="ClientLocation" context="" type="1" thread="1712" file="smsclientclass.cpp:653"> <![LOG[Discover Default MP]LOG]!><time="17:22:38.710+-60" date="04-19-2011" component="ClientLocation" context="" type="1" thread="1712" file="smsclientclass.cpp:1359"> <![LOG[Site Code is CEN; Management Point is CENTRAL.COMPANY.COM]LOG]!><time="17:22:38.726+-60" date="04-19-2011" component="ClientLocation" context="" type="1" thread="1712" file="smsclientclass.cpp:1369"> <![LOG[Setting Current Management Point]LOG]!><time="17:22:38.726+-60" date="04-19-2011" component="ClientLocation" context="" type="1" thread="1712" file="smsclientclass.cpp:863"> <![LOG[Management Point is CENTRAL.COMPANY.COM]LOG]!><time="17:22:38.726+-60" date="04-19-2011" component="ClientLocation" context="" type="1" thread="1712" file="smsclientclass.cpp:868"> <![LOG[GetCurrentManagementPointEx]LOG]!><time="17:22:38.741+-60" date="04-19-2011" component="ClientLocation" context="" type="1" thread="2396" file="smsclientclass.cpp:1039">

boot media is tied to the site it's built on, you can script around it cheers niall My step by step SCCM Guides I'm on Twitter > ncbrady

Thanks Niall. I'll script an automatic discovery then once the OS is built. Any thoughts on whether that could be run from within a latter part of the task sequence or whether it could only be done once the OS is fully running?

The later part of the task sequence (anything after the Setup Windows and ConfigMgr task) is in the full OS. Why not just create boot media on the child sites for use with the child sites?Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

Thanks guys. I put some vb to autoupdate the site code towards the end of the TS and that seems to sort it. Now on to the next issue...! Cheers Simon

glad you got it sorted Simon, where did you place the step ? keep an eye in your smsts.log to see where packages are being pulled from My step by step SCCM Guides I'm on Twitter > ncbrady

Hi Niall, At the moment, I have the step at the end of the task sequence, after the Install Software step. We are currently just prep'ing for a pilot next week so the bulk of the packages are only on our pilot secondary server. However, some packages are distributed to both the secondary and the primary and appear to be being pulled from the secondary during the task sequence. I'll keep an eye on it and maybe do some more testing when the pilot is underway next week. If it looks necessary, I'll move the task to before the Install Packages step. TGIF ;-) Cheers Simon