Re: Add Workstations to Domain


"FrankVrba" <FrankVrba@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3C957D3E-8AC8-46DA-930C-1D8FD4E372AC@xxxxxxxxxxxxxxxx
Herb,

What if you have several DCs. Can one of them be demoted and promoted
into
the same domain?

Sure, but why would you do that?

I've never done that but I did consider it once when an
issue came up. What about the FSMO? Thanks.

You must/should make arrangements for FSMO, GC, DNS, and WINS (if
you are in a routed environment) when you remove DCs that have any of these
jobs.


--
Frank


"Herb Martin" wrote:


"Somchai" <Somchai@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6CAECA69-86A0-493D-BA75-939DA8CB8B5E@xxxxxxxxxxxxxxxx
I don't know where to start. First off all I had a complete screwed up
AD
and no DNS anymore and I couldn't install the DNS anymore.

Then we have to get that fixed. What does it mean "couldn't install the
DNS
anymore"?

You can pretty much always INSTALL DNS Server -- if you cannot do that
due to disk problems or your server OS/registry is screwed up you might
need to restore a System State Backup (you have one, right?) or do a
REPAIR INSTALL (from the original CDROM into the current installation
direction, being sure to CONFIRM the REPAIR.)

As no users could
login to the DC anymore (the PC's still could access other PC's which
were
shared) I demoted and then promoted the AD again.

Don't do that (anymore). It is practically never necessary.


Now accessibility to the
server is here again, however, I still see all the PC's I can not
access
the
shares anymore and there are no PC's shown in the Computers in the AD.

You recreated the Domain (when you re-installed AD) so you must now
re-add the computer accounts and rejoin them to the domain.

Your users will need new accounts as well and you have likely screwed up
your PROFILES so they will reset to the default (by default).

Is it
possible to reinstate these PC's to the AD whithout joining them new to
the
new AD?

No, not unless you have that System State Backup (or an ASR backup.)

Never re-install AD like that unless you wish to destroy the domain and
all accounts (both user and computer.)

Thanks





.

Relevant Pages

  • Re: removal of one of my AD-Integrated DNS servers
    ... After that check that DNS is complete cleaned from it. ... Then you can start with a fresh install and promote it again to DC. ... My thought was to wipe the upgraded DCs clean and install 2003 ... upgrading, I usually shy away from upgrades because of the *junk* ...
    (microsoft.public.win2000.dns)
  • Re: Deader than a doorknob PDC w/AD
    ... the two DCs with some reservations. ... > roles and which one hosts DNS. ... > always advise to install the Support Tools and the Resource Kit Tools ... On the W2K DC check which DCs host the FSMO roles. ...
    (microsoft.public.windows.server.active_directory)
  • Re: event ID: 1083 and 1955 ntds replication
    ... ensure that the DNS zone for your domain allows Dynamic Updates ... DCs at this DC for DNS. ... Check replication and force replication. ... You install the support tools either from your Windows installation ...
    (microsoft.public.windows.server.active_directory)
  • Re: Bind 8.x 2003 Clarification
    ... > All clients XP/2000 point to Unix Bind servers for name resolution. ... > None of the DCs have DNS installed. ... the DNS management console without DNS installed requires you to install the ...
    (microsoft.public.windows.server.dns)
  • Re: Preparing network connection after AD install
    ... I didn't install exchange yet. ... known symptoms of having exchange installed on DC and bad DNS ... Do not place the ISP DNS server or any other DNS on the ...
    (microsoft.public.windows.server.active_directory)