(imported topic written by StacyLee)
Has anyone written a property to retrieve the License Key file from Office Installations?
(imported comment written by BenKus)
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
(imported comment written by StacyLee)
The license key when you first install office
(imported comment written by BenKus)
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:
-
Buy the commandline version of keyfinder.exe from http://www.product-key.com/keyfinders/keyfindercommandline.htm .
-
Put the “keyfinder.exe” file in your BES Server webroot folder (default location is at “C:\program files\bigfix enterprise\bes server\wwwrootbes”).
-
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”
-
This Task will become relevant on all your Windows computers. Use the task action to run it on all computers.
-
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
1 Like
(imported comment written by 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?
(imported comment written by BenKus)
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
(imported comment written by sgreenwall91)
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.
(imported comment written by jefta_vito91)
Hi Ben,
How to retrieve the product ID of Office (not OS)?
(imported comment written by kevin_tang91)
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}”
(imported comment written by jefta_vito91)
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?
(imported comment written by BenKus)
Are you referring to the keyfinder approach that I posted earlier or what Kevin Tang posted recently?
Ben
(imported comment written by jefta_vito91)
I reffered to Kevin. I did some change on the subkey under Registration and now it works. Thanks a lot.
(imported comment written by Rupen)
Hi Jef:
will you please share that file to me. Thank you. This file doesn’t work properly.
(imported comment written by SammyPotter91)
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?