- Oct 16, 2002
- 142
- 0
- 0
This weekend I have a little job to complete - I have done something like this before but just wanted to get any opinions on best approach.
THE WAY IT IS NOW: W2k Domain controller (is very old), a few other servers (just file servers), about 30 workstations, various printers and other devices. Email is currently POP3 hosted elsewhere.
WHAT I'M DOING: New W2k3 SBS server going in - old domain controller will be demoted but soldier on as a file server and license server for some floating licenses. When the domain was originally setup, the wag who put it in named the internal domain the same thing as the external domain (.com). I fixed this by simply putting in pointers in DNS to our externally hosted sites but it's annoying. When I put in the new controller I am changing the internal domain to a .local.
I want the fastest (but good) approach possible to finish this. It's not a big deal to create active domain accounts since there are only 30 users or so but I would rather not. What I don't want to do is spend a huge amount of time migrating each local user profile at the individual workstations (or heaven forbid corrupting user profiles).
MY GAME PLAN:
Plan 1: Turn on the new domain controller, and try to use ADMT to copy the accounts over to the new controller. If that doesn't work then:
Plan 2: Create each account separately on the new DC and use "CONNECT COMPUTER" (the sbs wizard) on each workstation to join the new domain. (This will preserve local user profiles, right??)
Plan 3: If these just don't work, create each account, join each workstation to the domain, then copy the old local user account over manually to the new local user account.
Advice? Also I would like to if this takes not very long, then start the Exchange migration, using just for now, a pop3 connector. Is there some best way to do that? My plan was to create the exchange mailbox for each person, then join their outlook to it, then copy the contents of their .PST into the exchange mailbox (doing this locally on each workstation). There are some good reasons not to do everything this weekend and instead use a pop3 connector for a month or so - there are some laptops that I will not get access to (they are Macs to boot) and also I am just haven't prepared everything for a DNS switch (changing it to point to us instead of the external pop).
Thank you very much in advance to anybody who replies - I just want a little guidance.
THE WAY IT IS NOW: W2k Domain controller (is very old), a few other servers (just file servers), about 30 workstations, various printers and other devices. Email is currently POP3 hosted elsewhere.
WHAT I'M DOING: New W2k3 SBS server going in - old domain controller will be demoted but soldier on as a file server and license server for some floating licenses. When the domain was originally setup, the wag who put it in named the internal domain the same thing as the external domain (.com). I fixed this by simply putting in pointers in DNS to our externally hosted sites but it's annoying. When I put in the new controller I am changing the internal domain to a .local.
I want the fastest (but good) approach possible to finish this. It's not a big deal to create active domain accounts since there are only 30 users or so but I would rather not. What I don't want to do is spend a huge amount of time migrating each local user profile at the individual workstations (or heaven forbid corrupting user profiles).
MY GAME PLAN:
Plan 1: Turn on the new domain controller, and try to use ADMT to copy the accounts over to the new controller. If that doesn't work then:
Plan 2: Create each account separately on the new DC and use "CONNECT COMPUTER" (the sbs wizard) on each workstation to join the new domain. (This will preserve local user profiles, right??)
Plan 3: If these just don't work, create each account, join each workstation to the domain, then copy the old local user account over manually to the new local user account.
Advice? Also I would like to if this takes not very long, then start the Exchange migration, using just for now, a pop3 connector. Is there some best way to do that? My plan was to create the exchange mailbox for each person, then join their outlook to it, then copy the contents of their .PST into the exchange mailbox (doing this locally on each workstation). There are some good reasons not to do everything this weekend and instead use a pop3 connector for a month or so - there are some laptops that I will not get access to (they are Macs to boot) and also I am just haven't prepared everything for a DNS switch (changing it to point to us instead of the external pop).
Thank you very much in advance to anybody who replies - I just want a little guidance.