Peter van der Woude

I think there has to be another one...

I also don't get the part that "the USMT process doesn't start". Because looking at these logs I see a working scanstate, which means that USMT is used/ started. So what exactly is going wrong? Maybe you can post you smsts.log

Correct, take a look here for the supported systems: http://technet.microsoft.com/en-us/library/ff977062.aspx

Is that the only message from the log?

Nope, there is a hotfix with R3. The features of R2 are also included in R3.

That is indeed normally correct, unless you follow the guidance in the Technet article. It's even a supported scenario since recently. Besides this it's the only way, knowning that a client can only be assigned to one WSUS/ SUP (and using SCCM it's not possible to create auto aprove rules).

Correct, using AD Sites is only a solution if they are setup in the AD Sites and Services.

That's correct, but on the other side you always have to make a new base image a few times a year to get it up-to-date with patches (unless you do it like this ). So it's almost never a bad idea to put some, not often changed, software in the base image.

Just delete the mandatory assignments of the Advertisement.

Those settings shouldn't be needed. It is possible that there is an update that is breaking it... Is there a really big update between the October updates, which you are deploying? Otherwise it get's a trial-and-error game to see which update is causing it.

You can only Advertise multiple Task Sequences, and make them selectable, when they don't have a Mandatory Schedule.

It's pretty straight forward. First install the hotfix and then R3.

I don't see/ get the problem... If your are going to distribute via SCCM, then what does it matter that the distribution server of Forefront doesn't support R2? You could deploy the updates like described here: http://technet.microsoft.com/en-us/library/dd185652.aspx

Well... security-wise I wouldn't use a DC for any Site Roles. But if you want to do it anyway then I would even prefer Domain Admins above BUILTIN\Administrators. For the reason why, see: http://technet.microsoft.com/en-us/library/cc700835.aspx

But can you do something with it? Like adding a package or something?

I thought that DISM supports everything from Vista SP1 and newer, so no XP... For ImageX, take a look here: http://technet.microsoft.com/en-us/library/dd744377(WS.10).aspx

Then you to, or Extend the AD, or apply a GPO. Take a look here for more information: http://technet.microsoft.com/en-us/library/bb633194.aspx

Looks really cowl!

That's the result you are looking for! Double click that and you can browse to the model the machine.

Are using Select model, or Select * ?

Please give some more information. What is happening and when? Did you check the logs?

The Package Distribution works the for Software Update Packages as for normal Software Packages. So when your Boundaries are setup correctly the clients will download from the correct DP. The client will only connect to the Software Update Point to check for compliance and sent status notifications.

That's weird, how are you trying that?

Possible, when F8 is enabled, it is possible to start Wbemtest from the commandline. Within Wbemtest you can test your WMI (queries). The parts where the driver packages get applied.

WMI is something that exist in the Operating System, even WinPE contains a subset of WMI. This subset is easily enough to query WMI for the model of the computer. Based on the information about the Variables that you are using and the repeating of the driver installation, I would say that the driver selection proces isn't going good. To be sure of that it might be handy to take a look at the smsts.log, to see what it says about picking the drivers/ driverpackage.