Pics or it didn’t happen From: [email protected] [mailto:[email protected]] On Behalf Of Schwan, Phil Sent: Tuesday, August 25, 2015 8:31 AM To: [email protected] Subject: RE: [mssms] adding the MBAM inventory classes to default client inventory classes
OK, finally got it. At first I wasn’t seeing it in WMIExplorer on the server under ROOT\CIMV2\sms so I didn’t figure that was it…but I did eventually find it under ROOT\CIMV2\sms\inv_temp. Once I deleted it in wbemtest I was able to import that last section. All is well ☺ Thanks for the quick feedback, everybody! -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 Jimmy Martin Sent: Tuesday, August 25, 2015 7:57 AM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] adding the MBAM inventory classes to default client inventory classes The way I finally got it to import into the cm console was to import the mof into the wmi of a client and then pointing to that pc in the console to import. *BUT* I later found that everything was STILL not right. I never found a syntax error and even went as far as having Sherry go over it and that NEVER worked. So after all that, I then deleted that class from wmi on the cm server and then did a reimport of that class and it worked and the view got created From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Schwan, Phil Sent: Monday, August 24, 2015 6:35 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] adding the MBAM inventory classes to default client inventory classes It’s the SMS_DEF.MOF that’s giving me the issues. I already modified the configuration.mof file with the appropriate additions. -Phil From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Niall Brady Sent: Monday, August 24, 2015 2:44 PM To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] adding the MBAM inventory classes to default client inventory classes make sure you are importing the right mof, there are two ! edit the configuration.mof and import the sms_def.mof, which one are you having issues with On Mon, Aug 24, 2015 at 8:22 PM, Schwan, Phil <[email protected]<mailto:[email protected]>> wrote: No, I’m not seeing them on the server. -Phil From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Jimmy Martin Sent: Monday, August 24, 2015 2:02 PM To: [email protected]<mailto:[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]<mailto:[email protected]>] On Behalf Of Sherry Kissinger [[email protected]<mailto:[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… If I check the mof syntax, it does not know sms_class_template 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... 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... ________________________________ Legal Notice: This email is intended only for the person(s) to whom it is addressed. If you are not an intended recipient and have received this message in error, please notify the sender immediately by replying to this email or calling +44(0) 2083269015 (UK) or +1 866 592 4214 (USA). This email and any attachments may be privileged and/or confidential. The unauthorized use, disclosure, copying or printing of any information it contains is strictly prohibited. The opinions expressed in this email are those of the author and do not necessarily represent the views of 1E Ltd. Nothing in this email will operate to bind 1E to any order or other contract.
