Hi
Hoping someone will have a quick answer for this!
We have a central site server & a number of primaries - all of our OSD config (Images, TS's, Col's & Adverts) is on the central, and we are still deploying XP. New builds & rebuilds need to be done at several AD sites, and frequently not on the site where the finalised machine will end up. The build & process has been ported from SMS 2003 OSD.
Brief overview of build process...
1. PXE boot using pre-execution hook.
2. Pre-execution scripts determine if authorised, machine name & TS required from third party database & then use Maik Koster's webservice to add the machine to the required collection.
3. TS then executed & machine built
Obviously as all the OSD is on the central site, this is where the machine ends up following the Setup Windows & ConfigMgr TS step.
What I would like to do is be able to change the SMSSITECODE parameter using a script before the client setup is run. In this way the client would end up assigned to the correct SCCM site regardless of where it is physically built. (note I can determine the site required from machine name, and appreciate I will have to either script or manually remove the temporary machine that will have been created on the central during the build process).
I've thought I'd be able to make a number of conditional Setup Windows & ConfigMgr TS steps, with the SMSSITECODE installation parameter specified on each one depending on the condition. It seems the SMSSITECODE parameter is not permitted as an Installation Option of this step.
I'm assuming that the step makes use of the _SMSTSSiteCode built in task sequence variable. Could someone explain if this is actually how it works & if the variable could be changed during the TS before the config manager client is installed.
Many thanks