Device driver additions and modifications since the April 12, 2021 Release.
Symptoms: Nvidia software security update – ALL GPU product lines Nvidia reported a security issue with their entire catalog of graphics drivers in mid-December 2020, citing, “NVIDIA has released a software security update for NVIDIA® GPU Display Driver. This update addresses issues that may lead to denial of service, escalation of privileges, data tampering, or information disclosure.” (Security Bulletin: NVIDIA GPU Display Driver - January 2021) Resolution: As a consequence, and in an effort to not include drivers known to contain security flaws within the UIU Driver Database, UIU Support has undertaken the extensive effort to not only remove reportedly affected drivers but also to include the new, secured drivers as offered by Nvidia as of January 2021. The UIU Driver Database (release DB-21-01-26) contains only the newly-released drivers from Nvidia and, despite our best efforts, may result in a gap in coverage for select associated hardware IDs. As it is not feasible for Big Bang’s lab to host every conceivable Nvidia product, we’ve attempted to provide coverage for all modern Nvidia product hardware IDs. If it is determined that we’re missing coverage, and Nvidia has provided a secured, newly-released driver, UIU Support will consider it their highest priority to include that driver in the next release of the UIU Driver Database. Your continued patience is appreciated. Furthermore, UIU Support is committed to regularly revisiting Nvidia’s Security Bulletin in an attempt to discover any newly-released drivers post DB-21-01-26 release. NOTE: Compromised Nvidia drivers will continue to exist in established UIU Repositories until UDBs prior to and including DB-21-01-26 are removed and updates are performed with the "cleanup" feature. Please contact UIU Support with questions or concerns. NOTE: Customers may notice a reduction in the size of the UIU Repository depending on configuration and this is expected. Please contact UIU Support with questions or concerns.
Details: Microsoft ended support for the Windows 7 operating system on January 14, 2020. UIU Support has recorded a marked reduction in support requests regarding the deprecated OS and has also reported a distinct lack of Windows 7 drivers offered for newly introduced hardware. As we continue to work on our driver streamlining process, we have noted that Nvidia has elected to not produce secured drivers for Windows 7-based hardware IDs. We have therefore determined that it is an appropriate time to remove Windows 7 from our full driver database release. Two static Windows 7 only driver databases will be made available on demand; one (based on DB-21-01-26) that contains no Nvidia drivers (all previous drivers are presumed to be compromised), and one (based on DB-20-12-29) that contains the Nvidia drivers as represented prior to Nvidia's Security Bulletin: NVIDIA GPU Display Driver - January 2021. Please contact UIU Support for more information. As of this release, no additional Windows 7 drivers will be added to the UIU Driver Database.
Details: UIU Support has recently witnessed several situations wherein updating of firmware addresses specific driver issues. See Release Notes from June 16, 2020 for two examples. UIU Support strongly recommends that, if customers are experiencing issues, the firmware (BIOS/UEFI) be updated immediately. If the target machine continues exhibiting issues, please contact UIU support for additional troubleshooting.
The full driver database exceeds 20Gb in size (20.8 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.
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 UIU Classic Mode (as of UIU 5.8.0.x) requires the .NET 4.6 Framework.
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.
Symptoms: Warning flagged in log with WSA Error: 11001. Resolution: Behavior of UIUPrep modified to account for discrepancies in located package paths.
Symptoms: SCCM halts with Error while running UIU Deployment Configuration step. UIU.log in WinPE ends with “Client Site Name: (null)”. Resolution: Behavior of UIUPrep modified to account for unexpected returns from AD Site variables.
Details: Added a "-smsforceclr" switch which may be included in the UIU task element under the options tab in order to allow NOMAD-enabled deployments to consider distribution point package shares in addition to NOMAD cache locations. This only affects NOMAD-enabled deployments.
Details: Added a "-forceipaddressing" switch which may be included in the UIU task element under the options tab in order to allow UIUPREP to use IP addresses as opposed to machine names for determination and access of UIU repository content.
Details: Added a "-packagepath "\\path\one, \\path\two, \\path\three"" switch which may be included in the UIU task element under the options tab in order to allow UIUPREP to use the existing SCCM network access account to access package path locations without requiring the "-networkresource" switch. Customers using the "-packagepath" switch no longer are required to use the "-networkresource" switch in order to access UIU package path locations if those locations have been configured to allow the SCCM network access account default access to those locations. This should eliminate the use of the cumbersome "-networkresource" switch when supplementing customer-maintained UIU repository locations in addition to SCCM distribution point locations. For more information, please contact UIU Support.
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 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.
April 19, 2021 - RELEASE
This is an update of the UIUPREP application ONLY.
Symptoms: UIUPREP failed to located a NOMAD cache under specific circumstances. Resolution: Updated the PSR cache selection logic.
Symptoms: In environments where a distribution point does not have a local management point, the UIU may receive a location via CLR that is not local to the target machine. This frequently causes longer UIU run times than desired. Resolution: Updated the ADSITE resolution logic to more accurately determine local distribution point location(s).
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.
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.
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.
UIU Support
Device driver additions and modifications since the March 25, 2021 Release.
The full driver database exceeds 18Gb in size (18.8 Gb IMP). Please follow the guidelines below for optimal performance. This database release still covers Windows 7 through Windows 10 (64-bit only).