No, I’m not seeing them on the server. -Phil
From: [email protected] [mailto:[email protected]] On Behalf Of Jimmy Martin Sent: Monday, August 24, 2015 2:02 PM To: [email protected] Subject: RE: [mssms] adding the MBAM inventory classes to default client inventory classes Check on your server and see if you see the classes within the mof already exist within wmi on your cm server. It seems like I deleted them there and then reimported From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Schwan, Phil Sent: Monday, August 24, 2015 12:50 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] adding the MBAM inventory classes to default client inventory classes Jimmy, did you ever get this resolved? I’m seeing the exact same issue with an MBAM integration. I’ve actually isolated it down to the section of the sms_def.mof file listed at the TechNet entry (https://technet.microsoft.com/en-us/library/dn656927.aspx). I’ve broken out the other three sections into their own files and imported them successfully, but no matter what I do to the formatting the Win32Reg_MBAMPolicy session continues to generate the same error. Mofcomp /check says the syntax is valid, but the HINV import in the Default Client Settings continues to puke every time. -Phil _________________________________________________________________ Phil Schwan | Technical Architect, Enterprise Windows Services Microsoft VTSP ([email protected]<mailto:[email protected]>) Project Leadership Associates | 2000 Town Center, Suite 1900, Southfield, MI 48075 Lync: 312.756.1626 Mobile: 419.262.5133 www.projectleadership.net<http://www.projectleadership.net/> [linkedin_logo-19x20] <http://www.linkedin.com/in/philschwan> [Twitter-Logo1-20x20] <https://twitter.com/philschwan> [wordpress-logo3] <http://myitforum.com/myitforumwp/author/philschwan> [Description: Description: Description: Arrow email]Lead with Strategy. Leverage Technology. Deliver Results. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Greg Thomas Sent: Monday, January 12, 2015 7:24 PM To: Jimmy Martin <[email protected]<mailto:[email protected]>> Cc: [email protected]<mailto:[email protected]> Subject: RE: [mssms] adding the MBAM inventory classes to default client inventory classes I'm sure we've all seen cases where copy/paste from a webpage has a special character or the quotes are wrong. Can you make sure you're pasting into notepad rather some other text editor and just verify that the single and double quotes look right. If it's working fine for Sherry (p.s. many thanks for RegToMof) but it's giving you a syntax error, there is likely something simple like that. Of course, Sherry is somewhat of a mof wizard, so it's possible there is some magic involved :) On Jan 12, 2015 2:15 PM, Jimmy Martin <[email protected]<mailto:[email protected]>> wrote: Well crap That doesn’t import either. I tried on the server as well as my 2 workstations with the same result. I went ahead and exported my hardware inventory classes to see if you could spot something there that was ill defined and blocking this. It has something to do with the sms_class_template definition as the file will not mofcomp successfully unless I add the definition to the top of the mof. Wont import either way From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Sherry Kissinger Sent: Monday, January 12, 2015 1:05 PM To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] adding the MBAM inventory classes to default client inventory classes well, I dunno what you're doing. But the attached works just fine for me in my lab; to import into default agent settings. that's just for importing; the configuration.mof changes still have to be done. On Monday, January 12, 2015 9:49 AM, Jimmy Martin <[email protected]<mailto:[email protected]>> wrote: http://technet.microsoft.com/en-us/library/dn237295.aspx Jimmy Martin (901) 227-8209 From: [email protected]<mailto:[email protected]> [[email protected]] On Behalf Of Sherry Kissinger [[email protected]] Sent: Monday, January 12, 2015 9:44 AM To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] adding the MBAM inventory classes to default client inventory classes "but the mof data on the Microsoft site absolutely will not import. I am importing into the default settings…" what's the .mof on the Microsoft site? On Monday, January 12, 2015 9:36 AM, Jimmy Martin <[email protected]<mailto:[email protected]>> wrote: Hi Guys, From the documentation, this seems so simple… but the mof data on the Microsoft site absolutely will not import. I am importing into the default settings… [cid:[email protected]] If I check the mof syntax, it does not know sms_class_template [cid:[email protected]] If I add the sms_class_template information to the top of the mof, it will check out syntax wise but it still doesn’t import. I’m sure its something simple I am missing here Jimmy Martin | Engineer | Information Technology | BMHCC - CORPORATE Phone: (901) 227-8209 | [email protected]<mailto:[email protected]> Opinions expressed above are not necessarily those of Baptist. This message and any files transmitted with it may contain legally privileged, confidential, or proprietary information. If you are not the intended recipient of this message, you are not permitted to use, copy, or forward it, in whole or in part without the express consent of the sender. Please notify the sender of the error by reply email, disregard the foregoing messages, and delete it immediately. P Please consider the environment before printing this email... This message and any files transmitted with it may contain legally privileged, confidential, or proprietary information. If you are not the intended recipient of this message, you are not permitted to use, copy, or forward it, in whole or in part without the express consent of the sender. Please notify the sender of the error by reply email, disregard the foregoing messages, and delete it immediately. P Please consider the environment before printing this email... This message and any files transmitted with it may contain legally privileged, confidential, or proprietary information. If you are not the intended recipient of this message, you are not permitted to use, copy, or forward it, in whole or in part without the express consent of the sender. Please notify the sender of the error by reply email, disregard the foregoing messages, and delete it immediately. P Please consider the environment before printing this email... This message and any files transmitted with it may contain legally privileged, confidential, or proprietary information. If you are not the intended recipient of this message, you are not permitted to use, copy, or forward it, in whole or in part without the express consent of the sender. Please notify the sender of the error by reply email, disregard the foregoing messages, and delete it immediately. P Please consider the environment before printing this email...
