Domain controllers CPU pinned

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Our DCs CPUs are pinned at 100% by the system process and the LSASS process.
We use SMS 2.0 and it looks like the SMS clients (aprox 3000 clients) are
trying to authenticate multiple times per second, which in turn pins these
processes on the DC's. I have tried restarting the server service which
helps temporarily. Anyone see a similar problem with SMS 2.0 clients and
win2k DC's?
 
I've seen quite the opposite --in fact, I've got a case open as we speak re.
this issue (lots of auth reqs) but against the Primary SMS server (a member
not a DC).

What accounts is SMS using? The DCs use different accounts to the clients
(introduced in SP5 to remove a number of the known lockout issues).

If LSASS is sapping your memory --you've got a leak. There've been a number
of leaks -especially depending on the SP update route you took.

Can you give us a bit more info.? e.g. OS, SP level, SMS SP level, how you
know SMS is chucking so many auth packets, etc.

You might find it helpful to cross post (not multipost) this into the SMS
groups too.
 
We are running win2k SP4. SMS 2.0 is running sp5.
The DC's security logs are showing several dozen account logon event ID 673
or 672 event ids per sec per workstation. Source is security. It looks like
the account is SMSClient_(sitename) account. These DCs are remote location
servers that are also CAP's for SMS.
 
Yes, that's the account for clients to talk to a CAP and/ or DP.

Have you, by any chance, restored a CAP from backup recently? You can
'resync' that password, I believe, by reinstalling SMS (or perhaps the SP)
on the site server in question.

Here's a KB:
-- http://support.microsoft.com/?id=227033


Perhaps you can now crosspost to the SMS groups...
 
Back
Top