Hi Sherry Kissinger,
Thank you, Can you guide me how to configure “ConfigItem in a
Baseline” in SCCM 2012 server.
Regards
Rajan
From: [email protected] [mailto:[email protected]] On
Behalf Of Sherry Kissinger
Sent: 11 February 2015 06:08
To: [email protected]
Subject: Re: [mssms] Microsoft Office Activation status through SCCM 2012
VAMT would likely work for most companies; one of the challenges in some
companies is that someone, or some service, having the rights to remotely reach
out and query wmi on systems. VAMT says "VAMT uses WMI to remotely manage
activations and other related tasks on managed systems" -- that to me means
that whatever account VAMT is using to query WMI or affect WMI needs to have
admin rights on every target--which may or may not be easily done in a company.
If it's just an inventory extension, or a ConfigItem in a Baseline just asking
for the same info which VAMT is asking for "are you licensed yes or no"--that
doesn't require any new credentials; or a high-rights account to run.
But yes, VAMT would likely work fine in most situations.
On Tuesday, February 10, 2015 6:23 PM, Jim Pogue <[email protected]
<mailto:[email protected]> > wrote:
I’m not sure if this would be any easier for you but can’t you just use You can
use VAMT 3.1? I don’t think that requires a KMS server to be running and you
can install it as part of MDT.
That will gives you a pretty in depth report on what is activated and what is
not with net BIOS name.
I am pretty new to this game so if I’m wrong please forgive me.
From: [email protected] <mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Sherry Kissinger
Sent: Tuesday, February 10, 2015 6:10 PM
To: [email protected] <mailto:[email protected]>
Subject: Re: [mssms] Microsoft Office Activation status through SCCM 2012
SoftwareLicensingProduct is already in hardwareinventory classes; it's one of
the AI classes. You may not have it enabled by default: I would turn on ID,
LicenseStatus, Name, and apparently PartialProductKey -- but that's only for
the OS--whether that's licensed or not. for Office; that looks like it's
elsewhere. and based on that script above, you really only want the values
where partialproductkey <> null.
I could probably custom mof-edit both of those (separately) with a
configuration.mof edit + something to import. Let me know if you're
interested/want that. I'd have to test that in my lab first.
It could also be a couple of configItems; "where partial policy <> null", spit
out licensestatus value; and you want licensestatus to be =1 for both of those
wmi classes; that wouldn't tell you which specific thing wasn't licensed--a mof
edit would be better for more detail info; but if you're just looking for a
yes/no is it licensed, a couple configitems would work.
On Tuesday, February 10, 2015 3:49 PM, "[email protected]
<mailto:[email protected]> " <[email protected]
<mailto:[email protected]> > wrote:
http://www.autoitscript.com/forum/topic/140000-someone-with-a-script-to-check-if-win-office-are-activated/
Check out that script, it is available in wmi.
Sent from Windows Mail
From: Jason Wallace <mailto:[email protected]>
Sent: Tuesday, February 10, 2015 3:54 PM
To: [email protected] <mailto:[email protected]>
There is not a built in report. Now forgive me if I am wrong but you can check
activation status by running a command? You can trap that in a script and
return a true or false. That'd be really easy in compliance & settings and lead
to a report
On 10 Feb 2015, at 19:25, Rajan Tri <[email protected]
<mailto:[email protected]> > wrote:
Hi Friends,
I am looking for the SCCM 2012 report for Microsoft Office
product Activation status. Is it feasible ?
Regards
Rajan
MiTek Holdings, Inc., 2011-2014, All Rights Reserved
This communication (including any attachments) contains information which is
confidential and may also be privileged. It is for the exclusive use of the
intended recipient(s). If you are not the intended recipient(s), please note
that any distribution, copying, or use of this communication or the information
in it is strictly prohibited. If you have received this communication in error,
please notify the sender immediately and then destroy any copies of it.
