Does anyone know of a place to get all the best practices for a windows 2000 multiple domain -> Windows 2003 single domain (intra-forest).
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Grillenmeier, Guido Sent: Monday, December 12, 2005 5:19 PM To: [email protected] Subject: RE: [ActiveDir] ADMT Request it's less point and click these days, at least if you do it right, since you should certainly leverage the include-file options to select the objects for the migration (also allows to rename objects during the migration). However, I doubt that James even has a problem with the migration of users and groups (although I've also used multiple sessions to speed up larger scale migrations with ADMTv3). The more lengthy task is obviously the processing/migration of the clients - here multiple sessions are useful for many reasons, especially to run the tool with different credentials so that it can connect with different account data to the various clients (if these reside in various source domains). Or even just to handle processing of batches. Especially now that ADMT has a cool retry option that will go after all those clients that are forever offline (and it even performs post-migration checks on the clients to see that they've migrated successfully...) The way I've helped myself was to use a terminal server with multiple connections for the different sessions - the RDC session name will be visible and allow you to keep the sessions appart. And when connected to a session - your account would tell you that this is the Denver session or you could even add some other notes on the desktop or whereever, if this helps you keep the sessions appart... /Guido -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Coleman, Hunter Sent: Dienstag, 13. Dezember 2005 00:33 To: [email protected] Subject: RE: [ActiveDir] ADMT Request It's been ages since we ran our migration, but at the time we scripted it using the sample scripts that accompanied ADMT. If you go that route, you can have multiple log files that are uniquely named and not run into the session confusion. You'll also get much more consistent results from the scripts, as you won't have mischecked options or typos that seem inevitable in lots of point/click scenarios. Hunter -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Monday, December 12, 2005 3:47 PM To: [email protected] Subject: [ActiveDir] ADMT Request Hi All I am not sure anybody that can do anything with this listens on this list but we have been using ADMT v.3 with great success for a very large scale migration. The multi session ability has been a huge benefit to us. We are running into a problem keeping multiple sessions straight. How hard would it be to include a description field that you can fill in when you start the session that would then show up in the title bar for the session (something like Session DENVER, California, etc) Just a wish. James R. Day Active Directory Core Team Office of the Chief Information Officer National Park Service 202-230-2983 [EMAIL PROTECTED] List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
