[ActiveDir] Seperate forest migration notes
A company was acquired. Seperate 2000/2003 forest, now a two-way trust exists, but we are looking at migrating their users, mailboxes, computers, and servers into our forest.Working on a plan to test moving a user, mailbox, computer, and server into our forest. Plan: Select test users and computersInstall ADMTTest user migration via ADMTTest computer migration via RDP manaully or script (must locate)Test mailbox migration via Exchange Migration WizardLogin as user and test services/access Am I missing anything? Any tips?Thanks,...D-- CPDE - Certified Petroleum Distribution EngineerCCBC - Certified Canadian Beer Consumer
Re: [ActiveDir] Seperate forest migration notes
Overall, that's pretty good for the plan. If you haven't already seen it, there's a migration cookbook available on Microsoft's website. Some things to pay attention to: name resolution for the clients - it's important :) Trust configurations - if a recent enough version, there are some security components that you'll want to be aware of - specifically quarrantine and sidfiltering. Be sure those are configured appropriately for your environment. Order of migration: Be sure to understand the impacts of the order that you migrate the users. I don't know enough about the versions of Exchange, but it would make sense to move the users after or before you move the mailboxes. All the users or all the mailboxes pretty much. If you try to do both at the same time, it can be difficult to troubleshoot and you'll slow your migration down trying to chase the issues. That leads to expectations: Be sure that nobody expects to stay in the partially-migrated state for very long while you chase down integration issues. Once you start, be prepared to sprint to the finish line. Co-existence sucks. No doubts about that. If you try to continue on with migration and coexistence and new projects and...etc you'll be torn to the winds. Your best bet is to continue to push regardless of the issues once you begin (post pilot of course). Did I mention name resolution? That's important, so I don't mind mentioning it twice. Planning is your friend when it comes to migrations. I imagine that Guido might chime in here. I hear he's done this once or twice. :) On 8/29/06, Danny <[EMAIL PROTECTED]> wrote: A company was acquired. Seperate 2000/2003 forest, now a two-way trust exists, but we are looking at migrating their users, mailboxes, computers, and servers into our forest.Working on a plan to test moving a user, mailbox, computer, and server into our forest. Plan: Select test users and computersInstall ADMTTest user migration via ADMTTest computer migration via RDP manaully or script (must locate)Test mailbox migration via Exchange Migration WizardLogin as user and test services/access Am I missing anything? Any tips?Thanks,...D -- CPDE - Certified Petroleum Distribution EngineerCCBC - Certified Canadian Beer Consumer
Re: [ActiveDir] Seperate forest migration notes
Thank you, Al! I will provide an updated outline of our plan based on your suggestions.One question, though: Does anyone know what ADMT v3 is not capable of migrating in the environment I outlined? On 8/29/06, Al Mulnick <[EMAIL PROTECTED]> wrote: Overall, that's pretty good for the plan. If you haven't already seen it, there's a migration cookbook available on Microsoft's website. Some things to pay attention to: name resolution for the clients - it's important :) Trust configurations - if a recent enough version, there are some security components that you'll want to be aware of - specifically quarrantine and sidfiltering. Be sure those are configured appropriately for your environment. Order of migration: Be sure to understand the impacts of the order that you migrate the users. I don't know enough about the versions of Exchange, but it would make sense to move the users after or before you move the mailboxes. All the users or all the mailboxes pretty much. If you try to do both at the same time, it can be difficult to troubleshoot and you'll slow your migration down trying to chase the issues. That leads to expectations: Be sure that nobody expects to stay in the partially-migrated state for very long while you chase down integration issues. Once you start, be prepared to sprint to the finish line. Co-existence sucks. No doubts about that. If you try to continue on with migration and coexistence and new projects and...etc you'll be torn to the winds. Your best bet is to continue to push regardless of the issues once you begin (post pilot of course). Did I mention name resolution? That's important, so I don't mind mentioning it twice. Planning is your friend when it comes to migrations. I imagine that Guido might chime in here. I hear he's done this once or twice. :) On 8/29/06, Danny <[EMAIL PROTECTED]> wrote: A company was acquired. Seperate 2000/2003 forest, now a two-way trust exists, but we are looking at migrating their users, mailboxes, computers, and servers into our forest.Working on a plan to test moving a user, mailbox, computer, and server into our forest. Plan: Select test users and computersInstall ADMTTest user migration via ADMTTest computer migration via RDP manaully or script (must locate)Test mailbox migration via Exchange Migration WizardLogin as user and test services/access Am I missing anything? Any tips?Thanks,...D -- CPDE - Certified Petroleum Distribution EngineerCCBC - Certified Canadian Beer Consumer -- CPDE - Certified Petroleum Distribution EngineerCCBC - Certified Canadian Beer Consumer
Re: [ActiveDir] Seperate forest migration notes
I found some more information, however, in the "Before using ADMT v3" help document included with ADMT, is states that the account that I am running ADMT, must be a member of the administrators group on all computers that I want to migrate. How would I accomplish this? Thanks,...DOn 9/5/06, Danny <[EMAIL PROTECTED]> wrote: Thank you, Al! I will provide an updated outline of our plan based on your suggestions.One question, though: Does anyone know what ADMT v3 is not capable of migrating in the environment I outlined? On 8/29/06, Al Mulnick <[EMAIL PROTECTED]> wrote: Overall, that's pretty good for the plan. If you haven't already seen it, there's a migration cookbook available on Microsoft's website. Some things to pay attention to: name resolution for the clients - it's important :) Trust configurations - if a recent enough version, there are some security components that you'll want to be aware of - specifically quarrantine and sidfiltering. Be sure those are configured appropriately for your environment. Order of migration: Be sure to understand the impacts of the order that you migrate the users. I don't know enough about the versions of Exchange, but it would make sense to move the users after or before you move the mailboxes. All the users or all the mailboxes pretty much. If you try to do both at the same time, it can be difficult to troubleshoot and you'll slow your migration down trying to chase the issues. That leads to expectations: Be sure that nobody expects to stay in the partially-migrated state for very long while you chase down integration issues. Once you start, be prepared to sprint to the finish line. Co-existence sucks. No doubts about that. If you try to continue on with migration and coexistence and new projects and...etc you'll be torn to the winds. Your best bet is to continue to push regardless of the issues once you begin (post pilot of course). Did I mention name resolution? That's important, so I don't mind mentioning it twice. Planning is your friend when it comes to migrations. I imagine that Guido might chime in here. I hear he's done this once or twice. :) On 8/29/06, Danny <[EMAIL PROTECTED]> wrote: A company was acquired. Seperate 2000/2003 forest, now a two-way trust exists, but we are looking at migrating their users, mailboxes, computers, and servers into our forest.Working on a plan to test moving a user, mailbox, computer, and server into our forest. Plan: Select test users and computersInstall ADMTTest user migration via ADMTTest computer migration via RDP manaully or script (must locate)Test mailbox migration via Exchange Migration WizardLogin as user and test services/access Am I missing anything? Any tips?Thanks,...D -- CPDE - Certified Petroleum Distribution EngineerCCBC - Certified Canadian Beer Consumer -- CPDE - Certified Petroleum Distribution EngineerCCBC - Certified Canadian Beer Consumer -- CPDE - Certified Petroleum Distribution EngineerCCBC - Certified Canadian Beer Consumer
Re: [ActiveDir] Seperate forest migration notes
You can add your account to administrators group on all computers using restricted group in GPO. http://support.microsoft.com/Default.aspx?kbid=279301 On 9/9/06, Danny <[EMAIL PROTECTED]> wrote: I found some more information, however, in the "Before using ADMT v3" help document included with ADMT, is states that the account that I am running ADMT, must be a member of the administrators group on all computers that I want to migrate. How would I accomplish this? Thanks, ...D On 9/5/06, Danny <[EMAIL PROTECTED]> wrote: Thank you, Al! I will provide an updated outline of our plan based on your suggestions.One question, though: Does anyone know what ADMT v3 is not capable of migrating in the environment I outlined? On 8/29/06, Al Mulnick <[EMAIL PROTECTED]> wrote: Overall, that's pretty good for the plan. If you haven't already seen it, there's a migration cookbook available on Microsoft's website. Some things to pay attention to: name resolution for the clients - it's important :) Trust configurations - if a recent enough version, there are some security components that you'll want to be aware of - specifically quarrantine and sidfiltering. Be sure those are configured appropriately for your environment. Order of migration: Be sure to understand the impacts of the order that you migrate the users. I don't know enough about the versions of Exchange, but it would make sense to move the users after or before you move the mailboxes. All the users or all the mailboxes pretty much. If you try to do both at the same time, it can be difficult to troubleshoot and you'll slow your migration down trying to chase the issues. That leads to expectations: Be sure that nobody expects to stay in the partially-migrated state for very long while you chase down integration issues. Once you start, be prepared to sprint to the finish line. Co-existence sucks. No doubts about that. If you try to continue on with migration and coexistence and new projects and...etc you'll be torn to the winds. Your best bet is to continue to push regardless of the issues once you begin (post pilot of course). Did I mention name resolution? That's important, so I don't mind mentioning it twice. Planning is your friend when it comes to migrations. I imagine that Guido might chime in here. I hear he's done this once or twice. :) On 8/29/06, Danny <[EMAIL PROTECTED]> wrote: A company was acquired. Seperate 2000/2003 forest, now a two-way trust exists, but we are looking at migrating their users, mailboxes, computers, and servers into our forest.Working on a plan to test moving a user, mailbox, computer, and server into our forest. Plan: Select test users and computersInstall ADMTTest user migration via ADMTTest computer migration via RDP manaully or script (must locate)Test mailbox migration via Exchange Migration WizardLogin as user and test services/access Am I missing anything? Any tips?Thanks,...D -- CPDE - Certified Petroleum Distribution EngineerCCBC - Certified Canadian Beer Consumer -- CPDE - Certified Petroleum Distribution Engineer CCBC - Certified Canadian Beer Consumer -- CPDE - Certified Petroleum Distribution EngineerCCBC - Certified Canadian Beer Consumer
Re: [ActiveDir] Seperate forest migration notes
Thanks - I will try that out. Also, do you know if the Windows firewall needs any exceptions for the computer migration component to function?On 9/8/06, Chong Ai Chung <[EMAIL PROTECTED]> wrote: You can add your account to administrators group on all computers using restricted group in GPO. http://support.microsoft.com/Default.aspx?kbid=279301 On 9/9/06, Danny <[EMAIL PROTECTED]> wrote: I found some more information, however, in the "Before using ADMT v3" help document included with ADMT, is states that the account that I am running ADMT, must be a member of the administrators group on all computers that I want to migrate. How would I accomplish this? Thanks, ...D On 9/5/06, Danny <[EMAIL PROTECTED]> wrote: Thank you, Al! I will provide an updated outline of our plan based on your suggestions.One question, though: Does anyone know what ADMT v3 is not capable of migrating in the environment I outlined? On 8/29/06, Al Mulnick <[EMAIL PROTECTED]> wrote: Overall, that's pretty good for the plan. If you haven't already seen it, there's a migration cookbook available on Microsoft's website. Some things to pay attention to: name resolution for the clients - it's important :) Trust configurations - if a recent enough version, there are some security components that you'll want to be aware of - specifically quarrantine and sidfiltering. Be sure those are configured appropriately for your environment. Order of migration: Be sure to understand the impacts of the order that you migrate the users. I don't know enough about the versions of Exchange, but it would make sense to move the users after or before you move the mailboxes. All the users or all the mailboxes pretty much. If you try to do both at the same time, it can be difficult to troubleshoot and you'll slow your migration down trying to chase the issues. That leads to expectations: Be sure that nobody expects to stay in the partially-migrated state for very long while you chase down integration issues. Once you start, be prepared to sprint to the finish line. Co-existence sucks. No doubts about that. If you try to continue on with migration and coexistence and new projects and...etc you'll be torn to the winds. Your best bet is to continue to push regardless of the issues once you begin (post pilot of course). Did I mention name resolution? That's important, so I don't mind mentioning it twice. Planning is your friend when it comes to migrations. I imagine that Guido might chime in here. I hear he's done this once or twice. :) On 8/29/06, Danny <[EMAIL PROTECTED]> wrote: A company was acquired. Seperate 2000/2003 forest, now a two-way trust exists, but we are looking at migrating their users, mailboxes, computers, and servers into our forest.Working on a plan to test moving a user, mailbox, computer, and server into our forest. Plan: Select test users and computersInstall ADMTTest user migration via ADMTTest computer migration via RDP manaully or script (must locate)Test mailbox migration via Exchange Migration WizardLogin as user and test services/access Am I missing anything? Any tips?Thanks,...D -- CPDE - Certified Petroleum Distribution EngineerCCBC - Certified Canadian Beer Consumer -- CPDE - Certified Petroleum Distribution Engineer CCBC - Certified Canadian Beer Consumer -- CPDE - Certified Petroleum Distribution EngineerCCBC - Certified Canadian Beer Consumer -- CPDE - Certified Petroleum Distribution EngineerCCBC - Certified Canadian Beer Consumer
RE: [ActiveDir] Seperate forest migration notes
Yes. Try doing file://computername/c$ to a few of the computers in question. If you can't connect, you have a firewall issue. If you can connect, but can log in with the account you are using for the migration, you have a permission issue. Those 2 tests must pass before you can do any migration. Sincerely, _ (, / | /) /) /) /---| (/_ __ ___// _ // _ ) / |_/(__(_) // (_(_)(/_(_(_/(__(/_(_/ /) (/ Microsoft MVP - Directory Serviceswww.akomolafe.com - we know IT-5.75, -3.23Do you now realize that Today is the Tomorrow you were worried about Yesterday? -anon From: DannySent: Fri 9/8/2006 2:06 PMTo: ActiveDir@mail.activedir.orgSubject: Re: [ActiveDir] Seperate forest migration notes Thanks - I will try that out. Also, do you know if the Windows firewall needs any exceptions for the computer migration component to function? On 9/8/06, Chong Ai Chung <[EMAIL PROTECTED]> wrote: You can add your account to administrators group on all computers using restricted group in GPO. http://support.microsoft.com/Default.aspx?kbid=279301 On 9/9/06, Danny <[EMAIL PROTECTED]> wrote: I found some more information, however, in the "Before using ADMT v3" help document included with ADMT, is states that the account that I am running ADMT, must be a member of the administrators group on all computers that I want to migrate. How would I accomplish this? Thanks, ...D On 9/5/06, Danny <[EMAIL PROTECTED]> wrote: Thank you, Al! I will provide an updated outline of our plan based on your suggestions.One question, though: Does anyone know what ADMT v3 is not capable of migrating in the environment I outlined? On 8/29/06, Al Mulnick <[EMAIL PROTECTED]> wrote: Overall, that's pretty good for the plan. If you haven't already seen it, there's a migration cookbook available on Microsoft's website. Some things to pay attention to: name resolution for the clients - it's important :) Trust configurations - if a recent enough version, there are some security components that you'll want to be aware of - specifically quarrantine and sidfiltering. Be sure those are configured appropriately for your environment. Order of migration: Be sure to understand the impacts of the order that you migrate the users. I don't know enough about the versions of Exchange, but it would make sense to move the users after or before you move the mailboxes. All the users or all the mailboxes pretty much. If you try to do both at the same time, it can be difficult to troubleshoot and you'll slow your migration down trying to chase the issues. That leads to expectations: Be sure that nobody expects to stay in the partially-migrated state for very long while you chase down integration issues. Once you start, be prepared to sprint to the finish line. Co-existence sucks. No doubts about that. If you try to continue on with migration and coexistence and new projects and...etc you'll be torn to the winds. Your best bet is to continue to push regardless of the issues once you begin (post pilot of course). Did I mention name resolution? That's important, so I don't mind mentioning it twice. Planning is your friend when it comes to migrations. I imagine that Guido might chime in here. I hear he's done this once or twice. :) On 8/29/06, Danny <[EMAIL PROTECTED]> wrote: A company was acquired. Seperate 2000/2003 forest, now a two-way trust exists, but we are looking at migrating their users, mailboxes, computers, and servers into our forest.Working on a plan to test moving a user, mailbox, computer, and server into our forest. Plan: Select test users and computersInstall ADMTTest user migration via ADMTTest computer migration via RDP manaully or script (must locate)Test mailbox migration via Exchange Migration WizardLogin as user and test services/access Am I missing anything? Any tips?Thanks,...D -- CPDE - Certified Petroleum Distribution EngineerCCBC - Certified Canadian Beer Consumer -- CPDE - Certified Petroleum Distribution Engineer CCBC - Certified Canadian Beer Consumer -- CPDE - Certified Petroleum Distribution EngineerCCBC - Certified Canadian Beer Consumer -- CPDE - Certified Petroleum Distribution EngineerCCBC - Certified Canadian Beer Consumer
RE: [ActiveDir] Seperate forest migration notes
BTW, here's how I add the ADMT account to the relevant admin groups before the known good "Restricted Group" option was invented. If you find out that "Restricted Group" is not working for you, try the script option. Sincerely, _ (, / | /) /) /) /---| (/_ __ ___// _ // _ ) / |_/(__(_) // (_(_)(/_(_(_/(__(/_(_/ /) (/ Microsoft MVP - Directory Serviceswww.akomolafe.com - we know IT-5.75, -3.23Do you now realize that Today is the Tomorrow you were worried about Yesterday? -anon From: DannySent: Fri 9/8/2006 1:12 PMTo: ActiveDir@mail.activedir.orgSubject: Re: [ActiveDir] Seperate forest migration notes I found some more information, however, in the "Before using ADMT v3" help document included with ADMT, is states that the account that I am running ADMT, must be a member of the administrators group on all computers that I want to migrate. How would I accomplish this? Thanks,...D On 9/5/06, Danny <[EMAIL PROTECTED]> wrote: Thank you, Al! I will provide an updated outline of our plan based on your suggestions.One question, though: Does anyone know what ADMT v3 is not capable of migrating in the environment I outlined? On 8/29/06, Al Mulnick <[EMAIL PROTECTED]> wrote: Overall, that's pretty good for the plan. If you haven't already seen it, there's a migration cookbook available on Microsoft's website. Some things to pay attention to: name resolution for the clients - it's important :) Trust configurations - if a recent enough version, there are some security components that you'll want to be aware of - specifically quarrantine and sidfiltering. Be sure those are configured appropriately for your environment. Order of migration: Be sure to understand the impacts of the order that you migrate the users. I don't know enough about the versions of Exchange, but it would make sense to move the users after or before you move the mailboxes. All the users or all the mailboxes pretty much. If you try to do both at the same time, it can be difficult to troubleshoot and you'll slow your migration down trying to chase the issues. That leads to expectations: Be sure that nobody expects to stay in the partially-migrated state for very long while you chase down integration issues. Once you start, be prepared to sprint to the finish line. Co-existence sucks. No doubts about that. If you try to continue on with migration and coexistence and new projects and...etc you'll be torn to the winds. Your best bet is to continue to push regardless of the issues once you begin (post pilot of course). Did I mention name resolution? That's important, so I don't mind mentioning it twice. Planning is your friend when it comes to migrations. I imagine that Guido might chime in here. I hear he's done this once or twice. :) On 8/29/06, Danny <[EMAIL PROTECTED]> wrote: A company was acquired. Seperate 2000/2003 forest, now a two-way trust exists, but we are looking at migrating their users, mailboxes, computers, and servers into our forest.Working on a plan to test moving a user, mailbox, computer, and server into our forest. Plan: Select test users and computersInstall ADMTTest user migration via ADMTTest computer migration via RDP manaully or script (must locate)Test mailbox migration via Exchange Migration WizardLogin as user and test services/access Am I missing anything? Any tips?Thanks,...D -- CPDE - Certified Petroleum Distribution EngineerCCBC - Certified Canadian Beer Consumer -- CPDE - Certified Petroleum Distribution EngineerCCBC - Certified Canadian Beer Consumer -- CPDE - Certified Petroleum Distribution EngineerCCBC - Certified Canadian Beer Consumer
RE: [ActiveDir] Seperate forest migration notes
Ugh! I wish they would invent a computerish thingamabob that reads your mind and paste the link you are thinking :0. Here's the sample script. http://www.akomolafe.com/Portals/1/add-to-loc-grp.txt Sincerely, _ (, / | /) /) /) /---| (/_ __ ___// _ // _ ) / |_/(__(_) // (_(_)(/_(_(_/(__(/_(_/ /) (/ Microsoft MVP - Directory Serviceswww.akomolafe.com - we know IT-5.75, -3.23Do you now realize that Today is the Tomorrow you were worried about Yesterday? -anon From: Akomolafe, DejiSent: Fri 9/8/2006 2:18 PMTo: ActiveDir@mail.activedir.orgSubject: RE: [ActiveDir] Seperate forest migration notes BTW, here's how I add the ADMT account to the relevant admin groups before the known good "Restricted Group" option was invented. If you find out that "Restricted Group" is not working for you, try the script option. Sincerely, _ (, / | /) /) /) /---| (/_ __ ___// _ // _ ) / |_/(__(_) // (_(_)(/_(_(_/(__(/_(_/ /) (/ Microsoft MVP - Directory Serviceswww.akomolafe.com - we know IT-5.75, -3.23Do you now realize that Today is the Tomorrow you were worried about Yesterday? -anon From: DannySent: Fri 9/8/2006 1:12 PMTo: ActiveDir@mail.activedir.orgSubject: Re: [ActiveDir] Seperate forest migration notes I found some more information, however, in the "Before using ADMT v3" help document included with ADMT, is states that the account that I am running ADMT, must be a member of the administrators group on all computers that I want to migrate. How would I accomplish this? Thanks,...D On 9/5/06, Danny <[EMAIL PROTECTED]> wrote: Thank you, Al! I will provide an updated outline of our plan based on your suggestions.One question, though: Does anyone know what ADMT v3 is not capable of migrating in the environment I outlined? On 8/29/06, Al Mulnick <[EMAIL PROTECTED]> wrote: Overall, that's pretty good for the plan. If you haven't already seen it, there's a migration cookbook available on Microsoft's website. Some things to pay attention to: name resolution for the clients - it's important :) Trust configurations - if a recent enough version, there are some security components that you'll want to be aware of - specifically quarrantine and sidfiltering. Be sure those are configured appropriately for your environment. Order of migration: Be sure to understand the impacts of the order that you migrate the users. I don't know enough about the versions of Exchange, but it would make sense to move the users after or before you move the mailboxes. All the users or all the mailboxes pretty much. If you try to do both at the same time, it can be difficult to troubleshoot and you'll slow your migration down trying to chase the issues. That leads to expectations: Be sure that nobody expects to stay in the partially-migrated state for very long while you chase down integration issues. Once you start, be prepared to sprint to the finish line. Co-existence sucks. No doubts about that. If you try to continue on with migration and coexistence and new projects and...etc you'll be torn to the winds. Your best bet is to continue to push regardless of the issues once you begin (post pilot of course). Did I mention name resolution? That's important, so I don't mind mentioning it twice. Planning is your friend when it comes to migrations. I imagine that Guido might chime in here. I hear he's done this once or twice. :) On 8/29/06, Danny <[EMAIL PROTECTED]> wrote: A company was acquired. Seperate 2000/2003 forest, now a two-way trust exists, but we are looking at migrating their users, mailboxes, computers, and servers into our forest.Working on a plan to test moving a user, mailbox, computer, and server into our forest. Plan: Select test users and computersInstall ADMTTest user migration via ADMTTest computer migration via RDP manaully or script (must locate)Test mailbox migration via Exchange Migration WizardLogin as user and test services/access Am I missing anything? Any tips?Thanks,...D -- CPDE - Certified Petroleum Distribution EngineerCCBC - Certified Canadian Beer Consumer -- CPDE - Certified Petroleum Distribution EngineerCCBC - Certified Canadian Beer Consumer -- CPDE - Certified Petroleum Distribution EngineerCCBC - Certified Canadian Beer Consumer
Re: [ActiveDir] Seperate forest migration notes
Other then firewall, Windows XP SP2 includes security enhancement features that will prevent the successful migration of computer accounts using ADMT. Before carry out migration, you will also need to set the following key to a value of 0 HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\RPC\RestrictRemoteClients Check also following services are started on the computer- Remote Registry- Alerter You can enforce these changes using GPO and revert the changes using GPO after computer account migration completed. On 9/9/06, Akomolafe, Deji <[EMAIL PROTECTED]> wrote: Ugh! I wish they would invent a computerish thingamabob that reads your mind and paste the link you are thinking :0. Here's the sample script. http://www.akomolafe.com/Portals/1/add-to-loc-grp.txt Sincerely, _ (, / | /) /) /) /---| (/_ __ ___// _ // _ ) / |_/(__(_) // (_(_)(/_(_(_/(__(/_(_/ /) (/ Microsoft MVP - Directory Services www.akomolafe.com - we know IT-5.75, -3.23Do you now realize that Today is the Tomorrow you were worried about Yesterday? -anon From: Akomolafe, DejiSent: Fri 9/8/2006 2:18 PM To: ActiveDir@mail.activedir.org Subject: RE: [ActiveDir] Seperate forest migration notes BTW, here's how I add the ADMT account to the relevant admin groups before the known good "Restricted Group" option was invented. If you find out that "Restricted Group" is not working for you, try the script option. Sincerely, _ (, / | /) /) /) /---| (/_ __ ___// _ // _ ) / |_/(__(_) // (_(_)(/_(_(_/(__(/_(_/ /) (/ Microsoft MVP - Directory Services www.akomolafe.com - we know IT-5.75, -3.23Do you now realize that Today is the Tomorrow you were worried about Yesterday? -anon From: DannySent: Fri 9/8/2006 1:12 PMTo: ActiveDir@mail.activedir.org Subject: Re: [ActiveDir] Seperate forest migration notes I found some more information, however, in the "Before using ADMT v3" help document included with ADMT, is states that the account that I am running ADMT, must be a member of the administrators group on all computers that I want to migrate. How would I accomplish this? Thanks,...D On 9/5/06, Danny <[EMAIL PROTECTED]> wrote: Thank you, Al! I will provide an updated outline of our plan based on your suggestions.One question, though: Does anyone know what ADMT v3 is not capable of migrating in the environment I outlined? On 8/29/06, Al Mulnick <[EMAIL PROTECTED]> wrote: Overall, that's pretty good for the plan. If you haven't already seen it, there's a migration cookbook available on Microsoft's website. Some things to pay attention to: name resolution for the clients - it's important :) Trust configurations - if a recent enough version, there are some security components that you'll want to be aware of - specifically quarrantine and sidfiltering. Be sure those are configured appropriately for your environment. Order of migration: Be sure to understand the impacts of the order that you migrate the users. I don't know enough about the versions of Exchange, but it would make sense to move the users after or before you move the mailboxes. All the users or all the mailboxes pretty much. If you try to do both at the same time, it can be difficult to troubleshoot and you'll slow your migration down trying to chase the issues. That leads to expectations: Be sure that nobody expects to stay in the partially-migrated state for very long while you chase down integration issues. Once you start, be prepared to sprint to the finish line. Co-existence sucks. No doubts about that. If you try to continue on with migration and coexistence and new projects and...etc you'll be torn to the winds. Your best bet is to continue to push regardless of the issues once you begin (post pilot of course). Did I mention name resolution? That's important, so I don't mind mentioning it twice. Planning is your friend when it comes to migrations. I imagine that Guido might chime in here. I hear he's done this once or twice. :) On 8/29/06, Danny <[EMAIL PROTECTED]> wrote: A company was acquired. Seperate 2000/2003 forest, now a two-way trust exists, but we are looking at migrating their users, mailboxes, computers, and servers into our forest.Working on a plan to test moving a user, mailbox, computer, and server into our forest. Plan: Select test users and computersInstall ADMTTest user migration via ADMTTest computer migration via RDP manaully or script (must locate)Test mailbox migration via Exchange Migration WizardLogin as user and test services/access Am I missing anything? Any tips?Thanks,..
Re: [ActiveDir] Seperate forest migration notes
The most simple way is to migate the computers with the admin of the source domain (should be admin on all computers). This admin should be admin in the target domain, or at least you should delegate the appropriate rights in the target domain (add computers). cheers Hans --- Danny <[EMAIL PROTECTED]> wrote: > I found some more information, however, in the > "Before using ADMT v3" help > document included with ADMT, is states that the > account that I am running > ADMT, must be a member of the administrators group > on all computers that I > want to migrate. How would I accomplish this? > > Thanks, > > ...D > > On 9/5/06, Danny <[EMAIL PROTECTED]> wrote: > > > > Thank you, Al! I will provide an updated outline > of our plan based on your > > suggestions. > > > > One question, though: Does anyone know what ADMT > v3 is not capable of > > migrating in the environment I outlined? > > > > > > On 8/29/06, Al Mulnick <[EMAIL PROTECTED]> wrote: > > > > > > Overall, that's pretty good for the plan. If you > haven't already seen > > > it, there's a migration cookbook available on > Microsoft's website. Some > > > things to pay attention to: name resolution for > the clients - it's important > > > :) Trust configurations - if a recent enough > version, there are some > > > security components that you'll want to be aware > of - specifically > > > quarrantine and sidfiltering. Be sure those are > configured appropriately for > > > your environment. > > > > > > Order of migration: > > > Be sure to understand the impacts of the order > that you migrate the > > > users. I don't know enough about the versions of > Exchange, but it would make > > > sense to move the users after or before you move > the mailboxes. All the > > > users or all the mailboxes pretty much. If you > try to do both at the same > > > time, it can be difficult to troubleshoot and > you'll slow your migration > > > down trying to chase the issues. > > > > > > That leads to expectations: > > > Be sure that nobody expects to stay in the > partially-migrated state for > > > very long while you chase down integration > issues. Once you start, be > > > prepared to sprint to the finish line. > Co-existence sucks. No doubts about > > > that. If you try to continue on with migration > and coexistence and new > > > projects and...etc you'll be torn to the winds. > Your best bet is to > > > continue to push regardless of the issues once > you begin (post pilot of > > > course). > > > > > > Did I mention name resolution? That's important, > so I don't mind > > > mentioning it twice. > > > > > > Planning is your friend when it comes to > migrations. > > > > > > I imagine that Guido might chime in here. I > hear he's done this once or > > > twice. :) > > > > > > > > > On 8/29/06, Danny <[EMAIL PROTECTED]> wrote: > > > > > > > > A company was acquired. Seperate 2000/2003 > forest, now a two-way trust > > > > exists, but we are looking at migrating their > users, mailboxes, computers, > > > > and servers into our forest. > > > > > > > > Working on a plan to test moving a user, > mailbox, computer, and server > > > > into our forest. Plan: > > > > > > > > Select test users and computers > > > > Install ADMT > > > > Test user migration via ADMT > > > > Test computer migration via RDP manaully or > script (must locate) > > > > Test mailbox migration via Exchange Migration > Wizard > > > > Login as user and test services/access > > > > > > > > Am I missing anything? Any tips? > > > > > > > > Thanks, > > > > > > > > ...D > > > > > > > > > > > > -- > > > > CPDE - Certified Petroleum Distribution > Engineer > > > > CCBC - Certified Canadian Beer Consumer > > > > > > > > > > > > > > > > -- > > CPDE - Certified Petroleum Distribution Engineer > > CCBC - Certified Canadian Beer Consumer > > > > > > -- > CPDE - Certified Petroleum Distribution Engineer > CCBC - Certified Canadian Beer Consumer > __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com List info : http://www.activedir.org/List.aspx List FAQ: http://www.activedir.org/ListFAQ.aspx List archive: http://www.activedir.org/ml/threads.aspx
Re: [ActiveDir] Seperate forest migration notes
Yep, that would be one of the easiest ways. Put the source migration account into the source domain admins (domain admins is in the workstation administrators by default) and into the target domain built-in\administrators group. If you've modified the group membership of the source domain local workstations from default, you'll want to use some of the other methods mentioned without question. The changes to the registry of the xp sp2 workstations is a good thing to be aware of as is the changes to the W2K3 SP1 servers if that's where you run the tool. Check the readme and be sure your hotfixes are up to date. AlOn 9/11/06, Hans Halbmayr <[EMAIL PROTECTED]> wrote: The most simple way is to migate the computers withthe admin of the source domain (should be admin on allcomputers). This admin should be admin in the targetdomain, or at least you should delegate theappropriate rights in the target domain (add computers).cheersHans--- Danny <[EMAIL PROTECTED]> wrote:> I found some more information, however, in the> "Before using ADMT v3" help > document included with ADMT, is states that the> account that I am running> ADMT, must be a member of the administrators group> on all computers that I> want to migrate. How would I accomplish this? >> Thanks,>> ...D>> On 9/5/06, Danny <[EMAIL PROTECTED]> wrote:> >> > Thank you, Al! I will provide an updated outline > of our plan based on your> > suggestions.> >> > One question, though: Does anyone know what ADMT> v3 is not capable of> > migrating in the environment I outlined? > >> >> > On 8/29/06, Al Mulnick <[EMAIL PROTECTED]> wrote:> > >> > > Overall, that's pretty good for the plan. If you > haven't already seen> > > it, there's a migration cookbook available on> Microsoft's website. Some> > > things to pay attention to: name resolution for> the clients - it's important > > > :) Trust configurations - if a recent enough> version, there are some> > > security components that you'll want to be aware> of - specifically> > > quarrantine and sidfiltering. Be sure those are > configured appropriately for> > > your environment.> > >> > > Order of migration:> > > Be sure to understand the impacts of the order> that you migrate the > > > users. I don't know enough about the versions of> Exchange, but it would make> > > sense to move the users after or before you move> the mailboxes. All the> > > users or all the mailboxes pretty much. If you > try to do both at the same> > > time, it can be difficult to troubleshoot and> you'll slow your migration> > > down trying to chase the issues.> > >> > > That leads to expectations: > > > Be sure that nobody expects to stay in the> partially-migrated state for> > > very long while you chase down integration> issues. Once you start, be> > > prepared to sprint to the finish line. > Co-existence sucks. No doubts about> > > that. If you try to continue on with migration> and coexistence and new> > > projects and...etc you'll be torn to the winds.> Your best bet is to > > > continue to push regardless of the issues once> you begin (post pilot of> > > course).> > >> > > Did I mention name resolution? That's important,> so I don't mind > > > mentioning it twice.> > >> > > Planning is your friend when it comes to> migrations.> > >> > > I imagine that Guido might chime in here. I > hear he's done this once or> > > twice. :)> > >> > >> > > On 8/29/06, Danny <[EMAIL PROTECTED]> wrote:> > > > > > > > A company was acquired. Seperate 2000/2003> forest, now a two-way trust> > > > exists, but we are looking at migrating their> users, mailboxes, computers,> > > > and servers into our forest. > > > >> > > > Working on a plan to test moving a user,> mailbox, computer, and server> > > > into our forest. Plan:> > > >> > > > Select test users and computers > > > > Install ADMT> > > > Test user migration via ADMT> > > > Test computer migration via RDP manaully or> script (must locate)> > > > Test mailbox migration via Exchange Migration > Wizard> > > > Login as user and test services/access> > > >> > > > Am I missing anything? Any tips?> > > >> > > > Thanks,> > > > > > > > ...D> > > >> > > >> > > > --> > > > CPDE - Certified Petroleum Distribution> Engineer> > > > CCBC - Certified Canadian Beer Consumer > > > >> > >> > >> >> >> > --> > CPDE - Certified Petroleum Distribution Engineer> > CCBC - Certified Canadian Beer Consumer> > --> CPDE - Certified Petroleum Distribution Engineer> CCBC - Certified Canadian Beer Consumer>__Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection aroundhttp://mail.yahoo.comList info : http://www.activedir.org/List.aspx List FAQ: http://www.activedir.org/ListFAQ.aspxList archive: http://www.activedir.org/ml/threads.aspx
