Section 1: Requirements and Limitations
UIU Supported Hardware and MDT Environment
Any business-class PC machines and OEM hardware or "white-box" hardware containing only business-class components will be supported.
All supported hardware must meet the following minimum criteria:
- PCs must be ACPI Compliant
- PCs must contain at least 1Gb of free hard drive space
- PCs hardware must meet MS requirements for applicable OS
- PCs hardware must have a minimum of 250Mb of free space on each target PC (after OS deployment)
Note: Any BBLLC-produced list of supported hardware may not be complete and is subject to OEM-produced hardware without change or exception. (We make every attempt to stay current with of all the latest hardware and chipsets, however occasionally we aren’t made aware of new models or components released by the manufacturer.)
Supported Operating Systems (for Deployment to PC machines):
- Windows XP (Professional or Tablet) SP2 or SP3 32-bit
- Windows 7 (Professional or Enterprise) 32-bit and 64-bit
- Windows 8.1 (Professional or Enterprise) 32-bit and 64-bit
- Windows 10 (Professional or Enterprise) 32-bit and 64-bit
- Windows Thin PC (WinTPC)
The supported MDT environment must meet the following criteria:
- MDT 2012 Server or MDT 2013 Server installed on Windows operating system
- MDT Server Internet access – Required for UIU product Updates (Live ONLY)
- The MDT environment must be sufficiently designed to replicate the UIU Repository, with approximately 1Gb available on the Server and 20Gb available on Repository Share to be used.
- .NET 4.0 runtime (This will be installed by setup if it is not detected) – Required for installation
- UIU License Key (This can be found on your license certificate) – Required for installation
- Administrator level access to the MDT Server – Required for installation
- Network connectivity to all client PCs – Required for deployment with UIU
Technical Support Requirements
- The MDT system must be tested and proven capable of deploying a supported Windows operating system independently, (without the UIU software.)
- Submission of log files and supporting information as requested by UIU Support personnel
- The UIU is not designed to image Windows Server operating systems and no technical support will be provided.
Section 2: Definitions
Deploy or Deployment = Provide a UIU-augmented Standard Client Task Sequence to a MDT Deployment Share for distribution during OS deployment
Section 3: Quick steps
- Select the default Standard Client Task Sequence type or edit an existing deployment Task Sequence
- Use the Task Sequence Editor “Add” menu feature to select “UIU Machine Configuration” from the “Universal Imagining Utility” item
- The UIU Machine Configuration task must be placed after the “Add Windows Recovery (WinRE)” task in the OS Deployment Sequence
- Modify any UIU parameters as desired (incl. required UIU source directory UNC)
- Update Deployment Share after adding UIU to the Task Sequence
Section 4: Using the Universal Imaging Utility Plug-in for MDT (UIU)
MDT 2012 or MDT 2013
Share the UIU Repository Directory as a UNC Path
During Installation of the UIU for MDT Plug-in, you were asked to provide a network location in which to install the UIU Repository. This network location needs to be shared and available to target PC’s via UNC path.
Locate network path specified during Installation, right-click on the root directory and select Sharing.
Select “Share…” in the Network File and Folder Sharing Section.
Enter either the Administrator account or other specific account setup for target machines to access the UIU Repository and provide at least Read/Write access for that user on this share.
Open the Deployment Workbench on the MDT server
Create a Standard Client Task Sequence
Navigate to Deployment Shares>MDT Deployment Share and select Task Sequences
Right-click on the Task Sequences node and select “New Task Sequence”
Click “Next” to continue
Enter the desired Task Sequence ID and Name
Click “Next” to continue
Select Standard Client Task Sequence
Click “Next” to continue
Select OS to deploy (must be an image collected with Deploy & Capture LTI)
Click “Next” to continue
Specify a Product Key (if desired)
Click “Next” to continue
Configure OS Settings
Click “Next” to continue
Provide Administrator password (if desired/required)
Click “Next” to continue
Complete the Wizard
Add the UIU Machine Configuration Task
Select the created Standard Client Task Sequence; right-click and select “Properties”
Navigate to the Task Sequence tab>Post-Install branch
Highlight the task directly before "Next Phase" in the Postinstall branch
In the Standard Client Task Sequence, "Add Windows Recovery (WinRE)" is the task directly preceding "Next Phase"
The UIU Machine Configuration task must be placed directly before "Next Phase" in the Postinstall branch of the task sequence
Select: Add>Universal Imaging Utility>UIU Machine Configuration
In the Standard Client Task Sequence, the UIU Machine Configuration task should appear after
the Windows Recovery (WinRE) task
Be sure that the UIU task exists in the sequence directly before “Next Phase”!
Configure the UIU Machine Configuration Task
Highlight the UIU Machine Configuration task to edit Properties
Browse to select or enter the UIU Repository Directory UNC Path as shared previously (at the beginning of Section 4)
Select the “Use Credentials to access this Repository” option if different credentials are required
Select “Signed Drivers Only” if required
Select this feature to instruct the UIU to only copy drivers that have been digitally signed specifically by their OEM. No unsigned drivers or drivers signed by Big Bang will be presented to the target machine.
Enter Additional Command Line Arguments in the “Advanced Switches” text box if instructed to do so by UIU Support (advanced users only)
Apply Changes <Apply>
Click “OK” to close
If you've made any changes that affect the boot image, including adding storage (HDC) drivers or network drivers, you'll need to update the MDT Deployment Share. Please refer to the following site link details:
Update the MDT Deployment Share: When Why and How
Deploy UIU for MDT to Target Machines
Boot target machines via PXE or using the created MDT LiteTouch ISO on a bootable DVD
Complete the MDT wizard on the booted target machines; be sure to select the task sequence that contains the UIU Machine Configuration task.
Deploy your UIU-prepared Windows operating system.
UIU plug-in (MDT & SCCM) TRIAL with Windows 10
The native "build and capture" WIM image creation method supported in Windows 10 capable SCCM and MDT task sequences has been witnessed to interfere with the UIU TRIAL process, rendering it unuseable only for Windows 10 build 10240 (released in July 2015), an RTM release. It is not unreasonable to assume that an RTM version would be expected to exhibit faults (bugs).
Windows 10 build 10586 "Maintenance Release 1511" (a.k.a. Service Pack), released on Nov 15 of 2015, behaves correctly as expected using WIM images created with the "build & capture" process.
If you're performing a trial of the UIU plug-in for SCCM or MDT, please refrain from using the "build and capture" technique to produce a deployable image of Windows 10 RTM (build 10240). Instead, install the OS from ISO and collect an image using DISM (available for free in Windows 10 ADK) to capture the WIM which may then be imported into SCCM or MDT for deployment with the UIU Trial product. Please feel free to contact UIU Support for assistance if necessary.
Big Bang will not continue to investigate the failed interaction with "build and capture" images of Windows 10 RTM (build 10240) as relates to its TRIAL product.
Big Bang recommends that customers use the latest release of Windows 10, which not only works with our TRIAL product, but also contains important and critical fixes to the OS build.
For Target Machines not connected to a network:
UIU for MDT Off-Network (Offline Media) Procedure
In deployment instances where it is desirable or necessary to deploy an operating system while not connected to a network or when PXE services are not available, MDT (similar to SCCM) provides a method to produce media to be used off-network, (also referred to as Offline Media). The following procedure will assist in creating effective off-network media (USB preferred due to aggregate package sizes) including the use of the UIU plug-in for MDT:
- The configured MDT environment must have ability to deploy images without UIU (prerequisite).
- If not already installed, install UIU plug-in for MDT on same PC as Deployment Workbench
- If not already installed, Install UIU plug-in for MDT using directions from UIU plug-in for MDT Install Guide
- Create new application, selecting an appropriate name, (e.g. “UIUForMDT”):
- Navigate to Deployment Workbench > Deployment Shares > [Deployment Share name] > Applications and create a new folder called "UIUforMDT" or the like for the purposes of inclusion into a Selection Profile (Step 4.2.1).
- Navigate to Deployment Workbench > Deployment Shares > [Deployment Share name] > Applications > UIUforMDT folder and right-click "New Application".
- During create application wizard, select “Application with Source Files” and browse to the installed location for the UIU Repository, (e.g. "[deployment share]\applications\uiu\data"). This creates an MDT-compatible application package with the UIU Driver Database fully extracted and ready for use. If the UIU plug-in for MDT was installed in the default location, choose that location instead, ("c:\program files (x86)\UIU\Data").
If you wish to conserve disk space between the installation directory and the Deployment Share, (which may be on the same disk drive), select the checkbox labeled, "Move the files to the deployment share instead of copying them."
IF THIS OPTION IS SELECTED, a registry change is required in order for the UIU plug-in Updater application to properly update the product in the moved location. First, close the UIU Updater appliction in the system tray! In order to affect this registry change, navigate (in regedit.exe) to Big Bang LLC>UIU>UIUSD within the Software hive, (on 64 bit machines, this is located further in the WOW6432Node), and change the PackageSourceDirectory key to reflect the new UIU repository location, (e.g. C:\DeploymentShare\Applications\UIUforMDT\UIUforMDT). If the key does not exist, (as is the case with default installations of the UIU plug-in for MDT), the String Value key (PackageSourceDirectory) must be manually created. When the UIU Updater application is re-launched, it will be directed to the new location. The UIU Updater application can be manually launched from C:\Program Files (x86)\UIU\bin\uiupluginupdater.exe.
- In the Destination field, give a name for the application, (eg. “UIU For MDT”). This will dictate the physical folder name in the Deployment Share. Note: This will be the location used in the registry edit annotated in the previous step.
- In Command Details, a command line argument is required, (even though not used in this context). Supply a null or “dummy” executable such as “notepad.exe”. NOTE: This application will not actually ever be launched via the MDT Application Installer! For further explanation, please contact UIU Support.
- Finish the New Application wizard.
- Add UIU Machine Configuration step to the desired offline deployment task sequence. (Refer to the UIU plug-in for MDT User Guide)
- Change the UIU Repository Directory UNC path to the following:
([UIUForMDT] should match the application name as entered in step 2.2.4
- Creating off network media
- If Deployment Share has multiple operating systems, applications, or packages, now is the time to create additional folders for other components so that an optimized (slim) offline Selection Profile can be created. Copy appropriate content from the Deployment Share to each folder created as desired. These folders may be selected individually to exclude unwanted applications from being copied to the off-network media.
- Under Advanced Configuration > Selection Profiles, create a New Selection Profile choosing only the Applications and Operating Systems that are desired for the particular off-network deployment.
- NOTE: Selecting more than what is necessary will result in larger than necessary ISO files or USB storage requirements.
- Once the Selection Profile has been created, right-click on Advanced Configuration > Media and Create New Media using the selection profile desired. Remember the save location that you designate in this wizard for later use.
- Format USB drive (recommended) using Diskpart.exe. This USB drive should be large enough to hold the entire media as defined by the Selection Profile used. (As a point of note, the inclusion of an OS, UIU for MDT and the off-network task sequence “bare bones configuration” is approximately 14 Gb in size.)
- On a computer running the Windows operating system, insert the USB drive.
- From a command prompt, run Diskpart.exe
- Execute the command “list disk” to determine the disk number associated with the device.
- Input the following commands, where N is the disk number identified in the previous step:
- select disk N
- create partition primary
- select partition 1
- format fs=fat32 [ntfs] [quick]
Note: UEFI partitions will only boot with fat32 formatted USB drives. Diskpart.exe is a powerful utility and can cause damage to your system. Make sure to format the correct drive!
- After media has been created there will be a “Content” folder in the save location that was chosen in step 4.3. Copy the contents of the Content folder to your freshly formatted USB.
- Test the bootable USB containing the off-network media for desired results before implementing the process in any production environment.
A network access account other than a domain administrator account is recommended the UIU Source share (UNC Path) in MDT 2012. It is recommended that an account be specifically created for that purpose.
The following Section has been excerpted from the following Microsoft TechNet article and copyrights are attributed to Microsoft:
Configure the Network Access Account
Section 5: DEPLOYMENT
What will I see on my deployed machines?
Boot into WINPE
Typical Install Task Sequence steps through “Apply Operating System”
MDT Client executes the “UIU Machine Configuration” task
Settings selected in the UIU Machine Configuration task are initialized and UIUPREP is executed.
UIUPREP copies necessary UIU Software components
UIUPREP copies all necessary executables and supporting files to the target machine.
UIUPREP Analyzes Hardware Devices
All hardware components on the target machine are discovered and analyzed for applicable Hardware IDs.
UIUPREP Copies UIU Required Drivers
UIUPREP identifies all required UIU drivers as analyzed in the previous step and copies only the required driver files to the target machine. Any drivers mandated by the inclusion of a UIU Discovery Tool Package are included.
UIUPREP Installs Triggers
UIUPREP will analyze discovered hardware ID’s to determine if any Big Bang triggered drivers are necessary and prepare them to be copied into the Local Driver Store.
UIUPREP Clears the Local Driver Store
UIUPrep removes unnecessary driver components in order to allow Microsoft’s driver enumeration method to function efficiently.
UIUPREP Installs the Copied Drivers
UIUPrep installs the copied drivers into the Local Driver Store to be presented to and enumerated by Microsoft mini-setup.
Upon completion, UIUPREP will initiate a restart of the target machine.
UIUPREP Invokes Microsoft’s Mini-Setup to perform Sysprep-related functions and driver enumeration.
At this point the UIU releases control to the MDT Task Sequence for completion of any tasks that followed the “UIU Machine Configuration” task. The target machine operating setup is complete and login may be initiated.
Section 6: TRIAL VERSION OF THE UIU
Trial versions of the UIU for MDT may not obtain driver or executable updates from Online Updates.
The Trial versions available for download include the latest executable and driver database versions.
Trial versions of the UIU for MDT may shut down the operating system of target machines where trial images are deployed. Notification or warnings may be displayed during the installation of the UIU for MDT on the MDT server as well as on target machines after deployment.
Deployments to target machines using a Trial version of the UIU for MDT are designed for test environments only, and shall not be deployed to live environment PCs.
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.
The Trial version of the UIU will install a Trial Background for the Windows login screen and all users. This Trial Background is not included in the licensed version of the UIU.
Section 7: Updating the UIU for MDT
The UIU will be updated from time to time with code changes, feature additions and periodic driver database updates. These updates may be performed through an online updating service offered by Big Bang LLC or through a manual method initiated by UIU Support. The Updater application also provides Contact information and documentation references.
Online Updates (Where the MDT server is Internet-aware)
If the MDT server on which the UIU for MDT has been installed has access to Internet services over HTTP (port 80), UIU Online Updates may be invoked through an UIU Updater application that remains running and available in the system tray.
UIU Check For Updates
When the Updater application starts or the schedule set in Options, an attempt to contact Big Bang LLC’s Online Update service will be made to identify UIU Program or Driver Database updates.
If updates are available, the following screen is displayed indicating the specific version of the program or driver database that is in use and the newer version that is available.
UIU Updates Available
Select “Update Now” to apply new versions of the UIU program or the Driver Database.
Scheduling Online Updates check
The UIU Updater application may be set to check for updates made available through Big Bang LLC’s online update service. In the Options Menu, the Updater application may be set to “Do Not Automatically Check for Updates” or to “Automatically Check for Updates” at a specified time period selectable by day of the week and time of day. A selection of Download Mirror sites are presented and one may be chosen to ensure efficient downloads regardless of geographic location.
UIU Updater application - Options
UIU Set Temporary Location - Options
In order to allow temporary files associated with Online Updates to be stored in a location other than the default folder (C:\Program Files\UIU\Data
), an option is provided to allow for selection of alternate temporary file storage. This temporary file store will be cleared after Updates are applied.
Update in Progress
Manual Update - UIU plug-in for MDT (executables)
If the PC/server on which the UIU has been installed does not have access to Internet services, the UIU offers an alternative method to apply program updates.
Download the UIU plug-in executable package from UIU Support Downloads
Extract all files from the compressed download and save all files to a directory on the PC/server on which the UIU has been installed.
If the existing uiupluginupdater.exe is already running (as evidenced in the system tray), close the existing UIU Updater from the system tray on the PC/server which the UIU has been installed.
Copy the newly downloaded and extracted uiupluginupdater.exe to the installed location on the PC/server which the UIU has been installed, replacing the existing, older uiupluginupdater.exe; (default location is C:\Program Files\UIU\bin or C:\Program Files (x86)\UIU\bin, depending upon PC architecture). If the UIU plug-in for MDT repository has been installed in a non-standard location, please be sure to copy the newly downloaded and extracted uiupluginupdater.exe to the \uiu\bin folder in that location. NOTE: If the UIU Updater to be replaced is called uiumdtupdater.exe, please contact UIU Support as additional steps may be required.
Run the new uiupluginupdater.exe from the location to which it has been copied; (default location is C:\Program Files\UIU\bin or C:\Program Files (x86)\UIU\bin, depending upon PC architecture).
Manual Update - UIU plug-in for MDT (driver database)
If the PC/server on which the UIU has been installed does not have access to Internet services, the UIU offers an alternative method to apply driver database updates.
Download the UIU plug-in UIU Driver Database package from UIU Support Downloads
Extract all files from the compressed download and save all files to a directory to which the UIU Updater will have access.
If it is running, open the UIU Updater from the system tray on the PC/server which the UIU has been installed. If it is not running, launch the UIU Updater from C:\Program Files\UIU\bin or C:\Program Files (x86)\UIU\bin, depending upon PC architecture.
Navigate to Options (left hand side menu).
Select “Import UIU DAT”.
Browse to the directory to which the uncompressed file(s) were saved (a green box will indicate that valid updates were found).
When the import completes, close the “Import DAT” window to return to the main Updater panel.
If the UIU program is to be updated, please remember to close the the Microsoft Deployment Toolkit and note that if updates include GUI changes, it may be necessary to remove and re-add the UIU Machine Configuration task to all applicable sequences. Please refer to online release notes for details.
Do not attempt to modify the UIU Package by any means other than the UIU Updater application as this will render the UIU inoperable.
Update License Key
In the event that a UIU license key must be updated, this function may be performed from the Home (UIU) screen of the Updater Control Panel, which is located in the system tray. If the UIU Updater has been closed, it may be re-launched from C:\Program Files(x86)\UIU\bin\UIUPluginUpdater.exe.
Update License Key - Menu Selection
Navigate to the Home (UIU) menu item and select "Update License Key" from the bottom of the Updater Control Panel screen.
Note: the "Update License Key" option is only available when "No Updates Available" is displayed.
Enter new UIU License Key for validation.
Select "OK" to proceed.
Section 8: Creating Custom Driver Packages
UIU Support may provide you with a UIU Custom Driver Set in order to troubleshoot driver issues within your environment. At this time the implementation of these custom sets will be manual.
During Task Sequence editing, while modifying the properties of the UIU Machine Configuration
task, an “Additional Command Line Arguments” text box is made available to augment the execution of the UIU for MDT plug-in.
In the case where UIU Support has requested that a custom driver be added for testing and field verification, the following custompath
switch would be applied in that text box.
The switch syntax for adding custom drivers is:
The variable <unc-path-to-custom-drivers-folder> denotes a UNC path to a folder containing the applicable “custom” drivers. This path must be accessible by the same network credentials used to run the UIU Machine Prep task. It is recommended always enclosing this path in double quotes.
In this example, DeploySRV1 is the server name. The custom folder should be created and populated before applying this “Additional Command Line Argument”.
Note: The location of the custom files need not be in the same location as the UIU Driver Repository as long as it is accessible by all target PCs during OS deployment and with the same network credentials as the UIU Driver Repository.
Section 9: 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.
When using the UIUDT to either pre-determine if drivers will be missing, (potentially leading to blue-screen BSOD errors) or when experiencing driver “bangs”, Support will be notified of the specific driver(s) either automatically based on Internet connectivity or when you submit the results file to UIU Support
How do I get the UIUDT?
The new UIU Discovery Tool v2.0 may be downloaded from UIU Support Tools Download
How do I run the UIUDT?
The UIUDT process has changed! Please refer to the UIUDT v2.0 Instructions before attempting
to execute the new UIUDT.
Section 10: 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):
Direct Telephone Support: 414-369-5020
(M-F 9:00am-5:00pm Central:GMT-6)
Email Support: email@example.com
Send UIU Support an email
When contacting support, please be ready to provide the following information:
The MDT system must be tested and proven capable of deploying a supported Windows operating system independently, (without the UIU plug-in for MDT software.)
Version of the UIU plug-in for MDT
Revision of the Driver Database (including Custom Driver Packages, and any MDT Driver Packages)
UIU License Key
Version of MDT (2012 or 2013)
Version of Windows Server OS including Service Pack
Process used to create an operating system image used in the Install Task Sequence, (Build & Capture, DISM\ImageX Capture, etc.)
PC Operating System and Service Pack
PC Make/Model of Recipient (deployed to) machine(s)
UIU log file (C:\Program Files\UIU\UIULog.htm)
Nature of the Problem; Blue Screen, Continual Reboot, Missing Hardware Driver, etc.
In situations relating to UIU Plug-in for MDT failures, please be able to provide the following files from the MDT server:
UIU Plug-in log file (C:\ProgramData\UIU\UIU_Plugin.htm)
In situations relating to missing or incorrect hardware drivers, please be able to provide the following files from the Recipient Machine:
UIU log file (C:\Documents and Settings\<administrator account name>\Application Data\UIU\UIU.log)
SETUPAPI Log (C:\windows\setupapi.log)
Windows 7, 8.1 and 10 (32-bit or 64-bit)
UIU log file (C:\ProgramData\UIU\UIU.log) ~ hidden directory by default
SETUPAPI Log (C:\windows\inf\setupapi.dev.log) -- Windows 7 only
SETUPAPI Setup Log (C:\windows\inf\setupapi.setup.log) -- Windows 8.1 & 10 only
NOTE: Technical Support and Updates are only available for operating systems and hardware currently supported by the UIU. Please see the section titled “Section 1: Requirements and Limitations” for more details.
Please review this User Guide
the Universal Imaging Utility plug-in for MDT.