How To Sysprep Windows 10
My name is Jitesh Kumar, and I have more than three years of experience in the IT Domain, having expertise in Windows 10 deployment, including the diverse Microsoft tools (ConfigMgr, MDT) and deployment solutions. I'll take more than posts in the time to come.
In this post, you will learn details well-nigh running Sysprep capture Windows ten Image using DISM (Deployment Image Servicing and 1000anagement) Tool.
Introduction
DISM is a command-line tool that tin can service a Windows paradigm or prepare a Windows Preinstallation Environment (Windows PE) paradigm. Information technology tin can be used to mount and service a Windows epitome from a .wim file, .ffu file, .vhd file, or a .vhdx file and update a running operating system. Information technology can be used with older Windows image files (.wim files).
DISM is in the c:\windows\system32 folder of all Windows 10 installations, but y'all can run DISM in the command prompt from any location.
Why Use DISM -In virtually organizations, Windows Image deployments are preferred through Microsoft Deployment Tools [SCCM, MDT]. Just, due to applied policies in the environment several times, we are not permitted to run the capture Task Sequences.
What is SysPrep?
Sysprep (System Preparation) prepares a Windows installation (Windows customer and Windows Server) for imaging, allowing you to capture a customized installation. Sysprep removes PC-specific information from a Windows installation, "generalizing" the installation to be installed on dissimilar PCs.
With Sysprep, you can configure the PC to boot to audit mode, where you tin can make boosted changes or updates to your image. Or, you can configure Windows to kicking to the Out-of-Box Experience (OOBE).
Benefits of using Sysprep
- Removes system-specific information from Windows. Sysprep can remove all organization-specific information from an installed Windows image, including the computer security identifier (SID). The Windows installation tin can then be captured and installed throughout an organization.
- Configures Windows to boot to Audit mode. Audit mode enables you to install third-party applications and device drivers, likewise as to test the functionality of the computer.
- Configures Windows to boot to Windows Welcome. Configures a Windows installation to kick to Windows Welcome the next time the computer starts. In full general, yous configure a organization to kick to Windows Welcome immediately before delivering the estimator to a client.
- Resets Windows Product Activation. Sysprep tin can reset Windows Product Activation upward to three times.
Limitations
- You must use but the version of Sysprep that is installed with the Windows image that you intend to configure
- Only an administrator can run Sysprep.
- Simply ane case of Sysprep can run at a fourth dimension.
- Sysprep must not be used on upgrade installation types. Run Sysprep only on clean installations.
- The Sysprep tool runs but if the estimator is a fellow member of a workgroup, not a domain. If the computer is joined to a domain, Sysprep removes the figurer from the domain.
- You tin run
Sysprep
command up to 1001 times on a unmarried Windows image. After running Sysprep 1001 times, you must recreate your Windows prototype.
Prerequisites
Software Requirements
- Hyper-5
- Windows Operating Organization ISO
- Windows ADK to create a WinPE ISO (Download)
Overview – Windows Capture Process
The following steps aid you to perform the windows capture. Once you have the prepared machines with all prerequisites, customizations.
- Run Sysprep Utility
- Kicking a virtual machine in WinPE
- Run DISM Command to cature the image, shop the prototype either to network share/USB storgae
- Once the process completed, you lot will get Windows Prototype (.wim) file

Create WinPE ISO
The next step is to create a WinPE ISO to use with Virtual Machine
Starting time the DISM (Deployment and Imaging Tools Environment) Run equally ambassador.

Run the below command for copies of amd64 boot files.
copype amd64 C:\WinPE_amd64

Started creating Windows PE working directory in the specified location.

Once Windows PE working directory is successfully created. Use MakeWinPEMedia with the /ISO pick to create an ISO file that contains the WinPE files.
MakeWinPEMedia /ISO C:\WinPE_amd64 C:\WinPE_amd64\WinPE_amd64.iso

The WinPE ISO has been successfully generated.

Why We Need Virtual Machine to Ready for Capturing?
Tips! Building an image from a VM allows you to use Checkpoint/state restores. With checkpoint, you lot can revert your operating system country to whatsoever saved land later, which is useful to run right before you begin the capture process. That is a value-added feature for experimenting with software or tweaks that may cause issues in the operating system.
Capturing an paradigm from hardware volition issue in driver injection failure on several new models coming out now. When building a universal image for deployment, yous practise not want any hardware-specific configurations in your image.
Additional Tips & Tricks
While preparing the arrangement to capture, yous have to consider these steps.
- Perform a make clean installation of Windows Operating System.
- During installation create a local Administrator business relationship.
- After installation is complete, log in to the system with created local Ambassador account.
Before connecting with the network, ensure that the Windows store apps do not get automatically updated.
Apply Local GPO Calculator Configuration/Authoritative Templates/Windows Components/Shop Enable -Turn off Automatic Download and Install of updates policy
Perform 'Set up for prototype capture' prerequisite tasks
- Check for Windows update to install the latest patches to the system.
- Don't include drivers in captured Epitome.
- Don't install any Microsoft Store apps using the Microsoft Store.
- Verify that necessary applications, updates and language packs are installed on Windows, Time Zone is configured and validate other system personalization.
- Earlier start capturing, make clean upward your system.
- Remove Quick Access history from file explorer.
- Run Disk Clean-up, empty the Recycle Bin, Some other mutual directories that tin exist cleaned upward include: %LocalAppData%\temp,C:\Windows\Temp.
- Delete all profiles before running SYSPREP. The merely profiles that should be in WIM is Ambassador and Default.
- Remove unwanted Built-in apps form Windows Store.
Why Should We Generalize the Paradigm?
We need to generalize the epitome to remove unique specific information, replace the Computer SID related to an image and brand information technology ready for deployment on dissimilar platforms.
Generalize Image and Run Sysprep
Insert Disk to mount the WinPE ISO (created explained in the in a higher place section) file past providing the path where the ISO file is located. To kick the prepared image in WinPE, that will exist needed to start the capturing.

Once the ISO file is mounted, it will appear as shown below

- Employ SYSPREP to prepare the system for capture
- Sysprep can exist executed in two modes either through the GUI or Command prompt.
GUI Mode
Outset the Sysprep.exe utility Run as administrator located in folder C:\Windows\System32\sysprep directory.

- Tick the Generalize checkbox and select Shutdown options.
- Shutdown – Once sysprep complete, machine will automatically shutdown.

Click on OK to start the procedure.

Sysprep started running. Please wait for a few moments! Once Sysprep completes, the automobile will shut downward after processing the changes.

Command Prompt
- Start control prompt Run equally administrator.
- Go to Sysprep folder to locate Sysprep utility and blazon the following command for execution.
Sysprep.exe /generalize /oobe /shutdown

Sysprep started running. Delight wait for a few moments! Once Sysprep completes, the machine will shut downwards afterward processing the changes.

The system generalizes the images and shutting downwardly. Start the virtual machine. Your virtual machine should appear like this.

Capture Windows Paradigm after Generalize
Boot the virtual auto with Windows PE media.
You may be prompted to "Printing any key to kick from CD or DVD…..". Become alee and printing the key.
Important: Yous may need to click inside the window to ensure that your keystrokes are sent to the virtual machine.

The machine should boot to the Control prompt for PE, identified every bit X:\

Important! The system must be connected with the stable network to save the prototype file to the network share.
- Place the network IP address where you will save the capture image.
- Use cyberspace utilize control to map a network shared folder to salvage the image.
- If prompted provide the user credentials for connection.

Run the following Dism command to capture the Windows partition. For Example :
Dism /Capture-Prototype /Compress:maximum /ImageFile:\\<NetworkSharePath>\SurfacePro.wim /CaptureDir:D:\ /Proper noun:"SurfacePro"
/ImageFile: Specifies the path of the file where the paradigm will save.
/Shrink: Specifies the type of compression used for the initial capture operation. The maximum
pick provides the all-time compression.
/CaptureDir: Specifies the directory to which the image was applied.
Note: Assigning of drive letters to partitions is handled past WinPE when it beginning boots up, normally assigns the System Reserved partition a bulldoze letter of the alphabet C: and the OS partition a drive letter D:
Here the epitome capture is running.

The Image file is successfully captured in a shared binder, Copy the image and apply it for deployment.

Deploy Capture Windows Paradigm
Nosotros can either use WinPE, Configuration Managing director, or Microsoft Deployment Tools to deploy the captured paradigm.
The post will aid you manage the deployment of Windows Captured Image & Deploy Windows Image using MDT + SCCM – Deploy Windows Captured Image Using SCCM and MDT.
Troubleshooting
Windows image will cause Sysprep to fail when yous update an app from the Microsoft Store. That app becomes tied to the logged-in user account.
Yous may encounter an issue that occurs when yous remove or update a provisioned Microsoft Store app by using the Microsoft Store and then running Sysprep on the computer.

Review the log file at %Windir%\System32\Sysprep\Panther\setupact.log. The following error appears in the log files.

This Microsoft article discusses an upshot when you remove or update a provisioned Microsoft shop app.
To resolve this issue, remove the appx package for the user. Y'all will get package information from the log file.
- Start Powershell run every bit administrator.
- Type the following command to remove the bundle.
- Run
Remove-AppxPackage -Parcel <packagefullname>
from PowerShell.
Resources – Sysprep Capture Windows 10 Image
- Sysprep (System Preparation) Overview
- Windows 10 Update Enhancements Number of Devices Updates Every Hr
How To Sysprep Windows 10,
Source: https://www.anoopcnair.com/sysprep-capture-windows-10-image-using-dism/
Posted by: baumgriat2001.blogspot.com
0 Response to "How To Sysprep Windows 10"
Post a Comment