How To Create A Custom Image Windows 10
Installing Windows ten is easy; every bit a Windows ambassador or expert user, all yous have to practice is download an ISO from Microsoft, fire it to an external device and use it to kick the PC or laptop.
In fifteen to 30 minutes, you'll accept a clean, fresh Windows 10 installation, but it still volition crave some work earlier information technology's prepare for production utilise. Yous'll need to install software and the desktop and personalize the Start menu to meet your requirements. Then, you'll demand to repeat this process for each of your PCs and echo that procedure whenever a reinstall is necessary.
At that place is a different method you can take. First, you should install Windows 10, customize it to your needs, install all the software you demand, capture that installation and use it to create an ISO. Using this customized ISO for your installation media, yous need half an hour to clean install Windows 10 with all your software and personalization. When you want to change something in your ISO, add or remove software, alter personalization, or update or upgrade Windows 10, you only update the paradigm and create a new ISO. It's fast and easy to do, and it tin can work for whatever Windows administrators.
Getting started with a custom ISO
To create a custom ISO, you need install media for your preferred Windows x edition and software, a technician automobile -- a Microsoft term that means a PC on which you can build OS images -- and almost twenty minutes longer than it would have to clean install Windows 10 and all your software i time.
The procedure of creating a custom ISO breaks downwardly into five distinct parts:
- Install Windows and prepare assets while installing
- Update and customize Windows, install software
- Generalize Windows image with Windows System Preparation Tool (Sysprep)
- Capture Windows epitome, create the ISO
- Update/Change the ISO
Apart from whatsoever software y'all pre-installed in your Windows paradigm, you don't need whatsoever third-party tools, apps or other software; everything is done using native Windows ten and Microsoft tools.
Y'all should follow these steps to create a custom ISO for a Windows ten desktop.
i. Install Windows and ready assets
Install Windows ordinarily until it stops at the Region Choice screen subsequently the last reboot. When the desktop requests a product central, select the "I don't have a product key" option. Windows does not need to be activated for this process.
This example uses a Hyper-5 Generation 1 virtual machine (VM) every bit the technician motorcar, with a 64 GB virtual difficult disk. Before starting the VM, you should alter its settings to use Standard Checkpoints instead of default Production Checkpoints.
Installation takes 15 minutes or so to complete. While it'southward running, you have time to prepare some assets on your host machine. First, download and install the Windows 10 Assessment and Deployment Kit (ADK). Adjacent, create an unattended answer file using the Windows System Epitome Manager (SIM), which is part of the Windows ADK. Don't panic even if you are a Windows SIM newbie. Information technology's easy to utilise.
If yous are feeling unsure almost this, or if Windows SIM looks likewise intimidating, input the following respond file into a blank file using Notepad (Figure 1).
The values shown in bold reddishabove are explained below.
ProcessorArchitecture =adm64 for 64 fleck Windows,x86 for 32 bit
Logo = OEM logo (120*120 pixel bitmap (.bmp)) file
Manufacturer = Whatever you lot like
SupportHours = text string (9 AM to v PM, 10:00 – eighteen:00, 24/7 etc.)
SupportPhone = whatsoever phone number
SupportURL = whatever URL
OEMName = Whatever yous similar
RegisteredOwner = Whatever you lot like
TimeZone = As per Microsoft fourth dimension zone names
All the preceding respond file components are optional, except ProcessorArchitecture -- this component is mandatory. If you do not need or desire to set a fourth dimension zone, for example, y'all should remove this line:
<TimeZone>Westward. Europe Standard Time</TimeZone>
When you lot're done customizing the answer file, save it as unattend.xml. You should create a new folder on Microsoft OneDrive and name it "Deployment Assets." Salvage your respond file in this folder.
Next, prepare an OEM logo image if one is needed. Whatever bitmap epitome (.bmp) will exercise, but its size must exist exactly 120 x 120 pixels. Save the epitome every bit oemlogo.bmp in the Deployment Avails binder.
Alter groundwork images, colors, sounds and screensavers on your host machine, so save your settings as a theme file. Save all the themes you'd like to include in the custom ISO into your Deployment Avails folder likewise. This folder is where you'll notice the items you need to customize your ISO again and again.
2. Update and customize Windows, install software
When Windows installation is done, the last setup out of box experience (OOBE) begins. The process stops to let you to select the region but instead of doing that, printing Ctrl + Shift +F3.
Windows interrupts its normal setup and restarts in audit mode, a special customization mode for Windows. Considering no user accounts exist on the desktop still, information technology signs you into inspect way using the built-in administrator account. Click on "Cancel" to close it, and so alter the display resolution if the default 1024 x 768 is too small for you to piece of work in.
Yous can now install your software and update Windows. Do not run any programs yet. If, for example, the installer shows "Run this application at present" selected in a final prompt, unselect it and close that installer. Practice not install any hardware drivers -- fifty-fifty those that Windows Update installs automatically will exist removed afterwards. If any installer or update requires a restart, practise it. Windows returns to audit way after restart. If you want to download software, you lot must use Microsoft Border.
Import the Deployment Assets yous prepared while Windows was installing on your technician motorcar. If you saved assets on OneDrive, sign into your OneDrive account. Download the oemlogo.bmp file and save it to the C:\Windows\System32 folder. Practise the aforementioned for the answer file unattend.xml and salve information technology to the C:\Windows\System32\Sysprepfolder. Information technology is important for y'all use these file names exactly as shown, and to save them to the folders specified.
Customizing the installed paradigm
You do non need to save the Windows themes that you prepared. Select a desktop theme on OneDrive and instead of saving it, select Open up to employ information technology to the technician machine. Because Windows is non activated in inspect mode, y'all cannot use personalization options (e.m., themes, colors etc.). Applying an imported theme is your only ways to customize theme and desktop appearance.
Open File Explorer and customize information technology as you lot like. You can adjust icon size, hide or show the Ribbon, show item selection boxes, show Details or Preview pane, show Libraries in Navigation pane and so on.
The post-obit PowerShell command exports your current Kickoff layout to the file named C:\Windows\System32\MyStart.xml:
Export-StartLayout C:\Windows\System32\MyStart.xml
When you lot've exported the file, open the Grouping Policy Editor with the command Win + R, blazon gpedit.msc. The Group Policy Editor is not available in Home and Single Language Windows 10 editions. Browse to Local Computer Policy > Administrative Templates > Start Carte du jour and Taskbar in the left-hand pane, then double click Beginning Layout on the correct-hand pane.
Enable policy past enteringC:\Windows\System32\MyStart.xml every bit the Start Layout File, then click on OK to salve that policy.
This policy forces each user business relationship to apply your customized Start layout.
Two batch files are still missing from this customization. They run one time each time a new user signs in for the first time. The starting time file resets File Explorer's Contempo Files and Quick Access. To build this file, type or copy and paste the following 2 lines into a new Notepad text file:
echo Y | del
%appdata%\microsoft\windows\recent\automaticdestinations\*
del %0
This batch file resets Quick Access and then deletes itself because it but exists and runs when a new user signs in for the first time. In Notepad, select File > Save As, type%appdata% in the address bar in the Save As prompt, so press Enter to open up AppData\Roaming folder.
Browse to the folder named Microsoft\Windows\Start Menu\Programs\Startup.Save the file as RunOnce.bat and select "Save As type: All files" in Notepad's Salve As prompt.
The second batch file is a Visual Bones Script (.vbs) file. Its purpose is to greet new users the first time they sign in, after which it deletes itself. This file is optional, but it is something you lot should probably include in your customized images. Type or copy and paste the following text into a new Notepad text file:
Dim WshShell, Welcome Set up WshShell = WScript.CreateObject("WScript.Beat") Welcome = WshShell.Popup("Welcome to customised Windows 10 with pre-installed software.", lx, "Windows x", vbOKOnly) Select Instance Welcome instance 1 MsgBox "Post-obit software has been installed: Office 365 (2016), Adobe reader, VLC Player, Chrome, Firefox and Opera. You will too find some pre-installed themes in Settings > Personalize > Themes.", vbOKOnly, "Windows 10" Stop Select MsgBox "Have Fun with Windows ten!", vbOKOnly, "Windows 10" DeleteScript() Function DeleteScript() Set objFSO = CreateObject("Scripting.FileSystemObject") strScript = Wscript.ScriptFullName objFSO.DeleteFile(strScript) Cease Function
Save this file equally Welcome.vbsto the same folder where yous saved RunOnce.bat. Over again, select the "Save As blazon: All files" option in Notepad's Save As prompt.
If you like, you lot can likewise set both the unattend.xml and Welcome.vbs files on the host while Windows is installing.
three. Generalize Windows prototype with Sysprep
1 small -- but important -- step you must take before running Sysprep is creating a segmentation on the Hyper-5 VM to store a captured Windows image. If you are using a physical PC every bit the technician auto, this is unnecessary. Instead, you can simply use an external HDD or flash drive to store that image.
Create free space in Disk Direction
Open Deejay Direction and shrink the original C: segmentation to create free space for a new partition in which to capture a Windows image. It needs to be big enough for the install.wim file you'll capture after. For example, a custom Windows 10 Pro x64 ISO could include the post-obit software pre-installed: Office 365 Business, Macrium Reflect, Opera, Chrome, Firefox, VLC thespian, Adobe Reader, Malwarebytes, TeamViewer, 7-Aught, Notepad++, and other software that varies from build to build.
As described, this results in an install.wim file that's between 5 to 6 GB in size. To compensate, you ordinarily decrease x GB (10,240 MB) from C:. That'southward enough for most users. So, get out Deejay Management.
To help identify key partitions later, rename the system drive C: to Windows and the new partition to Epitome or whatever other distinctive name. Create a new folder on the new capture drive (East:) named Scratch. You volition need it when capturing the image as a temporary working binder using the DISM command.
Prep and run Sysprep
If yous are running a Hyper-Five VM, create a checkpoint at present. If y'all are using another virtualization program, create a snapshot. If using a concrete PC, you should create a system image now. Checkpoints and snapshots accept just a minute, while imaging a physical PC takes a bit longer.
Check that the built-in admin's or current user'southward Downloads folder is empty and that no software installers or assets are left in that location. Run Disk Cleanup to remove all temp files, Recycle Bin content and other bloat.
To run Sysprep, open up the command prompt. The desktop will automatically elevate it because you are signed in using the built-in administrator account. Run the following command:
%windir%\system32\sysprep\sysprep.exe /generalize /oobe
This control runs Sysprep with Generalize and OOBE switches and so shuts down. The Generalize switch removes all hardware-related data such as drivers and registry entries, resets Upshot Viewer, removes all shadow copies -- restore points -- and disables the built-in administrator account.
The OOBE switch forces Windows to run its setup phase the next fourth dimension Windows boots from this prototype as if information technology were a normal Windows setup. Considering Windows was generalized, information technology generates a new unique SID for each such installation.
Sysprep reads the respond file unattend.xml from C:\Windows\System32\Sysprep folder. In this case its most important line reads <CopyProfile>true</CopyProfile>. When true, CopyProfile copies all our customizations to the default user profile in the subconscious Default binder in the Users binder. That profile is used equally the base contour whenever a new user account gets created.
4. Capture Windows image, create the ISO
Once Sysprep finishes working its magic, the Windows 10 installer shuts down. Boot the technician car using the Windows 10 install media -- the aforementioned you used in the beginning to install Windows. Practice non let it kicking from difficult disk, an HDD or SSD if using a concrete automobile or VHD if y'all're using Hyper-V.
At the beginning prompt when Windows setup asks for region and language settings, instead of selecting annihilation and starting installation, press Shift + F10 to open the Recovery Console Command Prompt. Typediskpart and printing Enter to start the disk sectionalization utility, then typelisting vol to list all available volumes, or partitions. For this example, the Hyper-5 VM list vol shows this data:
You lot can see why it'southward important to name the deejay partitions so you tin can identify them hands.
Annotation that the Recovery Panel does not use the same bulldoze ID policy as Windows x. Yous need to be sure which drive has Windows installed and which drive will store the captured image for customization and re-use.
Typeget out and press Enter to exit the deejay partition utility.
Enter the following control:
dism /capture-paradigm /imagefile:East:\install.wim
/capturedir:D:\ /ScratchDir:E:\Scratch
/proper name:"W10PROx64" /compress:maximum
/checkintegrity /verify /bootable
Check and note the post-obit of import details:
- /imagefile:E:\ = drive where install.wim volition be saved
- /capturedir:D:\ = bulldoze where Windows is installed
- /ScratchDir:E:\ = bulldoze where temporary working folder Scratch is located
- /proper noun: = any name you similar in quotes, not of import but obligatory, here you can see the version of Windows: 64-chip Win10 Pro
Printing Enter to start.
This will take some time to complete. On slow physical machines, information technology can have up to xx to 25 minutes. During the start half of that period, you won't see a progress indicator.
When this command has finished, eject the install media -- in Hyper-V select Media bill of fare > DVD Bulldoze > Eject. Next, shut the command prompt and restart the technician machine. This time, kick usually from HDD or VHD and let it work through normal OOBE setup.
While the technician car is preparing and setting upwardly Windows, right-click the original Windows 10 ISO image you lot used to mount it on the host computer every bit a virtual DVD. And so, open information technology in File Explorer and copy its entire contents to a new folder on the host HDD.
When the technician machine is ready and your initial user is logged into the desktop, copy your newly created install.wim file from the epitome drive (East:) to the Sources subfolder in the binder where you lot copied the original Windows installation files. In this example, that'south D:\ISO_Files\Sources folder. It will replace the original Windows x install.wim file.
Hyper-V users should also create a checkpoint now on their technician VM to capture a pristine arrangement paradigm.
Windows imaging tools
Run Deployment and Imaging Tools Environs elevated every bit an admin. Information technology is installed as part of the Windows ADK and you can find it in Offset > West > Windows Kits. Blazon CD\ and press Enter to set up the working folder to the root of the C: bulldoze. Enter this control:
oscdimg.exe -m -o -u2 -udfver102 -bootdata:2#p0,e,
bd:\iso_files\kicking\etfsboot.com#pEF,east,
bd:\iso_files\efi\microsoft\kick\efisys.bin
d:\iso_filesd:\Win10PROx64.iso
The preceding control is one long continuous command line though it breaks beyond multiple lines in this article.
Cheque and the note post-obit details:
- d:\iso_files = path to folder where you copied original install files
- d:\Win10PROx64.iso = path and your preferred name for new ISO
With all this piece of work completed, making the ISO takes only a infinitesimal or two. When that'southward done, y'all can burn down the ISO to a DVD or flash drive; it will work on both BIOS/MBR and UEFI/GPT systems to install your customized Windows with its pre-installed software.
v. Update or change the ISO
The beauty of using Hyper-V VM equally technician machine lies in how easy it makes the task of maintaining and updating a customized install image. For example, Windows Insider: Fast Ring receives new pre-release builds frequently and participants may want to upgrade their ISOs at the same stride.
When yous feel similar irresolute the ISO, you can simply use the Hyper-V technician VM's standard checkpoint yous should have created just before running Sysprep Windows. You lot tin can add and remove software, update software, run Windows updates, apply a new theme or do whatever else yous might need to exercise.
When that'due south done, you should run Deejay Cleanup, create a new checkpoint so you can restore to this point, echo Sysprep, capture a new install.wim and make a new ISO. This process volition exist much faster now. The whole process takes only minutes because both Windows and basic software are already installed.
Upgrading the custom ISO
Every bit a Windows Insider, you might besides be interested in upgrading the ISO. When a new build arrives, you should restore the checkpoint you created when the technician machine was fully fix upwardly after capturing the install.wim file. You can't use the checkpoint made in audit mode before Sysprep, because upgrading Windows in audit mode is non possible.
Once you've booted to normal mode, yous can upgrade to the latest Insider build or the side by side feature update build using Windows Update or a standard ISO epitome. When that upgrade completes, enter the following command in an elevated command prompt to restart Windows in audit mode:
%windir%\system32\sysprep\sysprep.exe /audit /reboot
Windows restarts, and so signs into audit mode using the built-in administrator account. Your initial user account already exists, so you should open Settings app > Accounts > Other users and delete all existing user accounts and their profile folders.
You should also delete the custom install.wim file from last fourth dimension if information technology'southward still located on the image drive -- East: in this case -- and check to ensure that the Scratch folder still exists. If not, you lot must recreate it manually.
Source: https://www.techtarget.com/searchenterprisedesktop/tip/How-to-create-a-custom-ISO-for-Windows-10
Posted by: walkeriiii1981.blogspot.com
0 Response to "How To Create A Custom Image Windows 10"
Post a Comment