WORKGROUP\MACHINENAME$ explanations

• alucpu

  SSC Enthusiast

  Points: 187

  More actions

  April 13, 2019 at 12:33 pm

  #3261068

  Hello everyone,

  I have a Window Server 2016 no domain controller but just the default WORKGROUP, with a local MSSQLSERVER 2017 instance, and an IIS Server 10.

  If the application pool try to access SQL Server with the following accounts:

  IIS APPPOOL\website.com is impersonated as IIS APPPOOL\website.com

  LocalService is impersonated as NT AUTHORITY\LOCAL SERVICE

  NetworkService is impersonated as WORKGROUP\SERVERNAME$

  LocalSystem is impersonated as WORKGROUP\SERVERNAME$

  I'd like to know why is used the account WORKGROUP\SERVERNAME$ for network service and system,

  Whereas on my old Window Server 2008 R2 this behaviour was not present.

  I've been digging a lot, most people say that when your try to reach a remote resource the user WORKGROUP\SERVERNAME$ is used,

  but in my case I'm connecting from the local server to the local sql server instance using a similar connection string:

  Data Source=(local);Integrated Security=True;......

  Thanks for your help.