Exchange Server Forums
Forums |
Register |
Login |
My Profile |
Inbox |
RSS 
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
Windows 2003 Migration
|
Users viewing this topic:
none
|
Logged in as: Guest
|
Login  | |
|
 Limited time MSExchange.org offer! -- 1.Sep.2008 1:00:00 PM
|
|
TechGenix and SolarWinds have partnered to provide free copies of SolarWinds Exchange Monitor to all visitors who join the MSExchange.org Forums. SolarWinds Exchange Monitor is a handy desktop dashboard that continuously monitors Microsoft Exchange to deliver real-time insight into Exchange services, mail queue sizes, and host server health. Learn more about Exchange Monitor and the free offer!
|
Windows 2003 Migration - 21.May2004 9:37:00 PM
|
|
|
Scuba Steve
Posts: 62
Joined: 13.Aug.2003
From: Oldsmar, FL
Status: offline
|
I would like to bounce a few questions off of you in order to have a better understanding of the steps to take in order to:
1. Migrate a Windows 2000 Domain Controller (sseco-01) to a new Windows 2003 Server (sseco-dc). Including moving all 5 FSMO roles to this server, and also all files and folders as this server will also be our file server (with permissions).
2. Move all mailboxes from our Exchange 2000 server (which is also the old domain controller sseco-01) to the new Exchange 2003 server.
The question I have is: Is it better to do the domain controller tasks first or do the Exchange tasks first?
I have found the MS KB article 324801 ôHOW TO: View and Transfer FSMO Roles in Windows Server 2003ö which gives me detailed instructions on how to transfer the 5 FSMO roles. I donÆt think that will be a problem. But how can I easily move the files and folder with permissions to the new server? Can I even back up the share permissions and just restore the entire share with files to the new server?
For Exchange, the Mailbox move wizard will be utilized to move all mailboxes and the pfmigrate.wsf tool will be used to replicate the public folders from the Exchange 2000 server to the 2003 server. But what do I need to change as far as the new domain controller settings? I think I need to change the Recipient Update Service Server from the old sseco-01 to the new sseco-dc. Is this correct? Is there anything else that I need to do considering the DC changes and the decommissioning of the Exchange 2000 server?
|
|
|
|
|
RE: Windows 2003 Migration - 26.May2004 7:19:00 PM
|
|
|
Scuba Steve
Posts: 62
Joined: 13.Aug.2003
From: Oldsmar, FL
Status: offline
|
Anyone?
|
|
|
|
|
RE: Windows 2003 Migration - 28.May2004 7:16:00 PM
|
|
|
Randy Temple
Posts: 158
Joined: 1.Aug.2002
From: Michigan
Status: offline
|
Scuba steve,
I was in the kind of the same situation you were. It really doesnt matter which one you do first. I would suggest doing you windows 2000 role promotion first. If you are in native mode in windows 2000 look up the kb article to promote a 2003 server into a windows 2000 native mode domain. The orginal 2000 domain controller will have to be shut down while promoting the 2003 server. I would suggest doing this first because transfering roles in a ad enviornment can be the toughest thing to do. I transfered my roles pretty easy. I would suggest not having all of your roles on the same server, microsoft says you should not have a global catalog server and your infrastructure master on the same server. I would also suggest not having this server act as your file server either. It is just me but if my server is a DC that is all i want it to do. Again just my thought process.
With the excahnge migration i would suggest bringing up and 2003server with ex2003 create a test account make sure they can send innner office and it routes mail to the outside. Slowly move on part of your org over if all goes well contiune to mover more people.
|
|
|
|
|
RE: Windows 2003 Migration - 28.May2004 7:20:00 PM
|
|
|
Randy Temple
Posts: 158
Joined: 1.Aug.2002
From: Michigan
Status: offline
|
Witht the exchange tasks it has utilities you can run from it. It will test your envoirnmet to see if it will install correctly. You will have to run a domain prep and i believe a forest prep. forgive my ignorance i went through this proccess 4-5 months ago and i forgot, but there is a utility that will run you through the proper steps to install exchange03.
After your role transfer i would suggest leavign it up for a couple of days check the event logs on the new server just to make sure everything is kosher. Then if all is good from your enviornment i would suggest going through with the mail server implementation.
|
|
|
|
|
RE: Windows 2003 Migration - 28.May2004 7:52:00 PM
|
|
|
Randy Temple
Posts: 158
Joined: 1.Aug.2002
From: Michigan
Status: offline
|
Question about the filtering:
I was looking at that how would that work with public folders? We have mail sent from the outside into our public folders. We are regulated by the state we sell wine and liquor and have new licenses sent to these folders. If you are filtering recipients who are not in the dircetory would this filter out my public folders?
|
|
|
|
|
RE: Windows 2003 Migration - 28.May2004 8:00:00 PM
|
|
|
Scuba Steve
Posts: 62
Joined: 13.Aug.2003
From: Oldsmar, FL
Status: offline
|
Are you asking about the new Intelegent Message Filter? Or the recipient restrictions under the Message delivery propertys in global settings.
I think the recipient restrictions will not accept e-mails to addresses that do not exist in the active directory. So if someone was just trying to spam your server with emails to some address that really doesn't exist, Exchange 2003 would not accept the message because the address doesn't exist. This saves your server from having to generate NDR's that gets hung up in the SMTP outbound queue.
|
|
|
|
|
RE: Windows 2003 Migration - 28.May2004 8:51:00 PM
|
|
|
Randy Temple
Posts: 158
Joined: 1.Aug.2002
From: Michigan
Status: offline
|
Are you asking about the new Intelegent Message Filter? Or the recipient restrictions under the Message delivery propertys in global settings.
I think the recipient restrictions will not accept e-mails to addresses that do not exist in the active directory. So if someone was just trying to spam your server with emails to some address that really doesn't exist, Exchange 2003 would not accept the message because the address doesn't exist. This saves your server from having to generate NDR's that gets hung up in the SMTP outbound queue.
ans: i was talking about the global setting unders message deliver. The check box states that "filter recipients that are not in the active directory". My question is they are a recipient in AD correct. Granted they are not a user but they have some sort of variable to recieve an email message from the outside. I would assume they would be labeled a recipient. I dont know if this is correct. IF they are labeled a "recipient" then this filter would allow messages to be routed correctly to them.
|
|
|
|
|
RE: Windows 2003 Migration - 28.May2004 8:56:00 PM
|
|
|
Scuba Steve
Posts: 62
Joined: 13.Aug.2003
From: Oldsmar, FL
Status: offline
|
Right! quote:
|
|
|
|
 New Messages |
 No New Messages |
 Hot Topic w/ New Messages |
 Hot Topic w/o New Messages |
 Locked w/ New Messages |
 Locked w/o New Messages |
|
 Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts |
|
Printable Version
