Windows Server 2008 and Exchange 2000 (Full Version)

All Forums >> [Microsoft Exchange 2000] >> General



Message

outerheaven11 -> Windows Server 2008 and Exchange 2000 (8.Jul.2008 2:54:20 PM)

I have a Windows 2000 domain with Exchange 2000 in a small office. The main domain controller and Exchange 2000 are on separate Windows Server 2000 boxes. I have one additional Server 2000 box on the network for redundancy for AD and DNS, nothing else.

I want to update to Server 2008 to replace my aging 2000 Server primary domain controller (I'm simply referring to the FSMO holder in this case). Exchange 2000 is still working fine and if possible, I want to avoid having to pony up several thousand dollars for a new version of Exchange, Windows Server and new hardware at this point. Ideally I would like to upgrade our domain to be 2008 compatible and run by the 2008 server as the FSMO holder / main file and application server with Exchange 2000 remaining on the other 2000 server.

Is it possible to have this configuration with Server 2008, or do I need to upgrade my domain to be 2003-compatible first and move on from there? Has anyone else worked with a similar configuration? What other issues or concerns should I be aware of?

Here's the setup I have versus what I would like to have:

Currently:

Win2k Server 1 - FSMO holder / file, print and app server, AD, DNS, DHCP
Win2k Server 2 - Exchange 2000
Win2k Server 3 - redundancy for AD and DNS

Desired:

Win2008 Server - FSMO holder / file, print and app server, AD, DNS, DHCP
Win2k Server 2 - Exchange 2000
Win2k Server 3 - redundancy for AD and DNS (is this still possible on a 2008 domain?)

Would scrapping our current configuration and installing a fresh domain using SBS 2008 be a better solution for a 30 person office that needs Exchange for e-mail?  Any help or feedback would be greatly appreciated.  Thanks.



Jesper Bernle -> RE: Windows Server 2008 and Exchange 2000 (8.Jul.2008 3:05:45 PM)

quote:

ORIGINAL: outerheaven11

...

Would scrapping our current configuration and installing a fresh domain using SBS 2008 be a better solution for a 30 person office that needs Exchange for e-mail?  Any help or feedback would be greatly appreciated.  Thanks.


It would be more cost effective but if you´re thinking aling those lines, why not even consider Essential Business Server 2008?



outerheaven11 -> RE: Windows Server 2008 and Exchange 2000 (8.Jul.2008 4:22:23 PM)

I wasn't aware that a public beta was available, thanks.  Downloading now. 



Exchange_Geek -> RE: Windows Server 2008 and Exchange 2000 (9.Jul.2008 1:13:31 AM)

  • Exchange Server 2003 Service Pack 2, Exchange 2007, and Exchange 2007 SP1 (when released) are supported in environments that either partly or entirely use writeable Windows Server 2008 directory servers.
  • Exchange 2000 Server Service Pack 3 and all previous versions of Microsoft Exchange are not for use with Windows Server 2008 directory servers. The following restrictions apply with respect to Exchange 2000 Server Service Pack 3:
    • Exchange 2000 Server Service Pack 3 can exist in an Active Directory forest that contains Windows Server 2008 directory servers, but Windows Server 2008 directory servers should not be installed in Active Directory Sites that contain Exchange 2000 Server.
    • If Windows Server 2008 directory servers must be deployed Active Directory Sites that contain Exchange 2000 Server you must first hard-code directory service access (DSAccess) on the Exchange 2000 Server servers in the site to point to directory servers running Windows Server 2003 or Windows 2000 Server.

  • No version of Microsoft Exchange uses read-only domain controllers (RODCs) or read-only global catalog servers (ROGCs). However, Microsoft Exchange works in environments that include RODCs or ROGCs, as long as there are writeable domain controllers available. Exchange 2007 effectively ignores RODCs and ROGCs. Exchange 2003 also ignores RODCs and ROGCs in default conditions where Exchange components automatically detect available domain controllers. No changes were made to Exchange 2003 to make it read-only directory server-aware. Therefore, trying to force Exchange 2003 services and management tools to use RODCs may result in unpredictable behavior.

http://msexchangeteam.com/archive/2007/08/16/446709.aspx



Page: [1]