Can't speak to Bindview, but for your listed problems:
 
1-All migrated accounts, accessing all resources in the source domain show the problem? Can you verify with ADSIEdit that the SIDHistory attribute is populated on the migrated accounts?
 
2-We occasionally ran into profile migration problems, but it was a low percentage. You definitely want the user to be logged off, and you will increase your chances of success if you reboot the macine prior to the migration and don't login until after it automatically reboots post-migration. This insures that the ntuser.dat files aren't held by processes preventing the migration agent from acting.


From: Ellis, Debbie [mailto:[EMAIL PROTECTED]
Sent: Friday, November 07, 2003 10:19 AM
To: '[EMAIL PROTECTED]'
Subject: [ActiveDir] Bindview and ADMT

Have any of your guys used the Bindview Migration tool?  We have been testing the newest ADMT but have run into several problems that are listed below.  Have any of you had similar problems?

 

  1. If a member of the domain admin or domain user group is migrated, there are problems with accessing the resources in the source domain.  SIDhistory was migrated and instructions from ADMT were followed.
  2. There are problems migrating the local profiles on the user's desktops.  It shows they were migrated over and no error message in the log files, but they were not migrated.  We have tried with the user logged off and logged on.

 

Reply via email to