Thanks, this seems to be the easiest way to do it. Wasn't aware of this class, and it is already defined in the SMS_DEF.MOF file. Just need to enable it and turn on (2) of the attributes (description, licenseStatus). Then we can run a report filtering by the description "VOLUME_KMSCLIENT".
Appreciate the help. Christopher Bodnar Enterprise Architect I, Corporate Office of Technology:Enterprise Architecture and Engineering Services Tel 610-807-6459 3900 Burgess Place, Bethlehem, PA 18017 [email protected] The Guardian Life Insurance Company of America www.guardianlife.com From: <[email protected]> To: <[email protected]> Date: 07/30/2013 12:52 PM Subject: RE: [mssms] KMS clients not activating Sent by: [email protected] http://social.technet.microsoft.com/wiki/contents/articles/5675.determine-windows-activation-status-with-powershell.aspx http://msdn.microsoft.com/en-us/library/windows/desktop/aa394520(v=vs.85).aspx You should be able to pull that class, and just create a report based on the state. Christopher Catlett Consultant | Detroit Office 248-876-9738 |Fax 877.406.9647 Sogeti USA 26957 Northwestern Highway, Suite 130, Southfield, MI 48033-8456 www.us.sogeti.com From: [email protected] [ mailto:[email protected]] On Behalf Of CESAR.ABREG0 . Sent: Tuesday, July 30, 2013 12:41 PM To: [email protected] Subject: Re: [mssms] KMS clients not activating We ran into some issue with a batch of machines that OEM upgrade entry key was empty in the BIOS. these were all IBM On Tue, Jul 30, 2013 at 9:06 AM, Jason Sandys <[email protected]> wrote: I haven’t really looked at, but the SoftwareLicensingService class that is part of AI is supposed to be for Windows activation. You should/may be able to use it. The Volume Activation Management Tool (VAMT), part of the AIK (although that’s a really old version) and ADK (and also downloadable separately) will also connect to systems are tell you their activation status. J From: [email protected] [mailto: [email protected]] On Behalf Of Christopher Bodnar Sent: Tuesday, July 30, 2013 10:52 AM To: [email protected] Subject: [mssms] KMS clients not activating Wondered if anyone else has done something similar. We have a KMS infrastructure for our Windows 7 and Windows 2008 machines. I've recently found that some machines have had issues with activation, and the groups responsible for remediating have used various work arounds, so these machines still aren't activating. I think it's a small number but I'm trying to figure out the best way to find out exactly what machines, and how many. All of these boxes report into SCCM. I was thinking about running a VBScript in DCM (doing that for a few things already) and based on the output of a slmgr.vbs /dli command create a custom WMI class to hold a Yes/No value. so the script would look in the out put for something like the extended PID. There is no single point of direct access to the client machines. Multiple sites, multiple forests, multiple DMZ subnets...etc..... so the SCCM route would be preferred. Anyone doing something like this? Easier way? Suggestions? Thanks Christopher Bodnar Enterprise Architect I, Corporate Office of Technology:Enterprise Architecture and Engineering Services Tel 610-807-6459 3900 Burgess Place, Bethlehem, PA 18017 [email protected] The Guardian Life Insurance Company of America www.guardianlife.com ----------------------------------------- This message, and any attachments to it, may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are notified that any use, dissemination, distribution, copying, or communication of this message is strictly prohibited. If you have received this message in error, please notify the sender immediately by return e-mail and delete the message and any attachments. Thank you. ----------------------------------------- This message, and any attachments to it, may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are notified that any use, dissemination, distribution, copying, or communication of this message is strictly prohibited. If you have received this message in error, please notify the sender immediately by return e-mail and delete the message and any attachments. Thank you.
<<image/jpeg>>
<<image/jpeg>>
