DB-20-06-16 Driver Database Update Make-Model DB-20-06-16.pdf UIU DB-20-06-16 Drivers.pdf --> June 16, 2020
Customer-requested drivers since May 7, 2020 Release. Includes DB-20-05-15 release.
See Attached: UIU DB-20-06-16 Drivers.pdf
See Attached: Make-Model DB-20-06-16.pdf
Symptoms: It has been observed in several instances that some applications of Intel chipsets may overheat when utilizing more recent driver sets combined with older BIOS/UEFI firmware versions. Resolution: UIU Support strongly recommends that, if customers are experiencing an overheating issue, the firmware (BIOS/UEFI) be updated immediately. If the target machine continues overheating, please contact UIU support for additional troubleshooting.
Symptoms: Various hardware models which include the Intel(R) Smart Sound Technology (Intel(R) SST) OED component experience driver bangs post-deployment. Resolution: Updated Audio Driver set to correct issues across multiple machines. If the problem persists, UIU Support strongly recommends that the firmware (BIOS/UEFI) be updated immediately. If the problem persists, please contact UIU support for additional troubleshooting.
The full driver database exceeds 31Gb in size (31.4 Gb IMP). Please follow the guidelines below for optimal performance. This database release still covers Windows 7 through Windows 10 (64-bit only).
USB Flash drives need to be formatted with the NTFS file system before the driver database will successfully transfer. Network share access is recommended.
The Big Bang Support Team would like to remind our customers to please clear out any drivers represented in the Custom folder(s) prior to testing with a new version of the UIU Driver Database as neglecting to do so may result in false negative installations. Please contact a UIU Support representative with questions or concerns.
Customer-requested drivers since April 28, 2020 Release.
The full driver database exceeds 31Gb in size (31.1 Gb IMP). Please follow the guidelines below for optimal performance. This database release still covers Windows 7 through Windows 10 (32/64bit).
The Big Bang Support Team would like to remind our customers to please clear out any drivers represented in the Custom folder(s) prior to testing with a new version of the UIU Driver Database as neglecting to do so may result in false negative installations. Please contact a Support Representative with questions or concerns. Thank you!
April 30, 2020 - RELEASE
This is an update of the UIUPREP application ONLY. Changes in this version of the UIUPREP application do not affect the UIU Classic Mode product.
Details: Added a "-cmautoimportrepository" switch for UIU Classic Mode: This switch enables Classic Mode CLI to automatically discover a UIU Repository Import (IMP) file in the same directory as the Classic Mode executable. In the event that multiple IMP files exist, the first (alphanumerical) entry is selected, based on file name. This switch is overridden by the -cmrepositoryimportpath switch, so if a user provides both, the value provided by -cmrepositoryimportpath is selected. If the -cmautorepositoryimport switch is provided and Classic Mode is unable to locate any IMP files, Classic Mode writes an error dialogue ("Classic Mode does not continue automatically if the -cmautorepositoryimport switch is provided and cannot locate a UIU Repository Import (IMP) file.") and exits. For more information, please review the UIU Classic Mode User Guide
Symptoms: Servicing older Windows PE media (3.x & 4.x) requires 32-bit specific binaries (DISM) which do not load under a 64-bit process, resulting in error conditions. Big Bang recommends that Winodw PE version 10 be employed. Contact UIU Support for additional information.
The original UIU 4.x — known in recent years as the UIU Classic — accommodated all OS deployment solutions, including those that do not utilize Microsoft's Windows PE, by storing the entire UIU Driver Database within the OS image. The UIU Classic Mode is an updated version of that methodology for those users that do not use a WinPE-based deployment solution.
The UIU Classic method has been integrated into a optimized modern GUI, (though the basic process was preserved as much as possible for ease of adoption).
Users employing OS deployment solutions that are not based on Windows PE (e.g. Linux-based solutions like CloneZilla and FOG)
Please refer to the UIU Classic Mode - User Guide for detailed implementation and usage instructions.
The UIU Classic Mode (as of UIU 5.8.0.x) requires the .NET 4.6 Framework.
UIU Support
This is an update of the UIUPREP application ONLY. Changes in this version of the UIUPREP application do not affect the UIU 5 product.
Details: UIU proxy support has been included, including new support for CLI. This new development should facilitate proxy support (address/port), and optionally, a username/password.
Symptoms: Unhandled Error exception when attemptin to import an IMP file. Resolution: Code modified to corrctly import IMP files.
Symptoms: When employing ADK options in UIU with ADK 1803 installed on the UIU 5 Console machine, DISM commands fail to execute properly. This issue is under investigation. Work-Around: When employing ADK options, please use an earlier version of Microsoft ADK on the console machine, (e.g. ADK 1709). Resolution: With ADK 1803 installed on the UIU 5 Console machine, a pop-up window stating "Using Windows 10 or later" will be presented. Selecting the "OK" button will allow the ADK process to proceed. Alternatively for unattended operations, an earlier version of ADK should be employed, (e.g. ADK 1709).
The UIU 5 (as of UIU 5.7.x.x) now requires the .NET 4.6 Framework.
This (and future) versions will require Driver.imp files (e.g. DB170411-p5460.imp) for those operations. Online UIU 5 Updates will be unaffected..
Details: On deployed machines only, the Log folder & UIU data folder have been migrated from Program Files to ProgramData. UIU log files on deployed machines are now located under the ProgramData\UIU directory. Additionally, resources needed by each application are extracted/placed in the ProgramData\UIU\bin directory (temporarily). Program Files is no longer used for any resources or logs. NOTE: The UIU 5 Installation log files are also now located in ProgramData\UIU; other install files remain in Program Files.
Symptoms: When integrated with the UIU, the Microsoft Management Console snap-in fails in error after selecting OK or APPLY in a task sequence that contains the UIU task element. Resolution: The integration components have been modified to correct the issue.
Symptoms: In some environments, when selecting apply in the UI Deployment Configuration task sequence element, the apply function causes an exception, resulting in a failed plug-in configuration. Resolution: The UIU plug-in apply process has been modified to handle errors properly and not throw an exception.
Symptoms: Servicing older Windows PE media (3.x & 4.x) requires 32-bit specific binaries (DISM) which do not load under a 64-bit process, resulting in error conditions. Big Bang recommends that Windows PE version 10 be employed. Contact UIU Support for additional information.
To download Microsoft Deployment Toolkit (MDT), build 8456, click the following link: Microsoft Deployment Toolkit (MDT) v6.3.8456.1000
Please refer to the UIU Plug-ins 2.0 - MDT User Guides for detailed implementation and usage instructions.
The UIU Plug-ins 2.0 is a versatile solution that may be invoked though the standard MDT Deployment Workbench interface via a task element (UIU Deployment Configuration) or directly through a Run Command Line task element. Furthermore, The UIU may be invoked manually from within a Windows PE session under the direction of UIU Support. Multiple modes of operation have been provided to accommodate environmental differences as well as policy/change control restrictions.
In MDT, integration consists of the inclusion of a uiusms.dll in the "C:\Program Files (x86)\Microsoft Deployment Toolkit\bin" directory as well as a modification (additional section appended) to the Actions.xml file in the same directory. If integration is not desired or permitted, an Administrator may launch the UIU Plug-ins 2.0 from a Run Command Line task element (with the correct arguments) to achieve a successful result. For more information on alternative methods of invoking the UIU Plug-ins 2.0, Please contact UIU Support.
This version of the UIU requires the use of UIU IMP files to establish a UIU Repository from locally existing files. If bandwidth allows, Big Bang recommends that the UIU Repository be established (and regularly updated) from Big Bang's Online Updates resources. UIU DAT files are not supported. UIU Import files (*.IMP) contain required driver files, driver database(s) and UIU components which are used to populate a UIU Repository from which deployed target machines will draw necessary files during OS deployment Task Sequence executions. These files are used in conjunction with the UIUPM.
Symptoms: When using the CLI feature of the UIUPM application to perform updates against a repository, the updates may not complete fully. Resolution: Development to alleviate this issue is ongoing.
Symptoms: UIUPM behavior will stall at "Refreshing" when selecting the Microsoft System Center Configuration Manager option under the Microsoft menu. -or- On a dedicated Provider, the operations framework is not installed when performing an install operation. Resolution: These instances currently require a manual installation process. Contact UIU Support for details. Development for a resolution is ongoing.
Symptoms: In some SCCM environments, when installing or updating the UIU plug-in, some SCCM task sequences cannot be accessed by the UIUPM application when attempting to modify the task sequence with current UIU license key information, resulting in a failed plug-in installation. Resolution: The UIU plug-in installation/update process has been modified to not fail on error when processing task sequence UIU license key updates. It is advisable to review the log to determine which (if any) task sequences failed to update properly. A manual process can still be performed on the affected task sequences. Contact UIU Support for more information. Further development regarding this issue is ongoing.
Symptoms: When SCCM has been configured to utilize "HTTPS ONLY" (Native Mode), the UIUPREP application running in WinPE fails to locate a UIU Repository Package with the UIU Deployment Configuration task sequence element configured for UIU Hybrid OS deployments. Resolution: Support for "HTTPS ONLY" (Native Mode) when using UIU Hybrid OS deployment configuration has been added. This solution requires UIUPREP.EXE v5.10.0.0 or newer. Please contact UIU Support for more information.
Symptoms: When UIUPREP calls Nomad PSR, which returns machine name, the subsequent DNS translation may provide an incorrect IP address in cases of DNS scavenging. Resolution: UIUPREP (5.10.0.0 or newer) will now resolve the machine name provided by Nomad PSR and use the associated IP address when verifying a Nomad peer/cache and when downloading files.
Please refer to the UIU Plug-ins 2.0 - SCCM User Guides for detailed implementation and usage instructions. The UIU Plug-ins 2.0 for SCCM version 2.1.0.0 (or newer) also includes support for 1E Nomad/Active Efficiency. Please contact UIU Support for details.
The UIU Plug-ins 2.0 is a versatile solution that may be invoked though the standard SCCM Console interface via a task element (UIU Deployment Configuration) or directly through a Run Command Line task element. Furthermore, The UIU may be invoked manually from within a Windows PE session under the direction of UIU Support. Multiple modes of operation have been provided to accommodate environmental differences as well as policy/change control restrictions.
In SCCM, integration consists of the inclusion of a uiusms.dll in the "C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\bin" directory as well as the addition of necessary WMI classes (MOF) to support the UIU Plug-ins 2.0. If integration is not desired or permitted, an Administrator may launch the UIU Plug-ins 2.0 from a Run Command Line task element (with the correct arguments) to achieve a successful result. Furthermore, if an Administrator is not able to control the configuration of various SCCM Remote Console implementations (distribution of a single UIU dll file), the integration of the UIU Plug-ins 2.0 may prove to be problematic and utilizing the Run Command Line task element will alleviate those issues. For more information on alternative methods of invoking the UIU Plug-ins 2.0, Please contact UIU Support.
April 28, 2020
Customer-requested drivers since April 24, 2020 Release.
See Attached: UIU DB-20-04-24 Drivers.pdf
See Attached: Make-Model DB-20-04-28.pdf
April 24, 2020
Customer-requested drivers since April 13, 2020 Release. Due to rapid releases and COVID-19 preparation these release notes are related to DB-20-04-16.
See Attached: Make-Model DB-20-04-24.pdf
Symptoms: Various hardware models which include the Intel(R) Smart Sound Technology (Intel(R) SST) OED component experience driver bangs post-deployment. Resolution: Updated Audio Driver set to correct issues across multiple machines.
DB-20-04-13 Driver Database Update DESCR: DB-20-04-13 Driver Database Update Make-Model DB-20-04-13.pdf UIU DB-20-04-13 Drivers.pdf --> April 13, 2020
Customer-requested drivers since March 20, 2020 Release. Due to rapid releases and COVID-19 preparation these release notes are related to DB-20-04-06.
See Attached: UIU DB-20-04-13 Drivers.pdf
See Attached: Make-Model DB-20-04-13.pdf
The full driver database exceeds 30Gb in size (30.9 Gb IMP). Please follow the guidelines below for optimal performance. This database release still covers Windows 7 through Windows 10 (32/64bit).
March 20, 2020
Customer-requested drivers since March 3, 2020 Release. Due to rapid releases and COVID-19 preparation these release notes are related to DB-20-03-06, DB-20-03-07, & DB-20-03-13.
See Attached: UIU DB-20-03-20 Drivers.pdf
See Attached: Make-Model DB-20-03-20.pdf
The full driver database exceeds 30Gb in size (30.7 Gb IMP). Please follow the guidelines below for optimal performance. This database release still covers Windows 7 through Windows 10 (32/64bit).