Re: SAM Database Corrupt

This may seem like I'm nitpicking, but the distinction will become important
momentarily.

SBS 2008 (nor 2003 nor 2000) use SAM if they are domain controllers. SAM
was an NT4 technology and is only used for local authentication. Domain
authentication is handled by AD and (ideally) Kerberos.

This distinction is important because AD was built from the ground up to be
far more resilient than the old SAM database. Since the AD database would
be subject to unknown network conditions and would be passed around via
multi-master replication, the last thing MS wanted was one corruption being
passed around to an entire domain forest. AD, therefore, has a ton of
sanity checks built in. So the first order of business is to view the
system event logs and see what is happening with your system. No fix can be
proposed without knowing what went wrong.

-Cliff


"KenMoran" <> wrote in message
news:...
>
> Hi,
> I have a SBS 2008 std server that suddenly decided to forget all of the
> user passwords, in short the SAM database has gone bad on me.
>
> Can anyone suggest the best (read least destructive) way to recover
> form this. I'm going to attempt to boot into Active Directory recovery
> mode but any suggestions would be most welcome.
>
>
> --
> KenMoran
> ------------------------------------------------------------------------
> KenMoran's Profile: http://forums.techarena.in/members/158265.htm
> View this thread:
> http://forums.techarena.in/small-bus...er/1275212.htm
>
> http://forums.techarena.in
>