You need to find the unique program ID within the "Registration" key and remove it. NOTE: Do not delete the root "Registration" key as there may be legitimately installed Office programs that remain on a computer. Of course, other admins or users will not run the script when uninstalling Office programs, but it's not too hard to push the registry key removal after the fact to clean up. So how do you keep control of the inventory? I create a script that uninstalls each product automatically and also deletes the associated key. Take note of the where the Office version numbers would be:ġ5.0 (unconfirmed, but most likely): Office 2013 programs. HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Office\14.0\Registration HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\14.0\Registrationģ2-Bit Office program installed on 64-Bit OS: And here is where all of the magic lies:ģ2-Bit Office program installed on 32-Bit OS (or 64-Bit Office program installed on 64-Bit OS, this not confirmed): If the keys are removed, Spiceworks will no longer see the Office licenses. When uninstalling Office, the keys remain on the system, possibly in case a re-install is in order. There is one registry location that is left in the computer and Spiceworks sees a registration key in this location and associates a product with that key. I came across this issue with all Office versions (except 97 I believe).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |