Windows Server

MarkB · Guest

Sorry for the long message, but I thought specific detail might be good.

Our small company consists of 2 home offices that are networked via VPN over
the internet through broadband provided by cable companies. We have
implemented a single Windows 2000 domain. Each office has a Windows 2000
server that is a domain controller and is also an Exchange 2000 server.
There are a set of public Exchange folders that are replicated on each
server, so we have dual access to email messages (correspondence with
customers, etc.) One of the servers houses Visual Source Safe databases (we
are a development shop). We use SourceGear's SourceOffSite to access Source
Safe remotely. We each have a stand-alone Win2k server that routes VPN
traffic (this server is not member of the domain). We each have about 6
desktop/laptop client machines that are domain members. Note that we only
use Exchange to store and share emails; all external email traffic goes
through POP/SMTP servers on our commercially hosted internet domain
(separate/different from our Windows domain).

A few months ago both sites started having some odd Exchange problems; not
being able to send email, some Exchange services not starting, etc. Some of
these issues have been resolved (with Microsoft Support help using MSDN
Universal support incidents). As it stands, my partner cannot get Exchange
up (Attendant service wont start). Microsoft's solution is to uninstall IIS,
re-install IIS, reinstall Exchange and apply service packs.

Before these problems, we were planning to migrate to Windows Server 2003
and Exchange 2003. I purchased a new server box, and was going to bring this
up as a domain controller in the domain, install Exchange 2003 and VSS,
migrate data, etc. But with the issues we now have, I'm concerned that this
approach may have us migrate our problems as well.

So I was thinking that I might just create a new windows domain that the new
server box would be a domain controller of, with fresh installs of Exchange
2003 and Source Safe. We could then just copy the data over to the new
server. Then my partner could wipe his server's disk and do a fresh install
of Windows Server 2003 and Exchange 2003 as well. This would also allow us
to keep working in the old domain until the new one was completely ready.

Can anyone see why this is not a good way to go? I know I'd have to recreate
user accounts, etc. in the new domain ... but is there some "gotcha" to this
approach that I'm not seeing?

Thanks for any insights ...

Mark

Vincent Xu [MSFT] · Guest

Hi Mark,

We have 2 choices, in-place upgrade or restructure.

Reasons to upgrade:

1. Similar domain structures suitable to the needs of the organization.
2. Offers lowest risk/shortest time/fewest resources/no new servers.

Reasons to restructure:

1. Existing structure does not meet needs.
2. Organization cannot tolerate downtime.
3. Need optimum domain structure.

I think following 2 articles may help you make a decision.

Restructuring Active Directory Domains Between Forests
<http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/DepK
it/cead3dc3-4920-4b7a-b6fe-6111d44110b3.mspx>

Upgrading from Windows 2000 Domains to Windows Server 2003 Domains
<http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/DepK
it/8d926ba4-0323-45a6-96f0-db7f7cb33f6b.mspx>

Hope it helps.

Best regards,

Vincent Xu
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security

--------------------

	Windows Server Forum Index -> Migration	All times are GMT
Page 1 of 1