Web 部署代理可以在 IIS6 上的 80 以外的端口上运行吗?
我在使用 Windows 2003 机器时遇到了一些挑战,我需要在非 80 的端口上运行 Web 部署代理。默认情况下,MsDepSvc 将在 http://[server]/MsDeployAgentService 公开端点它显然隐式侦听端口 80。
我遇到的问题是该计算机还运行使用端口 80 的 Visual SVN Server,因此 Web 部署代理服务拒绝启动。 (至少这是我能得出的唯一合乎逻辑的结论。)我在同一台机器上有一个小型 SVN 管理应用程序,我想通过 Web 部署发布它,因此出现了难题。
是否可以在另一个端口上运行代理?显然,如果这是 IIS7,我们将使用 8172,一切都会很好,但不幸的是,这里的情况并非如此。有什么建议吗?
I've got a bit of a challenge with a Windows 2003 machine where I need to run the web deploy agent on a port which isn't 80. By default, MsDepSvc will expose an endpoint at http://[server]/MsDeployAgentService which obviously implicitly listens on port 80.
The problem I have is that the machine is also running Visual SVN Server which is using port 80 and as a result, the web deployment agent service refuses to start. (At least this is the only logical conclusion I can draw.) I have a small SVN management app on the same machine which I'd like to publish over web deploy hence the conundrum.
Is it possible to run the agent on another port? Obviously if this was IIS7 we'd be on 8172 and everything would be fine but unfortunately that's not the case here. Any suggestions?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(4)
有几种方法可以执行此操作:
选项 1:卸载并重新安装指定不同的端口:
命令行安装 MsDeployAgentService 并将其配置为侦听端口 8172,就像在 IIS7 上一样。
选项 2:重新配置现有服务以侦听端口 8172:
停止 msdepsvc (
net stop msdepsvc
)编辑以下注册表值:
它看起来像:
更改为:
查询 HTTP 侦听器:
您应该会看到结果中列出以下条目:
修改侦听器:
这应该响应:
HttpDeleteServiceConfiguration Completed with 0.
这应该响应:
HttpSetServiceConfiguration Completed with 0.
/a
开关中指定的 ACL 应与httpcfg query urlacl
命令报告的 ACL 匹配重新启动 msdepsvc (
net start msdepsvc
)。您可以通过执行以下操作来确认该服务正在侦听端口 8172:
<前><代码>netstat -an
您应该看到以下内容:
警告:
我会首先在非生产计算机上尝试此操作,以确保这正如你所期望的那样工作。
There's a couple of ways to do this:
Option 1: Uninstall and re-install Specifying a different port:
The command line installs the MsDeployAgentService and configures it to listen on port 8172 just like on IIS7.
Option 2: Re-configure Existing Service to listen on port 8172:
Stop the msdepsvc (
net stop msdepsvc
)Edit the following registry value:
It'll look something like:
Change to:
Query HTTP listeners:
Your should see the following entry listed in the results:
Modify listener:
This should respond with:
HttpDeleteServiceConfiguration completed with 0.
This should respond with:
HttpSetServiceConfiguration completed with 0.
The ACL specified in the
/a
switch should match the ACL reported by thehttpcfg query urlacl
commandRestart the msdepsvc (
net start msdepsvc
).You can confirm that the service is listening on port 8172 by doing:
You should see the following:
Warning:
I would try this on a non-production machine first to ensure this works as you expect.
这些是我必须按照 Kev 的秘诀对 Windows 7 进行的更改:
步骤 3:
netsh http show urlacl
第 4 步:
netsh http 删除 url=http://+:80/MSDEPLOYAGENTSERVICE/
netsh http 添加 url=http://+:8172/MSDEPLOYAGENTSERVICE/ sddl=D:(A;; GX;;;NS)
These are the changes I had to do for Windows 7, following Kev's recipe:
Step 3:
netsh http show urlacl
Step 4:
netsh http delete urlacl url=http://+:80/MSDEPLOYAGENTSERVICE/
netsh http add urlacl url=http://+:8172/MSDEPLOYAGENTSERVICE/ sddl=D:(A;;GX;;;NS)
不管怎样,我将 Kev 的可靠建议整合到一个批处理脚本中,以便一站式更改端口号。
了解更多:
For what it's worth, I glued together Kev's solid advice into a batch script for one stop shopping on changing port numbers.
Read More:
还值得了解找出哪些属性存储在哪个注册表项中的魔力 - 输入 Orca.exe - 用于读取/修改 MSI 数据库的宝贵且易于使用的工具(但尽量不要修改) 。
首先我们需要在Property表中找到该属性
找到属性后,转到注册表并查找其插入位置。
It is also worth knowing the magic behind finding out what property is stored in which registry key - enter Orca.exe - invaluable and simple to use tool for reading/modifying MSI database (try not to modify though).
First, we need to find the property in the Property table
Once the property is found, go to the Registry table and find where it is inserted.