What if the domain controller is also the exchange server? Can it remain
this way or should I separate the two . This small network with a low
usage
Exchange server with about 30 mailboxes.
Darrell
"Al Mulnick" <amulnick_No_SPAM@ncDOTrr.com> wrote in message
news:eMBEIBHSFHA.356@TK2MSFTNGP14.phx.gbl...
If that's the case, then likely it's best to introduce the new forest and
Exchange server and then migrate the users/mailboxes over.
Something like ADMT and or PFMIGRATE would be helpful there.
Al
"Darrell" <darrell_eddy@bellsouth.net> wrote in message
news:uEuugKFSFHA.1528@TK2MSFTNGP09.phx.gbl...
Yes. The applications are a client server app and exchange services
Darrell
"Al Mulnick" <amulnick_No_SPAM@ncDOTrr.com> wrote in message
news:ODpginESFHA.1528@TK2MSFTNGP09.phx.gbl...
What you're talking about sounds like you want to migrate to a new
domain
altogether.
Is that possible with your applications and such?
Al
"Darrell" <darrell_eddy@bellsouth.net> wrote in message
news:OvhBDeCSFHA.2788@TK2MSFTNGP09.phx.gbl...
Current Network scenario
FS1: Windows 2000 running DNS, and DHCP. It also houses the user
home
directories and Exchange 2000 for about 30 mailboxes, and is also
the
Domain
controller
FS2: Windows 2000 running SQL 2000, but not taxed at all.
Plan
Add a new server to replace FS1, upgrade to Exchange 2003, and
possibly
move
the user home directories to FS2, or a third server.
The current domain is the same as the registered public domain which
is
company.org; and I think I should move it to something like
company.local.
So, I believe that I also need to create a new domain and move all
network
resources from company.org, to company.local.
I need to some guidance as to how to accomplish all of this, or some
additional direction or suggestions.
Reply With Quote