Re: Recovering from a domain server crash without a backup.

I guess it helps if I actually give a link to the article.

http://support.microsoft.com/kb/249694/en-us


hth
DDS

"Danny Sanders" <DSanders@xxxxxxxxxxxxxxx> wrote in message
news:%23SEnzPmFIHA.1168@xxxxxxxxxxxxxxxxxxxxxxx
1) Is there ANY way to put a new domain server into an existing domain,
replacing the previous unit that crashed, without unjoining then
rejoining each and every client on the network?

When a domain is created it has a unique SID. The only way to carry that
unique SID to another DC is to install the new DC into the same domain
while it has a connection to the original DC and the unique SID will get
replicated from the original DC to the new DC. Installing a DC without it
having contact with the original DC will create a NEW SID. New SID = new
domain to your clients.


2) Same basic scenario as above only this time the server has not yet
crashed. Is there a way to export the various settings/credentials/etc
so that the newly created instance of the domain controller can simply
import them and have all the client PCs sign on like nothing has changed?

Easiest way is to have a second DC on the domain to hold the SID while you
reinstall the failed DC. If you have a server to use in the above example,
you would be better off setting it up in the domain before anything
happened to the original DC.

This article details how to move a DC installation. It's just plain
simpler and easier to have a second DC on the domain instead of trying to
move the install to another server.

hth
DDS



"Noctaire" <noctaire@xxxxxxxxx> wrote in message
news:uxbys0lFIHA.4308@xxxxxxxxxxxxxxxxxxxxxxx
1) Is there ANY way to put a new domain server into an existing domain,
replacing the previous unit that crashed, without unjoining then
rejoining each and every client on the network?

Scenario: A small company with 30-50 client PCs has a single Win2K3
domain server. All client PCs are members of the domain. The server
crashes and it is found that backups were not being performed. A new
instance, with the same domain name, is created from a fresh install.
Naturally, the existing client PCs will not be able to access the domain.
The basic solution is to remove the client PCs from the domain then join
them into the new domain to build the trust relationship with the new
domain controller. The problem though is that this means a new profile
has to be built on the client PC as well, including porting over e-mail
and the such.


2) Same basic scenario as above only this time the server has not yet
crashed. Is there a way to export the various settings/credentials/etc
so that the newly created instance of the domain controller can simply
import them and have all the client PCs sign on like nothing has changed?




.

Relevant Pages

  • Re: Recovering from a domain server crash without a backup.
    ... When a domain is created it has a unique SID. ... them and have all the client PCs sign on like nothing has changed? ... A small company with 30-50 client PCs has a single Win2K3 ... crashes and it is found that backups were not being performed. ...
    (microsoft.public.windows.server.general)
  • Re: Phantom email
    ... Two other client PCs do the same averaging about 800 ... I have Symantec Client Security on the server and done virus checks on all ... How do I track the source / paths of these emails to eliminate these? ... or put another way how do you know that the administrator account has sent and received this number of emails? ...
    (microsoft.public.windows.server.sbs)
  • FTP/Hotmail Issues with XP Clients thru SBS2003 R2
    ... I have a new SBS2003 installation with3 client PCs. ... Client PCs can log into FTP servers, but CANNOT upload files (the SBS ... but CANNOT login (the SBS Server ... thru to the netgear router ...
    (microsoft.public.windows.server.sbs)
  • Cannot send external mail from Outlook
    ... for incoming and using Smarthost to send external mail. ... none of the client PCs can send external mail from ... There was a SMTP communication problem with the recipient's email server. ... Sending using OWA from client PCs works perfectly. ...
    (microsoft.public.windows.server.sbs)
  • Re: LAN unaccesable until I disable/enable the Internet
    ... I don't always have my server switched on and I only have one router/DSL ... always on for internet access from the client PCs can be a pain. ...
    (microsoft.public.windows.server.sbs)