Re: Exchange 2003 and NT4 trusted domain
From: Peter Storkey (pstorkey_at_smeghead.ca)
Date: 06/07/04
- Next message: Dave Leonardi: "Re: Exchange Mailbox creation issue"
- Previous message: Dave Leonardi: "Re: Exchange Mailbox creation issue"
- In reply to: Daryl Maunder: "Re: Exchange 2003 and NT4 trusted domain"
- Next in thread: Jeff L: "Re: Exchange 2003 and NT4 trusted domain"
- Reply: Jeff L: "Re: Exchange 2003 and NT4 trusted domain"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 07 Jun 2004 15:30:39 GMT
On Sun, 6 Jun 2004 17:55:50 +1000, in microsoft.public.exchange.setup
you wrote:
>> <newsgroupsremoveandunderscore_jeff@availabletech.net> wrote:
>
>If you run Exchange 2003, you will need to install AD on at least on
>2000/2003 server, and buy Windows 200x CALS, whether you upgrade your
>existing domain, or install a parallel one, so there isnt a cost
>justification for what you suggest.
Thanks, you are correct. I've looked into the CALS a little more, and
we will indeed need to purchase the Windows 2003 CALS even if we only
use the server for Exchange.
There is another reason for wanting to maintain the NT4 domain and use
AD only for Exchange 2003 - our existing DNS hierarchy has a subdomain
for each site, which it seems will not play nicely with Active
Directory unless we make each of those DNS subdomains a separate
domain in AD.
The DNS hierarchy is configured this way so that we can maintain
uniform naming for accessing files in remote sites. For example, if a
user in site1 types "files" into their browser, they will connect to
files.site1.domain.com and if a user in site 2 types "files" into
their browser, they will connect to files.site2.domain.com etc.
>With 220 users over 20 sites, the number of users at most sites is obviously
>pretty small. There would be no need to have a server at the remote sites,
>especially with Outlook 2003 in cached mode, which uses an offline address
>book.
Currently our NT domain has the PDC and a BDC in our head office, and
a BDC at our second largest site. All other remote sites authenticate
against from either of those two sites. Our single Exchange 5.5 server
is also located at head office and users connect to it directly across
the WAN. This has worked ok for us so far - If we upgrade the domain
to AD, will this continue to be satisfactory ?
Our workstations are all Windows - we're in the process of
standardising on XP Professional. There is a Linux box at each site
that provides file/print, http proxy and dhcp.
So, as I see it, these are our choices:
Purchase Windows 2003 Server and CALS plus Exchange 2003 and CALS
Install a brand new AD and establish a trust between NT 4 and AD
Install Exchange 2003
Migrate mailboxes
Associate Exchange 2003 mailboxes with NT 4 accounts
PROs:
Existing DNS hierarchy is maintained
Strategy of migrating domain to Linux is maintained
CONs:
This seems to be possible but complicated and not recommended...
OR
Purchase Windows 2003 Server and CALS plus Exchange 2003 and CALS
Flatten DNS hierarchy
Upgrade NT 4 domain to AD
Install Exchange 2003
Migrate mailboxes
PROs:
Gives full benefit of AD to users
Simpler administration
CONs:
Flattened DNS hierarchy reduces functionality
Unable to migrate domain to Linux (Linux servers can remain member
servers)
I have a feeling that the first scenario will end up being more
trouble than it's worth. The overall goal is stability and user
satisfaction, so I guess we're going to have to seriously consider the
second option.
Thanks everyone for your comments and suggestions,
Pete
- Next message: Dave Leonardi: "Re: Exchange Mailbox creation issue"
- Previous message: Dave Leonardi: "Re: Exchange Mailbox creation issue"
- In reply to: Daryl Maunder: "Re: Exchange 2003 and NT4 trusted domain"
- Next in thread: Jeff L: "Re: Exchange 2003 and NT4 trusted domain"
- Reply: Jeff L: "Re: Exchange 2003 and NT4 trusted domain"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
