With the answer files complete, now it’s time to install Windows 10 on a reference Hyper-V virtual machine. You can naturally use any other virtualization platform for this, or even a spare physical PC, but I prefer Hyper-V and recommend it highly. To get started with Hyper-V in case you are not familiar with this
Search results for Customize Windows Image
In Part 1, we got MDT installed and set up. Here in Part 2, we will import operating systems to the MDT Deployment Workbench and create a Task Sequence to let us deploy Windows, and finally deploy a default Windows 10 install to a target device. Import Operating System To deploy an operating system, it
Most new computers with pre-installed operating system today are shipped with a so called factory recovery option which allows user to completely reset the computer by restoring an image stored in specific factory recovery partition. The problem with factory recovery is that it restores everything as the original equipment manufacturer (OEM) wants. This might include a bunch of “bloatware”, useless software like “30-day trial of XYZ” or “Tweak your PC with this fabulous tweaker” and so on. One of the first things any user wants to do when setting up a pre-installed Windows on a new computer is to get rid of all this bloatware.
Final phase of this project is to sysprep customized Windows image, capture it to a WIM file, and create an ISO for completely automated installation. Create a Checkpoint On your reference Hyper-V VM, create a checkpoint before proceeding. Select Action > Checkpoint in Virtual Machine Connection window, name the checkpoint as you wish, click YES to
OK, now it’s time to create an answer file to automate Windows Welcome (OOBE). To do that, please launch the Windows SIM and create a new answer file (File > New Answer File). Because you already created the catalog file in a previous post in this series (Part 2) you don’t have to go through the
Installing Windows 10 is done in three phases: Boot from install media, run Windows Setup (when done, restart is required) Configure hardware devices (one restart during, one restart when done) Windows Welcome (OOBE) In normal clean install, user interaction is required in phases 1 and 3, phase 2 being run automatically without user interaction.
Boot & forget Of all the operating systems I know, Windows is the most versatile and flexible when it comes to setting up totally automated, unattended “hands free” install media. Pretty much everything you might want to do can indeed be done. It’s just a matter of knowing how! In this series of posts, we
My subjective opinion: Full Flash Update (FFU) imaging is the best thing that has happened to Windows deployment. Ever. Where capturing your deployment image to a WIM file takes 10 minutes, capturing it to FFU takes under two. The time required to apply an FFU image is cut to less than half of what it
In August 2018, I wrote about how to cope with a small system disk, using my HP ProBook 470 G5 laptop as an example. This laptop includes both a 128 GB SSD and a 1TB HDD. My required software occupies 70+ GB, which makes it quite impractical to get software installed and user profiles stored
My Win10.guru partner Ed has an old device, a Dell Venue Pro 11 tablet. He got it upgraded to Windows Insider build 18317 with a clean install, but couldn’t get beyond that. Whatever he tried, he could not upgrade it to the latest Insider build, nor clean install it. Ed wrote about retiring this well-used