I have a bunch of remote computers I need to identify what version of MS Office they have installed. We need this so we can identify which computers are running Older versions of Office that are no longer supported or soon EOL. I tried a PS script to read the registry line HKLM:\\Software\\Microsoft\\Windows\\CurrentVersion\\Uninstall<\/p>\n
And WMIC and got all Microsoft products, but no o365 products<\/p>\n
Any ideas other than sneaker net?<\/p>","upvoteCount":5,"answerCount":8,"datePublished":"2022-04-22T16:49:52.000Z","author":{"@type":"Person","name":"spiceuser-vqh2p","url":"https://community.spiceworks.com/u/spiceuser-vqh2p"},"suggestedAnswer":[{"@type":"Answer","text":"
I have a bunch of remote computers I need to identify what version of MS Office they have installed. We need this so we can identify which computers are running Older versions of Office that are no longer supported or soon EOL. I tried a PS script to read the registry line HKLM:\\Software\\Microsoft\\Windows\\CurrentVersion\\Uninstall<\/p>\n
And WMIC and got all Microsoft products, but no o365 products<\/p>\n
Any ideas other than sneaker net?<\/p>","upvoteCount":5,"datePublished":"2022-04-22T16:49:53.000Z","url":"https://community.spiceworks.com/t/remotely-determine-the-office-version-installed/831122/1","author":{"@type":"Person","name":"spiceuser-vqh2p","url":"https://community.spiceworks.com/u/spiceuser-vqh2p"}},{"@type":"Answer","text":"
This is the PS script I ran as the Administrator:<\/p>\n
foreach ($computer in (Get-Content C:\\Script_tests\\computers422.txt)) {
\nwrite-verbose “Working on $computer…” -Verbose
\nInvoke-Command -ComputerName “$Computer” -ScriptBlock {
\nGet-ItemProperty HKLM:\\Software\\Microsoft\\Windows\\CurrentVersion\\Uninstall\\O365ProPlusRetail* |
\nSelect-Object DisplayName, DisplayVersion, Publisher
\n} | export-csv C:\\results.csv -Append -NoTypeInformation
\n}<\/p>\n
And this is the Response I received, I verified I could ping the computer:<\/p>\n
VERBOSE: Working on FERWD23MAY2019…
\n[FERWD23MAY2019] Connecting to remote server FERWD23MAY2019 failed with the
\nfollowing error message : The client cannot connect to the destination
\nspecified in the request. Verify that the service on the destination is
\nrunning and is accepting requests. Consult the logs and documentation for the
\nWS-Management service running on the destination, most commonly IIS or WinRM.
\nIf the destination is the WinRM service, run the following command on the
\ndestination to analyze and configure the WinRM service: “winrm quickconfig”.
\nFor more information, see the about_Remote_Troubleshooting Help topic.<\/p>\n