[Railman5]

IcemanND

very nice little app.

found windowx xp no probs

no office 2k

any news on when this might happen.

will be awesum then!

[IcemanND]

@Railman5 - Office 2000 encodes its key differently than any of the other applications, apparently it was a harder method to decode also. I haven't given up but it may take a little while.

Its not like M$ is just giving this information away, so its taking a little bit of sleuthing to find all of the locations and their encoding method.

[jaclaz]

It should be this:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\10.0\Registration\{913A0410-6000-11D3-8CFE-0050048383C9}

DigitalProductID

jaclaz

[jaclaz]

@IcemanND

Following my PM, I also found this:
http://www.elcomsoft.com/help/pspr/index.h...indowscdkey.htm

The ELCOMSOFT guy, says that:

Quote

As for Office CD key, please note that PSPR supports only Office 97, Office XP and Office 2003, but not Office 2000 (it seems that the CD key for this version is not stored in the system at all).

judging from the quality of his software, I tend to believe him rather than the "it is differently encrypted in the registry" version.

.....but the other "good guy" from nirsoft seems to have made it:
http://www.nirsoft.n...key_viewer.html

Anyone with Office 2000 installed willing to try it?

jaclaz

This post has been edited by jaclaz: 09 September 2005 - 10:40 AM

[Tezuka]

works on W2k3 Standard

if have feature to change it would be wrapped

[ringfinger]

As you know, works great on XP. Didn't get Office 2003 SP1 though.

[IcemanND]

@Tezuka - maybe in the future I'll add changing, not on the horizon at the moment.

@ringfinger - What odd version of Offce 2003 do you have? It works fine on my machine. check the registry at hklm\software\microsoft\office\11.0\registration
the GUID should be something like {90110409-6000-11D3-8CFE-0150048383C9}, the first 8 digits may be different. Then there should be DigitalProductId inside this key.

@all - still working on office 2000 products. and looking for any other suggestions.

[KamiQuazi]

worked with Windows XP Pro but no Office 2003

[noj-o]

Does not work for Office 2000 Premium.

HKLM\software\microsoft\office\9.0\Registration\DigitalProductID

Mine was empty. Wonder if that means anything?!?!?

[DotBet]

IcemanND, on Sep 6 2005, 09:59 PM, said:

If anyone has further suggestions, please let me know.
<{POST_SNAPBACK}>

Any chance you can make it find the keys for remote systems?
eg:My system boots a few different OS versions and each have different installed MS software. It would be nice to get 'all' keys from 'all' OS's and MS software from each drive at once.


Works on XP Pro SP2 for:

Microsoft Office FrontPage 2003
Microsoft Office Professional Edition 2003
Microsoft Windows XP
Visual Studio .NET Professional 2003 - English

[JoeMSFN]

Don't suppose there's any way to recover the key from windows that won't boot the registry is intact?
Basically Computer A doesn't boot. I take Computer A's hard drive and put it as a secondary in Computer B.

I run the nifty util here on Computer B and tell it to get the Keys from Computer A's hard drive.

Any chance of that? (or a registry viewer for the same thing?)

[jaclaz]

JoeMSFN said:

Any chance of that? (or a registry viewer for the same thing?)

looky here:
http://www.911cd.net...showtopic=16048

jaclaz

[IcemanND]

not an easy one, at least with my program. When I get some time I'll look into adding the ability to select where too look for the key, then you could mount the registry hive for the dead machine to your registry and read it.

[meister_sd]

I have a similar program and the changes I made to Office 2003 products was to change the second digit to reflect the service pack.

Office 2003 with no service packs

\{90110409-6000-11D3-8CFE-0150048383C9}

Office 2003 with SP1

\{91110409-6000-11D3-8CFE-0150048383C9}

This procedure also works with Visio, FrontPage, Project, etc.....

This post has been edited by meister_sd: 30 September 2006 - 11:46 PM

[IcemanND]

With the suggestions and testing help of Stealth111, I have been working on a new version of Keydecoder.

The current version I am working on has the following features for looking up Microsoft license numbers:

Quote

• Local Machine (default)
  
• Single Remote Machine
  • Enter the name of a remote machine you have access to via the Remote Registry service.
  
  
• List of Remote Machines
  • Specify text file with list of remote machines to access via remote registry service
  
  
• AD Query
  • Specify LDAP query of domain OU and return keys for all machines in that OU and it's sub OU's
  
  
• Offline Registry
  • You load the software registry hive under HKLM and specify the key name you assigned and it pulls the keys from there.
  
  
• Manual Decode
  • You enter the product name, and the hex data from the DigitalProductId field and it is decoded for you
  
  
• REG file (In progress)
  • Specify a registry file and it will scan the file looking for digitalproductid's and attempt to decode

All of the options are available via either gui or command line and the results can be save to a csv file.

I can't think of any other possible ways that one would want to try and access this information. But if anyone has any other suggestions let me know and I will look into added additional features.

At this time I have no intentions of providing any method to change the license numbers of any of the products.

[ricktendo]

This is gonna be sweet

[Stealth111]

TRUST ME... IT IS SWEET!! IcemanND has really brought his program from a casual "might use" type of program, to the type of program I will come to rely on day in and day out administering and auditing my buildings and the 1000's of systems in them. Every day he has been adding and changing the program from some simple suggestions I had made to him, of things that I might like to see the program do. He has been right there with the changes.. And with the exception of 1 isolate bug that we are looking into with a "ROGUE" machine in one of my buildings that won't play nice, the program is ROCK SOLID!! Thanks again IcemanND!! The AD scan absolutely kicks a**, I am working on passing the outputted results of the .csv file into another script to change keys that don't match a check file.. Changing the keys via vb is cake, but automating the process of checking them against a database and then changing them is another thing. See, I have kids that will try to get the product keys from our maachines and use them at home, ect.. So I DEPLOY GENERIC keys to the whole building, ALL THE SAME.. But I have a database of the ACTUAL keys for each system, that I can run a file and change the whole domain back to their original keys with the simple run of a script, when it come time for an audit, so you can see why I praise this program so much, it is looking like the final peice of my big puzzle..

[IcemanND]

New version: Will maintain the orignal basic version and the new version will be considered the Enterprise version 2.2.

If all you care about is the local machine you are running the utility on you only need the original. If you need to scan multiple systems from a list of machines, from a Active Directory list, offline registry, exported registry file, manual decode from direct data input, or want to search the entire registry from beginning to end and decide all possible DigitalProductIDs, then download the enterprise version.

[mullie]

Hi,

Just letting you know it doesn't Report Vista keys correcty. I'm running Vista Business Edition (Enterprise) and it returns BBBBB-BBBBB-BBBBB-BBBBB-BBBBB. I've looked at the DigitalProductID key for Vista, and it is quite different to the previous versions. There's also an additional key there called DigitalProductID4 now, which has a lot of data in it, but I've knocked up a little script to scan through that and can't find anything that matches my key. Every second hex pair in DigitalProductID4 is a 00 though, so it may be necessary to ignore those.

It does report Office 2007 correctly though.

Seeya,

Mullie

[mullie]

Oh, and by the way - Love your work!

Thanks,

Mullie