Can anyone tell me why lsass.exe is HOGGING the cpu after I install AD? I
have re-installed the machine with 2003 server, joined the domain as a
domain controller and bang! 100% cpu making the machine unusable!

Thanks,
Grant

Enable auditing of logon success\failure. This is the first thing to look at
.. If you have services that are trying to start using a nonexistent user
account this can cause it.

--
Richard McCall [MSFT]

"This posting is provided "AS IS" with no warranties, and confers no
rights."
"Grant" <gpsnett@hotmail.com> wrote in message
news:u%23Bn7O%233DHA.2468@TK2MSFTNGP09.phx.gbl...

Any idea on how to do set up auditing? It is a domain controller and when I
go to gpedit.msc >computer config>windows settings>security settings>local
policy - I see a list of things I can audit, but when I double click one the
options are greyed out. I don't know how to enable them?

Thanks,

Grant

"Richard McCall [MSFT]" <richmcc@online.microsoft.com> wrote in message
news:OLaRpfC4DHA.2348@TK2MSFTNGP10.phx.gbl...