

Thanks.Īccording to your description, WinRM service can’t start up using Domain users account. I'm hoping that I have missed something really obvious to get this working. There are no events in any of the event logs. If they have no work to do, for example, the Performance Logs and Alerts service." error dialog.
#How to add a user account with winrm windows#
However when I change the 'Log on as' account to the service account for WinRM the service will not start, with the classic "The Windows Remote Management (WS-Management) service on Local Computer started and then stopped. In local computer policy I have set up explicit user rights assignment so the service account can:.Added the service account to the local IIS_WPG group.Give my service account identical privileges to the built-in NetworkService account. By default the WinRM service runs under NT AUTHORITY\NetworkService.

While not ideal, I am prepared to switch the WinRM service to use the same service accountĪs the application pool. So, now when I try to connect to the server using PowerShell remoting it is expecting the WinRM service to be running as the same service account as my application pool. Led to having to set up an SPN for my service account as per

#How to add a user account with winrm plus#
It all worked fine until I needed to set up an IIS App Pool running under a domain user, plus using integrated auth. On Windows Server 2003 R2 I have configured PowerShell 2.0 and gone through the whole Enable-PSRemoting thing.
