Windows service start issue when using a service account - UPN vs samAccountName

Fix Computer 21 Reputation points
2022-08-26T01:50:14.73+00:00

We have a domain joined Windows Server 2019 with some services that are required to run with a service account.

When the service is configured to use domain\ServiceAccountName (samAccountName), the service starts automatically on Windows start-up.

When the service is configured to use ServiceAccoutnName@keyman (UPN), the service is unable to start automatically on Windows start-up, but i can login to Windows and manually start the service with no issue. The service can also start automatically with UPN when the startup type is set to Automatic (Delayed Start).

The error in Windows event log is "The account name is invalid or does not exist, or the password is invalid for the account name specified". Event ID is 7000.

We have a workaround but would like to know why, appreciate if some one can shed some light on this issue.

Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
3,457 questions
0 comments
Accepted answer
  1. Dave Patrick 426.1K Reputation points MVP
    2022-08-28T12:59:31.98+00:00

    Possibly something about the network was not ready. May need to wireshark it.

    --please don't forget to upvote and Accept as answer if the reply is helpful--

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Dave Patrick 426.1K Reputation points MVP
    2022-08-26T14:11:48.607+00:00

    May be a small one but I believe the samAccountName will search the domain and the UPN will search the forest for the account.

    --please don't forget to upvote and Accept as answer if the reply is helpful--