Peter van der Woude

Nope, ConfigMgr cannot do an upgrade of the OS (I don't even know a tool that can do that).

What about just using a step Connect To Network Folder?

You probably installed a CAS instead of a Primary Site

Did you try to extract the files with something like universal extractor?

Are there specific security rights on that key?

When the machine is already in the AD, then it won't be moved to a different OU during the Task Sequence.

Do you need to change the cache for new clients, then you need to use the SMSCACHESIZE parameter during the installation. Otherwise you need to either create a script to change is, or use a tool (like right-click) to change the size.

Also configure in the tab Deployment Settings the Make available to the following to include at least the Configuration Manager Clients.

The ccmsetup.log is for sccm client installation errors... for the scep client you should look in C:\ProgramData\Microsoft\Microsoft Security Client\Support

It should be possible with a Mandatory and Required Deployment of the Task Sequence.

That's possible, it can just update from the internet.

Take a look here at the documentation about Managing the driver catalog, it also mentions adding drivers to boot images: http://technet.microsoft.com/en-us/library/hh301101

Take a look at the loadstate.log for more information.

That setting indeed doesn't exist in ConfigMgr 2012. The only thing you can do is deploy the Application again and select the Uninstall action.

Have you seen the post on the Dell Wiki: http://en.community.dell.com/techcenter/os-applications/w/wiki/how-to-enable-trusted-platform-module-using-a-configmgr-2007-task-sequence.aspx

I think in the client.msi.log

There is a space between amd64 and the backslash. See in your scanstate.log: 2012-07-26 11:26:15, Info [0x000000] Startup exclusions - Adding excluded file pattern: C:\USMTbits\amd64 \* [*] 2012-07-26 11:26:15, Error [0x000000] EngineStartup caught exception: Win32Exception: c:\USMTbits\amd64 : The system cannot find the file specified. [0x00000002] class UnBCL::String *__cdecl UnBCL::Path::GetLongName(const class UnBCL::String *)[gle=0x00000002

Configure the ConfigMgr Integration?

Nope it doesn't matter which (kind of) boot image you will use.

I would use the Applications and let ConfigMgr 2012 do all the checking. One of the nice things about the new application model is that it can do all prerequisite and dependency checks for you.

Then you could play with the delay (in seconds) settings.

I always like the Ip address version the most, as it gives you the most control. Using Ad sites makes it harder to see which Ip addresses are part of it and also makes it really hard when you have to split it up.

Did you configure a deadline on the Software Update Deployment?

When the clients are able to download other packages from the DP, they should be fine.

What exactly do you mean? Do you have both, AD Site Boundaries and IP Address Range Boundaries?