I'm still having a problem getting our migrated profiles to load. We are migrating from 2003 roaming profiles to 2008. I am manually typing in the path to store the migrated profiles to prevent the mapped drive error I was having before. The profiles migrate successfully from first.last to first.last.wpaog.v2. I am not automatically updating the Terminal Services Profile Path on the user's AD account. When I then update the path to the new profile location and then log into a 2008 terminal server I keep getting a new profile. The newly migrated profile does not load. We have a 2003 AD environment. Here's what I've tried so far.
1. I've used all variations of the newly migrated profile name (first.last, first.last.wpaog, first.last.wpaog.v2 and first.last.v2.
2. I've gone to the new profile folder and added the user to the security list and/or gave them full rights and ownership.
Once again this is probably a simple and obvious thing.
This was an error on my part. I was trying to use a single migrated profile and assign it to a different domain accounts to test various logon scenarios without burning up our licenses on test accounts. Lesson learned!
Ned
I do have another problem heading your way....stay tuned.