very first thing I would do is look in DNS and see if I have any old invalid KMS servers. If a support tech built a machine and used a KMS key that machine will register as a KMS server in DNS. Also might have different ones configured in different DNS servers.
It will also be in the event viewer. http://technet.microsoft.com/en-us/library/ee939272.aspx This will tell you if DNS is telling them where to fins one nslookup -type=srv _vlmcs._tcp On Tue, Jul 30, 2013 at 10:52 AM, Christopher Bodnar < [email protected]> wrote: > 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* <http://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. >
<<image/jpeg>>
