ADMT v2 + XP SP3 - broken?

Did another Domain migration last week.

Followed my guide featured previously in this blog, except that we used ADMT v2 rather than v3 (it has been buggy in testing).

As it turns out, there was only (luckily) one XP Professional workstation that had been upgraded to SP3, and this was the only workstation that refused to run the ADMT conversion. Since it was only one machine, I manually migrated it, and didn't look into it further.

So ADMT v2 + XP SP3, beware!

Comments

[Rob]

Granted this is a fairly old post but things haven't got much better with ADMT 3 so it deserves a bump. I've just completed a major inter domain migration and SP3 machines, in particular IBM T60 laptops just won't budge. Funny that any earlier service pack work a treat (not good in a SOx compliant office). Having to resort to the inbuilt profile migration tool, manual migrations or registry hacks just don't cut it for me as an admin, nevermind the latter headaches. It gives validation to me (and management) that the only reason we use Windows (now virtual) in our environment is for Office. Everything else they have produced recently has been unfortunately sub-standard. Shame really.

[Victor Hong]

Rob, I agree ADMT 3 isn't much better, that's why we have stuck with v2 on AD migrations since it seemed to be the least buggy... but then this SP3 thing just makes me shudder! Yup, VDI is the only way to go now!

:S

Vic