Peter van der Woude

It's because the boundaries are assigned to site1 (the old site). So when the clients query for a site they will get the assigned site, which is site1...

That's weird... How do your Software Update Point (Component) settings look like?

Depends on the bandwidth... By using SCCM already on those location they can pull the updates from their local DP, so you don't have that traffic anymore. The only traffic you still have is of the wua client scanning for updates. So if that's to much traffic you should add a SUP on those locations, otherwise just go for it with a central SUP

Did you take a look at the execmgr.log?

#1 PXE Service Point is only required if you want to install the OS by using PXE boot (F12) #2 The post you are refering to is for ConfigMgr 2012 (beta2) and you are using ConfigMgr 2007, so you might want to look at this post: http://www.petervanderwoude.nl/post/capture-user-files-and-settings-offline-winpe-or-online-fullos-with-configmgr-2007/

The whole deployment will stop working... So always keep your deployments and packages clean.

Nvidia drivers are known for their problems during OSD... You're best option is to create a Software Package of the driver and run the Setup.

Correct. Just remember to use x64 version of scanstate/loadstate on x64 OS and x86 version on x86 OS.

Create one Task Sequence and use extra steps for the minor changes.

In the advertisement, just remove the mandatory schedule and the advertisement became optional

Then I would spent my time convincing the other department Simply because when somebody else suddenly, for wathever reason, wants to change that setting with GPO's, it will always overwrite your local settings...

And are the boundaries assigned to site1 or site2?

start with looking at the cas.log

Easiest solution is creating two task sequences and advertise them as optional task sequence. This gives you the option to select the task sequence you want.

Why not using GPO's?

Settings look correct. Did you look at the ccm.log if it still show any relevant information? Are you sure it's not a manual action?

Your last action that fails is to run \\epwh.ad\EPWORTH\Replicated Data\SoftDist\Install_CitrixClient_13\SCCM_CitrixComponentInstall_V13.cmd... Is, by any change that location also changed?

The MDT integration gives you extra options with creating new Task Sequence(s) and extra steps.

It's not really clear to me what you did and what exactly is the problem... So what steps did you perform? And at which point do you get problems?

See here: http://www.petervanderwoude.nl/post/configmgr-2007-and-removing-a-computer-from-a-collection-by-script/

What error messages do you have in your discoveries?

Do you have BITS enabled DPs? Also did you look at the network traffic in/out the site server?

So besides not being in collection HOL00021 the computer is also member of "GroupName"?

You can just reassign the clients, see also: http://technet.microsoft.com/en-us/library/bb680370.aspx

It just uses the wusa agent to install patches, so just disable that one. Or just remove the SCCM agent..