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

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. ... If you have a server to use in the above example, ... 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: Remote debugging?
    ... I have a remote client who is experiencing crashes in an MDI application I'm responsible for. ... I've tried to obtain as much information as possible in the form of data files, event logs and registry settings etc as well as user descriptions but I'm still unable to recreate the crashes locally. ... You don't need to send the .pdb files but you do need to send the .exe/dll's with debug info so that Dr. Watson will record stack dumps with full symbolic info. ...
    (microsoft.public.vc.mfc)
  • Re: Can we upgrade the OEMSBS2000 to SBS2003 R2
    ... missing a strong benefit of having a server to manage the emails. ... SCS personal firewall should not be confused with ISA client FW. ... For the client PCs: after you complete setting up SBS2k3, ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: Can we upgrade the OEMSBS2000 to SBS2003 R2
    ... but still I need to disconnect all the client pcs(I ... server and join to new server) - correct? ... "Eugene Tan" wrote: ... For the client PCs: after you complete setting up SBS2k3, ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: Can we upgrade the OEMSBS2000 to SBS2003 R2
    ... but still I need to disconnect all the client pcs(I ... server and join to new server) - correct? ... For the client PCs: after you complete setting up SBS2k3, ...
    (microsoft.public.backoffice.smallbiz2000)