Hmm well then the one installed is a volume lisence, it has the same reg key setup 901.....
They both Read Proffesional 2007.....
I will have some more stuff to check. The software was not purchased by or for me, I am trying to help someone else out who is having an issue with word on a server.
If it helps, under that same key, theres one dword value called "ConvertToEdition" that reads "Microsoft Office professional 2007". Whatever that means.
We were thinking the issue might be due to the license as it was seen in another issue. But I think it checks out. I appreciate all the help. I wish I could go into more detail, but it is work related.
I will post if we get the whole thing resolved, but this info helped greatly. It rules out on possible cause of the issue.
Ok as I have said in other businesses (businii?) "Identify problem and then go to lunch"
I will return and, after some lunch and playing my violin Sherlock-Holmes style, hopefully can figure this one out.
Perhaps the user used another volume license to install some extra office products such as VISIO, ONENOTE, or PUBLISHER. This would match the scenario (or what I know of it).
Additionally I have a present for us, as I managed to "Sherlock" that KB I promised earlier. Description of the numbering scheme for product code GUIDs in 2007 Office suites and programs
Hope this helps clarify.
Happy to help further if needed, and sign privacy disclosure
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.
If this is on a terminal server and you want to use it through remote desktop, you need special licensing.
Quote