In this article I will explain you how to approach the rollout/deployment phase.
Only once all the requirements gathering, configuration and infrastructure setup are complete you can obviously move into the rollout phase. Please refer the previous article on Win10 migration preparation and key requirements.
on Win10 migration preparation and key requirements.
The migration/deployment phase can be broken down into two parts:
- Pilot Rollout
- Global Rollout
The pilot rollout required in this case about 100 users selected from different departments, functions and geographical locations, in order to test and fine tune the deployment strategy. During this period, which might last 4-6 weeks, you will face real world challenges and issues, without affecting thousands of users, but just a limited number, therefore limiting impacts on business critical functions and BAU.
Once the pilot phase is over, all the lesson learnt are collected and translated into improvements towards the real rollout, you can move into rolling out into large numbers to the remaining user base.
In this case as we are working on thousands of users, the rollout could and should be broken into phases, according to your timeframes and constraints (e.g. batches of x hundreds of users located in certain offices).
A separate discussion should be just on users training, preparing them to work with the new OS, as well as closely monitoring the progress of the rollout, how it affects bandwidth and corporate network etc.
For further information feel free to get in touch.