ok; but that doesn't necessarily mean that the targets actually have something 
to say.  On the workstations which have run the baseline, do they have anything 
in root\cimv2\cm_adobeinfo?  If not, then either they simply have nothing to 
say; or the baseline didn't function as you expected it to do.

If you run the script manually, forget about ConfigMgr completely, does it make 
a cm_adobeinfo in WMI with instances?  If not, the boxes simply have nothing to 
say; and what you hoped it would do for you, regarding information available, 
won't fit your needs.
 


On Friday, February 20, 2015 8:06 PM, Rajan Tri <[email protected]> wrote:
  


Hi,
 
I have created and baseline and deployed to the acrobat installed test PCs.
It is success and able to evaluate from client configuration..
 
Regards
Rajan
 
From:[email protected] [mailto:[email protected]] On 
Behalf Of Sherry Kissinger
Sent: 21 February 2015 03:30
To: [email protected]
Subject: Re: [mssms] mof file for Adobe Acrobat products
 
 
Then... you made a package/program/advert?
you targeted that advert to that computer?
The computer successfully ran the advertisement?
that computer actually HAS something to say--it actually HAS something from 
Adobe installed which would require a license key; so there's something for 
that box to report?  (if the box doesn't have anything with licens-able stuff, 
there's nothing for it to report)
 
 
On Friday, February 20, 2015 9:35 AM, Rajan Tri <[email protected]> wrote:
 
Hi,
 
                “Cm_Adobeinfo” does not exist.
 
 
 
 
 
Regards
Rajan
 
From:[email protected] [mailto:[email protected]] On 
Behalf Of Sherry Kissinger
Sent: 20 February 2015 19:00
To: [email protected]
Subject: Re: [mssms] mof file for Adobe Acrobat products
 
Look at Inventoryagent.log on a client that you KNOW has the information 
locally in wmi, root\cimv2\cm_adobeinfo
 
is that client even attempting to send the information? 
 
 
On Friday, February 20, 2015 7:01 AM, Rajan Tri <[email protected]> wrote:
 
Hi,
 
                I tried below steps, but data output is not updating to SCCM 
server database.
 
 
Regards
Rajan 
 
 
From:[email protected] [mailto:[email protected]] On 
Behalf Of Sherry Kissinger
Sent: 19 February 2015 19:09
To: [email protected]
Subject: Re: [mssms] mof file for Adobe Acrobat products
 
You mean you want to try to use this?  
http://myitforum.com/myitforumwp/2012/06/13/gather-some-adobe-software-serial-numbers-using-configmgr-dcm-and-hardware-inventory/
 
 
 If so, let me break it down for you into basic steps (at least, this is how I 
do it)
1. Make a Collection of Pilot/Test machines which happen to have something 
installed from Adobe which are licensed; like reader isn't, but acrobat pro is.
2. Take that script, and create EITHER a ConfigItem OR a package/program.  I'll 
explain the package/program because it's easier to 'get' for most 
new-to-configmgr people.
  2a.  take the script, name it oh... adobelicense.vbs, and put it in a new 
folder on wherever you store your packages.
  2b.  Make a package, pointing to that source folder, and distribute to your 
DPs.
  2c.  make a program in that package; and all it needs to do is cscript.exe 
adobelicense.vbs
3. Deploy that program to your pilot collection; make the advert recurring, 
like weekly.  hidden/no reboot/suppress notifications, etc. the end user 
doesn't need to see a thing about it.
4. After deploying, and boxes have run it, look in WMI and confirm you see 
root\cimv2\cm_adobeInfo with stuff inside it on those pilot boxes.  Hopefully 
information you care about.
5.  Then it's a import of the mof snippet; that's in 6. inside that script.  
You just save that snippet out as importme.mof, take away the '  from the 
front, and import it into hardware inventory.  Note I wouldn't do that step 
until I *knew* those test clients had something in WMI to report.
 
6.  If you like it/it works like you think, then expand your pilot to whatever 
targets you want to target.
 
 
On Thursday, February 19, 2015 5:24 AM, Rajan Tri <[email protected]> wrote:
 
Hi,
 
                Thank you, I am getting confused. 
 
Can you explain in details like how to configure the SCCM server.
 
Regards
Rajan
 
From:[email protected] [mailto:[email protected]] On 
Behalf Of Sherry Kissinger
Sent: 18 February 2015 04:14
To: [email protected]
Subject: Re: [mssms] mof file for Adobe Acrobat products
 
This isn't quite what you mean; but our license folk were interested in this:  
http://myitforum.com/myitforumwp/2012/06/13/gather-some-adobe-software-serial-numbers-using-configmgr-dcm-and-hardware-inventory/
 
 
 
 
On Tuesday, February 17, 2015 3:12 PM, "Murray, Mike" <[email protected]> 
wrote:
 
This
 
From:[email protected] [mailto:[email protected]] On 
Behalf Of Daniel Ratliff
Sent: Tuesday, February 17, 2015 11:50 AM
To: [email protected]
Subject: RE: [mssms] mof file for Adobe Acrobat products
 
Why do you need a .mof file? Just use hardware inventory or asset intelligence. 
 
Daniel Ratliff
 
From:[email protected] [mailto:[email protected]] On 
Behalf Of Rajan Tri
Sent: Tuesday, February 17, 2015 2:34 PM
To: [email protected]
Subject: [mssms] mof file for Adobe Acrobat products
 
Hi,
 
                I am trying to enable Hardware inventory class for adobe 
acrobat products, But unable to find the options.
 
                Anyone tried this option? How can we create mof file for 
Acrobat products.
 
Regards
Rajan
 

The information transmitted is intended only for the person or entity to which 
it is addressed
and may contain CONFIDENTIAL material. If you receive this material/information 
in error,
please contact the sender and delete or destroy the material/information.


Reply via email to