URGENT!!!

[Roy Avery]

When we created our domain (Win2K Server on all DC's), we created our first DC, followed by a second
DC, which is also our Exchange Server, for the same site. One thing I've noticed, is that if our
first DC is down, our users will not get their login script, nor can they connect to their Exchange
Mailboxes. I've been told in the exchange2000.admin group that it is because our Exchange server DC
was never made into a GC. I'll take care of that after I take care of my first priority listed
below.

Last night, we had a catastrophic failure on our first DC. I reinstalled the OS and made it a
member of our domain. I am currently inventorying and cataloging my backup tapes. I do the
Grandfather, Father, Son backup scheme. My last successful backup was yesterday at 8:00 PM. So, I
have a Full Friday backup, and four Incremental backups, Monday through Thursday. I obviously need
to restore the System State, and am assuming this will automatically make the machine a DC again.
Do I only need to restore the System State from my last Incremental backup, or do I restore starting
with Friday, and ending with my last Incremental?

Once this is done, how do I make my second DC of the site, our Exchange server, able to supply the
login scripts, and to allow users to connect to their Exchange Mailboxes?

Thank you so much for the help.

 

[Roy Avery]

Sorry, I forgot the whole subject line.

 

[Herb Martin]

When we created our domain (Win2K Server on all DC's), we created our first DC, followed by a second
DC, which is also our Exchange Server, for the same site. One thing I've noticed, is that if our
first DC is down, our users will not get their login script, nor can they connect to their Exchange
Mailboxes. I've been told in the exchange2000.admin group that it is because our Exchange server DC
was never made into a GC. I'll take care of that after I take care of my first priority listed
below.

For small networks just make all DCs into GCs.

But this might not be your only problem -- DNS is a likely
additional or actual culprit. Exchange NEEDS that GC.
All the clients need DNS to be right.

Last night, we had a catastrophic failure on our first DC. I reinstalled the OS and made it a
member of our domain. I am currently inventorying and cataloging my backup tapes. I do the
Grandfather, Father, Son backup scheme.

Rotate 3 tapes, I suppose.

My last successful backup was yesterday at 8:00 PM. So, I
have a Full Friday backup, and four Incremental backups, Monday through Thursday. I obviously need
to restore the System State, and am assuming this will automatically make

the machine a DC again.

Yes, and it is ONLY on the Full -- an incremental cannot do System State
-- IF you have it selected for that backup.

Do I only need to restore the System State from my last Incremental

backup, or do I restore starting

with Friday, and ending with my last Incremental?

Incrementals have NOTHING to do with the System State.

Once this is done, how do I make my second DC of the site, our Exchange server, able to supply the
login scripts, and to allow users to connect to their Exchange Mailboxes?

You might want to do the "restore from backup" anyway, but if
you prefer you can also just do a "new DCPromo" since you
(seem to) have another DC.

Check DNS:: Dynamic
All internal machines (including DCs and DNS servers) are CLIENTS
of that internal, dynamic DNS (on their NIC properties) ONLY.
Multiple DNS servers (if any) must be fully replicated.

 

[Roy Avery]

Vamsi. No, I was not able to restore my DC with the System State backup. When I did, the machine
would not load the OS. It would blue screen due to an "Inaccessible Boot Device". Apparently it
was a driver issue. I was forced to sieze the FSMO rolls from Active Directory with my second DC
and also use the ADSI Edit utility to remove my original DC from Active Directory. Then I
reinstalled everything from scratch on the original DC and dcpromo'd it to a DC again. There was a
lot of work spent in vain before resorting to this. I wish I would have done that from the
beginning.

----------

Hello Mr.Roy Avery



this is Vamsi. I saw your posting in Microsoft Newsgroups with subject

"URGENT". are you able to sort the problem by restoreing Systemstate

backup.is the server automatically promoted as DC after restoring System

Sate backup.



Please tell me, as i have simmilar problem, our manager decided to use the

present server for other purpose and he provided new server for DC.now i

have to keep this new server in place of Old server. i dont want to disturb

that domain as i have 50 workstations connected to that domain.



can you please suggest with your experience.



Thanks in Advance.

Vamsi.