Pau Lo
asked on
large scale Windows/Office upgrade
do Microsoft issue any general guidance best practices when tackling large scale OS upgrade (windows 7 to windows 10, and office 2010 to the latest version) over a large scale number of devices, e.g. 1500 +. I wont be involved myself but having assurances the project will follow best practices and have considered all various risks & issues would be most useful.
McKnife
We need to know whether you will have new machines or keep the same machines. If same machines, if you plan to do an in-place upgrade or start fresh and if you start fresh, what deployment infrastructure is at hand.
ASKER
From what I understand it will be a mixture of new machines and upgrades on existing. SCCM is the primary tool used for software deployment.
So for those upgrades, did they plan inplace upgrades or fresh start (which many people will call "upgrading" as well)?
ASKER
I will ask the question, but it was more looking for general best practices/guidance from Microsoft themselves or other experts - for tackling these major upgrades rather than the fine detail of each possible approach. & plans/best practice guidance others have worked from in previous exercises that were of use etc.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thank you. I seem to recall Microsoft assessment & planning toolkit was quite well used a few years ago, not sure if its still something they maintain, but it gave some good reports on which devices were 'windows 10 ready' etc, or others which were not likely good candidates for upgrading in-place etc.
Microsoft has a lot of guidance on this already. And having SCCM definitely helps here. If the machine are on SCCM then you can go from onboarding them in the windows analytics dashboard which gives you upgrade readiness in the cloud to defining your groups and initiating true zero-touch upgrades. You can do in-place or even wipe-and-load (with profile backup and restore) from SCCM with no need to be at the machine even temporarily.
The SCCM and Win10 deployment docs on technet cover all of these scenarios in detail, but I'd definitely leverage SCCM for the volume of machines your considering snf I'd plan on doing upgrades in patches to ease training and catch app compat issues. SCCM handles the technical aspects of that easily.
The SCCM and Win10 deployment docs on technet cover all of these scenarios in detail, but I'd definitely leverage SCCM for the volume of machines your considering snf I'd plan on doing upgrades in patches to ease training and catch app compat issues. SCCM handles the technical aspects of that easily.