• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 213
  • Last Modified:

2000 domain with Exchange 2003?

Hi!

I have a Win 2000 domain today with Exchange 2000.
I have a member server running NT 4 (with a DB application that is not compatible on win 2000 Srv) in the domain.
Now I need to upgrade/ new purchase on HW that host Exchange 2000. I’m thinking that a maybe should install 2003 Srv witch Exchange 2003
I would like to get some recommendations about to solve domain level, can I keep the existing domain on 2000 level and have a 2003 Server with exchange included, or should I upgrade the domain level to only include 2003 DC’s?
0
Officeteam
Asked:
Officeteam
  • 5
  • 4
1 Solution
 
SembeeCommented:
You can run Exchange 2003 on a Windows 2003 server in a Windows 2000 domain without any problems. You don't miss much by not being at Windows 2003 native, so it isn't something to worry about at the moment.
If you do stick to Windows 2000 domain, then be sure to check for mangled attributes when doing forest prep and domain prep for Exchange 2003. Other than that it works fine.

Simon.
0
 
OfficeteamAuthor Commented:
Okay, thanks!
But can you please explane "be sure to check for mangled attributes when doing forest prep and domain prep for Exchange 2003" a litle bit closer?
The win 2003 server should in this senario not be a DC?

Peter
0
 
SembeeCommented:
That services me right for responding before eating...
The mangled attributes is a problem if you are putting Windows 2003 domain controllers in to a domain with Exchange 2000, not the other way round. So you can ignore that comment.

And yes - the Windows 2003 machine with Exchange 2003 should NOT be a domain controller. This is best practise and you will have a much better performing network.
However don't forget that changing the role of the server after Exchange has been installed is not supported. So if it was a member server then it must stay a member server.

Simon.
0
Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

 
OfficeteamAuthor Commented:
Okay,
The old server running DC and exchange will be replaced with a new Memberserver with 2003 and exchange 2003. Then it should just rock on?

Thanks!
0
 
SembeeCommented:
It should be fine.

If you haven't seen it already and you are intending to remove the original Exchange server, then this is THE article on how to do it.

http://support.microsoft.com/default.aspx?kbid=307917

Simon.
0
 
OfficeteamAuthor Commented:
until I remove the first (orginal) exchange 2000, anything to think about when I run a Exchange 2003 combi with Exchange 2000?
0
 
SembeeCommented:
Not really.
The main thing that catches people out is a smart host configured on the SMTP Virtual server. This stops email routing between the servers. Otherwise setup replication of the public and system folders first - before you move any mailboxes.
I tend to suggest going through that article up to but excluding removing the original server.

Simon.
0
 
OfficeteamAuthor Commented:
You wrote: going through that article up to but excluding removing the original server
With artical are you referencing to?
0
 
SembeeCommented:
This one.
http://support.microsoft.com/default.aspx?kbid=307917

It explains how to remove the original Exchange server. Therefore if you do every stage in that article (rehoming system folders etc) but don't actually remove the original Exchange server you can be sure that everything you need is on the new server.

Simon.
0

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now