This is the eighth or ninth machine I have downloaded MSDeploy to and have never had this problem before.
Whenever I try to deploy to the new machine I get the error message in the title. In searching the message on the web it seems that MSDeploy creates two user names (WDeployAdmin & WDeployConfigWriter). For whatever reason, they were not added on this server.
I checked the companion server that it will eventually be clustered with and, sure enough, both names were there.
I tried manually adding the user names and adding the new user to the Administrators group but that has also failed.
Not sure if I understand exactly what's gonig on - is the problem that you are getting errors when trying to do delegated actions for providers with those runAs users? By "cluster" do you mean that shared config will be used? (If yes on shared config, you
would probably want to skip the "Configure for Non-Administrator Deployments" component in the installer that sets up those rules, as WDeployAdmin and WDeployConfigWriter are created as local accounts, and won't work in shared config - or replace the users
in the delegation rules the first time you install with domain users instead and then skip that step for the other machines). Another item is that even if you add or change those accounts, you have to make sure to also update the delegation rule RunAs with
the user's current password, as this is stored in administration.config and would not be updated automatically.
If you can be a little more explicit about what is failing, I might be able to suggest a more targeted check or change to try.
webRonin
55 Posts
Login Failure: unknown user name or bad password
Mar 09, 2012 01:15 PM|LINK
This is the eighth or ninth machine I have downloaded MSDeploy to and have never had this problem before.
Whenever I try to deploy to the new machine I get the error message in the title. In searching the message on the web it seems that MSDeploy creates two user names (WDeployAdmin & WDeployConfigWriter). For whatever reason, they were not added on this server. I checked the companion server that it will eventually be clustered with and, sure enough, both names were there.
I tried manually adding the user names and adding the new user to the Administrators group but that has also failed.
What the heck is happening here?
krolson
350 Posts
Microsoft
Re: Login Failure: unknown user name or bad password
Mar 16, 2012 05:17 PM|LINK
Not sure if I understand exactly what's gonig on - is the problem that you are getting errors when trying to do delegated actions for providers with those runAs users? By "cluster" do you mean that shared config will be used? (If yes on shared config, you would probably want to skip the "Configure for Non-Administrator Deployments" component in the installer that sets up those rules, as WDeployAdmin and WDeployConfigWriter are created as local accounts, and won't work in shared config - or replace the users in the delegation rules the first time you install with domain users instead and then skip that step for the other machines). Another item is that even if you add or change those accounts, you have to make sure to also update the delegation rule RunAs with the user's current password, as this is stored in administration.config and would not be updated automatically.
If you can be a little more explicit about what is failing, I might be able to suggest a more targeted check or change to try.