USMT in my Task Sequence is not copying user files if the computer is not able to be joined to the domain. Is this acting as designed?
I haven't used the XP to Windows 7 migration task sequence in Production yet because of this. I've been testing it over and over again. When I kick the Task Sequence off, according to the logs, it is copying all of the user files/settings to
the hardlinked folder. Obviously, the computer will already have an account in AD. If I forget to delete that computer account before the task sequence tries to add the computer to the domain, I lose all of the user data. This could be a
disaster if this happens in production. Is this an expected behavior? Or is there something I am missing?
December 22nd, 2010 4:26pm