Page 1 of 4 123 ... LastLast
    Create media for automated unattended install of Windows 10

    Create media for automated unattended install of Windows 10

    How to create install media for completely automated unattended install of Windows 10
    Published by Category: Installation & Upgrade
    14 Nov 2017
    Designer Media Ltd

    Published by


    Kari's Avatar
    Finnish but not finished


    Location: A Finnish expat in Germany
    Posts: 12,971

    Show Printable Version 


    information   Information
    Installing Windows 10 is done in three phases:
    1. Boot from install media, run Windows Setup
    2. Configure hardware devices
    3. Windows Welcome (OOBE)

    In normal install, user interaction is required in phases 1 and 3, phase 2 being run automatically without user interaction. In phase 1 user selects language and keyboard layout settings for system accounts, enters product key for specific edition or selects edition manually if product key is not entered at this stage, and selects disk and partition to install Windows. When phase 1 is done, Windows restarts to phase 2 which is done without user interaction and when ready automatically restarts to phase 3.

    In phase 3 user selects region and language settings for user accounts, creates initial admin user account, chooses OneDrive and privacy settings and finally boots to desktop.

    In this tutorial we will create two answer files to automate phases 1 and 3. An answer file is set of commands and instructions in XML format to tell Windows setup what to do and how to proceed. We will need two answer files:
    • autounattend.xml to automate phase 1, Windows Setup
    • unattend.xml to automate phase 3, OOBE

    When done we will create a custom USB flash drive install media for unattended install. To install Windows 10 using this USB will be totally unattended, "Hands Free"; simply boot from USB and forget it, take a break, come back to PC to find everything is done, Windows fully installed without a single key press or mouse click, without any user interaction.

    The process as described in tutorial requires two computers, one or both of them can be virtual machines:
    • A technician machine
      • A computer or virtual machine with existing Windows 10 installation, any version and edition. Technician machine will be used to prepare answer files and other assets for custom install image
      • In this tutorial I will use my W10 PRO Insider Preview Build 17025 laptop as technician machine
    • A reference machine
      • A computer or virtual machine which has no operating system installed. Reference machine will be used to clean install Windows 10, customize it in Audit Mode, sysprep it and finally capture Windows install image (install.wim file) from it
      • If reference machine you want to use already contains an installed OS, existing installation must be wiped and replaced with a fresh clean install, or alternatively Windows 10 clean installed on another partition or disk on that machine (dual boot)
      • In this tutorial I will use a new Hyper-V virtual machine created specifically for this purpose as reference machine

    Both technician and reference machines can be either BIOS/MBR or UEFI/GPT machines, regardless for what partitioning system you are preparing answer files and USB install media.

    Tutorial is quite long, not because topic is complicated (it's not!) but rather because it is somewhat unfamiliar for most average users. I wanted to make this tutorial as easy to follow as possible for users who have never done anything like this, which requires quite a lot explaining and screenshots.

    Do not hesitate to post your questions and issues in this thread.




    Create media for automated unattended install of Windows 10 Contents Create media for automated unattended install of Windows 10
     Use links below to go to any step, back button of your browser to return to this list.


    Step One: Install Windows System Image Manager
    Step Two: Create a catalog file
    Step Three: Create answer file for Windows Setup
    Step Four: Create answer file for OOBE
    Step Five: Prepare assets
    Step Six: Install Windows 10 on reference machine
    Step Seven: Customize and capture Windows image
    Step Eight: Create USB install media





    Create media for automated unattended install of Windows 10 Step One Create media for automated unattended install of Windows 10
     Install Windows System Image Manager


    1.1) Windows System Image Manager (SIM) is part of Windows Assessment and Deployment Kit (ADK). On technician machine, download Windows ADK from Windows ADK downloads - Windows Hardware Dev Center

    If you are creating answer files for unattended install of Windows Insider build, download Windows Insider Preview ADK instead: Download Windows Insider Preview ADK

    1.2) Run the installer on technician machine, select Install to this computer. Don't panic when you see installer to tell it requires almost 7 GB, we will only need under 100 MB part of it:
    Name:  image.png
Views: 773
Size:  168.3 KB

    1.3) For purpose of this tutorial, we will only need Deployment Tools. You can unselect everything else:
    Name:  image.png
Views: 770
Size:  343.3 KB

    1.4) When installed, Windows SIM can be found and started from Start > W > Windows Kits > Windows System Image Manager:
    Name:  image.png
Views: 768
Size:  197.7 KB





    Create media for automated unattended install of Windows 10 Step Two Create media for automated unattended install of Windows 10
     Create a catalog file


    Note   Note
    Following steps require you are signed in on technician machine with an administrator account!

    2.1) Mount Windows 10 ISO on technician machine (tutorial)

    2.2) Copy ISO contents to a folder on hard disk (CTRL + A to select all in Explorer, CTRL + C to copy). I will use folder D:\ISO_Files for this and paste ISO content there (CTRL + V). When copied, unmount ISO (tutorial)
    Note   Note
    Please notice, to continue we will need install.wim file. If your Windows 10 ISO is ESD based (Media Creation Tool ISO), you must first convert install.esd to install.wim as told in this tutorial: Convert ESD file to WIM using DISM in Windows 10 Tutorials

    When done, delete install.esd file in your ISO_Files\Sources folder, replace it with converted install.wim file and continue from 2.3.

    2.3) Start Windows SIM (see 1.4). To create an answer file, Windows SIM needs a so called catalog file which will be based on install.wim file for a specific edition of Windows 10

    2.4) In Windows SIM, select File > New Answer File. You will be asked if you want to open a Windows image. Select Yes:
    Name:  image.png
Views: 762
Size:  119.8 KB

    2.5) Browse to and select install.wim in ISO_Files\Sources folder (or any other folder you used to copy ISO content for instance I_Copied_ISO_files_Here\Sources)
    Name:  image.png
Views: 756
Size:  245.4 KB
    Note   Note
    Creating a catalog file will take quite some time. Luckily you only need to create catalog file once. It will be created in same folder where install.wim file used to create it is located, in this example case now in my D:\ISO_Files\Sources folder. The filename will be install_Windows 10 XXX.clg where XXX is edition in question.

    Copy the catalog file to another folder to keep it for future needs:
    Name:  image.png
Views: 759
Size:  179.5 KB

    In the future you can open catalog file instead of creating a new one, Select a Windows Image dialog (see 2.5) accepts both WIM and CLG (catalog) files:
    Name:  image.png
Views: 758
Size:  21.5 KB

    2.6) In case your ISO is a multi edition one, select correct edition:
    Name:  image.png
Views: 757
Size:  86.9 KB

    2.7) If creating a new catalog file, Windows SIM will tell it must create one. Click Yes:
    Name:  image.png
Views: 749
Size:  98.1 KB

    2.8) Catalog will be created:
    Name:  image.png
Views: 752
Size:  36.2 KB





    Create media for automated unattended install of Windows 10 Step Three Create media for automated unattended install of Windows 10
     Create answer file for Windows setup


    3.1) Windows installation and setup is done in so called configuration passes. More information about configuration passes on Microsoft TechNet: How Configuration Passes Work.

    An answer file is made by adding components to various configuration passes, each component containing settings for that pass. There are seven different configuration passes, here shown in Answer File pane in Windows SIM:
    Click image for larger version. 

Name:	image.png 
Views:	21 
Size:	185.5 KB 
ID:	160815

    Configuration passes 5 auditSystem and 6 auditUser are not needed in normal Windows setup.

    3.2) Answer file autounattend.xml, first of two answer files we will prepare is the one that takes care of setup phase containing information about regional settings, accepting EULA, how to partition hard disk and in which partition Windows will be installed. It only contains components in pass 1 windowsPE

    3.3) In Windows SIM, expand Components in Windows Image pane bottom left:
    Name:  image.png
Views: 808
Size:  24.4 KB

    3.4) Component names start with amd64_Microsoft-Windows if you are working with catalog file for 64 bit Windows, and with x86_Microsoft-Windows for 32 bit Windows, and end with build number of the install.wim file used to create the catalog. In this tutorial I will omit these two parts when telling about which components need to added.

    To add region and language settings to answer file, right click component International-Core-WinPE, select Add Setting to Pass 1 windowsPE:
    Name:  image.png
Views: 808
Size:  373.9 KB
    warning   Warning
    Be sure to add International-Core-WinPE component, the one just above it has almost the same name without WinPE part. Adding the wrong component makes the answer file invalid!

    3.5) You will see that selected component was added to Answer File pane. Select it and enter required settings in Properties pane:
    Click image for larger version. 

Name:	image.png 
Views:	18 
Size:	191.3 KB 
ID:	160899
    • InputLocale: Your preferred default keyboard layout
    • SystemLocale: Your country or region
    • UILanguage: Windows language
    • UserLocale: PC location

    Note   Note
    UILanguageFallback is the language to be used for resources, notifications and system messages that are not localized (translated) to current Windows system language. US English (en-US) can and should be used for all partially localized languages. Arabic (ar-SA) and Chinese Hong Kong (zh-HK) are exceptions, in addition to en-US in Arabic fallback language can also be French (fr-FR) and in Chinese Hong Kong Chinese Taiwan (zh-TW).

    As I am using British English Windows 10 and Finnish keyboard layout, in my case I set location and language to en-GB (Great Britain), fallback to en-US and keyboard layout to Finnish (040b:0000040b).

    Some other keyboard / region codes:
    • Brazil - Portuguese > 0416:00000416, pt-BR
    • Canada - English > 1009:00000409, en-CA
    • Canada - French > 0c0c:00011009, fr-CA
    • France - French > 040c:0000040c, fr-FR
    • Germany - German > 0407:00000407, de-DE
    • UK - English > 0809:00000809, en-GB
    • USA - English > 0409:00000409, en-US

    Complete list: Default Input Profiles (Input Locales) in Windows | Microsoft Docs

    You can check current regional settings on technician machine in elevated PowerShell with following command and use them if answer file and USB install media you are creating will be used to install Windows 10 with the same settings:

    dism /online /get-intl

    Click image for larger version. 

Name:	image.png 
Views:	23 
Size:	391.7 KB 
ID:	160997

    3.6) Expand component International-Core-WinPE in Answer File pane, select SetupUILanguage, enter the Windows language in Properties pane. In this example as the install media is British English I enter en-GB:
    Click image for larger version. 

Name:	image.png 
Views:	14 
Size:	135.3 KB 
ID:	160829

    3.7) In Windows Image pane, browse to and select Setup, add it to Pass 1 winPE:
    Name:  image.png
Views: 809
Size:  328.4 KB

    3.8) Expand Setup component, select UserData, set AcceptEula to true, add organisation name (optional). Notice that in some settings which only accept preset values like AcceptEula here (it can only be true or false), selection is made from drop down list:
    Click image for larger version. 

Name:	image.png 
Views:	19 
Size:	243.9 KB 
ID:	160833

    This is a good example about what we are doing: If AcceptEula was left empty or set to false, setup would stop waiting user to accept EULA. When the whole point is to automate the setup, it is important to set it to true.

    3.9) Expand UserData, select ProductKey, add a generic product key:
    Click image for larger version. 

Name:	image.png 
Views:	16 
Size:	224.0 KB 
ID:	160834

    Generic product keys:
    • Windows 10 Home Single Language: 7HNRX-D7KGG-3K4RQ-4WPJ4-YTDFH
    • Windows 10 Home: TX9XD-98N7V-6WMQ6-BX7FG-H8Q99
    • Windows 10 Pro: VK7JG-NPHTM-C97JM-9MPGT-3V66T

    Education, Enterprise and Server editions, see following support article for generic install keys: Appendix A: KMS Client Setup Keys

    3.10) Time to configure and partition Windows system disk. In this example I will configure a single disk which will be partitioned to use all capacity after system partitions have been created for Windows partition C:.

    Right click Setup > DiskConfiguration in Answer File pane, select Insert New Disk:
    Name:  image.png
Views: 807
Size:  168.5 KB

    3.11) Select the disk you added in Answer File pane, set DiskID to be 0 and WillWipeDisk to true:
    Click image for larger version. 

Name:	image.png 
Views:	13 
Size:	168.8 KB 
ID:	160918

    When setup is run, this will wipe primary HDD, doing the same than DISKPART > SELECET DISK 0 > CLEAN.

    3.12) Expand disk in Answer File pane, right click Create Partitions and select Insert New CreatePartition to create first partition:
    Name:  image.png
Views: 801
Size:  182.5 KB

    If you are creating answer file for unattended install on BIOS / MBR based machines which require two partitions (System reserved, Windows), repeat this step and create one more partition. If you are creating answer file for UEFI / GPT based machines requiring at least four partitions (WinRe, EFI, MSR, Windows), repeat this step three more times. As I am preparing install media for UEFI / GPT, I need four partitions now:
    Name:  image.png
Views: 802
Size:  99.3 KB

    3.13) Select a partition (CreatePartition) in Answer File pane, set Order 1, Size 450, Type Primary:
    Click image for larger version. 

Name:	image.png 
Views:	17 
Size:	204.5 KB 
ID:	160929

    This creates the first partition, WinRE in GPT partitioning scheme or System Reserved in MBR scheme.

    3.14) GPT disk only: Repeat step 3.13 three more times to create EFI, MSR and Windows partitions. Set partition properties as shown in below table. All four partitions are required:

    PARTITION EXTEND ORDER SIZE (MB) TYPE
    WinRE False 1 450 Primary
    EFI False 2 100 EFI
    MSR False 3 16 MSR
    Windows True 4 Leave empty Primary

    MBR disk only: Repeat step 3.13 once and create Windows partition. Set partition properties as shown in below table. Both partitions are required:

    PARTITION EXTEND ORDER SIZE (MB) TYPE
    System Reserved False 1 450 Primary
    Windows True 2 Leave empty Primary

    Note   Note
    In both examples above, you will notice that we set the last partition (Windows in this case) to use all available space by setting Extend property to True instead of defining a size for the partition, leaving Size property empty (it must be left empty if Extend = True, do not enter any value!):
    Click image for larger version. 

Name:	image.png 
Views:	15 
Size:	208.0 KB 
ID:	160945

    If we would like to create additional data partitions, we would set Extend property for Windows partition to False and set a Size property for it instead (size in MB), then add additional partitions setting their size as preferred, extending the last partition to use all available space. You can only use Extend True for the last partition on disk.

    In below table example properties for partitioning HDD to have a 128 GB (131,072 MB) Windows partition, a 200 GB (204,800 MB) Data partition, and finally use rest of the disk for Games partition:

    PARTITION EXTEND ORDER SIZE (MB) TYPE
    WinRE False 1 450 Primary
    EFI False 2 100 EFI
    MSR False 3 16 MSR
    Windows False 4 131072 Primary
    Data False 5 204800 Primary
    Games True 6 Leave empty Primary

    3.15) In steps 3.13 and 3.14 we only created raw partitions. Each of them needs to modified. To do that, right click ModifyPartitions and select Insert New ModifyPartition:
    Name:  image.png
Views: 776
Size:  177.7 KB

    Repeat this to create a ModifyPartition setting for each partition you created in 3.13 and 3.14:
    Name:  image.png
Views: 785
Size:  130.7 KB

    3.16) GPT disk only: Set properties for each partition as shown below
    warning   Warning
    Only set a value for a setting when told so! Leave all other value fields empty.

    First the WinRE partition. Set it as follows:
    • Format = NTFS
    • Label = WinRE
    • Order = 1
    • PartitionID = 1
    • TypeID = DE94BBA4-06D1-4D40-A16A-BFD50179D6AC

    Click image for larger version. 

Name:	image.png 
Views:	13 
Size:	278.6 KB 
ID:	160974

    WinRE partition is the only one requiring specific TypeID. The ID must be exactly as shown above!

    Repeat the above three times, selecting a not yet modified ModifyPartition in Answer File pane and setting the properties for it. Below the properties for each of four GPT partitions:
    • ModifyPartition 1 (WinRE):
      • Format = NTFS
      • Label = WinRE
      • Order = 1
      • PartitionID = 1
      • TypeID = DE94BBA4-06D1-4D40-A16A-BFD50179D6AC

    • ModifyPartition 2 (EFI):
      • Format = FAT32
      • Label = System
      • Order = 2
      • PartitionID = 2

    • ModifyPartition 3 (MSR):
      • Order = 3
      • PartitionID = 3

    • ModifyPartition 4 (Windows):
      • Format = NTFS
      • Label = Windows
      • Letter = C
      • Order = 4
      • PartitionID = 4

    Remember: only modify properties to settings as told above, leaving other fields empty! Notice that small 16 MB MSR partition will not be formatted nor does it get a label.

    When done, you should have four CreatePartition components to create partitions, and four ModifyPartition components to configure them:
    Click image for larger version. 

Name:	image.png 
Views:	14 
Size:	233.0 KB 
ID:	160979

    3.17) MBR disk only: For MBR disk you only need two ModifyPartitions. Set their properties as shown below:
    • ModifyPartition 1 (System Reserved):
      • Active = True
      • Format = NTFS
      • Label = System
      • Order = 1
      • PartitionID = 1

    • ModifyPartition 2 (Windows):
      • Format = NTFS
      • Label = Windows
      • Letter = C
      • Order = 2
      • PartitionID = 2

    3.18) GPT disk only: Expand ImageInstall > OSImage component in Answer File pane, select InstallTo, set DiskID = 0 and PartitionID = 4 to tell Windows setup to install Windows on partition 4:
    Name:  image.png
Views: 783
Size:  84.7 KB

    MBR disk only: Expand ImageInstall > OSImage component in Answer File pane, select InstallTo, set DiskID = 0 and PartitionID = 2 to tell Windows setup to install Windows on partition 2

    3.19) Answer file has now all components and settings it needs. It also contains something not needed; before proceeding, delete all unused components (light blue icon) in Answer File pane under Setup main component, only leaving the three we've modified (dark blue icon: DiskConfiguration, ImageInstall, UserData).

    You can delete an unused component by selecting it and pressing DEL or right clicking it and selecting Delete:
    Name:  image.png
Views: 792
Size:  180.2 KB

    When done, your fully expanded Answer File pane should look like this:
    Name:  image.png
Views: 787
Size:  191.4 KB

    3.20) Validate answer file to check for possible errors (Tools > Validate Answer File):
    Click image for larger version. 

Name:	image.png 
Views:	17 
Size:	632.7 KB 
ID:	160991

    3.21) Save answer file as autounattend.xml in D:\ISO_Files folder (the folder where ISO content was copied to in step 2.2):
    Name:  image.png
Views: 784
Size:  125.3 KB

    3.22) The autounattend.xml answer file we created:

    Code:
    <?xml version="1.0" encoding="utf-8"?>
    <unattend xmlns="urn:schemas-microsoft-com:unattend">
        <settings pass="windowsPE">
            <component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <SetupUILanguage>
                    <UILanguage>en-GB</UILanguage>
                </SetupUILanguage>
                <InputLocale>040b:0000040b</InputLocale>
                <SystemLocale>en-GB</SystemLocale>
                <UILanguage>en-GB</UILanguage>
                <UILanguageFallback>en-US</UILanguageFallback>
                <UserLocale>en-GB</UserLocale>
            </component>
            <component name="Microsoft-Windows-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <DiskConfiguration>
                    <Disk wcm:action="add">
                        <CreatePartitions>
                            <CreatePartition wcm:action="add">
                                <Order>1</Order>
                                <Size>450</Size>
                                <Type>Primary</Type>
                            </CreatePartition>
                            <CreatePartition wcm:action="add">
                                <Extend>true</Extend>
                                <Order>4</Order>
                                <Type>Primary</Type>
                            </CreatePartition>
                            <CreatePartition wcm:action="add">
                                <Order>3</Order>
                                <Size>16</Size>
                                <Type>MSR</Type>
                            </CreatePartition>
                            <CreatePartition wcm:action="add">
                                <Order>2</Order>
                                <Size>100</Size>
                                <Type>EFI</Type>
                            </CreatePartition>
                        </CreatePartitions>
                        <ModifyPartitions>
                            <ModifyPartition wcm:action="add">
                                <Format>NTFS</Format>
                                <Label>WinRE</Label>
                                <Order>1</Order>
                                <PartitionID>1</PartitionID>
                                <TypeID>DE94BBA4-06D1-4D40-A16A-BFD50179D6AC</TypeID>
                            </ModifyPartition>
                            <ModifyPartition wcm:action="add">
                                <Format>FAT32</Format>
                                <Label>System</Label>
                                <Order>2</Order>
                                <PartitionID>2</PartitionID>
                            </ModifyPartition>
                            <ModifyPartition wcm:action="add">
                                <Format>NTFS</Format>
                                <Label>Windows</Label>
                                <Letter>C</Letter>
                                <Order>4</Order>
                                <PartitionID>4</PartitionID>
                            </ModifyPartition>
                            <ModifyPartition wcm:action="add">
                                <Order>3</Order>
                                <PartitionID>3</PartitionID>
                            </ModifyPartition>
                        </ModifyPartitions>
                        <DiskID>0</DiskID>
                        <WillWipeDisk>true</WillWipeDisk>
                    </Disk>
                </DiskConfiguration>
                <UserData>
                    <ProductKey>
                        <Key>VK7JG-NPHTM-C97JM-9MPGT-3V66T</Key>
                    </ProductKey>
                    <AcceptEula>true</AcceptEula>
                    <Organization>Ten Forums</Organization>
                </UserData>
                <ImageInstall>
                    <OSImage>
                        <InstallTo>
                            <DiskID>0</DiskID>
                            <PartitionID>4</PartitionID>
                        </InstallTo>
                    </OSImage>
                </ImageInstall>
            </component>
        </settings>
        <cpi:offlineImage cpi:source="catalog://agm-w10pro02/hyper-v/iso_files/sources/install_windows 10 pro.clg" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
    </unattend>
    Note   Note
    Notice that this answer file is for installing a 64 bit Windows 10 because the catalog file was based on a 64 bit install.wim file. If you want to use same answer file in installing 32 bit Windows, you must change all ProcessorArchitecture="amd64" references in answer file to ProcessorArchitecture="x86."




    Create media for automated unattended install of Windows 10 Step Four Create media for automated unattended install of Windows 10
     Create answer file for OOBE


    4.1) The second answer file is to take care of OOBE, to automate it bypassing region and keyboard selection and user account creation. To start, open Windows SIM and create a new answer file as you did in steps 2.3 through 2.5. Because the catalog file is already created, use it instead of install.wim to speed up process

    4.2) In step 3.4 you saw how to add components to answer file. Add required components now from Windows Image pane bottom left in Windows SIM to answer file as you did making the first answer file. First, add component International-Core to Pass 7 oobeSystem:
    Name:  image.png
Views: 745
Size:  446.0 KB

    In Windows Image pane, expand component Shell-Setup and add components as told below:
    - Add OEMInformation to Pass 4 Specialize
    Name:  image.png
Views: 747
Size:  256.2 KB

    - Add Shell-Setup > OOBE to Pass 7 oobeSystem
    - Add Shell-Setup > UserAccounts to Pass 7 oobeSystem

    Answer File pane should look like this after you have added necessary components:
    Name:  image.png
Views: 744
Size:  93.7 KB

    4.3) In Answer File pane, select Shell-Setup in pass 4 specialize. Set CopyProfile = true, OEMName as you wish, RegisteredOrganization as you wish, RegisteredOwner as you wish, and TimeZone if required (see explanation below screenshot). Leave all other property value fields empty:
    Click image for larger version. 

Name:	image.png 
Views:	17 
Size:	288.4 KB 
ID:	161029

    About TimeZone value: If no value given, Windows defaults to time zone according to language of the install media. US English Windows defaults to Pacific time, Finnish Windows to time in Finland, UK English Windows to UK time, Japanese Windows to time in Japan. In my case as I use UK English Windows which would default to UK time but I live in Germany, I want to set time zone accordingly to CET or as Windows understands it, to W. Europe Standard Time.

    In same way, if answer file and USB install media we are preparing would be used in East Coast USA, it would be a good idea to set time zone to EST / EDST setting TimeZone value Eastern Standard Time.

    Full list of valid time zone names: Microsoft Time Zone Index Values

    4.4) Select Shell-Setup > OEMInformation in Answer file pane, add Manufacturer, SupportHours, SupportPhone and SupportURL as you wish. If you want to add an OEM logo later (see step 5.1) when we prepare assets and install Windows on reference machine, add logo path and filename as C:\Windows\System32\oemlogo.bmp:
    Click image for larger version. 

Name:	image.png 
Views:	16 
Size:	237.9 KB 
ID:	161056

    Notice that OEMInformation is optional, not required. When added, if set the OEM logo image will be shown in Control Panel > System, and OEM info + link to given support URL in both Control Panel > System and Settings > System > About:
    Name:  image.png
Views: 770
Size:  16.7 KB

    4.5) Select International-Core in Answer File pane, set all values exactly as we did for the first answer file in step 3.5:
    Click image for larger version. 

Name:	image.png 
Views:	15 
Size:	192.6 KB 
ID:	161058

    4.6) Select Shell-Setup in Answer File pane in pass 7 oobeSystem, set the same RegisteredOrganization, RegisteredOwner and TimeZone as in step 4.3:

    4.7) Select OOBE in Answer File pane, set HideEULAPAge = True, set HideOEMRegistrationScreen = True, set HideOnlineAccountScreen = True, set HideWirelessSetupInOOBE = True, set ProtectYourPC = 1, set UnattendEnableRetailDemo = False:
    Click image for larger version. 

Name:	image.png 
Views:	8 
Size:	231.3 KB 
ID:	161685

    ProtectYourPC (read more) value can be 1, 2 or 3:
    • 1 = Recommended (default) level of protection
    • 2 = Only updates are installed.
    • 3 = Automatic protection is disabled.

    4.8) Expand UserAccounts, right click LocalAccounts, select Insert New LocalAccount:
    Name:  image.png
Views: 749
Size:  183.9 KB

    Fill in Description, DisplayName (as shown in login screen, Start etc.), Group (Administrators for admin accounts, Users for standard accounts), and Name (user profile folder name). I will first setup an admin account, I want all my machines to have a local admin account simply named as Admin:
    Click image for larger version. 

Name:	image.png 
Views:	17 
Size:	219.6 KB 
ID:	161050

    When done, I'll expand new account in Answer File pane and set password (optional):
    Click image for larger version. 

Name:	image.png 
Views:	12 
Size:	214.3 KB 
ID:	161051

    Don't worry; although shown in Windows SIM, when we save answer file the password will be encrypted, not shown. Be sure to remember the password if you set one here!

    I will repeat the above steps once because I also want to make a standard account for myself. Creating both accounts now they already exists on each machine on which I will install my custom Windows image:
    Click image for larger version. 

Name:	image.png 
Views:	12 
Size:	228.4 KB 
ID:	161053

    I will not set a password for this standard account. When not set, a user (myself in this case) can create a new password when signing in first time.

    4.9) Validating my answer file (see step 3.20) shows no errors:
    Click image for larger version. 

Name:	image.png 
Views:	14 
Size:	274.6 KB 
ID:	161096

    4.10) Create a new folder on technician machine to store assets for reference machine. I use folder Users\Kari\OneDrive\Assets to allow easy transfer using OneDrive. Save this answer file to your Assets folder as unattend.xml:
    Click image for larger version. 

Name:	image.png 
Views:	12 
Size:	153.4 KB 
ID:	161064

    If you will use a physical PC as reference machine, you can save your assets on a USB flash drive instead

    Close Windows SIM

    4.11) The unattend.xml answer file we created:
    Code:
    <?xml version="1.0" encoding="utf-8"?>
    <unattend xmlns="urn:schemas-microsoft-com:unattend">
        <settings pass="oobeSystem">
            <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <OOBE>
                    <HideEULAPage>true</HideEULAPage>
                    <HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
                    <HideOnlineAccountScreens>true</HideOnlineAccountScreens>
                    <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
                    <ProtectYourPC>1</ProtectYourPC>
                    <UnattendEnableRetailDemo>false</UnattendEnableRetailDemo>
                </OOBE>
                <UserAccounts>
                    <LocalAccounts>
                        <LocalAccount wcm:action="add">
                            <Password>
                                <Value>TQB5AFMAZQBjAHIAZQB0AFAAYQBzAHMAdwBvAHIAZABQAGEAcwBzAHcAbwByAGQA</Value>
                                <PlainText>false</PlainText>
                            </Password>
                            <Description>Main local admin account</Description>
                            <DisplayName>Admin</DisplayName>
                            <Group>Administrators</Group>
                            <Name>Admin</Name>
                        </LocalAccount>
                        <LocalAccount wcm:action="add">
                            <Description>Daily standard account</Description>
                            <DisplayName>Kari</DisplayName>
                            <Group>Users</Group>
                            <Name>Kari</Name>
                        </LocalAccount>
                    </LocalAccounts>
                </UserAccounts>
                <RegisteredOrganization>Ten Forums</RegisteredOrganization>
                <RegisteredOwner>Kari</RegisteredOwner>
                <TimeZone>W. Europe Standard Time</TimeZone>
            </component>
            <component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <InputLocale>040b:0000040b</InputLocale>
                <SystemLocale>en-GB</SystemLocale>
                <UILanguage>en-GB</UILanguage>
                <UILanguageFallback>en-US</UILanguageFallback>
                <UserLocale>en-GB</UserLocale>
            </component>
        </settings>
        <settings pass="specialize">
            <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <OEMInformation>
                    <Logo>C:\Windows\System32\oemlogo.bmp</Logo>
                    <Manufacturer>Ten Forums</Manufacturer>
                    <SupportHours>24/7</SupportHours>
                    <SupportPhone>+44 123 456 789</SupportPhone>
                    <SupportURL>https://www.tenforums.com</SupportURL>
                </OEMInformation>
                <CopyProfile>true</CopyProfile>
                <OEMName>Ten Forums</OEMName>
                <RegisteredOrganization>Ten Forums</RegisteredOrganization>
                <RegisteredOwner>Kari</RegisteredOwner>
                <TimeZone>W. Europe Standard time</TimeZone>
            </component>
        </settings>
        <cpi:offlineImage cpi:source="catalog://agm-w10pro02/hyper-v/iso_files/sources/install_windows 10 pro.clg" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
    </unattend>





    Create media for automated unattended install of Windows 10 Step Five Create media for automated unattended install of Windows 10
     Prepare assets


    5.1) Save optional OEM logo image to Assets folder. It must be a 120 * 120 pixels bitmap image (.bmp). Prepare and save custom Windows theme files to same folder, when we will customize reference machine in Audit Mode you can't use Personalize options to change colors and wallpaper but you can apply a theme pack file to do it for you.

    5.2) On technician machine, open Notepad, copy following code and paste in Notepad, save in Assets folder as RunOnce.bat:

    Code:
    echo Y | del %appdata%\microsoft\windows\recent\automaticdestinations\*
    del %0

    Do not run the batch file, it deletes itself! If you want to test it, make a copy and run it instead.

    This file will be copied to default user profile on reference machine, and from there to every user profile. It runs itself every time any user signs in first time clearing This PC, Quick Access and Recent files views, then deletes itself. Without it, some leftovers from reference machine's built-in administrator account would be shown in Quick Access.

    5.3) If you have installers for software you would like to include in your custom Windows image, save them, too, in Assets folder.

    5.4) In this example my Assets folder contains the unattend.xml answer file, an OEM logo image, RunOnce.bat from step 5.2, two themepack files and as an example of software installers, installer for VLC Player:
    Click image for larger version. 

Name:	image.png 
Views:	12 
Size:	188.1 KB 
ID:	161118





    Create media for automated unattended install of Windows 10 Step Six Create media for automated unattended install of Windows 10
     Install Windows 10 on reference machine


    6.1) Any PC or virtual machine can be used as reference machine. In this example I created a Generation 2 Hyper-V virtual machine with a 50 GB virtual hard disk
    warning   Warning
    Whatever PC or virtual machine you will use as reference machine, do not connect it to Internet when installing! Windows 10 Fall Creators Update version 1709 will in most cases cause Sysprep to fail when generalized (as we will do later) if machine was connected to network when installing.

    If Windows Setup finds Internet while installing, it will do so called app provisioning which will cause Sysprep to fail. This does not happen if you install without network connection and only connect network when booted to Audit Mode desktop as told in step 6.3.

    On physical machines, disconnect Ethernet cable before installing. On virtual machines, be sure network connection is disabled. In my case now, I selected Connection: Not connected in New Virtual Machine Wizard when creating my reference VM:
    Name:  image.png
Views: 747
Size:  132.7 KB

    6.2) If using a Hyper-V VM as reference machine, open its settings before booting and disable (unselect) automatic checkpoints (yellow highlight in screenshot). Be sure you are using Standard checkpoints:
    Name:  image.png
Views: 534
Size:  409.3 KB

    6.3) Install Windows 10 normally until OOBE starts and region settings screen is shown. Do not select anything, just press CTRL + SHIFT + F3 to restart to Audit Mode (press and hold down both CTRL and SHIFT keys, press F3, release all three keys):
    Click image for larger version. 

Name:	image.png 
Views:	13 
Size:	241.7 KB 
ID:	161120

    6.4) Windows will restart and sign you in to Audit Mode with built-in administrator account. Sysprep Prompt will be shown on screen. Click Cancel to close it:
    Name:  image.png
Views: 753
Size:  74.2 KB

    6.5) Connect reference machine to network





    Create media for automated unattended install of Windows 10 Step Seven Create media for automated unattended install of Windows 10
     Customize and capture Windows image

    Note   Note
    In this example case I am using OneDrive to transfer assets from technician machine to reference machine. You can of course transfer assets in any way you want to, for instance if your reference machine is a physical PC, you can save assets to a USB flash drive and use it for transfer.

    Network cannot be used, sharing being disabled in Audit Mode.

    7.1) If you saved the assets to OneDrive as I did, open Internet Explorer (WIN + R > type iexplore > press Enter, Edge can't be used in Audit Mode), go to onedrive.live.com and open the Assets folder:
    Click image for larger version. 

Name:	image.png 
Views:	13 
Size:	332.8 KB 
ID:	161123

    7.2) Save answer file unattend.xml in C:\Windows\System32\Sysprep folder:
    Click image for larger version. 

Name:	image.png 
Views:	12 
Size:	399.4 KB 
ID:	161124

    7.3) Save oemlogo.bmp in C:\Windows\System32 folder

    7.4) Save RunOnce.bat in C:\Users\Administrator\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Start-up folder
    Tip   Tip
    The AppData folder is hidden. A practical way to open it in Save as dialog is to type %appdata% in address field and press Enter. This opens the AppData\Roaming folder and you can now click yourself deeper to target folder:
    Name:  image.png
Views: 749
Size:  153.6 KB

    7.5) Theme files do not have to be saved, just open them to apply. If you want to install multiple themes to your custom image, open the one you want to be default theme for all user accounts last (you can't change themes in Audit Mode, just apply them):
    Click image for larger version. 

Name:	image.png 
Views:	12 
Size:	169.5 KB 
ID:	161127

    7.6) Run possible software installers without saving them:
    Click image for larger version. 

Name:	image.png 
Views:	13 
Size:	172.8 KB 
ID:	161128

    7.7) Create two new folders on root of C: drive, name them C:\Image and C:\Scratch. These folders will be needed when we capture the image
    Tip   Tip
    If you are using a Hyper-V VM as reference machine, create a checkpoint now. It allows you to return to this point in few seconds if something goes wrong with image capture or to make changes in image before it's captured.


    7.8) When done, press WIN + R to open Run prompt, type following command and press Enter:

    C:\Windows\System32\Sysprep\sysprep.exe /generalize /oobe

    Name:  image.png
Views: 747
Size:  77.5 KB

    7.9) Sysprep will run and generalize Windows image. When ready, Windows will shut down:
    Name:  image.png
Views: 750
Size:  68.4 KB

    7.10) Boot the reference machine from WinPE or Windows install media. In any case do not let it boot from hard disk!. In my case now, as I am using Generation 2 Hyper-V VM, I first changed the boot order in VM settings:
    Name:  image.png
Views: 750
Size:  178.1 KB
    Note   Note
    Hyper-V can be a bit tricky, you have to press a key to boot from install media or WinPE but the VM window opens slowly. If you miss the key press, reset VM as soon as it starts booting from VHD (Action menu > Reset) and try again.

    I repeat: do not let reference machine boot from HDD or in case of VM, from VHD!

    7.11) When booted from install media, press SHIFT + F10 to open Command Prompt. Type diskpart and press Enter (#1 in screenshot below), type list vol and press Enter (#2), type exit and press Enter (#3)

    Check drive letter for Windows partition (#4), all drives are listed under list vol command. In most cases it will be C: but occasionally, depending on hardware and connected disks, booting to WinPE or install media changes drive letters.

    Enter the following command and press Enter to capture Windows image (#5). Replace drive letter C: if necessary in /imagefile, /capturedir and /ScratchDir switches:

    Code:
    dism /capture-image /imagefile:C:\Image\install.wim /capturedir:C:\ /ScratchDir:C:\Scratch /name:"W10" /compress:maximum /checkintegrity /verify /bootable

    Dism will capture the image. Wait until it's done (#6), restart reference machine and let it boot normally from hard disk. Notice that boot will take quite some time because reference machine goes through automated OOBE.
    Click image for larger version. 

Name:	image.png 
Views:	11 
Size:	443.2 KB 
ID:	161134

    7.12) When reference machine has booted to desktop, sign in to your administrator account using password you set in answer file in step 4.8

    7.13) On technician machine, delete ISO_Files\Sources\install.wim file

    7.14) When reference machine has booted to desktop, copy newly captured Windows image (install.wim file) from C:\Image folder to technician machine to ISO_Files\Sources folder, same folder from where you deleted the original install.wim in previous step. In my case now I shared ISO_FIles folder on technician machine and mapped it on reference machine, copying new install.wim directly to target folder:
    Name:  image.png
Views: 747
Size:  158.0 KB

    You can of course copy the file in any way you prefer. Shut down reference machine when file has been copied





    Create media for automated unattended install of Windows 10 Step Eight Create media for automated unattended install of Windows 10
     Create USB install media


    8.1) The ISO_Files folder on technician machine now contains everything needed to create a "hands free" ISO:
    • Windows 10 install files copied from original ISO (step 2.2)
    • Original install.wim in Sources folder replaced with custom one (step 7.14)
    • Custom autounattend.xml answer file to take care of Windows setup (step 3.21)

    8.2) Create custom USB flash drive from ISO_Files folder by running PowerShell script as told in following tutorial: PowerShell Scripting - Create USB Install Media for Windows 10 Installation Upgrade Tutorials

    Alternatively, you can make an ISO image as told in Part Five in following tutorial, the tool used (Deployment and Imaging Tools Environment) was installed on your technician machine together with Windows SIM in step 1.2 and you do not have to download it again: Create Windows 10 ISO image from Existing Installation Installation Upgrade Tutorials

    When you have created new ISO, use your preferred tool / method to create USB or DVD install media

    That's it geeks! Happy computing

    Kari
  1.    3 Weeks Ago #1
    Join Date : Feb 2015
    3rd Rock
    Posts : 729
    WinX Pro x64 IP v14986

    Very well written. Good job, Kari!
      My ComputersSystem Spec
  2.    3 Weeks Ago #2
    Join Date : Nov 2013
    Chicagoland
    Posts : 33,893
    Dual boot Windows 10 FCU Pro x 64 & Insider 10 Pro

    Another excellent one, Kari! Well done!

    I was wondering what you've been working on. Lots of work went into this one I see.
      My ComputersSystem Spec
  3.    3 Weeks Ago #3
    Join Date : Oct 2013
    A Finnish expat in Germany
    Posts : 12,971
    Windows 10 Pro
    Thread Starter

    Quote Originally Posted by johngalt View Post
    Very well written. Good job, Kari!
    Thanks!


    Quote Originally Posted by HippsieGypsie View Post
    Another excellent one, Kari! Well done!

    I was wondering what you've been working on. Lots of work went into this one I see.
    Honestly, it took closer to 30 hours to write, excluding test installs but including about six hours to try to find what caused this error when I thought I was ready and tested the install media:
    Name:  image.png
Views: 694
Size:  60.4 KB

    That error message when you get it after running Sysprep means installation has gone beyond salvation, you must start from scratch. At the end I found out, as so often before, that the error was due a stupid newbie mistake I had done.

    In addition, it took a bottle and a half cheap supermarket whisky, two frozen microwave pizzas and about quarter of kilo dark roasted espresso.

    Kari
      My ComputerSystem Spec
  4.    3 Weeks Ago #4
    Join Date : Nov 2013
    Chicagoland
    Posts : 33,893
    Dual boot Windows 10 FCU Pro x 64 & Insider 10 Pro

    Quote Originally Posted by Kari View Post
    Honestly, it took closer to 30 hours to write, excluding test installs but including about six hours to try to find what caused this error when I thought I was ready and tested the install media:
    I got a glimpse of the hours you must spend after studying your basics in PS scripting, your dual-boot tutorial, then installs, and now this. I can somewhat relate, but in a much simpler fashion pounding on the keyboard doing business. Alt/Tabbing through multiple Excel & Word templates, multiple tabs in IE for material costs & other searches, estimating program, PDF viewer for blueprints, contacts app, automated telephone communications with a headset, bookkeeping/payroll, blah ba blah. Got to be somewhat routine, but then something changes or a new OS or program comes along to (so often) perform/navigate with/through things better and quicker. Then quadruple-checking proposals and contracts so to make profit instead of loosing my arse.

    That error message when you get it after running Sysprep means installation has gone beyond salvation, you must start from scratch. At the end I found out, as so often before, that the error was due a stupid newbie mistake I had done.
    Isn't that the truth! So often an overlooked simple mistake.

    In addition, it took a bottle and a half cheap supermarket whisky, two frozen microwave pizzas and about quarter of kilo dark roasted espresso.
    LOL! Yes, there are expenses, but I can tell you're in your peaceful solitude in creating what you enjoy as you often say. I believe man was created to create. Now up in age I've learned that the only satisfaction we get out of life is working to create. We may think it's other means, but that's the bottom line.

    What's your next project?

    BTW, I'm having problems with my dual boot. None of you doings, of course. Things are wacky in 17017 and had a BSOD about an hour ago in my FCU here. I'll post in my redo thread as soon I collect more info.
      My ComputersSystem Spec
  5.    3 Weeks Ago #5
    Join Date : Jan 2017
    Turku
    Posts : 1,781
    Windows 10 Pro IP Build 16299.19 (Branch: RS3 Release)

    WOW! This is one really comprehensive tutorial! This is a really great help for anyone who need a very specialized automated setup image created.

    Thanks a lot!
      My ComputersSystem Spec
  6.    3 Weeks Ago #6
    Join Date : Oct 2013
    A Finnish expat in Germany
    Posts : 12,971
    Windows 10 Pro
    Thread Starter

    Quote Originally Posted by slicendice View Post
    WOW! This is one really comprehensive tutorial! This is a really great help for anyone who need a very specialized automated setup image created.

    Thanks a lot!
    Thanks Slice

    I like to install using unattended media. It's so easy, you just plug in the USB, start the computer, go away to have a break and some 20 minutes later come back to PC to find fully installed Windows. As a bonus, it's your custom Windows with custom theme, user accounts already created, your favourite software installed and so on.

    This without a single key press or mouse click, of course excluding the one key press to tell PC to boot from USB (or DVD, this works the same way using DVD than USB).
      My ComputerSystem Spec
  7.    3 Weeks Ago #7
    Join Date : Oct 2013
    A Finnish expat in Germany
    Posts : 12,971
    Windows 10 Pro
    Thread Starter

    Quote Originally Posted by HippsieGypsie View Post
    What's your next project?
    This one:

    Geeks, when you have created your install media, keep it up to date:

      My ComputerSystem Spec
  8.    2 Weeks Ago #8
    Join Date : Nov 2017
    Posts : 3
    Windows 10

    Thank you for this amazing tutorial! I just created my first image and tested it. Unfortunately the install stopped when it got to the wireless configuration... Cortana started talking and all, which is quite annoying, and really my main motivation for making this image. I think I need HideWirelessSetupInOOB set to True, but this wasn't set in your tutorial. Is there any way to modify the unattend.xml after imaging? Or will I have to start from scratch? Also, I had to run windows update and restart about three times to get all the drivers working properly, however there was an issue with Intel(R) Smart Sound Technology (Intel(R) SST) OED, listed under System devices in Device Manager. I had to uninstall it and reinstall to fix this. I used hyper v to get the image so it would be hardware neutral... is it common to still have these types of issues?
      My ComputerSystem Spec
  9.    2 Weeks Ago #9
    Join Date : Oct 2013
    A Finnish expat in Germany
    Posts : 12,971
    Windows 10 Pro
    Thread Starter

    Hi Falconer, welcome to Ten Forums!


    Quote Originally Posted by falconer View Post
    I think I need HideWirelessSetupInOOB set to True, but this wasn't set in your tutorial.
    My apologies, I simply forgot that from original answer file and tutorial. I've now edited step 4.7 to include it and replaced screenshot accordingly.

    I have no good excuse. I just forgot it.


    Quote Originally Posted by falconer View Post
    Is there any way to modify the unattend.xml after imaging? Or will I have to start from scratch?
    You need to start from scratch in reference machine. Thinking of that, I edited tutorial adding new step:

    Quote Originally Posted by From tutorial
    6.2) If using a Hyper-V VM as reference machine, open its settings before booting and disable (unselect) automatic checkpoints (yellow highlight in screenshot). Be sure you are using Standard checkpoints:
    Name:  image.png
Views: 529
Size:  409.3 KB

    I added this tip in step 7.7, to be done just before you run Sysprep:
    Tip   Tip
    If you are using a Hyper-V VM as reference machine, create a checkpoint now. It allows you to return to this point in few seconds if something goes wrong with image capture or to make changes in image before it's captured.


    Quote Originally Posted by falconer View Post
    Also, I had to run windows update and restart about three times to get all the drivers working properly, however there was an issue with Intel(R) Smart Sound Technology (Intel(R) SST) OED, listed under System devices in Device Manager. I had to uninstall it and reinstall to fix this. I used hyper v to get the image so it would be hardware neutral... is it common to still have these types of issues?
    A suggestion:

    You could "inject" drivers to your install media, making it specific for that PC. Tutorial: DISM - Add or Remove Drivers on an Offline Image

    Keep a copy of your custom hardware independent install.wim file, only apply drivers for a specific PC to install media you will use for that PC. If the PC is already running Windows, all devices and drivers working, and you want to reinstall, check the note in step 2.2 in above mentioned tutorial. It shows how to capture drivers from existing Windows installation. Applying them to image you have all devices working straight after setup.

    Notice that this might make your install.wim file to be bigger than 4GB which in its turn might make it impossible to use a standard FAT32 formatted USB flash drive. In that case see end of this quite long post of mine in another thread for a workaround using Rufus to create USB media: How to move Windows 10 from OLD desktop to NEW laptop - Windows 10 Forums

    To avoid need to run Windows Update after Windows has been installed, you could also apply Windows updates to your custom install media. Tutorial: PowerShell Scripting - Update Windows 10 USB install media

    Kari
      My ComputerSystem Spec

 
Page 1 of 4 123 ... LastLast


Similar Threads
Tutorial Category
Installation & Upgrade PowerShell Scripting - Create USB Install Media for Windows 10
The way Windows operating system is delivered and installed has changed quite a lot from days when Windows 3.0 was delivered on 6 floppy disks. To install, you booted PC from floppy 1, which in its turn asked you to eject it and insert floppy 2 to...
Tutorials
Solved unattended TRUSTEER RAPPORT loading and install, suspicious activity
yesterday, 4 august 0400 south african time , my computer must have loaded trusteer rapport , made a system restore point before running it and my system time zone was set to cuiaba, brazil . i tried to go back to a pre trusteer rapport system...
AntiVirus, Firewalls and System Security
Is an unattended upgrade possible?
Hi, We've got hundreds of computers running Win 7 Pro that we'd like to upgrade to Windows 10. Is there a way of running the setup with an answer file? Anywhere I can get example answer files from? I don't really care what the settings...
Installation and Upgrade
Issue with "CopyProfile" option in Unattended Install
I have been creating generalized images for deployment in an enterprise scenario. In order to do so, I've installed Windows 10, booted into audit mode from the Welcome Screen, then customized Windows. After this, I can run sysprep with an unattend...
General Support
Another way of unattended PXE installation -- and it works :-)
I had a run on the preview 10240 by unattended installation. what I wanted to see is if I could create a golden image on one very old PC (HP Elitebook 6930p), sysprep it and afterwards apply that image by autoupdating the drivers to my Dell...
Installation and Upgrade
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 10:04.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums