Re: Restoring Trusts between client workstations and Domain Contro
- From: "Danny Sanders" <Danny.Sanders@xxxxxxxxxxxxxxxxx>
- Date: Mon, 2 May 2005 13:47:47 -0600
> 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.
>> >
>>
>>
>>
.
- Follow-Ups:
- References:
- Prev by Date: Perfmon
- Next by Date: DNS Entries missing
- Previous by thread: Re: Restoring Trusts between client workstations and Domain Contro
- Next by thread: Re: Restoring Trusts between client workstations and Domain Contro
- Index(es):
Relevant Pages
|
