From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754424AbdEHSxa (ORCPT ); Mon, 8 May 2017 14:53:30 -0400 Received: from esa7.dell-outbound.iphmx.com ([68.232.153.96]:21498 "EHLO esa7.dell-outbound.iphmx.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751883AbdEHSx2 (ORCPT ); Mon, 8 May 2017 14:53:28 -0400 From: X-LoopCount0: from 10.170.28.40 X-IronPort-AV: E=Sophos;i="5.38,310,1491282000"; d="scan'208";a="13744359" To: , CC: , , , , , , , , , Subject: RE: RFC: WMI Enhancements Thread-Topic: RFC: WMI Enhancements Thread-Index: AQHStXDRfWGz3Na/pUazu2XvXvLesqHF0EKAgASlkYCAABLTgIAA6aUAgAA5pYCAADDyAIAAOCOAgACXygCAADsZoIAAXFqA//+yhDCAAaJBgIAAfcEAgBdITWCAAHz2AP//vXJQgABepACABBB4gP//rG2wAASWK0QAAWGyMA== Date: Mon, 8 May 2017 18:26:53 +0000 Message-ID: <27661c9222e2452aa78ab1d1c1cd9015@ausx13mpc120.AMER.DELL.COM> References: <201704191854.51783@pali> <4e3e507b116443298427002c5aafed7f@ausx13mpc120.AMER.DELL.COM> <20170420131431.GM18887@pali> <20170420204436.GC3209@fury> <775ffd8f3327497cabd15ee7826cedaf@ausx13mpc120.AMER.DELL.COM> <20170505234436.GB25865@fury> <20170508152907.GA17700@fury> <20170508154725.GD17700@fury> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.208.86.26] Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by mail.home.local id v48IraQD024897 (Responding as plain text, your email probably got punted from the ML from being HTML) > > ... > > I'm not sure what you are asking about. Samba does not deal with WMI at all. The state of affairs is > explained at https://powershell.org/2015/04/24/management-information-the-omicimwmimidmtf-dictionary/ > -- old WMI (DCOM/RPC-based) is deprecated, new WMI based on WS-MAN is supported and OMI is the > implementation. We used to have a very limited attemt at writing DCOM stack and nobody worked on > it for years so it got removed. Thanks! That was a very interesting read. > Microsoft has already published a MOF parser as part of OMI work: https://github.com/Microsoft/omi/ > under MIT license. Unfortunately that's expecting text MOF, not this intermediary compiled format.