RE: [ActiveDir] Bindview and ADMT

[Fuller, Stuart]

Debbie,   I can speak to problem number 2.  We found during our migration of about 4000 workstations with ADMT v2, that rebooting the workstation right before running the migration made that problem go away.  Here is a list of reasons that we found "Why the user profile didn't migrate":   1. User logged in.  This can/will lock the user profile.  ADMT needs to change security on many files in the users "docs & settings" including the "ntuser.dat" file. If those files are open or locked for exclusive access then ADMT will fail.   2. Workstation not rebooted right before ADMT runs.  If you reboot then you guarantee that the user profile will not be locked.  During a normal user day various badly behaved applications or print drivers will hold open various parts of the user profile and generally not release it even if the user logs off.   3. Workstation "sick".  Sometimes we ran into occasional problems with workstation that were messed up for other reasons (e.g. bad Netware client, bad printer driver, bad workstation image, etc...)  ADMT in general will find those workstations and point them out to you that they need other work.    -Stuart     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?   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. 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.