Re: Restoring Trusts between client workstations and Domain Contro

Thanks Danny,

Same proceedure used repeatedly for Roaming Profiles. It's as good as it's
going to get, time to get busy.



"Danny Sanders" wrote:

> > 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?
>
>
>
>
> See:
>
>
> http://support.microsoft.com/default.aspx?scid=kb;en-us;255095
>
>
> hth
> DDS W 2k MVP MCSE
>
>
>
> "PapaGus" <PapaGus@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:C5F9C06B-E770-43D0-8D86-75C12853ED4C@xxxxxxxxxxxxxxxx
> > 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: 1 PC out of 20 cannot join Domain
    ... >> Is this computer pointed at the same DNS server as the PCs that can join? ... >> DDS W 2k MVP MCSE ...
    (microsoft.public.win2000.active_directory)
  • Re: The 8 megabytes reserved by Windows XP
    ... >>The 8 meg are there in case you convert your basic disks to dynamic disks. ... >>DDS W 2k MVP MCSE ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Multiple Domains
    ... >> I would start with creating a trust between the two domains. ... >> DDS W 2k MVP MCSE ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD/DNS infrastructure (long)
    ... > DDS W 2k MVP MCSE ... Yes, you're absolutely correct. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Joining PCs to Multiple Domains
    ... I don't think there is a way to do this without a third party app. ... DDS W 2k MVP MCSE ...
    (microsoft.public.windows.server.general)