Symptoms: If no DP locations respond to ping (within 200ms), UIUPrep fails to service drivers to the target machine. Resolution: UIUPrep pings each accessible Distribution Point (Package path) when attempting to discern from which to source the UIU Repository. This change continues to ping each path (and will use it for sorting purposes if provided multiple valid options if otherwise unable to determine the 'best', 'nearest' path), but no longer invalidates a path if it does not respond (or fails to respond within 200ms.)
Details: In accordance with the SCCM(MDT) Task Sequence engine, the UIUPREP application will now return an error code (1) in the event that a condition required for the UIU to function efficiently or completely has not been satisfied. SCCM and MDT users should be able to control whether or not Task Sequences continue under the "Options" panel of their UIU Deployment Configuration step via the "Continue on error" control.
Details: Our Support team has completed a comprehensive review of the UIU Driver Database, particularly with respect to its inclusion of unsigned drivers. In previous versions, when the "Signed Drivers Only" option had been selected, unsigned drivers may have been delivered to target machines but not employed. As of UIUPREP version 5.8.4.0, handling of unsigned drivers has been optimized to ensure that they are not even delivered to target machines when the "Signed Drivers Only" option has been selected.
The UIU Plug-ins 2.0 with SCCM (as of UIU 2.2.2.x) now requires the .NET 4.6 Framework.