如果您的目标是仅 Microsoft Windows 客户端服务器平台，则可以计划检测您的服务器代码并构建 WMI 提供程序。 WMI 来自标准 (WBEM)，但仅供 Microsoft 使用。但是，使用 WMI，您可以保留使用 Nagios 等开源管理工具的能力。在您的客户端计算机上，您的服务器状态仍然可以通过 PowerShell 或 VBScript 进行查询。
如果您的目标是混合 Windows Linux 客户端服务器平台，我认为 SNMP（是的，这个老东西）仍然留在竞争中，您可以计划检测您的服务器代码并构建 SNMP 代理服务器。这对于 Windows 机器来说并不难。该解决方案在任何平台上开放了大量的客户端管理工具。
仅当范围是私人使用时，我才会使用 Web 服务，您为服务器工具开发管理客户端，但据我所知，就管理而言，Web 服务并不是那么标准。
I would say that the answers really depends on the scope of you project.
If you target a Microsoft Windows only client server platform, you can plan to instrument your server code and build a WMI provider. WMI comes from a standard (WBEM) but it's for Microsoft usage only. However using WMI, you keep the ability to use open source management tools like Nagios. And on your client machine your server state stay queryable from PowerShell or VBScript.
If you target a mixt Windows Linux client server platform, I think that SNMP (yes this old stuff) still stay in the race, you can plan to instrument your server code and build an SNMP proxy server. This is not so hard on Windows box. This solution open a wide amount of client management tools on any platform.
I would use a web service only if the scope is private use, you develop the management client for your servers tools, but as far as I know Web service is not so standard as far as management is concern.
A web service interface would be how I'd do it. This really decouples server from the client and allows you the ability to use many different types of applications on the client-side to communicate with the server. Utilizing WMI within the services would also be part of going this route. WMI is a bit confusing at first, but offers the greatest amount of flexibility. There are also several libraries that can be used to abstract your code from the nitty-gritty of WMI and see it as a control layer.
发布评论
评论（2）
我想说，答案实际上取决于您项目的范围。
如果您的目标是仅 Microsoft Windows 客户端服务器平台，则可以计划检测您的服务器代码并构建 WMI 提供程序。 WMI 来自标准 (WBEM)，但仅供 Microsoft 使用。但是，使用 WMI，您可以保留使用 Nagios 等开源管理工具的能力。在您的客户端计算机上，您的服务器状态仍然可以通过 PowerShell 或 VBScript 进行查询。
如果您的目标是混合 Windows Linux 客户端服务器平台，我认为 SNMP（是的，这个老东西）仍然留在竞争中，您可以计划检测您的服务器代码并构建 SNMP 代理服务器。这对于 Windows 机器来说并不难。该解决方案在任何平台上开放了大量的客户端管理工具。
仅当范围是私人使用时，我才会使用 Web 服务，您为服务器工具开发管理客户端，但据我所知，就管理而言，Web 服务并不是那么标准。
I would say that the answers really depends on the scope of you project.
If you target a Microsoft Windows only client server platform, you can plan to instrument your server code and build a WMI provider. WMI comes from a standard (WBEM) but it's for Microsoft usage only. However using WMI, you keep the ability to use open source management tools like Nagios. And on your client machine your server state stay queryable from PowerShell or VBScript.
If you target a mixt Windows Linux client server platform, I think that SNMP (yes this old stuff) still stay in the race, you can plan to instrument your server code and build an SNMP proxy server. This is not so hard on Windows box. This solution open a wide amount of client management tools on any platform.
I would use a web service only if the scope is private use, you develop the management client for your servers tools, but as far as I know Web service is not so standard as far as management is concern.
我将使用网络服务界面来实现这一点。这确实将服务器与客户端解耦，并允许您能够在客户端使用许多不同类型的应用程序与服务器进行通信。在服务中使用 WMI 也是这条路线的一部分。 WMI 起初有点令人困惑，但它提供了最大的灵活性。还有几个库可用于从 WMI 的本质中抽象代码并将其视为控制层。
A web service interface would be how I'd do it. This really decouples server from the client and allows you the ability to use many different types of applications on the client-side to communicate with the server. Utilizing WMI within the services would also be part of going this route. WMI is a bit confusing at first, but offers the greatest amount of flexibility. There are also several libraries that can be used to abstract your code from the nitty-gritty of WMI and see it as a control layer.