While in-place upgrades are nice, there are quite a few scenarios when you need to use the old-school deployment scenarios (new computer, refresh computer and replace compute).
Side note:Check out my live production upgrade to Windows 10 video
The Windows 10 Setup Upgrade process
When using the /Auto:Upgrade switch to upgrade Windows 7/8/8.1 to Windows 10 (which migrates data, settings and apps) it does NOT support the following:
- Use a custom reference image
- Change from BIOS to UEFI or do other disk layout changes (partitioning)
- Upgrade when having third party disk encryption (for now, may change depending on vendor)
- Upgrade when third party antivirus software installed (for now, may change depending on vendor)
- Upgrade between architecture (e.g. x86 to x64)
- Change the language (base OS language)
- Change disk layout (partitioning)
- Change to a lower SKU (the /Auto:Upgrade can only upgrade to the same or higher SKUs)
- Upgrade a "boot from VHD" system
- Upgrade WIMBoot/Compressed OS
- Upgrade Windows To Go USB sticks
The conclusion is that even though upgrades works quite well, because of the limitations, we still need to have deployment solutions around a while longer :)
/ Johan
More ...