Re: Restoring Trusts between client workstations and Domain Contro



Ok, I know running only one DC in a production environment is risky but small
businesses have limited financial resources and who thought Windows could
crash unrecoverable?

Is this to say that brute force is my only option? If so, is there a
cleaner method of preserving and transferring the user's settings other than
copying and pasting a backup of their "Windows Special Folder"? A lot of
information gets lost in the process; like desktop configuration, Outlook
E-mail Account settings (Office 2k isn't as neat as Office 2003), etc...

Any input would be nice.



"Danny Sanders" wrote:

> > A recent problem left us with corrupt operating system forcing a rebuild
> > of
> > the server without the benefit of recent backup of SAM and SID's. How do
> > I
> > go about restoring communication between the client workstations (they
> > were
> > never disjoined from the Domain) and the newly configured Domain
> > Controller
> > with Active Directroy.
>
>
> A rebuild of the server created a new SAM. New SAM = new domain to your
> clients. You have to join the clients to the new AD domain.
>
>
> > A brute force method of leaving the Domain to join a workgroup, then
> > rejoining the Domain will work but is awfully messy and time consuming...
> > not
> > to mention the loss of some user settings.
>
> Yes it is. This is why one of MS's best practices is to add a second DC to
> the domain. If one fails the other will hold the SAM of the domain while you
> recreate the failed DC. This will eliminate the need to join your users to a
> "new" domain.
>
>
> hth
> DDS W 2k MVP MCSE
>
> "PapaGus" <PapaGus@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:A5967E43-B7BD-4783-9330-C29525E4F8DB@xxxxxxxxxxxxxxxx
> > Scenario: Windows 2k Advanced Server on small network of less than twenty
> > client workstations (WinXP Pro and Win2k Pro), running Active Directory.
> >
> > A recent problem left us with corrupt operating system forcing a rebuild
> > of
> > the server without the benefit of recent backup of SAM and SID's. How do
> > I
> > go about restoring communication between the client workstations (they
> > were
> > never disjoined from the Domain) and the newly configured Domain
> > Controller
> > with Active Directroy.
> >
> > The best I've been able to achieve is logon using credentials assigned to
> > "Active Directory Users and Computers", but Security Policies are not
> > applied
> > and resources are not being shared.
> >
> > A brute force method of leaving the Domain to join a workgroup, then
> > rejoining the Domain will work but is awfully messy and time consuming...
> > not
> > to mention the loss of some user settings.
> >
> > Any help is appreciated.
> >
>
>
>
.



Relevant Pages

  • RE: fallback solution for NT 4.0 upgrade
    ... Regarding the backup of SAM database, I would like to suggest some ... Using REGBACK will copy the records from the SAM into a new file. ... BACKUP directory already exists on drive C, and Windows NT is also ... | I have an NT 4.0 server I'd like to upgrade to 2000. ...
    (microsoft.public.windows.server.migration)
  • Re: Cannot Use System Infomation Function
    ... Most welcome, Sam. ... Scroll down to Server and make sure it is started. ... Troubleshooting Windows XP ... > I should mention also that when I close the System Information program, ...
    (microsoft.public.windowsxp.general)
  • Re: Restoring Trusts between client workstations and Domain Contro
    ... > businesses have limited financial resources and who thought Windows could ... >>> the server without the benefit of recent backup of SAM and SID's. ... >>> go about restoring communication between the client workstations (they ...
    (microsoft.public.windows.server.general)
  • Re: Upgrading from NT 4.0 to 2000 server
    ... > your windows 2000 member server up as a backup domain controller, ... In NT 4.0 the NT 4.0 PDC is the only DC that carries a writeable copy of the ... SAM, You MUST upgrade the existing NT 4.0 PDC to AD first in order to carry ... How to Upgrade Windows NT Server Version 4.0 to Windows 2000 ...
    (microsoft.public.win2000.general)
  • Re: Restoring Trusts between client workstations and Domain Controller
    ... A rebuild of the server created a new SAM. ... > client workstations, ...
    (microsoft.public.windows.server.general)