Topic
14 replies Latest Post - ‏2013-07-19T03:44:29Z by Rupen
StacyLee
StacyLee
17 Posts
ACCEPTED ANSWER

Pinned topic Office License Key Property

‏2006-08-23T16:11:58Z |
Has anyone written a property to retrieve the License Key file from Office Installations?
Updated on 2009-10-09T23:38:56Z at 2009-10-09T23:38:56Z by SammyPotter91
  • BenKus
    BenKus
    1408 Posts
    ACCEPTED ANSWER

    Re: Office License Key Property

    ‏2006-08-24T05:31:10Z  in response to StacyLee
    Hey Stacy,

    Are you talking about the license key you type in when you install Office or do you want the Product ID (which is like a serial number)?

    Ben
  • StacyLee
    StacyLee
    17 Posts
    ACCEPTED ANSWER

    Re: Office License Key Property

    ‏2006-08-24T19:47:49Z  in response to StacyLee
    The license key when you first install office
  • BenKus
    BenKus
    1408 Posts
    ACCEPTED ANSWER

    Re: Office License Key Property

    ‏2011-12-08T18:13:39Z  in response to StacyLee
    Hey Stacy,

    We considered building this inspector directly into BigFix because it would help our customers figure out which computers are using appropriate license keys. Unfortunately, our lawyers didn't think it was a good idea because some customers might get angry if someone used BES to steal the license keys and send them to the rest of the world.

    However, there is a relatively simple way to run a tool to get all the Microsoft keys (including Office, Windows, SQL Server, etc.) We have already done the work to make the Fixlet/Properties to retrieve this data in BES...

    Note that this requires you buy a small command-line tool from http://www.product-key.com/. I believe it will cost $6.95. As I understand the license agreement, you are licensed per-user and you can buy one copy of it and run it on as many computers as you would like, but you will need to double-check at http://www.product-key.com/keyfinders/licensekeyfinder.htm .
    Follow these steps:
    1. Buy the commandline version of keyfinder.exe from http://www.product-key.com/keyfinders/keyfindercommandline.htm .

    2. Put the "keyfinder.exe" file in your BES Server webroot folder (default location is at "C:\program files\bigfix enterprise\bes server\wwwrootbes\").

    3. In the BES Console, create a new Task that has the following:
    • Title: "Run KeyFinder"
    • Relevance:

    name of operating system as lowercase contains "win"

    • Action:

    download http://127.0.0.1:52311/keyfinder.exe
    wait __download\keyfinder.exe "{ pathname of parent folder of regapp "BESClient.exe" }\mskeys.txt"

    4. This Task will become relevant on all your Windows computers. Use the task action to run it on all computers.

    5. Create a global retrieved property called "MS Product Keys" with the following text:

    if (name of operating system as lowercase contains "win" AND exists file "mskeys.txt" of parent folder of regapp "BESClient.exe" ) then lines of file "mskeys.txt" of parent folder of regapp "BESClient.exe" else "n/a"

    You will then have every computer report all their product keys in BigFix.

    Attached is an export of the Task and Property that you can import to save you from steps 3-5 above (BES 6.0+ only).

    Ben
    Updated on 2011-12-08T18:13:39Z at 2011-12-08T18:13:39Z by BenKus
  • StacyLee
    StacyLee
    17 Posts
    ACCEPTED ANSWER

    Re: Office License Key Property

    ‏2006-08-30T20:57:53Z  in response to StacyLee
    Ben,

    I downloaded the trial but it gets stuck in a running state. It looks like it's because the trial version pops up a dos command window and pauses. I remember reading somewhere you guys have a way of supressing a DOS window. Would that be possible with this?
  • BenKus
    BenKus
    1408 Posts
    ACCEPTED ANSWER

    Re: Office License Key Property

    ‏2006-08-31T08:38:05Z  in response to StacyLee
    Hey Stacy,

    BES 6.0 Clients has new commands:

    • runhidden
    • waithidden

    These are identical to run/wait commands except that they don't show interface to the user... However, in the case you mention, it sounds like the application will stay paused regardless if it were hidden or not.

    It is only $6 for the full version. =)

    Ben
  • sgreenwall91
    sgreenwall91
    22 Posts
    ACCEPTED ANSWER

    Re: Office License Key Property

    ‏2008-09-03T19:46:16Z  in response to StacyLee
    This topic seems a little outdated but just wanted to point out that the same thing could be done using the free util from "MagicalJellyBean" -Keyfinder v2.0.1 (http://www.magicaljellybean.com). The latest version supports a command line run that will let you predefine the application you need the key for via a config file and send the results to a text document that could be queried.
    Updated on 2008-09-03T19:46:16Z at 2008-09-03T19:46:16Z by sgreenwall91
  • jefta_vito91
    jefta_vito91
    11 Posts
    ACCEPTED ANSWER

    Re: Office License Key Property

    ‏2009-03-17T05:45:31Z  in response to StacyLee
    Hi Ben,
    How to retrieve the product ID of Office (not OS)?
  • BenKus
    BenKus
    1408 Posts
    ACCEPTED ANSWER

    Re: Office License Key Property

    ‏2009-03-18T01:09:48Z  in response to StacyLee
    I thnk the same technique will retrieve the MS Office Key.

    Ben
  • kevin_tang91
    kevin_tang91
    5 Posts
    ACCEPTED ANSWER

    Re: Office License Key Property

    ‏2011-12-08T18:13:39Z  in response to StacyLee
    You can use the attached task and analysis to retrieve Microsoft product license keys. The task is used to retrieve license keys and write them into registry with the hex format. Then use the analysis to get back the keys.

    To modify the following code segment can retrieve more license keys for Microsoft products, such as:

    arrSubKeys(0,0) = "{"Windows" as hexadecimal}"
    arrSubKeys(0,1) = "SOFTWARE\Microsoft\Windows NT\CurrentVersion"
    arrSubKeys(1,0) = "{"Office XP" as hexadecimal}"
    arrSubKeys(1,1) = "SOFTWARE\Microsoft\Office\10.0\Registration"
    arrSubKeys(2,0) = "{"Office 2007" as hexadecimal}"
    arrSubKeys(2,1) = "SOFTWARE\Microsoft\Office\12.0\Registration"
    arrSubKeys(3,0) = "{"Office 2003" as hexadecimal}"
    arrSubKeys(3,1) = "SOFTWARE\Microsoft\Office\11.0\Registration\{{90110804-6000-11D3-8CFE-0150048383C9}"
    arrSubKeys(4,0) = "{"Project 2003" as hexadecimal}"
    arrSubKeys(4,1) = "SOFTWARE\Microsoft\Office\11.0\Registration\{{903B0804-6000-11D3-8CFE-0150048383C9}"
    arrSubKeys(5,0) = "{"Visio 2003" as hexadecimal}"
    arrSubKeys(5,1) = "SOFTWARE\Microsoft\Office\11.0\Registration\{{90510804-6000-11D3-8CFE-0150048383C9}"
    Updated on 2011-12-08T18:13:39Z at 2011-12-08T18:13:39Z by kevin_tang91
  • jefta_vito91
    jefta_vito91
    11 Posts
    ACCEPTED ANSWER

    Re: Office License Key Property

    ‏2009-03-25T08:59:24Z  in response to StacyLee
    The analyses only return license key for Windows, but it shows blank for Office, Visio and Project. Is there any modification that I need to make?
  • BenKus
    BenKus
    1408 Posts
    ACCEPTED ANSWER

    Re: Office License Key Property

    ‏2009-03-26T01:18:46Z  in response to StacyLee
    Are you referring to the keyfinder approach that I posted earlier or what Kevin Tang posted recently?

    Ben
  • jefta_vito91
    jefta_vito91
    11 Posts
    ACCEPTED ANSWER

    Re: Office License Key Property

    ‏2009-03-27T01:53:38Z  in response to StacyLee
    I reffered to Kevin. I did some change on the subkey under Registration and now it works. Thanks a lot.
  • SammyPotter91
    SammyPotter91
    1 Post
    ACCEPTED ANSWER

    Re: Office License Key Property

    ‏2009-10-09T23:38:56Z  in response to StacyLee
    sgreenwall
    This topic seems a little outdated but just wanted to point out that the same thing could be done using the free util from "MagicalJellyBean" -Keyfinder v2.0.1 (http://www.magicaljellybean.com). The latest version supports a command line run that will let you predefine the application you need the key for via a config file and send the results to a text document that could be queried.
    How does this work?