Peter van der Woude

You should always cleanup your Deployments and Deployment Packages and remove the expired and superseded updates.

Normally a hardlink migration would be ideal for a computer-refresh situation, but as you want to repartition the disk(s) it's not an option... You need to save the user data of the box (like a SMP).

This isn't an error... this is just a informational message that the content still has to be downloaded... Take a look at the execmgr.log for more information.

What is the source folder for the different packages?

When you for example look at the WindowsUpdate.log then where it says the client is looking for updates?

To install the SUP role on Windows Server 2012 (and WSUS 4.0), you need ConfigMgr 2012 SP1 (BETA)

Did you already check the client logs?

We need some more information.. Is it a new client? Did the advertisement already run on that client? Did you check the client logs?

Nope, WDS has nothing to do with this. Start by looking at the NetSetup.log and the netlogon.log at C:\Windows\debug.

It might be possible, but I can't think of any reason why you would want to do that....

Nope, that's not possible.

So it does show activity on the client-side? Then check the C:\Windows\ccmsetup folder for the installation log files and look for errors.

Where did you install the Software Update Point(s)?

Correct. In a situation with a CAS and 5 Primaries you will need an active SUP on all these Sites and that means a WSUS DB on all these Sites. See also: http://technet.microsoft.com/en-us/library/gg712696.aspx#BKMK_ActiveSUP

At what point does it fail? During the push or during the install?

Have you seen this: http://social.technet.microsoft.com/Forums/en-US/configmanagersecurity/thread/a4d69ae8-9871-47c4-a53f-540d6dcae27f

You need to give more information.... With this information, I can only tell you that HTTP error 401 is an authorization error....

You need to start looking in to the logfiles, in this case probably the smsts.log.

You can do that by doing something like this: http://www.petervanderwoude.nl/post/deploying-remote-server-administration-tools-for-windows-8-with-configmgr-2012/

This is a successful client push action. If the installation fails you need to look at the client installation logs.

You can start here: http://technet.microsoft.com/en-us/library/dd220460.aspx

Never tried it, but it states no where as a prerequisite.

What does it say in the execmgr.log?

It's still the same, you need to rebuild it. For the docs see: http://technet.microsoft.com/en-us/library/gg712686.aspx

That is correct, a client can only be assigned to a primary site.