Re: Restoring Trusts between client workstations and Domain Controller



> 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: Restoring Trusts between client workstations and Domain Contro
    ... copying and pasting a backup of their "Windows Special Folder"? ... >> 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: 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: passing object ByRef not updating object references
    ... Thanks for a quick reply Sam, but I'm afraid nothing has changed as of yet. ... Public Sub ClientChangedImplements ... Now I'll keep the client connected and stop the server and in the process, ...
    (microsoft.public.dotnet.framework.remoting)
  • Re: Cannot Use System Infomation Function
    ... Thanks, Sam. ... > "Can't collect information Access denied to Windows Management ... > Instumentation server on this computer. ... >> My profile has administrator privileges. ...
    (microsoft.public.windowsxp.general)

Loading