how to tell volume license

Thorsen said:

thanks Tim. I looked through the whole Uninstall regfiles and all of them were for 9012000 so all MS products installed are volume license.
I have some more things I will need to test. I appreciate all the digging and knowledge sharing.

I will mark as solved as my original question has been answered. Thanks all.

Interesting, I'll try to dig out my student and teacher edition of office 2007 (if I have it here) and install that. It's OEM for sure, just to verify the key in case the MS article is incorrect or redundant. By the way if the an other office product is installed and that office product is a 2003 release, the 90120000 plays differently (and you can also verify I guess you can also see the product name in the right pane ).
So 2003 would be
9 = RTM
0 = Enterprise
12 = Office Standard 2003
0000 = English

Where as Office 2007 would be
9 = RTM
0 = Volume License
12 = Office Version 12 (Major Version)
0000 = Minor Release 0000

Meanwhile i'll get back to if I can find that version of MSO S&T or if I think of another solution. Is there any more info you can give me, I'm surmising that you have more than once license installed and want to verify if it's a legit one belonging to the business.

Another thought - Given that the PC and all software should be owned by the business that you are working for, why not just reverse engineer. Strip the product keys out and see if they match your records?

Magic jellybean here i come

TimStitt said:

Interesting, I'll try to dig out my student and teacher edition of office 2007 (if I have it here) and install that. It's OEM for sure, just to verify the key in case the MS article is incorrect or redundant. By the way if the an other office product is installed and that office product is a 2003 release, the 90120000 plays differently (and you can also verify I guess you can also see the product name in the right pane ).
So 2003 would be
9 = RTM
0 = Enterprise
12 = Office Standard 2003
0000 = English

Where as Office 2007 would be
9 = RTM
0 = Volume License
12 = Office Version 12 (Major Version)
0000 = Minor Release 0000

Meanwhile i'll get back to if I can find that version of MSO S&T or if I think of another solution. Is there any more info you can give me, I'm surmising that you have more than once license installed and want to verify if it's a legit one belonging to the business.

Another thought - Given that the PC and all software should be owned by the business that you are working for, why not just reverse engineer. Strip the product keys out and see if they match your records?

I think everything in there is 2007. I will check. If the key is not a volume license key then it wouldn't show up in the registry as volume license. right? so the key should be volume license key. I can't use third party programs on this. it is a work server. I have another test I am going to run today to see if I can fix it.

Thanks again for help!

Note: Office is working, just not with other programs. And the reason (and a fix) for it not working with other programs is what I am trying to find.

Ah now i understand.

For many years I worked in hospitality IT and sometimes we'd have a problem where the software we supported wouldn't export to Excel or wouldn't mail merge to word or send emails to outlook. At times this was caused when office was updated (especially where *.rtf's were concerned; more often than not the issues were unregistered dll's, communication blocked via a firewall (especially with SQL and Netbui), group policy blocking, permission related, i.e. the user can open office or can run a 3rd party app; but doesn't have permission to use ODBC so can't send info to office, or just the different way the office can behave on earlier servers (<=2003).

How is the 3rd party software communicating with office? What 3rd party app is it? and are all office applications affected or just some/one?

EDIT - In case this helps, if your app uses ODBC check the permissions in the registry for ODBC.
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\ODBC
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ODBC
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\ODBC
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC
Lastly, search for any software installed ODBC entries in HKEY_USERS as well

and I forgot to mention that I don't have Office student and teacher edition with me in Singapore (but I think we moved on from that one )