Client Management Suite

 View Only
  • 1.  Client Management System - Windows Product Keys

    Posted Jan 05, 2011 12:56 PM

    Our workstations all have OEM editions of Windows XP Pro installed. Each machine has a product sticker that shows the Product Key for that machine. I need to be able to nuke and rebuild machines using the correct Product Key for that machine. To do that, I need to record the Product Keys somewhere. The CMDB seems a logical place to do that, but I can't figure out how.

    Where's the best place to record this information?



  • 2.  RE: Client Management System - Windows Product Keys

    Posted Jan 05, 2011 01:41 PM

    We were able to do this with v6 custom inventory (so it should be similar with v7), which creates a new dataclass and records the inventory.



  • 3.  RE: Client Management System - Windows Product Keys

    Posted Jan 05, 2011 02:04 PM

    Isn't the key encrypted in the registry?  I've always used third-party tools to do this.  I'd be interested how you accomplished it.



  • 4.  RE: Client Management System - Windows Product Keys

    Posted Jan 05, 2011 02:49 PM

    We came across a script that we were able to run to decode this. It was quite a few years ago, but I think this link at Altirigos was the starting point (or sanity check). However, I don't know if this will transfer well to NS7. And, since I was onsite when I did this, I'm limited in what I can share.

     

    (Hmm/// Maybe custom inventory wasn't the right process. We ran the script via SWD and created some custom reports)



  • 5.  RE: Client Management System - Windows Product Keys

    Posted Jan 11, 2011 08:46 AM

    There is a tool out there called "Magical Jellybean Keyfinder" or something similar; I believe it supports a command-line option to output to a CSV file.  You could write a script that runs that, then parses the CSV file and then either builds an NSI and puts it in the \Inventory folder, OR writes it to the registry where you can pick it up via Custom Inventory.

    One caveat; some antivirus programs detect it as a "hack tool" so you may need to exclude it from AV scanning.

    A note on the command line syntax:

    keyfinder.exe /savecsv c:\temp\ /close /file myregkey.csv

    The trailing \ on the path is required from what I found in my testing.



  • 6.  RE: Client Management System - Windows Product Keys

    Posted Apr 05, 2011 11:17 AM

    How do you plan on getting said keys onto the target system?  Recording them is one thing.  Getting them back once nuked and rebuilt is quite another.  Manually?  DS/sysprep?



  • 7.  RE: Client Management System - Windows Product Keys

    Posted Apr 07, 2011 09:57 AM
      |   view attached

    I have used the attached modified version of that script on NS7 with it being ran as a task against the clients, seems to work fine apart from 64 OS's. Can anyone help with this please?

    You will need to rename the file from .doc to .vbs

     

    And this is the SQL report I use:

    SELECT     dbo.Inv_Inv_AeX_SW_OS_and_Office_ProductKeys.[Product Name], dbo.Inv_Inv_AeX_SW_OS_and_Office_ProductKeys.[Product Key],
                          dbo.vComputer.Name
    FROM         dbo.Inv_Inv_AeX_SW_OS_and_Office_ProductKeys INNER JOIN
                          dbo.vComputer ON dbo.Inv_Inv_AeX_SW_OS_and_Office_ProductKeys._ResourceGuid = dbo.vComputer.Guid
    ORDER by dbo.Inv_Inv_AeX_SW_OS_and_Office_ProductKeys.[Product Name], dbo.Inv_Inv_AeX_SW_OS_and_Office_ProductKeys.[Product Key] ASC

    Attachment(s)

    doc
    productkeysnse.doc   8 KB 1 version