I was able to fix this issue. The problem was the scheduled (logon-triggered) tasks running under the Admin.NBName account. Once one of these tasks started, the SID of the Admin.NBName would be loade...
See more...
I was able to fix this issue. The problem was the scheduled (logon-triggered) tasks running under the Admin.NBName account. Once one of these tasks started, the SID of the Admin.NBName would be loaded under HKEY_USERS and AppVol virtualization would capture both HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileGuid & HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileGuid. Since the Admin.NBName SID already existed on the master image, a SID-bak key would be created and the SID key would then get one of these new TEMP paths. The solution was to convert the scheduled tasks to run under the SYSTEM account, which took some work for the task that was accessing UNC paths and changing AD attributes. After I had converted the tasks to SYSTEM tasks, I was able to completely remove the Admin.NBName profile from the master image. No more problem.