Just enough permissions for running Remote Powershell for Release Management RRS feed

  • Question

  • Is there a guide which we can follow detailing the minimum amount of permissions required for executing remote powershell in the context of a Release Management deployment?

    I have a vNext release so I deploying using powershell but not using DSC. I have a domain service account which I am using as the account under which the deployment should take place. I have had to do the following so far and still my deployment is not working:

    • http://blogs.msdn.com/b/powershell/archive/2009/11/23/you-don-t-have-to-be-an-administrator-to-run-remote-powershell-commands.aspx
    • https://social.technet.microsoft.com/Forums/en-US/24d5c01f-f6b7-4e06-b2e1-7cc16c4f1ad5/remote-getservice-as-normal-user-require-other-privileges?forum=winserverpowershell
    • Grant Full control to the C:\Windows\DtlDownloads folder

    The latest error I am getting in my RM logs is:

    System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> Microsoft.TeamFoundation.Release.Common.Helpers.OperationFailedException: System.AggregateException: Failed to install 'VisualStudioRemoteDeployeredb57b60-ff5a-44ca-b86f-106df43133fd' from service executable path VisualStudioRemoteDeployer.exe . Consult the logs below:
    Exception calling "SetRight" with "2" argument(s): "OpenPolicy failed: 5"
     CategoryInfo :NotSpecified: (:) [], MethodInvocationException
     FullyQualifiedErrorId :Exception
     ---> System.Management.Automation.RemoteException: Exception calling "SetRight" with "2" argument(s): "OpenPolicy failed: 5"
       --- End of inner exception stack trace ---


    Wednesday, October 28, 2015 10:18 AM


All replies