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).
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 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: 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: 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: 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.
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