Peter van der Woude

You really should be looking at the client logs (like Locationservices.log, Clientlocation.log and ClientIDmanager.log)

No idea, you might want to take a look at the smsts.log and/ or the scanstate.log

It's either that BITS is corrupt, or that BITS can't connect to the MP (via HTTP).

Is the package distributed to the DP and is it accessible for the clients?

Are you running ConfigMgr 2012? If so, then there is no need at all for WebDAV anymore.

Did you see the newest additions here: http://technet.microsoft.com/en-us/video/system-center-2012-configuration-manager-how-do-i-video-series.aspx

The only way they can be migrated is by connecting the old site as source hierarchy and use migration jobs. Import / export doesn't work, as ConfigMgr 2007 uses XML and ConfigMgr 2012 uses Zip.

It says wiping, because it's "emptying" the disk instead of formatting the disk.

That usually means that you are not receiving any policies... Check the clients logs, like the LocationServices.log

Ehhmm... so which version of ConfigMgr are you running (as Software Center is from 2012)? In both version you have to give the Deployment/ Advertisement a schedule.

I think you are missing the GPO for setting the users for Remote Assistance. I thought somewhere around here: Computer Configuration\Administrative Templates\System\Remote Assistance.

Good one... I don't know... Shouldn't you also first install the applications (like Outlook) before running USMT?

Then kick one of the working commandlines and specifiy a logfile to see where it goes wrong.

These are all installer errors and not SCCM -errors.... and lot's of command -lines that you try are mixed-up between exe's and msi's.... Start with working with a commandline that works out-side of SCCM and then start with using that in SCCM.

I would start with looking at UDI in MDT, it already brings a lot of these things out-of-the-box and integrates with SCCM.

Did you enable the Software Updates Agent and install the Software Update Point? If so then the SCCM client will set a local policy to point to WSUS/SUP.

You also need the include part above it.

Shouldn't be a problem as long as the clients can find the SCCM server and connect to it.

It's possible that the MP installation is still running or failing. Check the mpmsi.log for more information.

Unknown computers in the console are for general use with booting Unknown computers. As soon as the computer has a client it gets known and will show with it's own name.

AFAIK it's not possible to save the ConfigMgr policies to a file and apply them to a client....

You have to suppress reboots in the installation commandline of the application.

Always interested in scripts and tools

I usually use RelativeMove for that, like here: http://www.petervanderwoude.nl/post/some-basic-usmt-4-0-actions-explained/

Did you look at DirectAccess?