I’ve written and have been talking a fair bit recently on the need to consider a wipe-and-load approach to your Windows 10 migration. If you want to learn a bit more about why this is an important consideration, check out my blog on the subject.
Wiping the disk means the applications are all gone. If you implement an Application Mapping process within your Windows deployment process, you can ensure users automatically get the apps they need while eliminating software and version sprawl and standardizing on your corporate preferred apps at the same time. It can also reduce your software license liability, increase security (fewer old, unpatched versions lying around) and reduce support effort (maintaining a standard portfolio of known applications with consistent versions across the board).
What is Application Mapping?
Quite simply, it is automation that uses inventory information collected before the device is migrated, along with a mapping table that defines the identifier or command to install the ‘replacement’ application. The replacement may be the same application and version, a later version of the same application or a completely different application.