title: What permissions are required for a Release Management 2013 vNext release using Powershell
body: <p>I've configured the deployment to a web server using a service account. On the target machine remote powershell is enabled and the account has been added to the Remote Management Users group.</p>
  
  <p>I initiate a release and the following error occurs. If I add the service account to the local Administrators group on the web server then it succeeds. I can reproduce the same error by remoting into the web server, under the service account, and attempting to call <code>get-service</code>.</p>
  
  <pre><code>System.AggregateException: 
  Cannot open Service Control Manager on computer '.'. This operation might require other privileges.
   CategoryInfo :NotSpecified: (:) [Get-Service], InvalidOperationException
   FullyQualifiedErrorId :System.InvalidOperationException,Microsoft.PowerShell.Commands.GetServiceCommand
   ---&gt; System.Management.Automation.RemoteException: Cannot open Service Control Manager on computer '.'. This operation might require other privileges.
     --- End of inner exception stack trace ---
     at Microsoft.VisualStudio.Services.DevTestLabs.Deployment.Deployment.PowershellExecutor.Invoke(String errorContextMessage, Boolean writeResultToLog, Boolean isCancellable)
     at Microsoft.VisualStudio.Services.DevTestLabs.Deployment.Deployment.RemoteDeploymentHelper.AcquireMutexOwnerShip(String serviceName, String destinationPath, Int64 deploymentHeartbeatTimeoutSec)
     at Microsoft.VisualStudio.Services.DevTestLabs.Deployment.Deployment.DeploymentClient.&lt;RunAsync&gt;d__14.MoveNext()
  </code></pre>
  
  <p>Does anyone know the minimum permissions required for a service account to get this working? I want to avoid adding the account to the Administrators group.</p>