Re: Changing from a "child like" parent domain to a proper top level domain

Changing a domain name is neither a simple or riskless endeavor, especially
under Windows 2000. And in your situation I can see nothing on the
positive side of the ledger whatsoever to warrant such a change. The use
of a domain name such as "private.company.com" is perfectly proper and even
has some advantages when structuring public/private DNS. It's just a name - leave
well enough alone.

I personally would prefer a dc/gc at the remote site, but this depends on the
capabilities of the remote server, the VPN bandwidth and reliability, and
your own preferences. It should at least be a member server to facilitate
manageability.

Steve Duff, MCSE, MVP
Ergodic Systems, Inc.

<GreenWeenie65@xxxxxxxxx> wrote in message news:1124513700.663933.244770@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
A question for the wise members of this newsgroup from a lurker. I
have inherited the following infrastructure;

20 users at site A. Two Win2k servers with AD running in mixed mode.
The AD was configured as xxx.yyy.com. The primary server is the domain
controller and runs file and print sharing, while Exchange 2k is
running on the secondary server which is not a domain controller.
Email addresses are user@xxxxxxxx

5 users at a remote site, connected by VPN to Site A One Win2k server
running in workgroup mode for file and print sharing. The users
connect to Site A to access the exchange server.

I think the preferred arrangement would be a single yyy.com domain,
with three member servers. I can set up two OUs to manage users and
resources based on their location, but I don't think they need to
have their own xxx.yyy.com domain forest.

I am looking for the simplest path from "here" to "there" and
would appreciate any input. The steps I am currently considering:

· Create the yyy.com AD on the remote site Win2k server.
· Join the xxx.yyy.com AD to the yyy.com AD
· Move all active directory objects from xxx.yyy.com to yyy.com
· Demote the xxx.yyy.com server and since it was the only DC,
deleting its domain
· Have the two head office Win2k servers join the new yyy.com AD.
Promote one or both to be DC.

Would this plan work? Are there any pitfalls or roadblocks in adopting
this approach? What steps (if any) would be required within exchange?
FYI we are considering an upgrade to Win2k3/Ex2003 so if that would
make things easier, we'd do that upgrade first.


.

Relevant Pages

  • Re: Okay, what now?? Cannot publish -- now this is really strange
    ... If this fails to help then ask your host to run a Server Health Check on ... But -- I could see the remote site in FP. ... publish four new pages and three new photos. ... window; local website is in the left-side window. ...
    (microsoft.public.frontpage.programming)
  • RE: VPN Router query
    ... remote site to windows 2003 server on the main site. ... Then the SBS and Windows member server also connect to the switch. ... server and paste the results to the newsgroup. ...
    (microsoft.public.windows.server.sbs)
  • Re: Error 1054
    ... instead the remote site user will still use the ... Exchange server, the issue should be caused by the group policy is blocked ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • Re: Windows 2000 Server Replication Problem
    ... Just because you can ping a remote site doesn't mean that you can ... If you don't have the support tools installed, install them from your server ... Run dcdiag, netdiag and repadmin in verbose mode. ... I am having windows server 2000 Replication problem as follows ...
    (microsoft.public.win2000.active_directory)
  • Re: Changing from a "child like" parent domain to a proper top level domain
    ... At your remote site promote a member server to a domain controller (If you ... Make sure ALL clients are pointing to your AD dns server. ... · Create the yyy.com AD on the remote site Win2k server. ...
    (microsoft.public.win2000.active_directory)