none
The UAL and UE switches still do not appear to work together even after upgrading to USMT 5 RRS feed

  • Question

  • We are in the process of implementing OSD via SCCM 2012 (using MDT 2012 integration).  We are using USMT 5 via WADK 8 and initially will be doing USMT backup and restore via an HTA running separate from the task sequence (SMP role will be setup at a later date).  The problem is that the UEL switch is not working despite the claim that it was fixed in USMT 5 (see link below).

    The UEL switch was used in our environment with USMT 3 successfully and then removed with USMT 4 since it did not work. The specific issue seems to be that time and date for the NTUSER.DAT on old profiles is getting updated when running ScanState.exe.  From what I understand, this is what is used to determine the last logon date each given profile.  Anyone see this issue?

    Friday, November 1, 2013 7:22 PM

All replies

  • The problem in USMT 4 is that /UEL (User Exclude based on last logon) is actually an include rule that takes presedence. People usually have to separate the commands. eg. UEL on ScanState and UE on LoadState.

    Ned Pyle explains the new changes here.

    UEL and UE - In USMT 4.0, a /UEL exclusion rule would override the processing of a /UE exclusion rule, even though it was likely that if you were setting UE because you had specific need. USMT now returns to the USMT 3.01 behavior of UE overriding UEL.


    Blog: http://scriptimus.wordpress.com

    Friday, November 1, 2013 7:47 PM
  • Also, ScanState no longer messes up the NTUser.dat timestamp in USMT5(allegedly). 


    Blog: http://scriptimus.wordpress.com

    Friday, November 1, 2013 7:49 PM