Environment:
- Server: Windows Server 2012
- iis:8.0
- Web Deploy component: The component itself has been brought in, and I have installed 3.5
- vs:2015
Release process:
- Set up a site on the server, bind the domain name
- VS Select the project to publish, publish
- The first step and publish to the file system, select the configuration file
- The second step is to choose web Deploy with the following configuration information
-
- Server:https://YourServerIP:8172/msdeploy.axd(if the server is on a firewall remember to open port 8172)
- Site Name:yorsitename
- UserName: Here are two options, one is Windows account, login server account password, another option is IIS user, here need to create separately, and assign permissions, later introduced
- Destination URL: Your site is bound to the domain name, according to my observation, after the successful release will open this address in the client, to facilitate viewing the results of the publication
- One step at a time, this way to publish can preview the changes
Server configuration:
First make sure that IIS and Web deploy on the server are fully installed, and it is recommended that you choose a full installation when you install Web deploy, or you may have 401 errors.
The home page is selected in IIS, and an option in the feature list is called "Manage Service".
After opening, follow the settings in the picture, primarily to enable remote connections, and to select whether to use only Windows credentials or IIS credentials as required in the identity credential.
The WMSVC service is in the list of services: Web Mangement Service
Click your site , select IIS Manager permissions in the list of features, right click Allow users, select Windows type users, add your account
Right-click the site, select Deploy-enable Web Deploy publishing
Authorized users to select the user just added in the IIS Manager permissions, the other without the tube, click Settings, the results prompt successful, close.
Here, if everything is OK, follow the release process already available. If there are 550 errors, 401 authorization errors, etc., continue looking down.
The second authorization method, IIS credential authorization, is then introduced.
This is consistent with the Windows Credential authorization step, but remember to select the IIS user when you select an authorized user.
The IIS user is created by:
Select the home page , select IIS Manager users in the features list-add users.
Other questions:
401 Authorization error, you can try the following steps as follows:
- Create Wdeployadmin and Wdeployconfigwriter in the server local user. and set the password (the fourth step will also be used). Both check the "Password never expires" option.
- Add Wdeployadmin to Administrators group
- Open c:\\windows\system32\inetsrv\config-Properties-security, add wdeployconfigwriter and give modify and Write permissions
- Open IIS and select Management Service Delegation (manage service delegation) to fill in the user name and password you added in the first step by clicking "Edit"-"settings" on the right side of all users named wdeploy* here.
550 errors, try the following steps:
- Locate the site root directory
- Properties-Security-Assign Modify permissions to local service, iis_iusers
Various issues with Web Deploy publishing site