This time last year we did our Win7 roll out, coupled with a domain change. To do this, we used SCCM w/ USMT to capture their XP machines and migrate everything across - everything went fine, or so I thought...
We just implemented a new proxy server and upon checking out the old one to ensure that everyone was off it, we noticed ~20 or 30 users still using it. When I looked into these users applied policies, they were all appearing as the following:
User name UKDOM\Some.User
Last time Group Policy was processed 11/08/2012 13:22:48
Group Policy Objects
Applied GPOs
Name
Link Location
Revision
Default Domain Policy old.ukdomain.org AD (2), Sysvol (2)
USR/PA Applications Policy old.ukdomain.org/UK AD (1), Sysvol (1)
WKS/StartupScripts old.ukdomain.org/UK AD (1), Sysvol (1)
USR/Default Users Policy old.ukdomain.org/UK AD (73), Sysvol (73)
USR/ProxySH old.ukdomain.org/UK AD (36), Sysvol (36)
App/Prohibited Apps Policy old.ukdomain.org/UK AD (4), Sysvol (4)
It should be noted that when we did the USMT, we did a profile switch whereby we logged in as their NEWDOM\Some.User account, and provisioned that over their UKDOM\Some.User profile (regedit > load hive > set perms etc) - this worked perfectly fine for the 99% - but it's this 1% which is being a pest.
Apart from recreating these guys with a new profile which seemingly works, I was wondering if there was some other way of getting around this and fixing the issue rather than brute forcing it and causing my helpdesk bods a load of work in recreating 30 odd users profiles?