3

This is a 2-part question:

  1. Is there anything in a Windows Server 2003 domain environment that would cause accounts granted Log On As A Service rights to lose those rights after a few hours?
  2. And if not, am I just going insane?

2 accounts used for Office Communication Server on a Windows 2003 OCS server. Services start fine, then after stopping them, on next start, they are not granted the Log On As A Service right. Grant them, and the services start again.

... and then we repeat. What in the world would cause this?

0

2 Answers 2

4

Every few hours, eh? Hmm... sounds like Group Policy refresh.

Sounds like you've got a GPO overriding the local security policy.

Run Resultant Set of Policy (RSoP) on one of the affected server computers and see if you see a GPO doing anything with the "Logon as a Service" user rights assignment. My guess is that you do.

Either alter the GPO to include the accounts that need the right or change the scope of the GPO not to apply to those computers.

1
  • Yep, that's pretty much perfect timing for a Group Policy refresh.
    – mrdenny
    Jul 29, 2009 at 2:25
0

Note that this also applies to newer versions of Windows. The instructions to enable a domain user (or group) to retain this right after a GPO refresh are outlined very well here: https://www.coretechnologies.com/blog/windows-services/windows-service-forgets-password/. In case this goes away, I will summarize it here:

  1. Open the Group Policy Management Editor (not the local policy editor)
  2. Find your domain in the forest, right-click on 'Default Domain Policy', just inside it and choose 'Edit'.
  3. Navigate the tree to Computer Configuration/Windows Settings/Security Settings/User Rights Assignment (click there)
  4. Scroll down to 'Log on as a service' and double-click it
  5. Click 'Add User or Group' and add the user you want to have this right
  6. Click OK.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .