WEBINAR EXECUTIVE SUMMARY
How to Beat the Windows 10 Deployment Clock
- When migrating to Windows 10, extra work up front can save time on the back end.
- Create and use a Windows 10 image for deployment across the organization.
- Use best practices when migrating to Windows 10.
- Consider using Adaptiva OneSite to tackle the key challenges of Windows 10 deployment.
However, 86% of organizations surveyed have not yet completed their migration to Windows 10. Organizations that don’t migrate to Windows 10 by the deadline can purchase costly per seat aftermarket support from Microsoft. They can also choose to run an unsupported operating system, but doing so means running the risk of being out of compliance with regulatory and industry requirements and laws.
Although the migration to Windows 10 is complex, IT teams still have adequate time to migrate. With proper testing and piloting, you can use Microsoft-provided tools to deploy Windows 10 across the organization. You can also use solutions like Adaptiva OneSite, which helps businesses deploy Windows 10 across the organization quickly.
click presenter image to see bio
How to Beat the Windows 10 Deployment Clock
In our recent webinar, Brien Posey discussed how IT professionals can use Microsoft tools to migrate systems from Windows 7 to Windows 10. Chaz Spahn shared how Adaptiva OneSite helps businesses tackle the challenges of quickly deploying Windows 10 across the organization.
When migrating to Windows 10, extra work up front can save time on the back end.
IT teams may be feeling pressured to move to Windows 10 before Microsoft ends extended support for Windows 7 and may be tempted to cut corners. Although this might appear to save time during the initial move to Windows 10 by starting sooner, it can slow down the entire migration.
Although it takes more time, IT teams migrate many of the endpoint the operating systems from Windows 7 to Windows 10, rather than perform an upgrade. An upgrade between the versions can leave existing problems in place, which may be amplified and even more difficult to troubleshoot after the move to Windows 10. Migrating starts with a clean installation, so that pre-existing issues are not carried over.
Create and use a Windows 10 image for deployment across the organization.
“My philosophy behind Windows migrations is it’s best to do a little bit of extra work up front. It can save you a lot of time on the back end.”
Brien Posey, Contributing Editor, ITPro Today
Windows 10 migration steps.
- Create two Hyper-V virtual machines (VMs) with the newest Windows 10 image and all available updates applied.
- Install the MDT and Windows 10 Assessment and Deployment Kit (ADK) on one VM; this is the MDT environment; the second VM is used as an initial reference image.
- Create a Virtual machine manager (VMM) template from the VM set as the initial reference.
- Use the template to create a VM that can be imaged.
- Create the VM with no network connection to avoid accidental updates, which can cause Microsoft’s system preparation tool, Sysprep, to fail.
Remove unwanted software from the Windows 10 image, including pre-installed applications that are not beneficial to the business, such as games or Netflix
- Generalize to remove system-specific information, such as system name.
- Shutdown in order to shut down the machine so it is in a pristine state for deployment.
From within the Windows PE environment, run the DISM utility to capture the image that will be used for deployment. This creates a Windows Image (WIM) file based on the contents of the VM.
Note: DISM comes with Windows and is version specific; it cannot update an image that is newer that the DISM version in use.
Prepare the image within MDT:
- Create a deployment share.
- Create a folder for the operating system image; this helps organize the images.
- Use the Import Operating System wizard to select and import the WIM file.
- Add desired device drivers for deployment.
- Create a Task Sequence, typically using the standard client task sequence function. The Task Sequence can include product keys, drivers and even applications to install.
Use best practices when migrating to Windows 10.
Migrating to Windows 10 is a complicated process, and ignoring steps or rushing through the deployment can create problems. IT teams should keep the following in mind when implementing Windows 10 across the organization.
Testing is important. Take time to adequately test the process up front and find and troubleshoot problem areas early. This includes application installations included in the task sequence, which can be complicated and cause issues.
Run a pilot deployment program with a few power users who can help identify issues so they can be fixed before they happen organization-wide.
Migrate systems in batches to avoid overburdening both system and help desk resources.
Avoid deploying major Windows 10 updates while systems are still being migrated. Keeping versions consistent decreases confusion when interacting with machines across the business.
Manage updates using SCCM or MDT.
Consider using Adaptiva OneSite to tackle the key challenges of Windows 10 deployment.
The method described above is one of several methods available for Windows 10 deployment. Not only does Microsoft offer additional ways to migrate from Windows 7 to Windows 10, but companies like Adaptiva provide tools such as OneSite that simplify the deployment process.
Tackle the key challenges of windows 10 deployment.
P2P Memory Pipeline Architecture
Predictive Bandwidth Harvesting
Virtual SAN & State Migration Points
Programmable P2P PXE
Workflow Designer & Engine