Blog Posts tagged with Systems Deployment

Ask a question

Sysprep Creator Wizard

Scripting Ninjas is happy to announce Sysprep Creator

Download Link: https://support.quest.com/download-install-detail/6085104

Note: KACE Support Credentials are required.

Sysprep Creator is designed to assist with the creation of unattend.xml answer files to be leveraged by Windows 7, Windows 8, Windows 8.1, and Windows 10.


      1. Launch Sysprep Creator
      2. You will be prompted with a UI, choose the OS and Architecture to build an unattend.xml.
      3. Another UI with a total of 8 tabs appears with settings, which will need to be populated.
      4. Choose where to save the unattend.xml and if selected in step 2 the sysprep executor.
      5. Copy the unattend.xml (and sysprep_executor.exe if selected) to the machine in which you wish to sysprep.

      Release Notes:
      Due to Windows permissions, if the unattend.xml file is located at the root of the “System Drive”,
      sysprep_executor.exe will not be able to cleanup/delete it. [02/13/2018]
      -Automatically disable Windows Defender
      -added a few more provisioned apps (BubbleSaga, DisneyMagicKingdoms)
      -fixed issue with upgrade version
      -removed MiracastView from provisioned apps as it could not be removed [01/03/2018]
      -Add additional provisioned apps to be removed prior to sysprep (ESMCS-360)
      -tiledatamodelsvc setting has changed in Windows 10 1709 update (ESMCS-259)
      -beginning with Windows 10, version 1607, sysprep can be used to prepare an image that has been upgraded (ESMCS-358)
      -cancelling dialog on saving unattend quits the application (ESMCS-356) [03/22/2017]

      -sysprep creator no longer uses templates, each XML file is built from scratch
      -added Czech Republic to Location and language choices (ESMCS-229)
      -added countless Time Zones
      -added the ability to set taskbar links based on https://technet.microsoft.com/en-us/library/ff715544.aspx
      -added the ability to set OEM Information based on https://technet.microsoft.com/en-us/library/ff716332.aspx
      -added some OOBE options
      -added IE options, based on https://technet.microsoft.com/en-us/library/ff715726.aspx
      -added the ability to set a predetermined KMS key based on https://technet.microsoft.com/en-us/library/jj612867.aspx
      -added checking or Candy Crush, Twitter, AdobePhotoshopExpress, EclipseManager, ActiproSoftwareLLC, PandoraMediaInc, MicrosoftPowerBIForWindows, Microsoft.NetworkSpeedTest, Microsoft.Office.Sway, RoyalRevolt2, Minecraft, Facebook, ParadiseBay
       with the ability to remove them with executor prior to sysprepping (ESMCS-246)
      -fixed an issue with Spanish locale not being put in correctly (ESMCS-257)
      -moved installer to service.kace.com to avoid third paty site (ESMCS-261)
      -added check for Executor to check if tiledatamodelsvc running, if so, we set the service to disabled, and require a reboot. Upon running executor again, the service will be set to automatic, but not started
      -added ability to change Control Panel View and Icon Size
      -removed Network setting when building Windows 10 unattend as it is depricated
      -added ability to disable consumer feature from Windows 10 Enterprise
      -updated to check for KACE 7.0 agent
      -rebranded to Quest [02/03/2016]
      ****This update will need to be downloaded manually from http://www.scriptingninjas.com/scripts/sysprep_creator/sysprep_creator_installer.exe
      or click download and when it is completed, select 'No' for installing, this will copy the new installer to the desktop
      -fixed issue with update mechanism
      -fixed an issue in which a Windows 8 unattend was being produced instead of Windows 7 unattend. [01/16/2016]

      Windows 10 support
      Enlarged the UI
      Made UI look more like the K2000
      Added a warning if an unattend.xml file already exists in the location chosen to save
      Added a log file to %systemdrive%\ProgramData\Dell\KACE\Logs
      Sysprep Executor empties the recyle bin and cleans up previous logs/files and archives them in %systemdrive%\ProgramData\Dell\KACE\Logs
      Sysprep Executor Checklist - A checklist designed to make sure that System Imaging Best Practices are being followed according to
                      -The device should not be joined to a domain
                      -WMP Service should be disabled (query of WMPNetworkSvc Service)
                      -The Dell | KACE agent should not be installed
                      -No drive emulation application should exit on the device (Virtual Clonedrive, DAEMON Tools, Magic ISO)
                      -No antivirus can be detected
                              Checked via WMI
                      -VMWare Tools should not be installed
                      -Bitlocker can not be enabled
                              Checked via WMI, if protection status is set to 0 on they %systemdrive%
                      -No reboots can be pending
                              HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations
                      -Rearm count has to be higher than 1
                              -See https://social.technet.microsoft.com/Forums/windows/en-US/f8c7833b-58f0-43b4-a93a-b1a1689ecaf5/created-windows-7-image-with-expired-sysprep-rearm-count?forum=w7itproinstall and http://blogs.technet.com/b/askcore/archive/2011/05/11/sysprep-skiprearm-and-image-build-best-practices.aspx for more information
                      -Valid source media must be detected (Not OEM or Retail)
                      -Machine should not be upgraded from a previous version of Windows
      If the machine has been upgraded, sysprep executor can only quit, it will not sysprep
      If the device has bitlocker is enabled, or antivirus is installed, the user must quit Executor and fix these issues manually
      If none of the above are an issue, but WMP Service is running, VMWare Tools is installed, or drive emulation software is installed, a fix it button will be active.
      If the Fix it button is used, the uninstaller will launch, but will require some interaction from the user to complete the uninstall. [03/06/2015]
      -Changed installer so that it only installs where the script is run.
      -Changed sysprep_executor shutdown/reboot options to radio buttons
      -Changed sysprep_executor so the the unattend file is moved to \windows\system32\sysprep directory.
      -Changed sysprep_executor to have the sysprep commandline run the shutdown or reboot command.
      -Changed sysprep_executor so that the GUI goes away when sysprep run.
      -fixed issue where sysprep_executor was not deleting itself.
      -fixed issue where autologon would not set correctly if anything other than 0-9 was selected.
      -added the option to delete sysprep_creator after completion so that it didn't have to remain on image.
      -New Installer with Check for Updates Feature
      -New Sysprep Executor Option
      -Windows 8 Support
      -Field Checking
      -Persistent Plug and Play Device Option
      -Windows Activation Option
      -Activation Rearm Option
      -Sysprep Unattend Cleanup Option
      Bug Fixes:
      Fixed Join Domain double quote issue
      Fixed International Time Zone issue

      Please report bugs/feature request to corey@scriptingninjas.com and kent@scriptingninjas.com

      View comments (40)

      Upgrading to Windows 10

      *NOTE - If these tasks were downloaded and imported into your K2000 prior to September 4, 2015 please contact support.  We found an issue with the import of the task which we will need to fix on the backend.  The download available now does not have this issue.  We apologize for the inconvenience.

      Many users will want to upgrade their current operating system to Windows 10, retaining all their user data and applications.  In order to upgrade to Windows 10, one must utilize the same edition of Windows 10 as the older version of Windows.  For example, if running Windows 7 Professional or Ultimate, Windows 10 Professional must be used.  If running Windows 8 Enterprise then Windows 10 Enterprise must be used to upgrade the system.


      An upgrade to Windows 10 must take place within the operating system itself and cannot take place in KBE.  There are two methods to upgrading to Windows 10 using KACE appliances. The first method would be to create a K1000 script as outlined on an ITNinja blog post. The second method, which is detailed below, can be done from the K2000 with the provided tasks.
      *Note, to download the tasks, it is necessary to be a member of the K2000 community.


      First, use the current version of Media Manager to upload your Windows 10 source media, 3.7 SP2 supports Windows 10 so make sure you are using that version of Media Manager for the upload..  Once this is completed, the source media ID must be obtained from Library | Source Media.


      Upload the attached .PKG files, which will create a Windows 10 K-Image for each architecture along with a few tasks.  Preinstall tasks such as partitioning and formatting should not be added to the image (or it will no longer be an upgrade).  The image that is being applied to the machine has no files, so nothing is overwritten.  The midlevel task is a template that should be duplicated and edited.  This midlevel task copies down the Windows 10 source media, enables autologon to the workstation and writes a setupcomplete.cmd file that gets applied at the end of the upgrade process.


      The first few lines of the midlevel task contain variables that need to be changed by the user.

      strUser should be an admin username

      strPassword is the password of the above user

      strDomain is the name of the domain, or leave as localhost if leveraging a local user

      win10_source_cd_id is the ID number of the uploaded Windows 10 source media


      The post install task, “Upgrade Windows 10” does not have to be modified by default.  However, the last command line switch is ‘/dynamicupdates disable’.

      When Windows 10 setup begins, it will attempt to download available updates by default.  The command line switch above disables this behavior.  If you prefer for the updates to be downloaded immediately, just delete this switch from the command line.  For more commandline switches see http://winaero.com/blog/windows-10-setup-exe-command-line-switches/

      Back to K2000 Deployment Workbench

      View comments (39)

      Sysprep - Using the sysprep creator tool

      I wanted to post a quick tutorial for how we use the Sysprep Creator tool.
      Please be sure to select "How useful this was to you" at the top of the page.

      Launch Sysprep_Creator_x64.exe

      • Choose your version of Windows (We are not running the newest version)

      • Under Completion Action - choose your option.
        The executor is what launches the sysprep process and points to the unattend.xml

      • If you are running sysprep_Creator on the machine you are sysprepping, choose the "Delete Sysprep Creator at completion"

      • Click "Next"

      Step 1

      • Type in a name (we use a . In this field

      • Type in your organization name

      • Choose your time Zone

      • Click on the Step 2

      Step 2

      • Type in the username and password of a local administrator or one that you would like to have created

      • Choose how many times the computer can/will autologin after necessary reboots

      • If you are using the current profile on the system you are sysprepping as a template for all future users who login, you will want to be logged in as that account prior to sysprep and choose the "Copy profile of the user running sysprep"

      • Click Step 3 Tab

      Step 3

      • We do not make any changes on this screen since we join the domain as a post install task
      • Click Step 4 Tab

      Step 4

      • We use a KMS server so we want to check off that option and type in the KMS server FQDN

      • "Reset activation grace-period time" If your image is older and the timer only has a few days left, it can't hurt to check off this box

      • Click Create and choose the location you want to save the file(s)
        We save theses in two places.  A local network share and also place them inside the Samba Share of the K2000 under Drivers_postinstall\sysprep files so we can easily get to it from any machine.

      Sysprep execution

      • Login to the account you configured the default profile you want all users to use.

      • Copy the Unattend.xml to c:\Windows\System32\sysprep

      • Copy the sysprep_executor_x64.exe to the desktop

      • Double click on the executor file on your desktop.

        • Accept the UAC prompt

        • Choose Shutdown - You don't want it to reboot before you capture the image

        • Click browse and navigate to c:\windows\system32\sysprep\unattend.xml

        • Choose Open

        • When you are ready, click "Start Sysprep" and let it finish.  The system will Shutdown once complete 


          NOTE: I've noticed that I need to copy both files above to the desktop before trying to copy the unattend.sml to the sysprep directory.

          If you have any questions, feel free to let me know. If you have any additional input for me to add (or if I am completely wrong) I'd be happy to edit this post

      View comments (2)

      Deploying WinXP SP2 with RIS using Windows 2000 Server

      This video shows how you may use RIS to deploy Windows XP SP2 from a Windows 2000 server in fully unattended mode. From RIS installation and configuration, to slipstreaming Windows XP SP2, customizing the SIF (unattended answer file) and even including additional scripts and source files to automate the installation of additional software following the installation of Windows XP.

      Running Time: 25:54


      Detailed step-by-step walk through goes over creating a slipstreamed source (XP SP2), installing RIS (covering the nuances associated with handling XP on a Windows 2000 RIS server), creating a post installation script, etc.


      How to customize RIS by adding to the files installed using $OEM$ and automating this installation by customizing the answer file (SIF) using Setup Manager and even some changes outside this Wizard using notepad (to to have it automatically activate XP, include the product key, etc.).

      Be the first to comment

      Working with ImageX and Windows PE

      This video walks the viewer through installing Windows Server Codename Longhorn and creating a bootable Windows PE disk with ImageX included. It then shows how to use the Windows PE image to boot up and create a file based image (WIM) of the Longhorn Server and finally, how to apply that image to a new machine.


      Running Time: 18:50



      The image creation process is covered through generalization with sysprep; next the system is booted to Windows PE where a WIM (file based image) of the computer is taken using ImageX and saved to a network location .


      Finally, a new system is created and prepared with the diskpart utility within Windows PE where ImageX is again used-- this time to apply the previously taken image of Longhorn server to demonstrate its use. It should be noted that all of these steps also pertain to Windows Vista

      Be the first to comment
      Showing 1 - 5 of 195 results

      Top Contributors

      Talk About Virtualization