Re: adding client machines to active directory after changing DC
From: scottohiocomp (scottohiocomp_at_discussions.microsoft.com)
Date: 07/30/04
- Next message: Steven Cooke: "Re: Pushout and remove UltraVNC automatically"
- Previous message: Kevin Weilbacher: "Re: Pushout and remove UltraVNC automatically"
- In reply to: anonymous_at_discussions.microsoft.com: "Re: adding client machines to active directory after changing DC"
- Next in thread: Danny Sanders: "Re: adding client machines to active directory after changing DC"
- Reply: Danny Sanders: "Re: adding client machines to active directory after changing DC"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 30 Jul 2004 06:07:02 -0700
the situation didn't allow me to follow "best practices". does anyone have any suggestions on ways to do what i want to do in my situation, instead of ways i should have done what is already behind me?
"anonymous@discussions.microsoft.com" wrote:
> Agreed with the first response about having at least a 2nd
> dc for a replicated environment.
>
> Do you have backup? The answer better be Yes. If you do,
> you may be able to perform an authoritative restore and
> that may work also.
>
> If you don't have a backup, add this to your list of best
> practices.
>
> You can automate joining the domain by using NETDOM that
> is in the support tools. Please see
> http://support.microsoft.com/default.aspx?scid=kb;en-
> us;329721
>
> best of luck
> >-----Original Message-----
> >>I had a windows 2000 server domain controller that was
> dying from old age.
> >We bought a new server, installed and >configured Windows
> 2000 server and
> >exchange 2000 with the exact computer name, domain name,
> tcp/ip settings,
> >>everything the same as the old server. We recreated
> users in active
> >directory. After configuring, we simply disconnected
> >the old domain
> >controller from the network and connected the newly
> configured box.
> >
> >What you did was create a NEW domain. Even if you name it
> the same and
> >replicate TCP/IP settings, it is still seen as a new
> domain by the computers
> >because the SID is different.
> >
> >A better way to do it would have been to add the new DC
> to the existing
> >domain, transfer the FSMO roles and Global Catalog, set
> up DNS on the new
> >DC, point your AD clients to the new DNS server then
> demote the original DC.
> >Since you started off by adding the new DC to the
> existing domain the domain
> >SID will be replicated to the new DC and it will be seen
> as in the same
> >domain. No need to worry about resetting user profiles.
> >
> >One of the "best practices" for a domain is to have a
> second DC in the
> >domain in case the first DC crashes, the second DC will
> continue to hold all
> >domain/user info (SID).
> >
> >What you are going to have to do is go to each computer
> and add them to the
> >NEW domain.
> >
> >You see how much work has to be done if your original DC
> crashes, I would
> >suggest setting up a second DC on your new domain now.
> >
> >hth
> >DDS W 2k MVP MCSE
> >
> >"scottohiocomp" <scottohiocomp@discussions.microsoft.com>
> wrote in message
> >news:4B4EA11B-5D33-4007-B084-5F549A61467E@microsoft.com...
> >> Here is the situation: I had a windows 2000 server
> domain controller that
> >was dying from old age. We bought a new server,
> installed and configured
> >Windows 2000 server and exchange 2000 with the exact
> computer name, domain
> >name, tcp/ip settings, everything the same as the old
> server. We recreated
> >users in active directory. After configuring, we simply
> disconnected the
> >old domain controller from the network and connected the
> newly configured
> >box. Everything worked fine. The only problem is, is
> that none of the
> >users computers show in active directory, which creates
> problems with global
> >policy and such. I know we can go to each clients pc,
> and go through my
> >computer and run the network identification wizard, and
> then their computer
> >will show in active directory, but then I have to
> reconfigure all of their
> >desktop settings.
> >>
> >> Does anyone know of a easier way to get all of these
> computers to appear
> >in active directory. When I browse the network, it still
> shows all of the
> >computers, just not in active directory.
> >>
> >> Thanks
> >> Scott
> >
> >
> >.
> >
>
- Next message: Steven Cooke: "Re: Pushout and remove UltraVNC automatically"
- Previous message: Kevin Weilbacher: "Re: Pushout and remove UltraVNC automatically"
- In reply to: anonymous_at_discussions.microsoft.com: "Re: adding client machines to active directory after changing DC"
- Next in thread: Danny Sanders: "Re: adding client machines to active directory after changing DC"
- Reply: Danny Sanders: "Re: adding client machines to active directory after changing DC"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
