Migrating from Windows 8 to Windows 8.1

Microsoft has in a post at TechNet, shared its experiences while moving from Windows 8 to Windows 8.1. Moving away from the customary practice of providing upgraded version of Windows via traditional installation method, Microsoft followed a different course. Microsoft IT department opted for 'UPDATE', a more user-centric approach to reduce complexities in deploying the Windows 8.1 operating system.

Windows 8 to Windows 8.1 migration

The company believed the UPDATE method where an operating system update was rolled out like an application than an installation file was more suitable and appropriate for,

• Windows team had invested heavily in this process to offer a fast and seamless update process.
• The method offered a simple and easy way for users to initiate
• Reduced the complexity by leveraging capabilities (Microsoft System Center 2012 Configuration Manager) provided natively in the Windows update process.
• Preserved all user data, settings, and applications with no customization or configuration required

Moreover, Microsoft IT department found UPDATE method more convenient to deploy, manage, and support. It offered multiple benefits. For instance,

• The IT department of the company saw high success rate in deployments and help desk calls were reduced by significant percentage. So, less work for IT pros!
• The update required low user involvement during installation.

Main takeaway: Deploying as an update is faster and a cost effective alternative to creating complex zero-touch installation images. Plus, Windows adoption was more or increased.

The method was somewhat different for the enterprise setting. Any version of Windows 8 activated through Microsoft Volume Licensing was not offered the update in the Windows Store.

Instead, the same type of update installation was offered in an enterprise environment by using the Application Deployment feature in System Center 2012 Configuration Manager. It uses the same setup engine as the consumer update.

Microsoft IT had 2 options here,

1. They could push the update out.
2. Make the update available in the System Center 2012 Configuration Manager Company Portal so that users can pull it down at their convenience.

Push vs. Pull

System Center 2012 Configuration Manager (including Service Pack 1* and R2) supports “push” and “pull” installations.

Pull Installations

A self-service method, where users initiate the upgrade from the Company Portal.

Push installations

Microsoft IT can push the update out to systems that are not upgrade by a certain date. In short, the Windows 8.1 upgrade can be applied to systems as a scheduled activity.

Microsoft noticed the following benefits:

1. Microsoft IT saw 97% success rate in deployments and help desk calls were reduced by 48%.
2. The update installation preserved user data, settings, and applications.
3. The update required low user involvement during installation.
4. Using the available standard deployment images reduced complexity
5. The Windows 8.1 update hadlower cost than traditional operating system deployments.
6. Reporting leveraged the data collected in System Center 2012
7. Configuration Manager to gain insights into update deployment results.
8. The deployment method leveraged standard System Center 2012 Configuration Manager tools.

For complete information, visit this page.