866-754-3592

SCCM Plug-in User Guide



Section 1: Requirements and Limitations

UIU Supported Hardware and SCCM Environment

Any PC machines, OEM hardware, or "white-box" hardware containing business-class components will be supported.


All supported hardware must meet the following minimum criteria:

  • PCs must contain at least 1Gb of free hard drive space


  • PC hardware must meet Microsoft requirements for applicable Operating System(s)


  • Note: Any BBLLC-produced list of supported hardware may not be complete and is subject to variation due to market advancements. (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.)

    The supported SCCM environment must meet the following criteria:

  • SCCM 2007, 2012 or 2012 R2 Primary Site Server (or Central Site server) Internet access – Required for UIU product Updates (Live ONLY)


  • The SCCM environment must be sufficiently designed to replicate the UIU Package, with approximately 1Gb available on the Primary Site Server and 20Gb available on each Distribution Point to be used.


  • Supported Deployable Operating Systems:


  • 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)


  • Technical Support Requirements

  • The SCCM 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


  • Limitations

    The UIU is not designed to image Windows Server operating systems and no technical support will be provided.

    Security Access Considerations

    A network access account other than a domain administrator account must be specified for software distribution point(s) in SCCM 2012. It is recommended that an account be specifically created for that purpose. We encourage you to reference Microsoft SCCM 2012 documentation for required specific privileges.

    The following section has been excerpted from the following Microsoft TechNet article and copyrights are attributed to Microsoft: Configuring Content Management in Configuration Manager

    Configure the Network Access Account

    Client computers use the Network Access Account when they cannot use their local computer account to access content on distribution points; for example, this applies to workgroup clients and computers from untrusted domains. This account might also be used during operating system deployment when the computer installing the operating system does not yet have a computer account on the domain.

    Note
    Clients only use the Network Access Account for accessing resources on the network.

    Grant this account the minimum appropriate permissions to access the software for the content that the client requires. The account must have the Access this computer from the network right on the distribution point. Because you can create only one Network Access Account per site, this account must function for all packages and task sequences for which it is required.

    Warning

    When Configuration Manager tries to use the computername$ account to download the content and it fails, it automatically tries the Network Access Account again, even if it has previously tried and failed.

    Create the account in any domain that provides the necessary access to resources. The Network Access Account must always include a domain name. Pass-through security is not supported for this account. If you have distribution points in multiple domains, create the account in a trusted domain.

    Tip

    To avoid account lockouts, do not change the password on an existing Network Access Account. Instead, create a new account and configure the new account in Configuration Manager. When sufficient time has passed for all clients to have received the new account details, remove the old account from the network shared folders and delete the account.

    Security Note

  • Do not grant this account interactive logon rights.


  • Do not grant this account the right to join computers to the domain. If you must join computers to the domain during a task sequence, use the Task Sequence Editor Domain Joining Account.


  • WARNING: The Network Access Account cannot be configured on a central administration site!


    uiu logo user guide


    Section 2: Definitions


    Deploy or Deployment = Deliver (Advertise or Deploy) a UIU-augmented OSD Install Task Sequence to a Collection of machines

    uiu logo user guide


    Section 3: Quick steps

      1. Select or create the desired OSD Install Task Sequence

      2. Use the Task Sequence Editor “Add” menu feature to select “UIU Machine Configuration” from the “Universal Imagining Utility” item

      3. The UIU Machine Configuration task must be placed after the “Apply Operating System” task in the Install Task Sequence

      4. Modify any UIU parameters as desired

      5. Deploy the modified Install Task Sequence to a Collection or create SCCM Standalone Media to use during deployment


    uiu logo user guide


    Section 4: Distribute the UIU Package

    Distribute the UIU Package

    The UIU installation creates a package (in the Software Library>Application Management>Packages Node of the SCCM Console) called “UIU Package”. This package is not automatically distributed to the SCCM distribution network.

    Navigate to the following node: Software Library>Overview>Application Management> Packages (2012) Computer Management>Software Distribution>Packages (2007)




    Right-click on “UIU Package”


    select uiu package


    Select “Distribute Content” and click “Next” to proceed past the General screen.






    Select desired Distribution Point or Distribution Group(s)


    select distribution point


    Click “Next” and then close the wizard




    uiu logo user guide


    Section 5: Using the UIU plug-in: SCCM 2007

    Open the SCCM Configuration Manager Console on the SCCM Primary Site server (or Central Site Server)

    Create an Install Task Sequence for use with UIU

    Navigate to the following node:
    Site Database>Computer Management>Operating System Deployment>Task Sequence

    Right-click on the Task Sequences node and select “New Task Sequence”



    Select “Install an existing image package”


    create new task sequence


    Click “Next” to continue




    Enter the desired Task Sequence name and select a 32-bit version of a boot image.


    new task sequence information


    Click “Next” to continue




    Select Windows operating system “Image package”


    new task sequence install OS


    Click “Next” to continue




    Enter domain or workgroup information as desired


    new task sequence configure network


    Click “Next” to continue




    Select Configuration Manager Client Package and click “Next”


    new task sequence install configmgr client


    Click “Next” to continue




    Configure User State Migration features as desired


    new task sequence user state migration


    Click “Next” to continue




    Configure “Software Updates” option


    new task sequence include updates


    Click “Next” to continue




    Select “Software Packages” as desired


    new task sequence install software


    Click “Next” to continue



    Click “Next” on the Summary window and close the wizard

    uiu logo user guide


    Section 6: Considering the UIU plug-in: SCCM 2012 (incl. R2)

    Open the SCCM Configuration Manager Console on the SCCM Primary Site server (or Central Site Server)

    You now have to make a decision. How do you intend to approach operating system deployments. In short, you can make them faster or you can make them take up less space…

      1. SCCM 2012’s default methodology: using a technology to compress and store files on distribution points (similar to the WIM technology) & employing a Windows Store methodology wherein applications are copied to the deploying hardware for ‘staging’. This method utilizes less disk space on distribution points and takes longer to execute due to file copy bandwidth limitations.

      2. SCCM 2012 optional methodology: using a ‘network share’ method (similar to 2007) (refer to ‘Copy the Content’ below) wherein network shares managed by the distribution network supply files to SCCM clients as needed. This method utilizes approximately twice the disk space on distribution points and deploys 70-80% faster.

      3. SCCM 2012 custom methodology: If neither method inherent to SCCM 2012 satisfies all of the requirements of your Configuration Manager implementation, rest assured that UIU Support personnel can assist you in finding a method or alternate application of the UIU in order to make it work for you! Chances are, we’ve seen it before!



    uiu logo user guide


    Section 7: SCCM 2012 Optional Methodology Preparations

    In order to utilize the optional method, all non-application packages to be included (including the Configuration Manager Client) in the OS Deployment Task Sequence must have the data access settings changes (refer to the Data Access Requirements section below) applied prior to task sequence deployment. Noting that the included ‘Configuration Manager Client Package’ is not editable, an editable copy of the package will need to be created. Follow the instructions in Configuration Manager Client Requirements below to create an editable copy.

    Configuration Manager Client Requirements

    Right-click “Packages” in the Software Library>Overview>Application Management>Packages node.

    Select “Create Package from Definition”




    Select “Configuration Manager Client Upgrade”


    package definition client upgrade


    Click “Next” to continue




    Select “Always obtain source files from a source folder”


    package definition source files


    Click “Next” to continue


    Select “Network Path (UNC Folder)”

    Browse to source folder
    e.g. Network>Server Name>SMS_x64>Client




    Package Definition


    package definition source folder


    Click “Next” and then close the wizard



    Set the Data Access on the package to “Copy the content in this package to a package share on distribution points:” under Package Share Settings



    Data Access Copy Content


    data access content directly


    Click “OK” to proceed


    This enables the Deployment Option of “Access content directly from a distribution point when needed by the running task sequence”. For more information, See Deployment Considerations in Section 9.

    WARNING: Unless ALL packages referenced by a Task Sequence are configured with Data Access option “Copy the content in this package to a package share on distribution points:” under Package Share settings, the “Access content directly from a distribution point when needed by the running task sequence” option will not be available and deployments will be unsuccessful!

    ††These requirements are necessary to successfully Deploy a UIU-prepared Task Sequence using the "Access Content Directly..." distribution point option. They are not required for a successful deployment using the "Download Content Locally..." distribution point option, or when employing Stand-Alone Media.



    Distribute the Configuration Manager Client Upgrade content


    Data Access Requirements



    Right-click on Package (UIU or other non-application package referenced by a Task Sequence)

    Select “Properties”

    Select the Data Access tab

    Check the “Copy the content in this package to a package share on distribution points:” under the Package Share Settings sub-section



    Copy The Content


    data access copy content


    Click "OK" to proceed



    WARNING: Unless ALL non-application packages referenced by a Task Sequence are configured with Data Access option “Copy the content in this package to a package share on distribution points:” under Package Share settings, the “Access content directly from a distribution point when needed by the running task sequence” option will not be available!

    ††These requirements are necessary to successfully Deploy a UIU-prepared Task Sequence using the "Access Content Directly..." distribution point option. They are not required for a successful deployment using the "Download Content Locally..." distribution point option, or when employing Stand-Alone Media.


    In order to determine which packages are associated with a Task Sequence, highlight the Task Sequence and select the Reference Tab on the preview pane at the bottom of the window to view a list of all referenced packages.



    Task Sequence Package References


    task sequence package references


    –––



    uiu logo user guide


    Section 8: Using the UIU plug-in: SCCM 2012 (incl. R2)

    If modifying an existing Task Sequence, proceed to Adding the Machine Configuration Task step below. Otherwise,

    Create an Install Task Sequence for use with the UIU.

    Navigate to the following node:
    Software Library>Overview>Operation System>Task Sequence

    Right-click on the Task Sequences node and select “Create Task Sequence”



    Select “Install an existing image package”


    create new task sequence


    Click “Next” to continue



    Enter the desired Task Sequence name and select a boot image.



    Welcome Screen


    new task sequence information


    Click “Next” to continue






    Select Windows operating system “Image package”


    select windows operating system


    Click “Next” to continue






    Enter domain or workgroup information as desired


    workgroup or domain


    Click “Next” to continue






    Welcome Screen


    install configmgr client


    Click “Next” to continue


    Select Configuration Manager Client Package and click “Next”

    Select the package created in the Configuration Manager Client Requirements section section above, “Microsoft Configuration Manager Client Upgrade 5.0 ALL”




    Configure User State Migration features as desired


    configure user state migration


    Click “Next” to continue






    Configure “Include Updates” option


    include updates in image


    Click “Next” to continue






    Select “Install Applications” as desired


    install applications


    Click “Next” to continue




    Click “Next” on the Summary window and close the wizard


    uiu logo user guide


    Section 9: Add the UIU plug-in Configuration Task

    Add the UIU Machine Configuration Task

    Select the created OS Install Task Sequence or an existing Task Sequence; right-click and select “Edit”

    Select:
    Add>UIU Machine Configuration

    Drag the task to a point in the sequence between “Setup Windows and Configuration Manager” and “Apply Operating System”, preferably replacing “Apply Device Drivers”.

    There should be no need to utilize the “Apply Device Drivers” task as the UIU will provide all the drivers required. However, it may be useful in special circumstances. Our recommendation is to remove it from the sequence.




    UIU Task Sequence Editor


    uiu task sequence


    Click “OK” to proceed


    Browse for the “UIU Package” in Deployment Packages (the PackageID will be displayed in this field)

    Select Discovery Tool Package if requested by UIU Support and browse to the “UIUDT Package” ** in Software Distribution>Packages

    Select Custom Driver Package if requested by UIU Support and browse to the “Custom Package”** in Software Distribution>Packages

    ** Package names may vary depending upon the process used to create them in SCCM.





    Advanced Features

    Driver - Signed Drivers Only
    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 copied to the target machine.





    uiu logo user guide


    Deployment Considerations

    Right-click on the Task Sequence and select “Deploy” to begin the Deploy Software Wizard

    Complete wizard Deployment Settings as desired and at the Distribution Points step, select “Access content directly from a distribution point when needed by the running task sequence” to allow UIU to function properly.


    Deploy Software Wizard Distribution Points


    deploy software distribution points


    Click “OK” to proceed


    Next, finish the wizard and click “OK” to Deploy the configured Install Task Sequence to the desired Collection of machines.




    WARNING:
    During Deploy Software Wizard; at Distribution Points step, the “Access content directly…” Deployment Option in the drop-down menu MUST be selected in order for the UIU plug-in to function! Refer to the Configuration Manager Client Requirements section section above.

    ††  These requirements are necessary to successfully Deploy a UIU-prepared Task Sequence using the "Access Content Directly..." distribution point option. They are not required for a successful deployment using the "Download Content Locally..." distribution point option, or when employing Stand-Alone Media.


    Helpful Reminder

    In order to realize the optional method’s time savings, the procedures alluded to in the red “Warning” sections are required to enable SCCM 2012 to behave like its predecessor and not copy the packages locally, but instead to access them from selected Distribution Point(s). This procedure eliminates the network intensive copying and allows UIU to perform with minimal network impact.




    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.


    uiu logo user guide



    For Target Machines not connected to a network:

    UIU for SCCM 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, Configuration Manager natively provides a method to produce media for off-network use, (also referred to as Offline Media). The following links will assist in creating effective Configuration Manager offline media including the use of the UIU for SCCM, (USB preferred due to aggregate package sizes):

    SCCM 2007
    How to Create Stand-alone Media in SCCM 2007

    SCCM 2012
    How to Deploy Operating Systems by Using Media in Configuration Manager 2012



    uiu logo user guide


    Section 10: DEPLOYMENT

    What will I see on my deployed machines?




    Boot into WINPE


    Typical Install Task Sequence steps through “Apply Operating System”



    SCCM Client executes the “UIU Machine Configuration” task


    uiu machine configuration


    Settings selected in the UIU Machine Configuration task are initialized and UIUPREP is executed.






    UIUPREP copies necessary UIU Software components


    Copying UIU initializing

    Copying UIU extracting

    Copying UIU copying

    Copying UIU driver database


    UIUPREP copies all necessary executables and supporting files to the target machine.






    UIUPREP Analyzes Hardware Devices


    scanning hardware devices

    analyzing hardware devices


    All hardware components on the target machine are discovered and analyzed for applicable Hardware IDs.






    UIUPREP Copies UIU Required Drivers


    copy 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


    uiu dism session

    uiu adding package

    uiu staging drivers

    uiu shutting down dism


    –––


    UIUPrep installs the copied drivers into the Local Driver Store to be presented to and enumerated by Microsoft mini-setup.



    UIUPREP Completes


    uiu has completed


    Upon completion, UIUPREP will initiate a restart of the target machine.




    RESTART






    UIUPREP Invokes Microsoft’s Mini-Setup to perform Sysprep-related functions and driver enumeration.


    RESTART

    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.

    uiu logo user guide


    Section 11: TRIAL VERSION OF THE UIU

    Trial versions of the UIU may not obtain driver or executable updates from Online Updates.

    The Trial versions available for download include the latest updates.

    Trial versions of the UIU may shut down the operating system of target machines where trial images are deployed. Shut down warnings will be displayed during the installation of the UIU on the SCCM server as well as on target machines after deployment.

    Deployments to target machines using a Trial version of the UIU 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.




    UIU TRIAL product will present the following warning screen upon installation:



    Trial Warning


    uiu trial need key

    uiu trial license key


    –––





    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


    Section 12: Updating the UIU

    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 SCCM Primary Site server is Internet-aware)

    If the Primary Site server on which the UIU 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


    uiu checking for updates


    –––


    When the Updater application starts, either manually or as scheduled in Options, an attempt to contact Big Bang LLC’s Online Update service will be made to identify UIU Program or Driver Database updates.

    Note: The Updater may also be opened by clicking on “Check for Updates” in the SCCM Configuration Manager>UIU Utilities node





    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


    uiu updates available


    –––


    Select “Update Now” to apply new versions of the UIU program or the Driver Database.

    WARNING:

    If the UIU program is to be updated, please remember to close all instances of the SCCM Configuration Manager 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.





    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 and day of the week or month. 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 updater options


    –––







    UIU Set Temporary Location - Options


    uiu updater temporary location


    –––


    In order to allow temporary files associated with Online Updates to be stored in a location other than the default folder (C:\Program Files (x86)\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.




    UIU plug-in for SCCM Manual Update Process (SCCM server is not Internet-aware)

    If the Primary Site server on which the UIU has been installed does not have access to Internet services, the UIU offers an alternative method to apply program and driver database updates.

  • Download the UIU plug-in executable package and/or UIU Driver Database package from UIU Support Downloads

  • Extract downloaded files from the compressed download and save all files to a directory to which the UIU Updater will have access

  • If it is already running, open the UIU Updater from the system tray on the server which the UIU has been installed. If the UIU Updater is not running, launch the UIU Updater from C:\Program Files (x86)\UIU\bin\uiusccmupdater.exe

  • In the UIU Updater, navigate to Options (left hand side menu)

  • Select “Import UIU DAT”. (Note: All applicable files, not just DAT files, will be imported.)

  • Browse to the directory to which the uncompressed file(s) were saved (a green box will indicate that valid updates were found)

  • Click “Import”

  • When the import completes, click “Done” to return to the main Updater panel

  • Don't forget to initiate an “Update Distribution Points” package update in SCCM or schedule a package update as desired


  • WARNING:

    If the UIU program is to be updated, please remember to close all instances of the SCCM Configuration Manager 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.



    WARNING:

    Do not attempt to modify the UIU Package by any means other than the UIU Updater application as this will render the UIU inoperable.




    uiu logo user guide


    Section 13: Creating Custom Packages

    UIU Support may provide you with a UIU Custom Package in order to troubleshoot driver issues within your environment. At this time the creation of these UIU Custom Packages will be manual.

    Future versions of UIU will include a utility to automatically generate the package from a specific source location.

    Create a manual Custom Driver Package

    Receive a UIU Custom Package from UIU Support

    Right-click on the Packages node in SCCM Configuration Manager Console and select the “New > Package” wizard option.




    New Package Wizard - General


    uiu create custom package


    –––



    Enter a name that corresponds to the UIU Custom Package received from UIU Support and include descriptive comments to identify the purpose of the custom driver package.




    New Package Wizard – Data Source


    uiu custom data source


    –––



    Browse to and set the data source location where the received UIU Custom Package was stored.




    Complete the wizard with options required or desired. Distribute the package to distribution points and select the desired UIU Custom Package in the UIU Machine Configuration task of a new or current OSD Install Task Sequence, prior to advertisement/deploy.

    uiu logo user guide


    Section 14: 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?

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


    uiu logo user guide


    Section 15: 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 support, please be ready to provide the following information:

    The SCCM system must be tested and proven capable of deploying a supported Windows operating system independently, (without the UIU for SCCM software.)


  • Version of the UIU plug-in for SCCM
  • Revision of the Driver Database (including Custom Driver Packages, and any SCCM Driver Packages)
  • UIU License Key


  • Version of SCCM (2007 or 2012, etc.)
  • 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 missing or incorrect hardware drivers, please be able to provide the following files from the Recipient Machine:

    Windows XP
  • UIU log file (C:\Program Files\UIU\UIU.log)
  • SETUPAPI Log (C:\windows\setupapi.log)


  • Windows 7, 8.1 and 10 (32-bit or 64-bit)
  • UIU log file (C:\Program Files\UIU\UIU.log)
  • SETUPAPI Log (C:\windows\inf\setupapi.dev.log)


  • 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
    before employing
    the Universal Imaging Utility plug-in for SCCM.