locked
Command to find out office bit version for remote computers RRS feed

  • Question

  • Hello,

    Starting to (try) and learn more about powershell. 

    Is there a cmd line that will return info on whether an office install
    is 32 or 64 bit on remote computers?

    I've found info on how to obtain installed apps on remote computers, 
    but not the bit version:

    Get-WmiObject -Class Win32_Product -Computer *remote computer name*

    Thanks!

    Thursday, March 7, 2019 9:22 PM

All replies

  • Look at the installed folder.  If it is Programs x86m it is 32 bit.

    I can almost guarantee that all are 32 bit as that is the MS recommendation.


    \_(ツ)_/

    Thursday, March 7, 2019 9:58 PM
  • Hi,

    Indeed, it will "most likely" be 32bit, however one way is to check the Windows Registry, for example:

    Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Office\ClickToRun\Configuration" | Select Platform

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    Thursday, March 7, 2019 10:02 PM
  • Thanks, but I need something that will obtain this info off of a remote computer.

    Is there something I could add to make that work?

    Thursday, March 7, 2019 10:04 PM
  • I need this info off of remote computers.


    Thursday, March 7, 2019 10:05 PM
  • The registry method will not work for older versions of Office.

    If you are using the O265 install the WIn32_Product and the registry version will not work.

    You can run the above code using remoting.

    You can look in the registry to find other methods to detect Office installations and configurations.


    \_(ツ)_/

    Thursday, March 7, 2019 10:10 PM
  • You can also query remotes like this:

    reg query \\alpha\HKLM\SOFTWARE\Microsoft\Office\ClickToRun\Configuration /v platform

    Where "alpha" is the remote system.


    \_(ツ)_/

    Thursday, March 7, 2019 10:16 PM
  • You can also query remotes like this:

    reg query \\alpha\HKLM\SOFTWARE\Microsoft\Office\ClickToRun\Configuration /v platform

    Where "alpha" is the remote system.


    \_(ツ)_/

    Thanks. I tried that using both just the computer name, and also the full computer name (i.e.  sfd-jkotson10 & sfd-jkotson10.ngad.local) and in both instances i get:  ERROR: The network path was not found.

    I've verified the computer name by pinging it, and by running the pwrshell cmd to obtain the serial number

    Thursday, March 7, 2019 10:33 PM
  • The reg query requires the Remote Registry service to enabled and running.

    Blog: https://thesystemcenterblog.com LinkedIn:

    Thursday, March 7, 2019 10:37 PM
  • The reg query requires the Remote Registry service to enabled and running.

    Blog: https://thesystemcenterblog.com LinkedIn:

    Ahh... gotcha. Thanks.  Our computers are imaged &  managed out of our NY office (I'm on the West Coast). I just tried 5 different machines and get the same "network path not found".

    The service is disabled on my pc, so it appears that's the case on all of the pcs here.

    Thursday, March 7, 2019 10:44 PM
  • Only two choices available.  Look at the folders or use remoting.

    \_(ツ)_/

    Thursday, March 7, 2019 10:54 PM
  • Hi,

    Was your issue resolved? 
    If you resolved it using our solution, please "mark it as answer" to help other community members find the helpful reply quickly.
    If you resolve it using your own solution, please share your experience and solution here. It will be very beneficial for other community members who have similar questions.
    If no, please reply and tell us the current situation in order to provide further help.

    Best Regards,
    Lee


    Just do it.

    Monday, March 11, 2019 5:52 AM