Migration: 2000 Server DC with Exchange to single 2003 SBS Premium
Hello,
I have been hired to perform migration from old 2000 Server with AD and Exchange 2000 to new server box running SBS 2003 Premium. I do not have too much information about current setup, below is what I got so far about old server setup (old system administrator left the company with all the information about setup, customer knew just administrator's password :-) :
Old server (Dual P III CPUs) act as domain controller for domain name alpha.com (all domain names are unreal, used as example for purposes of current question). However, all email processed by exchange and received by users is for accounts ending xxxxx@beta.com. I don't know how previous sysadmin set it but it worked fine.
Server is running DNS, but there is no DHCP server set (all workstations use static private IPs, ipconfig shows DHCP enabled: no).
1. So, I have to install 2003 SBS on new box (which I already did, but right now it is just separate server without AD and all followinf tasks). New server (lets name it SBS) will be domain controller for domain "beta.com". Old domain name "alpha.com" will be not in use once migration is done and old 2000 server is retired. I have to migrate all user accounts (or I can re-create them on SBS, they are only 10-12 users), and there are no complicated policies or so on old 2000. They use just one shared folder and one network printer. Probably it will be really easier just to set new SBS as domain controller for beta.com and then just create necessary user accounts, what do you think? New setup will use DHCP as opposite to old. Also, I'm planning to use built-in ISA server - that's why I bought server with 2xLANs.
2. The next task will be more difficult. I have to migrate email accounts or do whatever I need to do to have all old email, contacts, calendars and tasks inported in appropriate user acconts on new SBS server. They do not use any shared calendars or contacts, but some accounts are with thousands messages and when I looked on the server, the space used by files in Exchange server folder (where priv1.edb and priv1.stm files are located, ) is about 16GB. I have no idea is there any problem because old domain name is alpha.com and new one will be beta.com... How can I do this? What is the easiest way? Can I just simply extract all user information and save it as separate files and then use tool to import it to each user account at SBS? Or I should create the same set of accounts on new server and then import the whole database?
3. Once everything is done, I have to run through each workstation and login using new accounts because right now they login as user@alpha.com and with new server it will be user@beta.com. That means their email must be already imported in their accounts on new SBS. I don't see any easier way to setup workstations for new server, but maybe you know....
I have remote access to the server so if you need more details, please let me know, I'll be happy to obtain this information ASAP. The migration process should be done until Monday morning, so I have 4 days including Thanksgiving :-). Although I have some experience with regular Windows 2000/2003 setups, this will be my first attempt to migrate and manage exchange. I'll try to get more information from other questions here, at EE, but most of them cover different scenarios. Some of them contain iformation about SwingMigration, is it something I can use in my case with different domains? I will prefer to use regular methods if possible, at least because they are free.
All your help will be greatly appreciated, I may need to ask you additional questions to clarify the steps.
Thanks.
I have been hired to perform migration from old 2000 Server with AD and Exchange 2000 to new server box running SBS 2003 Premium. I do not have too much information about current setup, below is what I got so far about old server setup (old system administrator left the company with all the information about setup, customer knew just administrator's password :-) :
Old server (Dual P III CPUs) act as domain controller for domain name alpha.com (all domain names are unreal, used as example for purposes of current question). However, all email processed by exchange and received by users is for accounts ending xxxxx@beta.com. I don't know how previous sysadmin set it but it worked fine.
Server is running DNS, but there is no DHCP server set (all workstations use static private IPs, ipconfig shows DHCP enabled: no).
1. So, I have to install 2003 SBS on new box (which I already did, but right now it is just separate server without AD and all followinf tasks). New server (lets name it SBS) will be domain controller for domain "beta.com". Old domain name "alpha.com" will be not in use once migration is done and old 2000 server is retired. I have to migrate all user accounts (or I can re-create them on SBS, they are only 10-12 users), and there are no complicated policies or so on old 2000. They use just one shared folder and one network printer. Probably it will be really easier just to set new SBS as domain controller for beta.com and then just create necessary user accounts, what do you think? New setup will use DHCP as opposite to old. Also, I'm planning to use built-in ISA server - that's why I bought server with 2xLANs.
2. The next task will be more difficult. I have to migrate email accounts or do whatever I need to do to have all old email, contacts, calendars and tasks inported in appropriate user acconts on new SBS server. They do not use any shared calendars or contacts, but some accounts are with thousands messages and when I looked on the server, the space used by files in Exchange server folder (where priv1.edb and priv1.stm files are located, ) is about 16GB. I have no idea is there any problem because old domain name is alpha.com and new one will be beta.com... How can I do this? What is the easiest way? Can I just simply extract all user information and save it as separate files and then use tool to import it to each user account at SBS? Or I should create the same set of accounts on new server and then import the whole database?
3. Once everything is done, I have to run through each workstation and login using new accounts because right now they login as user@alpha.com and with new server it will be user@beta.com. That means their email must be already imported in their accounts on new SBS. I don't see any easier way to setup workstations for new server, but maybe you know....
I have remote access to the server so if you need more details, please let me know, I'll be happy to obtain this information ASAP. The migration process should be done until Monday morning, so I have 4 days including Thanksgiving :-). Although I have some experience with regular Windows 2000/2003 setups, this will be my first attempt to migrate and manage exchange. I'll try to get more information from other questions here, at EE, but most of them cover different scenarios. Some of them contain iformation about SwingMigration, is it something I can use in my case with different domains? I will prefer to use regular methods if possible, at least because they are free.
All your help will be greatly appreciated, I may need to ask you additional questions to clarify the steps.
Thanks.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
If macs are a factor, then I'd recommend using .lcl instead of .local. The mac issues are purely with OS 10.2 and earlier aand then only with .local - not any other domain (like .lcl).
ASKER
Thanks, leew
In the meantime, I've got an idea about how (maybe) i can do my migration.
1. I will install SBS and cannet to the Internet using second ISP / router and domain name beta.lcl to avoid problems with Macs.
2. Will create accounts for about 10 users on new SBS server, assign rights, etc.
3. Then I will use ExMerge tool ( http://www.microsoft.com/downloads/details.aspx?FamilyID=429163ec-dcdf-47dc-96da-1c12d67327d5&displaylang=en ) to extract user's data into separate .PST files which I will later import/merge to newly created user accounts on new server. I was thinking also about using local .PST files on workstations which I can archive and then import into their new accounts locally on their machines. Once it's done, they will be uploaded on the server, right? The problem with local databases is that I should change mail delivery location to personal folders and it will take alot of time. Also, I have no idea how I can do it on Mac so I will need to create temporary accounts for Mac users on PCs just to download their data and have it for migration. So if ExMerge can extract this data on the server and then import it on new server regardless of differencies (maybe) in account names this solution should work for me.
Red something about offline defrag...should I use it?
4. Next step will be to sit on each workstation and join new domain (several hours downtime will be not a problem, I can replace old server with new one once I finished with ExMerge), create new user accounts, copy all their files and setting up their Outlook clients. Found some info about Active Directory Migration Tool v.2.0 ( http://www.microsoft.com/downloads/details.aspx?FamilyID=788975b1-5849-4707-9817-8c9773c25c6c&displaylang=en ) but still not sure is it helpful in my situation (can't understand how it work, Microsoft doesn't explain it well).
5. Will need to copy shared folder to new location and share it - bot a big deal. Printers also.
For small network probably this is the easiest way. What do you think, will it work?
2 leew: sbsmigration.com's product... are you familiar with it? Will it work in my case? Because I'm going to use different domain name, and I have no idea how it will migrate Exchange since the original server is set for different domain.. Is the migration process using their tools long, how long it may last? What is involved in this process? I found this:
- [TempDC] Clean install a Windows 2003 Server (using SBS media) as a workgroup server only.
- Manually join it to the existing SBS domain, preparing this server as a Temp DC.
- Install DNS, perform DCpromo and designate as a Global Catalog Server.
- Replicate DNS and AD then shutdown and disconnect
- Seize all FSMO roles
- Purge the Active Directory metabase and DNS of all previous Domain Controllers, Exchange and DNS Server references
- [FinalDC] Clean install Windows 2003 Server just as before, reuse the original SBS Server name and IP. This server will look just like the previous SBS for name, IP, AD, and UNC/URL paths.
- Install DNS, perform DCpromo, designate as Global Catalog Server.
- Replicate DNS and AD.
- Seize all FSMO roles, purge the Temp DC from DNS and AD
- Finish normal SBS Setup using this Server
- Complete the balance of migration of Exchange, all Data, and shared resources
- If desired, perform a migration of the intact Exchange Information Store as a direct mount of the previous Information Store as if it were an offline restore. Reconnect mailboxes.
- Perform a direct substitution of the new server for the old SBS
- Deploy Applications as normal for SBS.
... but it looks like they use the same domain name for migration, in my case new domain name means new user accounts for local machines... And as I see, I have to re-install Windows one more time during the migration...
awaiting...
In the meantime, I've got an idea about how (maybe) i can do my migration.
1. I will install SBS and cannet to the Internet using second ISP / router and domain name beta.lcl to avoid problems with Macs.
2. Will create accounts for about 10 users on new SBS server, assign rights, etc.
3. Then I will use ExMerge tool ( http://www.microsoft.com/downloads/details.aspx?FamilyID=429163ec-dcdf-47dc-96da-1c12d67327d5&displaylang=en ) to extract user's data into separate .PST files which I will later import/merge to newly created user accounts on new server. I was thinking also about using local .PST files on workstations which I can archive and then import into their new accounts locally on their machines. Once it's done, they will be uploaded on the server, right? The problem with local databases is that I should change mail delivery location to personal folders and it will take alot of time. Also, I have no idea how I can do it on Mac so I will need to create temporary accounts for Mac users on PCs just to download their data and have it for migration. So if ExMerge can extract this data on the server and then import it on new server regardless of differencies (maybe) in account names this solution should work for me.
Red something about offline defrag...should I use it?
4. Next step will be to sit on each workstation and join new domain (several hours downtime will be not a problem, I can replace old server with new one once I finished with ExMerge), create new user accounts, copy all their files and setting up their Outlook clients. Found some info about Active Directory Migration Tool v.2.0 ( http://www.microsoft.com/downloads/details.aspx?FamilyID=788975b1-5849-4707-9817-8c9773c25c6c&displaylang=en ) but still not sure is it helpful in my situation (can't understand how it work, Microsoft doesn't explain it well).
5. Will need to copy shared folder to new location and share it - bot a big deal. Printers also.
For small network probably this is the easiest way. What do you think, will it work?
2 leew: sbsmigration.com's product... are you familiar with it? Will it work in my case? Because I'm going to use different domain name, and I have no idea how it will migrate Exchange since the original server is set for different domain.. Is the migration process using their tools long, how long it may last? What is involved in this process? I found this:
- [TempDC] Clean install a Windows 2003 Server (using SBS media) as a workgroup server only.
- Manually join it to the existing SBS domain, preparing this server as a Temp DC.
- Install DNS, perform DCpromo and designate as a Global Catalog Server.
- Replicate DNS and AD then shutdown and disconnect
- Seize all FSMO roles
- Purge the Active Directory metabase and DNS of all previous Domain Controllers, Exchange and DNS Server references
- [FinalDC] Clean install Windows 2003 Server just as before, reuse the original SBS Server name and IP. This server will look just like the previous SBS for name, IP, AD, and UNC/URL paths.
- Install DNS, perform DCpromo, designate as Global Catalog Server.
- Replicate DNS and AD.
- Seize all FSMO roles, purge the Temp DC from DNS and AD
- Finish normal SBS Setup using this Server
- Complete the balance of migration of Exchange, all Data, and shared resources
- If desired, perform a migration of the intact Exchange Information Store as a direct mount of the previous Information Store as if it were an offline restore. Reconnect mailboxes.
- Perform a direct substitution of the new server for the old SBS
- Deploy Applications as normal for SBS.
... but it looks like they use the same domain name for migration, in my case new domain name means new user accounts for local machines... And as I see, I have to re-install Windows one more time during the migration...
awaiting...
2. Use the wizards to create the accounts if you don't use SBS Migration
3. An offline defrag shouldn't be necessary. But be prepared for exmerge to take considerable time. To help speed, use another physical local disk (if possible). You MAY try a USB drive, but make sure it's operating at 2.0 speeds and not USB 1.1 speeds.
Exmerge doesn't care about names other than user names. And if those change between domains, just rename the PST files to match the new account names (not @ - just the plain old usernames).
4. AD Migration tool can be used... I despise it as you'll often spend hours trying to get it to work right and troubleshooting why user x had a problem. If you don't use it and you don't use the sbsmigration tools, you will lose your user profiles and everyone will start from scratch. Data won't be lost but registry settings will. There is a tool on my tech tools page (don't recall the name of it now) that may be able to migrate user profiles, but the last time I used it, there were sporadic issues (sorry, I don't recall what - nothing show stopper, just annoying reset of this item or something). Look for the newer version - ADMT 3.0 (That profile tool I mentioned can be found on www.lwcomputing.com/tips/static/techtoolkit.asp
5. About 14 months ago, I rebuilt the domain for a client of mine with 15 workstations. It took me 2 days (plus hours of little annoyances (like "why aren't the e-mail addresses in outlook auto-filling in?"). It was the first SBS domain I setup and I changed the system to a hardware RAID reinstalled from scratch. You'd think it would be easy... but there's a LOT of work, even for 10 machines. This is why a migration is still preferable. You said you have some SBS customers already. I believe the SBSMigration pack is a technician license that you can use for other clients... even if it doesn't prove appropriate for you here, it's an excellent tool to have. I've only been consulting full time and using SBS mostly for the last 3 years. To date, none of my clients have migrated from an existing domain (SBS or otherwise) to a new SBS 2003 system (at least none with any semblance of a real domain setup). So I have yet to have the opportunity to use the SBS Migration toolkit. I'd tell you to hold off and see if Jeff or another SBS expert can chime in, but it's a holiday weekend and you're on deadline that might find no one else sees this until after your deadline. All I can say is like I said before... the one guy who posted recently in a question I participated in who said he had a problem with it, still wholeheartedly recommended it to the asker of the question.
I'm not sure off hand about the other thing you found... and I'm afraid my brain is shutting down for the night (bad thing - I still have a 45 minute drive home). I'll try to check back in 48 hours (just moved, no internet at home - only the office). Hopefully someone else can continue helping you.
3. An offline defrag shouldn't be necessary. But be prepared for exmerge to take considerable time. To help speed, use another physical local disk (if possible). You MAY try a USB drive, but make sure it's operating at 2.0 speeds and not USB 1.1 speeds.
Exmerge doesn't care about names other than user names. And if those change between domains, just rename the PST files to match the new account names (not @ - just the plain old usernames).
4. AD Migration tool can be used... I despise it as you'll often spend hours trying to get it to work right and troubleshooting why user x had a problem. If you don't use it and you don't use the sbsmigration tools, you will lose your user profiles and everyone will start from scratch. Data won't be lost but registry settings will. There is a tool on my tech tools page (don't recall the name of it now) that may be able to migrate user profiles, but the last time I used it, there were sporadic issues (sorry, I don't recall what - nothing show stopper, just annoying reset of this item or something). Look for the newer version - ADMT 3.0 (That profile tool I mentioned can be found on www.lwcomputing.com/tips/static/techtoolkit.asp
5. About 14 months ago, I rebuilt the domain for a client of mine with 15 workstations. It took me 2 days (plus hours of little annoyances (like "why aren't the e-mail addresses in outlook auto-filling in?"). It was the first SBS domain I setup and I changed the system to a hardware RAID reinstalled from scratch. You'd think it would be easy... but there's a LOT of work, even for 10 machines. This is why a migration is still preferable. You said you have some SBS customers already. I believe the SBSMigration pack is a technician license that you can use for other clients... even if it doesn't prove appropriate for you here, it's an excellent tool to have. I've only been consulting full time and using SBS mostly for the last 3 years. To date, none of my clients have migrated from an existing domain (SBS or otherwise) to a new SBS 2003 system (at least none with any semblance of a real domain setup). So I have yet to have the opportunity to use the SBS Migration toolkit. I'd tell you to hold off and see if Jeff or another SBS expert can chime in, but it's a holiday weekend and you're on deadline that might find no one else sees this until after your deadline. All I can say is like I said before... the one guy who posted recently in a question I participated in who said he had a problem with it, still wholeheartedly recommended it to the asker of the question.
I'm not sure off hand about the other thing you found... and I'm afraid my brain is shutting down for the night (bad thing - I still have a 45 minute drive home). I'll try to check back in 48 hours (just moved, no internet at home - only the office). Hopefully someone else can continue helping you.
ASKER
Still not finished with migration :-( Got several problems with existing network setup like router and firewall devices which serve old production server but nobody know the passwords for them, and also they are very old (no GUI, just CLI). So first I have to discover how to setup the network in proper way because right now all the workstations are connected directly to the router (which is Riverstone RS3000 with 24-port switch) and use static public IPs (!). Don't ask me why previous administrator set it this way :-)
So I'm going to ask some additional questions relared to my currents problems and once I finish with them I'll come back here to finish with Exchange.
So I'm going to ask some additional questions relared to my currents problems and once I finish with them I'll come back here to finish with Exchange.
ASKER
When I started workstations were with static public IPs, I had to set private IPs for them to allow them to share files.
ASKER
Finally got everything up and running, I didn't use any tools for migration - just set new server and created accounts on it from scratch as I described in my comment above. Then imported old user Exchange data into new accounts locally from .PST files. Thanks for all your help, guys.
ASKER
The problem with domain name beta.local vs beta.com was discussed with you before here:
In my current case, they use 4 Macs in their network, and I remember that .local can cause problems if the default domain name ends of .local. If there is not a problem for Macs to join domains with .local - fine, I can name it beta.local, but if it, it there any reason why I can't name it beta.com? Will .local simplify the setup, or opposite, will .com make it more difficult?
P.S. I'm going to read some info from your page as well. I have some SBS installations behing, but customers does not use exchange, just AD part and SBS...