Home
> Uncategorized > 401 Not Authorized For MSDEPLOY (msdeployAgentService)
401 Not Authorized For MSDEPLOY (msdeployAgentService)
When you get this error from msdeploy:
“Error: The remote server returned an error: (401) Unauthorized.”
you need to give the remote user elevated rights to get authorization.
http://support.microsoft.com/kb/951016
http://blogs.msdn.com/b/vistacompatteam/archive/2006/09/22/766945.aspx
To disable UAC remote restrictions, follow these steps:
- Click Start, click Run, type regedit, and then press ENTER.
- Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
- If the LocalAccountTokenFilterPolicy registry entry does not exist, follow these steps:
- On the Edit menu, point to New, and then click DWORD Value.
- Type LocalAccountTokenFilterPolicy, and then press ENTER.
- Right-click LocalAccountTokenFilterPolicy, and then click Modify.
- In the Value data box, type 1, and then click OK.
- Exit Registry Editor.
Categories: Uncategorized
THANK YOU!
muchas gracias
You are a god amongst men. I was trying to web deploy to Windows 7 with RemoteAgent and getting “An unsupported response was received. The response header ‘MSDeploy.Response’ was ‘V1′ but ‘v1′ was expected. The remote server returned an error: (401) Unauthorized.” and this fixed it. Thank you so so so much.
thank you so much!
Why didn’t I find this post 4 hours ago.
yes…i have same feeling..
thx for posting this solve
help me a lot!!
you made my day !!!!
Why is there no hint doing that in the documentations from Microsoft?
This worked for me. I tried various combinations of msdeploy.adx, msdeployagentservice, http, https, windows auth, windows + iis auth, etc.
My settings from VS2012 to a Windows 7 Server
Publish Method: Web Deploy
Service URL: http://IPOnLocalVPN/msdeployagentservice
Site / Application: Default Web Service/myApp
User Name: MachineName\Admin
Password: blah
Pretty agonizing that all of the MS documentation fails to mention this little key. I guess my naive question is this a fail in the documentation, or a workaround because I didn’t do something else? (Keeping in mind that I worked on this connection problem for about 7 hours as an IIS noob, and read ~20 different articles from different sources on Web Deploy and then error remediation).
Blech.