Standards-based Management in Windows Server “8”

re: Standards-based Management in Windows Server “8”

Zoltan Micskei — Wed, 23 May 2012 08:41:48 GMT

@Steve: thanks for the answer!

re: Standards-based Management in Windows Server “8”

Steve Lee [MSFT] — Tue, 22 May 2012 15:41:42 GMT

@Zoltán, the way the WS-Man 1.1 spec is currently written, implementations are conformant whether they use /wsman-anon or not since it is not required although it is recommended to follow that convention. You are correct that for historical reasons (WinRM was originally written as WS-Man 1.0 spec was being developed) WinRM chose the current implemented approach. Supporting the recommendation is something we could consider for a future release. However, because it is just a recommendation and not required, any other implementation (such as BMCs) may have also chosen not to support the /wsman-anon suffix. My recommendation would be for the client to try both approaches in a heterogenous environment.

re: Standards-based Management in Windows Server “8”

Serhad MAKBULOĞLU — Fri, 13 Apr 2012 07:49:30 GMT

Thank you for share!

re: Standards-based Management in Windows Server “8”

Zoltán Micskei — Fri, 06 Apr 2012 08:37:51 GMT

Great post and respect for the huge work done in Server 8!

When talking about heterogeneous management using WS-Management, I have a question about one of the functionalities in the current implementations: anonymous identify. The WS-Man 1.1 spec [DSP0226] only contains recommendations (R5.4.5-2: “it is recommended that the network address for resources that do not require authentication be suffixed by the token sequence /wsman-anon” and R11-4 “A service that supports the wsmid:Identify operation may expose this operation without requiring client or server authentication… the network address be suffixed by the token sequence /wsman-anon/identify”).

Openwsman for Linux implements anonymous identify according to this recommendation. WinRM chose a different approach (maybe for historical reasons?): anonymous identify requests also go to /wsman with the extra conditions specified in WS-WSMV 3.1.4.1.23 “…when the request is unauthenticated and the following HTTP header is present WSMANIDENTIFY: unauthenticated”.

Thus if I have a mixed environment with devices all supporting WS-Management but using different implementations, as far as I can see there is no standard way to discover what type of OS/WS-Man stack they are running, and separate checks have to be implemented for Windows and Linux.

I tried this in the beta of Windows Server ‘8’, but it also does not listen on wsman-anon. What would you recommend for anonymous wsman identify in heterogeneous environments?

re: Standards-based Management in Windows Server “8”

Marco Shaw — Fri, 06 Apr 2012 00:58:00 GMT

Please consider redoing the images and removing the auto-correct underlining... It's "not so pretty"...

re: Standards-based Management in Windows Server “8”

Jeffrey S. Patton — Mon, 02 Apr 2012 18:42:56 GMT

I think it shows how much of a geek I am, but this is one of the most exciting blog posts I've read about Windows Server 8, and I just can't tell you how excited I am for the oportunity to dig into this more!

Thanks for all the hard work and effort!