866-754-3592

UIU Classic User Guide




Chapter 1 - UIU Features and Requirements

Universal Imaging Utility Functionality

The concept behind the UIU is to create a single Microsoft Windows 10, 8.1, 7 or XP image file that can be successfully deployed across any hardware platform. By following the directions included you will be able to create an image of a single PC and deploy it to nearly any other PC, desktop or laptop, regardless of hardware components, without incident, allowing for an easily-maintainable image and a highly supportable PC environment.

Universal Imaging Utility Requirements

  • An ACPI Compliant PC
  • Windows 7 or 8.1 or 10 (Professional or Enterprise; 32-bit or 64-bit)  OR
  • Windows XP (Professional or Tablet) SP2 or SP3 – 32-bit
  • Microsoft Windows Volume License Key
  • 30 GB of free hard drive space
  • DVD-ROM Drive
  • Disk imaging application (Symantec Ghost, Altiris, Acronis, etc.)
  • Internet connectivity required for UIU updates - Licensed users only
  • Internet connectivity required for UIU Discovery Tool  (UIUDT) Analysis
  • All hardware must meet MS requirements for applicable OS

Universal Imaging Utility Limitations

  • Windows 2000 operating systems are not supported by the UIU v4 product due to limitations with MS .Net Framework requirements.
  • The UIU is not designed to function with Windows 2000 Server, Windows 2003/2008 or 2012 Server.  (No technical support.)
  • The UIU is not designed to function with 64-bit XP or Vista versions of MS operating systems.
  • The UIU is not designed to function with RAID based systems.  (No technical support.)
  • A UIU image created will not be compatible with older, non-ACPI compliant (Standard PC) systems.
  • Deployment from a SCSI based system to an IDE/ATA/PATA/SATA system may fail. Support only for migrating to non-RAID SCSI from an IDE/ATA/PATA/SATA system.

Definitions

Base PC or Base machine:
A selected hardware platform that meets UIU Requirements, on which an installation of a supported Windows OS will be established.

Base Image:
A machine-specific image captured from the Base PC containing only the supported OS and optional Microsoft updates. This image is established prior to the execution of UIU or Sysprep.

Master Image:
A machine-specific image captured from the Base PC containing the supported OS and optional Microsoft OS updates (i.e. your Base Image), plus environment-specific OS configurations and organization-specific applications with optional application updates. This image is established prior to the execution of UIU or Sysprep.  

It is possible for your Base Image to be synonymous with your Master Image in the case where no environment-specific OS configurations, organization-specific applications or optional application updates have been implemented after your Base Image was captured.

UIU Image or UIU-prepared Image:
A Universal or non-machine-specific image (derived from a Master Image) which has been captured from the Base PC after the UIU has been successfully executed and Sysprep has been invoked in a supported manner (either through the UIU or manually in conjunction with particular UIU switches).


uiu logo user guide


Chapter 2 - Creating a Universal Image

Creating a Universal Image requires following 3 steps:
Step 1: Prepare a Base machine - Windows XP, Windows 7 or Windows 8.1 or Windows 10
Step 2: Retrieve UIU Program and Driver Updates
Step 3: Install the UIU and Create a Universal Image

Step 1: Prepare a Base machine

As a general rule, a motherboard with a BIOS date after January 1999 will be ACPI compliant and those with a BIOS date after January 2004 will be ACPI Uniprocessor compliant. Please consult the documentation below, your manufacturer’s documentation, or refer to Microsoft Knowledge Base Article number 216573, for an explanation of how Windows determines ACPI compliance.

To determine the type of power management used on your Master PC (XP only), open the Device Manager and expand the Computer branch.

Non-ACPI systems will display Standard PC and are not supported.

Base machine Setup Requirements

  • On a blank hard drive, install a supported version of Windows XP, Windows 7, 8.1 or 10 from a Volume License CD. OEM and single installation CDs should not be used as they may be hardware or manufacturer specific and may require individual activation.

    For more information on Windows 7 (and newer) Volume License methods, please refer Microsoft KB Article 929712 which may be found at the following link:
    Microsoft Volume Activation information

    Also, consult the following Microsoft Volume Licensing guide:
    Microsoft Volume Licensing Information

  • Do not install drivers or driver updates from your PC manufacturer or Microsoft. CANCEL any “New Hardware Found” pop-up references unless absolutely necessary, (e.g. Network Card drivers.) Missing drivers will not cause problems for the UIU.

    Be sure to capture a "Base Image" of this Base Machine as a best practice. This is a requirement for UIU Support.
  • Set the driver signing policy to IGNORE in System Properties – Hardware - Driver Signing (only applies to Windows XP). Although Big Bang makes every effort to only include signed drivers, occasional necessary drivers, (primarily SCSI and SATA) are unsigned. Selecting IGNORE will prevent pop-ups from pausing the execution of the UIU. Windows 7 & Vista unsigned drivers are addressed automatically dependent upon the customer’s decision on whether or not to allow their use, (e.g. FDCC requirements)

  • Set the “Use visual styles on windows and buttons” to ON (check the box) in System Properties – Advanced - Performance Settings - Visual Effects.

  • Prepare your Base machine with Master Image configurations; default system settings, default user settings, administrator passwords, etc., that are required for your environment.

  • After all setup for the Base PC – (Master Image configuration) is completed – machine settings, default user settings, etc., restart the PC and login as the local Administrator one last time to verify.

  • If PC manufacturer drivers were installed, open Add/Remove Programs, and remove any hardware related applications. For example, SoundMax sound card installations should be uninstalled. After reboot, CANCEL any new hardware wizard windows that open.


  • NOTE: A "Master Image" can be used for ongoing maintenance in conjunction with the UIU. However, a captured "Base Image" IS REQUIRED FOR SUPPORT.


    Known Windows Issue: Microsoft Kernel-mode driver framework Version 1.11 Update for Windows 7

    Symptoms:
    In Windows 7, select drivers that require an updated kernel-mode framework will not install and will potentially prevent successful image deployment.

    Resolution:
    Update the Microsoft Kernel-Mode Framework to version 1.11. It is also our recommendation that the User-Mode Driver Framework version also be updated to version 1.11 for Windows 7 deployments.
    Kernel-Mode Driver Framework version 1.11 update for Windows 7, and Windows Server 2008 R2

    User-Mode Driver Framework version 1.11 update for Windows 7, and Windows Server 2008 R2




    Base machine Recommendations:

    The following recommendations are best practices that will improve the success of a UIU image and the associated improvement in productivity with respect to imaging in any organization.

  • Build your UIU image on a machine that is two to three years old. The goal is to set up Windows on a machine where most of the drivers are automatically installed by Windows (inbox drivers only) without additional drivers that are associated with specific hardware components, particularly those that install/invoke software applications. If an older machine is not available, you can still build a UIU image using nearly any PC system.

  • If deploying to laptops, consider turning off the Num-Lock key in Windows.

  • Test, disable, or do not fully install remote viewing software applications such as Symantec pcAnywhere, Remotely Anywhere, etc. These applications often times have a mirror video driver that must be installed after the image is on the new hardware in order to associate to the correct video card. Installing it as part of the Master Image may cause the remote control applications to fail.

  • Execute the MIMIC (Master Image Machine Integrity Check) utility from the UIU Main menu. Review the findings and decide what actions are necessary based on your organization’s business processes.

  • UIU v4.x requires Microsoft .NET Framework Version 3.5 SP1 installed on the base machine. UIU v4.x includes a redistributable MS .Net 3.5 SP1 Framework and will install it when the UIU.exe is first executed if the necessary framework does not already exist.

  • Windows Installer 3.1 or later may be required to install the .Net framework and UIU v4.x will install this if necessary.

  • Windows 7 & newer have the .Net Framework integrated and therefore does not necessitate a separate installation of this component although updates to the version of .Net may be necessary.

  • NOTE: To manually install MS .NET Framework Version 3.5 SP1, go to Microsoft’s web site to download the software or install it as a matter of course in executing Microsoft OS Updates.



Step 2: Retrieve UIU Program and Driver Updates

Login as the local administrator and launch the UIU* from the desired location, (DVD, USB drive, network drive, etc.) to begin the UIU installation process. After the UIU tests for an Internet connection, review the “Big Bang LLC End-User and Evaluation License Agreement” (EULA).

EULA and UIU License Key


uiu license key


* You must be Logged-in as the Local Administrator when launching UIU.exe (not just a User with administrative rights)

Enter your UIU License Key, and click on “Next”. The key will be automatically validated as it is entered. Note: your valid UIUv3 License Key will be accepted and does not need to be replaced with a UIUv4 key.

Proxy Services

If your organization employs a proxy service for Internet access, Connection Settings will allow you to enter the requisite credentials and re-test for Internet connectivity.

Proxy Service Settings


uiu proxy


Click “OK” to continue once Internet access has been assessed.

Support Notice

Please note the Support Notice pop-up window, reminding you to capture a Base Image of your Base PC, prior to UIU preparation. This is required for UIU Support and will ensure that you have a consistent Base Configuration to return to for troubleshooting.
NOTE: Although a Master Image will be necessary for ongoing maintenance with the UIU, a Base Image IS REQUIRED FOR SUPPORT.

Updater Application Update

The UIU Updater application will automatically detect an available new version and download/restart the update process.

Program and Driver Updates

If you have Internet connectivity, the UIU will automatically check for program and driver updates unless you checked the “Skip Updates” box on the EULA and License Key screen.
You will first be asked to select a location to which your updated UIU will be saved. If you elect to save these files to your Base PC (locally) and do not wish the UIU program to be included in your UIU Image, please move the entire UIU directory structure to a removable media device or network drive.

Select Save Location


uiu save configuration path


You will then be notified about updates to the UIU Program and Driver Database and be given the option to download the Driver Updates by selecting “Next”. You may select all operating systems or only ones pertinent to your organization or only the one OS for the current run of the UIU. You may choose to not employ Driver Updates at this point by selecting “Skip Updates & Run UIU” button.

UIU Updates


uiu online updates


After the Updates have been discovered and if you have elected to download either set of updates, you will have the option to run the UIU immediately, using those updates saved to your chosen location. If you have moved them, simply browse to the location where you have elected to store them and you will find a complete (updated) UIU program directory.

loading uiu


Step 3: Install the UIU and Create a Universal Image

Master Image Machine Integrity Check (MIMIC) Now that the Base PC Setup Requirements and Recommendations have baddressed, Big Bang recommends that you run the Master Image Machine Integrity Check (een MIMIC) program, either independently or as part of the UIU Configuration Process. In order to run it independently, select the MIMIC icon on the menu bar and launch by clicking the large button on the left hand side of the screen.
The MIMIC scan may take a few seconds to process; let it complete its scan and review the results.

* You must be Logged-in as the Local Administrator when launching UIU.exe (not just a User with administrative rights)

UIU Menu - MIMIC


uiu mimic




MIMIC – Independent Execution


uiu mimic independent


Verification Indicators

  • Green indicators signify that the MIMIC check was found to be in compliance with UIU best-practices and the corresponding item should not inhibit or prevent the UIU from executing or causing problems on deployed machines
  • Yellow indicators signify issues discovered that may cause problems while executing the UIU or on deployed machines
  • Red indicators signify issues discovered that will prevent the UIU from executing properly or at all
  • Blue Indicators signify UIU Advanced Options which are not in use


Note: Red or Yellow indicators with silhouette & shovel signify that MIMIC is capable of helping resolve the issue. Click on the indicator itself to initiate this process for each indicator marked.

Running MIMIC independently operates exactly as it does running during the UIU Configuration Process. The difference, aside from the condensed view of the utility, lies in the ability to quickly run the application on an intended Base machine to check for compliance and compatibility with Universal Imaging.

UIU Discovery Tool – UIUDT


The UIU Discovery Tool (UIUDT) is designed to analyze machines in your environment to determine their compatibility with the UIU Driver Database.

  • If you’d like your UIU Image to only include drivers pertinent to the hardware deployed in your environment – Storage capacity or governmental compliance
  • When you’re looking at a new model of PC – Pre-determine if drivers will be missing, potentially leading to blue-screen errors (BSOD)
  • When you’re experiencing driver “bangs” – Support will be notified of the specific driver either automatically based on Internet connectivity or when you submit the results file to support@bigbangllc.com

How do I run the UIUDT?

ALERT: The UIUDT process has changed! Please refer to the UIUDT v2.0 Instructions before attempting to execute the new UIUDT.

The new UIU Discovery Tool v2.0 may be downloaded from UIU Support Tools Download.


NOTE: As of UIUv4.6, the UIU Discovery Tool will allow you to compare the results of a particular machine to any and every Windows OS that is supported by the UIU (Including Windows 8.1 or 10 32/64-bit) and use the new OS-Independent Results Data Files to prepare an image, regardless of OS!

Previous versions of the UIUDT will result in an error. Download the v4.6 (or greater) version of the UIUDT from the UIU Download Manager site.


Will this make my Universal Image Smaller?

Regardless of Internet connectivity, the OS-independent Results Data File(s) will be collected. Big Bang recommends that you save them in a single location.

The UIU now allows you to select them for consideration, parsing them and only extracting drivers required for the subset of hardware on which the UIUDT Results data files were collected.

Your Universal Image can now contain a subset of the UIU driver database, detected to be required for your environment, potentially making the UIU local footprint smaller.


What about my Privacy?
We at Big Bang LLC take your privacy very seriously. NO customer-specific information is transmitted over the internet or stored on Big Bang servers. Your UIUDT analysis results will be solely associated with your UIU License key information in an effort to better support all of the hardware in your environment. Please read our Privacy Statement for more information.

UIU Menu – Download Sysprep Executables

Before the UIU Configuration Process, you will need to obtain the version of Sysprep applicable to the Windows OS that you are employing. The Microsoft Sysprep utility is designed to help in the imaging process by reinitializing the hardware plug-and-play search, as well as handling SID changes. There are different versions of Sysprep used depending on the operating system and service pack. The UIU will automatically detect the OS version and verify Sysprep before using it.

UIU Menu - Sysprep


uiu sysprep


The Sysprep files are available on your Windows installation CD or they can be manually downloaded from Microsoft. Additionally, if you have an internet connection on your Base PC, the UIU has an integrated Sysprep download feature. Sysprep in Windows 8, 7 & Vista

Windows 8, 7 & Vista utilize distinct versions of Sysprep that are included in the operating system and therefore are not necessary to obtain elsewhere.

Sysprep in Windows 64-bit

64-bit versions of Windows 8 and 7 utilize a distinct 64-bit version of Sysprep that is included in the operating system.

The UIU will accept the 32-bit version of your Sysprep answer file and will convert it to a 64-bit compatible version. You will receive a prompted warning. If the UIU is supplied with data and the answer file is collected, it will produce a 64-bit answer file.

Required Sysprep.inf (XP ONLY) Fields


[Unattended]
OemSkipEula=Yes  ;Skips End User License Agreement or EULA
TargetPath=\WINDOWS  ;Location of Windows XP installation only
TargetPath=\WINNT  ;Location of Windows 2000 installation only
UpdateInstalledDrivers=yes DriverSigningPolicy=Ignore  ;Loads all drivers during Mini-Setup regardless of driver signatures.

[GuiUnattended]
AdminPassword=  ;must match the local admin password
OEMSkipRegional=1  ;Skips regional settings - uses default set in image
TimeZone=35  ;Time Zone - East=35, East(Indiana)=40, Central=20 ,Mountain=10, Mountain(Arizona)=15, Pacific=4 ,Alaska=3 Hawaii=2
OemSkipWelcome=1  ;Skips the welcome page in mini-setup

[UserData]
FullName=Default  ;This is Windows registration information only
OrgName=Organization  ;This is Windows registration information only
ComputerName=*  ;Random name set during mini-setup
ProductID=XXXXX-XXXXX-XXXXX-XXXXX-XXXXX  ;Windows VLK CD Key
[Display]  ;Set display resolution - do not exceed the capabilities of your target PCs.
BitsPerPel=32
Xresolution=1024  ;Enter the settings appropriate for your organization
YResolution=768  ;Enter the settings appropriate for your organization
Vrefresh=75

[Identification]  ;Delete unused domain or workgroup information
JoinDomain=  ;Domain Name (does not require “.com”)
DomainAdmin=  ;Domain Admin ID (does not require Domain Name)
DomainAdminPassword=
JoinWorkgroup=

[Networking] InstallDefaultComponents=Yes  ;Installs standard network components – TCP/IP, Client for MS Networks, File/Print Sharing, etc.


uiu logo user guide


Chapter 3 - UIU CONFIGURATION PROCESS


After the UIU has been updated and installed, you are ready to begin. The Configuration Wizard will help you to collect all required information for UIU preparation and allow you to save that configuration for future maintenance.

The configuration process consists of four steps:



MIMIC Verification


Regardless of whether or not you elected to run MIMIC independently from the UIU Main Menu, the configuration process will automatically invoke the utility to verify compliance with the UIU. You have the opportunity to correct discovered problems at this point. If corrections are required and either addressed manually or through the MIMIC utility, it is Big Bang’s recommendation as a best-practice to exit the UIU and re-capture your Master Image for long-term stability of UIU-prepared images during your cloning maintenance cycle.

MIMIC operates as part of the UIU Configuration Process exactly as it does when run independently from the UIU Menu.

  1. Green indicators signify that the MIMIC check was found to be in compliance with UIU best-practices and the corresponding item should not inhibit or prevent the UIU from executing or causing problems on deployed machines
  2. Yellow indicators signify issues discovered that may cause problems while executing the UIU or on deployed machines
  3. Red indicators signify issues discovered that will prevent the UIU from executing properly or at all
  4. Blue Indicators signify UIU Advanced Options which are not in use
Note: Red or Yellow indicators with silhouette & shovel signify that MIMIC is capable of helping resolve the issue. Click on the indicator itself to initiate this process for each indicator marked.

MIMIC – UIU Configuration


uiu mimic configuration


Import/Configure Sysprep



  • The UIU installation will offer the option to download the Sysprep files directly from Microsoft if you do not have them, or it will allow you to browse for the files if you do have them.


  • When manually browsing for the Sysprep executable files, the following two files must be made available to the UIU.


  •      setupcl.exe
         sysprep.exe


  • Once the Sysprep.exe file is located, if a Sysprep.inf answer file is available in the same directory, the UIU will use that file. If a Sysprep.inf file is not available, the necessary information can be entered in the UIU wizard, and the UIU will build the Sysprep.inf file and copy it to the appropriate location on the Master PC.


  • NOTE: You must at least incorporate the specific functions listed under the “Unattended” section of the Sysprep.inf file below in order for the UIU to work correctly. Using the Sysprep Setup Manager Application to create your Sysprep.inf file will create a file that is not fully compatible with the UIU, and may cause your UIU image to fail after deployment.


    Sysprep in Windows 8, 7 & Vista

    The required answer file for Sysprep in Windows 8, 7 & Vista is named Unattend.xml (as opposed to Sysprep.inf). The XML format requires very specific syntax and it is recommended that the UIU be relied upon to create the answer file in the course of executing the application. If your organization requires features within the Unattend.xml, outside of what the UIU interface provides, please refer to Microsoft’s documentation relating to Unattend.xml and consult UIU Support for guidance on which parameters should not be used.

    UIU Microsoft Sysprep Configuration Options
    Windows XP

    UIU requires Microsoft Sysprep files – Sysprep.exe, Setupcl.exe, and Sysprep.inf. Select “Import Sysprep” to locate the EXE files. If your answer file (Sysprep.INF) is also stored in that same directory, it will automatically be imported. If your INF file is stored in a separate location, select “Import Sysprep Answer File” to locate and import your answer file.

    Sysprep Configuration Collection


    uiu sysprep answer file creation


    UIU Sysprep.inf Creation

    If you do not have a prepared answer file for your organization, the UIU Sysprep Configuration wizard will assist you in creating one, based on the information in the General, System and Network tabs, which will be effective in your environment. Select “Create New Sysprep File” from the dropdown as shown below. The resultant answer file may now be exported when complete. Simply follow the Save As prompts.

    Create New Sysprep Answer File


    uiu create new sysprep answer file


    The General Tab includes inputs for entering the Windows License Key, time zone and screen resolution settings. A Microsoft Windows Volume License Key (VLK) is strongly recommended, and is required to avoid Windows XP Activation.

    The System Tab includes inputs for the Organization and User that Windows is registered to, (not actual Windows user logon information), Computer Name and Local Administrator Password.

    The Network Tab includes inputs for configuration settings to allow for joining a Windows Domain or Workgroup.

    UIU Microsoft 8, 7 & Vista and Unattend XML
    Configuration Options


    If you did not have an Unattend.xml file available in the directory from which UIU.EXE was executed or you did not import an alternative Unattend.xml, the UIU will create the Unattend.xml file for you based on the information in the “Configure Sysprep” tabs.

    If you do not have a prepared answer file for your organization, the UIU Sysprep Configuration wizard will assist you in creating one, (based on the information in the General, System, Network and Advanced tabs), that will be effective in your environment. Select “Create New Sysprep File” from the dropdown as shown below. The resultant answer file may now be exported when complete. Simply follow the Save As prompts.


    Sysprep - Advanced Tab


    uiu sysprep prepare configuration


    The General Tab includes Time zone and Display settings. The System Tab includes inputs for the Owner and Organization that Windows is registered to, (not actual Windows user logon information), Computer Name and Local Administrator Password as well as an option to use the Administrator profile as a template for all local users created. The Network Tab includes inputs for configuration settings to allow for joining a Windows Domain or Workgroup. The Advanced Tab includes Auto Logon settings (incl. credentials) and Network Location selection. The Advanced Tab also includes an option to invoke Windows Welcome on all deployed PC’s. This option, if the box is checked, will prompt for Computer Name, Username (User Account), Password (User Account), PC Location (Internet, Work or Home) and Windows Updates default behavior on each machine to which that UIU Image is deployed. Computer Name only: If you’d like to only be prompted for Computer Name in Vista (or newer OS), simply remove the Computer Name field from your Unattend.XML file and import it through the UIU interface. The UIU will parse that omission and provide a prompt at the beginning of mini-setup for Computer Name (only). Note: Simply leaving the computer name blank when using the UIU interface, (Sysprep Options) a random computer name will automatically be generated according to default behavior. You must import the prepared, Unattend.XML without a Computer Name field.

    Include Discovery Tool Files, *.uiudt (optional)


    An optional feature available during the UIU Configuration Process allows you to include UIUDT Results Files compiled from machines in your environment to extract only UIU drivers necessary for your environment.


    Include UIUDT Results Files


    uiu discovery tool results


    Select “Browse File” to locate UIUDT Results files and include them in the UIU Configuration. In order for this feature to be effective in your environment, you must include UIUDT Results files from every Make/Model of PC on which you intend to deploy your Universal Image.

    Select “Clear List” to remove all included UIUDT Results Files. Select “Remove Files with Errors” to remove UIUDT Results files that reflect an error. This will clear the error state and activate the “Finish” button.

    Select Advanced Options


    The Advanced Options of the UIU are designed to help automate future installations of the UIU as well as handle specific logging and reboot options.


    Advanced Options (XP Options)


    uiu advanced XP options


    Advanced Options include:
    • UIU Boot Options – Windows XP ONLY – UIU Startup selected by default – Select the default UIU Boot Option mode to facilitate the boot of deployed machines using Uni/Multiprocessor computer types or ACPI computer types.
    • Boot Menu Timeout – Windows XP ONLY – Select the duration that the UIU Boot Menu will display on deployed machines (default=15sec).
    • If zero “0” is selected, no menu will be displayed on deployed machines and the selected Boot Option will take effect automatically!
    • Shutdown Options – After UIU completes, the Master system, select the desired option which include Shutdown after completion (default), Reboot PC after UIU completion, Exit UIU after completion (New) and Disable Auto Shutdown. Avoid making system changes to your UIU-prepared configuration prior to capturing a UIU Image.
    • Maintain Default Administrator Profile – Off by default – When selected in Windows 7/8.1/10, the default Administrator account will be enable after deployment.
    • Pre-Install SCSI Drivers – Off by default – If the UIU image will be deployed to machines with SCSI (non-RAID) hard drives, select the Pre-Install SCSI Drivers checkbox. There is no need to select it if you do not have SCSI based systems to which you intend to deploy your Universal Image. The SCSI drivers included with the UIU will be installed into your base system. This function will add a few minutes to the configuration of the UIU and to the UIU-invoked configuration of each deployed PC.
    • Boot to Ghost Virtual Partition – Off by default – This option is displayed when available and when selected, will invoke the Ghost virtual partition, allowing the session to respond to a console task if available.
    • Signed Drivers Only – On by default – This will prevent any UIU-provided drivers that are not digitally signed from being copied to the local machine.
    • Remove UIU Drivers After Deployment – Off by default – This option will remove all UIU drivers after each deployed machine has detected and installed applicable drivers.
    • Remove .Net Framework – Off by default – This option will remove all UIU-installed .Net Framework versions (not v2.0).
    • Sysprep Command Line Options – Allows for modification of the command line that the UIU invokes during the process. This feature is only for advanced users and should only be modified as directed by UIU Support. Errant changes may cause the UIU to fail.
    • Set Optimal Display Resolution – Off by Default – Allows a deployed image to query the target machine’s primary video adapter and attached monitor to obtain and set the display resolution to the negotiated optimal parameters (resolution & color depth). Note: Refresh rate is set to 60MHz. CRT monitors may need to be adjusted for optimal refresh rate.


    UIU Boot Options (XP ONLY)
    Detailed Option Description


    When installing the UIU, the default UIU Boot Option must be selected. Upon deploying a Universal Image, the UIU Boot Menu screen will be displayed before the UIU allows Windows mini-setup to run. Both “UIU Startup” and “UIU Legacy Startup” options will be displayed in the menu. The option listed first will launch within 15 seconds. In the event one option does not boot successfully, the other option should be selected manually from the UIU Boot Menu screen upon the deployed machine’s next boot.

    (As always, new drivers are continually added to the UIU, some of which may impact the ability of the system to boot successfully – e.g. SATA Controller drivers.)

    UIU Startup (Default Option) A Universal Image booted using this option automatically addresses Computer Types “ACPI Uniprocessor PC” (Uniprocessor) and “ACPI Multiprocessor PC” (Multiprocessor) systems only. These systems may not have been compatible with versions of UIU prior to 3.7.1.x.

    UIU Legacy Startup (Selectable Option) Selecting the “UIU Legacy Startup” will boot the system in the same way UIU did prior to 3.7.1.x, and supports multiple Computer Types including legacy ACPI and most Uniprocessor and Multiprocessor systems.

    In an environment containing a mix of ACPI systems and Uni/Multiprocessor systems, either option may be selected as the default UIU Boot option. The “UIU Legacy Startup” will be the most effective if the number of ACPI systems outweighs the incompatible Uni/Multiprocessor systems. If several new machine types have been introduced, however, including Intel Centrino II laptop systems, the “UIU Legacy Startup” should not be selected by default, but rather used on the individual legacy machines at boot up.

    UIU Boot Menu on Deployed Machines

    Below is an example of a UIU Boot Menu displayed on deployed machines wherein the UIU Startup option was selected during the UIU Configuration Process.

    UIU Boot Menu Screen – Deployed UIU Image


    uiu xp boot menu


    Note: In the event that you do not change the selection during the timeout period for deployed machines that require a boot option other than the selected default, you may experience a blue screen or other Windows fault. Simply reboot the machine and choose the alternative selection to successfully boot and allow the UIU to configure the PC.

    Saving your Configuration

    When you have completed the required portions of the UIU Configuration Process, the Finish button on the bottom of the screen will become active. You may use the Back button to review settings or the Cancel button to exit the UIU. If you select Cancel, the UIU will remove all temporary files except for the UIU log.

    When you select Finish, you will be presented with one final screen. You have the option to Save your UIU Configuration information by checking the Enable Save box and browsing for a location to which you may save your settings.

    Final Pre-UIU Configuration


    uiu final configuration


    NOTICE: This screen represents your LAST CHANCE to exit the UIU without changes to the OS that may compromise encrypted data!

    If the machine on which the UIU has been installed utilizes SID-based encryption methodologies or software serializations, or if this is not the machine that you intended to run the UIU on for purposes of producing a Universal Image, please select “Abort” to exit the UIU (with appropriate cleanup of temporary files).

    If you are certain that the machine on which you have installed the UIU is your Base Image machine for which you have collected a Base Image and a Master Image, select “Start UIU” to begin the process of modifying your Base PC into your new Universal Image configuration, ready to be collected by the cloning software of your choice.

    Preparing Base Machine with UIU


    uiu prepare base machine


    While the UIU makes modifications to create your Universal Image configuration, you will be presented with General, Technical and Support Information. You will also be presented with progress indicators at the bottom of the screen, displaying the action that the UIU is currently executing.

    The UIU will log your machine hardware, copy the UIU Driver Database, complete the configuration of the operating system and reset the machine to a pre-installation state. We strongly recommend that no changes, except those expressly recommended by UIU Support, be made to the OS after the UIU is finished. Certain types of changes may cause the deployed images to fail.

    Congratulations


    uiu ready


    When the Universal Image configuration has been completed, close the UIU and do not simply RESTART the PC! Instead, shut it down and capture your new Universal Image before rebooting the UIU-prepared machine to Windows. The captured Universal Image will be deployable cross-platform, reducing deployment overhead and streamlining support efforts.

    UIU AutoRun Mode

    An alternative method to run the UIU, without user interaction is UIU AutoRun Mode.

    The UIU AutoRun feature is designed to allow you to Standardize and expedite your UIU Master Image creation with the UIU, in a fully unattended or automated mode, (as long as all of the required information and supporting files are supplied).

    This mode will allow a prepared UIU process to be executed by any staff with the assurance that the correct technical specifications of your environment are adhered to, regardless of skill. All UIU features will function as expected through the process.

    A valid Sysprep unattend file and a uiuconfig.cfg file are required at minimum. Additional files include UIUDT files, prepared from machines in your environment.

    New Command Lines (used at command line or in uiuconfig.cfg file)

    –autostart
    This flag will trigger the UIU to run in AutoRun.

    –autoignoremimicwarnings
    This flag will prevent the MIMIC Warnings from halting the AutoRun process.

    –uiudtfilesfolderpath <folderpath>
    This flag sets the folder path ("<folderpath>") of where the ".uiudt" files that are to be imported are located.

    –autoignoreinvaliddtfiles
    This is used in combination with "-uiudtfilesfolderpath" to prevent the uiu from importing invalid ".uiudt" files.

    SAMPLE “uiuconfig.cfg” file

    –startpath C:\CD
    –regkey XXXXXX-!v4!XXXX (place your UIU license key here)
    –autostart
    –autoignoremimicwarnings
    –skipupdates


    Auto Run


    uiu autorun mode


    When you run the UIU in AutoRun mode, the first screen you will see provides a countdown. When the countdown reaches "0" the UIU will begin execution.

    Click on "Start Now" to bypass the countdown.
    Click on "Quit" to quit UIU.

    The UIU will follow a typical path, performing each of the functions and features of the UIU provided that the necessary information is provided in the correct format.

    UIU Updates Screen during AutoRun

    If an invalid key (or no key) is inserted in the configuration file, you will receive an error and have a chance to enter a valid key license key. Click "Next" to proceed.

    If no Internet connection is detected, you will receive an error and have a chance to change connection preferences or skip updates. Click "Next" to proceed.

    If updates are found by the uiuupdate.exe, it will automate the process by downloading, compiling and using the latest Executables package and Driver Database (for the current operating system ONLY). If no updates are found, the UIU AutoRun process will continue.

    UIU Configuration Process during AutoRun

    During the AutoRun process you will notice that the main launch menu is skipped and the UIU Wizard is initiated. In the wizard, the navigation on the right has been disabled and that the bottom navigations have changed. Also, the advanced option screen has been removed. All advanced configuration should have been set in the UIU configuration file “uiuconfig.cfg”.

    MIMIC during Auto Run


    uiu autorun example


    During AutoRun mode, you will see screens similar to the image above, indicating the step that the UIU is currently automatically executing. If there are errors or warnings, the UIU will halt the AutoRun process and you will see notifications similar to the following examples:

    Example 1: MIMIC Warning UIU has detected that during the MIMIC step there not all validations passed and there has been a warning. Click "Resume" to continue; Click "Ignore" to ignore the warning and proceed with UIU process; Click "Cancel" to quit UIU.

    Example 2: Sysprep Error UIU has detected that the Sysprep step has invalid fields. The resume button will be disabled until all the fields have been fixed. Click "Resume" to continue; Click "Cancel" to quit UIU.

    Example 3: UIUDT Error UIU has detected that the "Discovery Tool Files" step has invalid ".uiudt "files. The resume button will be disabled until the invalid files have been removed from the list. Click "Resume" to continue; Click "Cancel" to quit UIU.

    When all UIU Configuration entries are satisfied, the UIU will display a “Final Countdown” during which the UIU execution may still be aborted.

    Final Countdown


    uiu final countdown


    Final countdown before the machine configuration is kicked off. Click "Abort" to quit UIU.

    UIU Command-Line Switches

    All switches must be preceded by a dash “-“ with associated data separated by a <space>


    Associated with UIU Advanced Options (GUI)
    legacyboot –– Default to Legacy Boot Option
    noturnoff –– Disable Auto Shutdown
    reboot –– Reboot PC after UIU completion
    preinstallscsi –– Pre-install SCSI Drivers
    signed –– Extract and use digitally-signed drivers ONLY
    useghostvp –– Invoke Ghost Virtual Partition after UIU completes
         (e.g. uiu.exe -unsigned -preinstallscsi)
    deletedrivers –– Remove UIU drivers after deployment
    skipupdates –– Instructs the UIU to Skip Program and Driver Updates (Associated with UIUupdate feature)
    bmto –– Set the number of seconds that the UIU Boot Menu is displayed on deployed machines. (Default=15 sec)


    Additional command-line switches:
    disablesatapreinstall –– Disable pre-installation of SATA drivers
    disablesysprepvalidation –– Disable validation of Sysprep answer file; requires the use of sysprepinflocation switch or import a Sysprep.inf file during the UIU Configuration Process
    nosysprep –– Do not invoke Sysprep
    osd –– Enable UIU to run in conjunction with Microsoft OSD


    dat –– Specify driver.dat location (include driver.dat after path) <path and filename> (e.g. uiu.exe –dat c:\UIU\driver.dat)
    exedat –– Specify exe.dat <path and filename>
    proxyhost –– Specify Proxy Host address
    proxyport –– Specify Proxy Port number
    regkey –– Specify UIU License Key to use
         (e.g. uiu.exe -regkey XXXXXXXyour UIULicenseKeyXXXXXXX)
    syspreplocation –– Specify location of sysprep.exe <path and filename>
    setupcllocation –– Specify location of setupcl.exe <path and filename>
    sysprepinflocation –– Specify location of sysprep.inf <path and filename>
    skipversioncheck –– Disable OS/SP version validation of Sysprep executables
    uiudir –– Specify local UIU temporary folder location <path only>
    autostart –– Trigger AutoRun Mode of UIU execution


    autoignoremimicwarnings –– Prevent MIMIC warnings from interrupting the AutoRun process 

    uiudtfilesfolderpath <folderpath> –– Sets the folder path("<folderpath>") of where the ".uiudt" files that are to be imported are located. 

    autoignoreinvaliddtfiles –– This is used in combination with "-uiudtfilesfolderpath" to prevent the uiu from importing invalid ".uiudt" files. 



    Cumulative example: ..\uiu.exe -signed -preinstallscsi -reboot -dat c:\UIUutility\driver.dat -regkey XXXXXXXyour UIUlicenseKeyXXXXXXX 



    UIUCONFIG.CFG File (example)


    uiu config file example


    uiu logo user guide


    Chapter 4 – Trial Version of the Universal Imaging Utility

    Trial Splash Screen


    uiu trial splash


    • Trial versions of the UIU may not download the driver or executable updates. Trial users must contact Big Bang directly in order to receive updates for testing. The Trial versions available for download include the latest updates.
    • Trial versions of the UIU may shut down the operating system of machines where trial images are deployed. Shut down warnings will be displayed during the installation of the UIU as well as after deployment.
    • Windows images created with a Trial version of the UIU are designed for test environments only, and shall not be deployed to live environment PCs.
    • The Trial version of the UIU will contain a Trial Background for the Windows login screen and all users. This Trial Background is not included in the licensed version of the UIU.
    • There is no method for turning a Trial UIU image into a Licensed UIU image, as the modifications made by the Trial version are part of the actual image.
    • TRIAL users will be presented with the following warning screen:
    • It is imperative that the TRIAL UIU product NOT be executed on any production PC including an active user PC where business data may be stored.
    • IT is imperative that no TRIAL UIU Image be deployed to any production PC. The TRIAL UIU product is intended for evaluation use only in pre-production or testing environments.
    • Some antivirus applications may mistakenly identify BBGINA.DLL and/or TWUNK.DLL as threats. These two files are necessary for the UIU TRIAL product to function and should not be removed, modified, moved or quarantined.


    uiu logo user guide


    Chapter 5 - Re-Imaging After Modifying your Universal Image Configuration

    Part of the appeal of the UIU is that when changes must be made, they need only be made on one image. When the time comes, deploy your saved Master Image to your Base PC, make the necessary or desired modifications (incl. OS Updates, antivirus definition file updates, application updates, etc.), capture a new Master Image, and simply re-execute the UIU. Capture your new Universal Image and deploy to new machines in your environment or as part of your PC support procedures.

    Big Bang strongly recommends that you always run the UIU on a clean installation of Windows (Base Image of Master Image) rather than on a machine where the UIU has already been executed, or to a machine that has received a Universal Image.

    Application Deployment Best Practices

    Big Bang recommends that you maintain the fewest possible applications in your Master Image, employing other application deployment methodologies (e.g. Ghost AI or Microsoft MDT) to provide applications within your environment. Not only is this best-practice more supportable and maintainable, it will also avoid application compatibility issues, particularly with programs that rely on the local Windows SID configuration/settings.


    uiu logo user guide


    Chapter 6 – Troubleshooting a Universal Image

    Below are some of the most common troubleshooting issues relating to the UIU, and possible causes, listed by order of commonality.

    1. Problem: Blue Screen or Continual Rebooting:
    2. Problem: A pop-up “New Hardware Found” wizard opens during the mini-setup or the Device Manager shows an exclamation (“driver bang”) and a garbled name for the Monitor after sending a UIU image.
    3. Problem: The Device Manager shows a “driver bang” for a device other than the Monitor.
    4. Problem: Checkboxes in the UIU user interface do not appear to change when selected.


    uiu logo user guide


    Chapter 7 - Technical Support

    Technical Support

    As part of the licensing agreement with Big Bang LLC, technical support for the Universal Imaging Utility (UIU) is available for one year from the original purchase date. Big Bang LLC technical support can be reached through the following methods:

    On Line Support Form (Preferred):
    UIU Support

    Direct Telephone Support: 414-369-5020
       (M-F 9:00am-5:00pm Central:GMT-6)

    Email Support: support@bigbangllc.com Send UIU Support an email

    When contacting Big Bang LLC for support, please be prepared to provide the following information:

  • Operating System and Service Pack
  • PC Make/Model of Base build machine
  • PC Make/Model of Recipient (deployed to) machine(s)
  • Version of the UIU and Revision of the Driver Database
  • UIU License Key
  • UIU log file (C:\Program Files\UIU\UIULog.htm)
  • UIUDT log file (C:\Program Files\UIU\UIUDTLog.htm)
  • Nature of the Problem; Blue Screen, Continual Reboot, Missing Hardware Driver, etc.


  • In situations relating to missing or incorrect hardware drivers, please be able to provide the following files from the Recipient Machine:

    Windows XP
  • UIU log file (C:\Documents and Settings\\Application Data\UIU\UIU.log)
  • SETUPAPI Log (C:\windows\setupapi.log)

  • UIUDT log file (C:\Program Files\UIU\UIUDTLog.htm)


  • —or—

    Windows 10, 8.1, 7 (32-bit or 64-bit)
  • UIU log file (C:\Program Files\UIU\UIU.log)
  • UIU log file - MDT plug-in ONLY (C:\ProgramData\UIU\UIU.log) ~ hidden directory by default
  • SETUPAPI Log (C:\windows\inf\setupapi.dev.log)
  • SETUPAPI Setup Log (C:\windows\inf\setupapi.setup.log) -- Windows 10 only

  • UIUDT log file (C:\Program Files\UIU\UIUDTLog.htm)


  • *Technical Support and UIU Updates are only available for operating systems and hardware currently supported by the UIU. Please see the section titled “Universal Imaging Utility Features and Requirements” for more details.


    Please review this Setup Guide
    before installing
    the Universal Imaging Utility.