Robust Office Inventory Scan Tool (ROISCAN)

ROIScan is a VBScript inventory for all Microsoft Office installations on the computer to help troubleshoot patch and product installation issues. Ver 1.9.1

4 Star
Add to favorites
E-mail Twitter Digg Facebook
  • How do I download this?
    3 Posts | Last post August 02, 2019
    • How do I download this?
    • That seems like a major oversight.  If there's a download option, I don't see it either.  So copypasta.  Highlight the first few characters.  Scroll all the way to the bottom.  Hold shift and click the end of the doc.  It should highlight the whole thing without having to scroll the massive document.  Then copy and paste into a text file.  Save as VBS.
    • Note that other TechNet Gallery items DO have a download button.  Not sure why there is none here.
  • identifying bitness of office komponents
    1 Posts | Last post October 18, 2018
    • we are deploying access 2016 runtime >32 bit< to our customers.
      the 32 bit runtime cannot be installed if a 64 bit office component is preinstalled.
      so far so clear.
      therefore our Installation-script must first identify if >ANY< office 64 bit components are installed on the targetted System, e.g.
      "64bit Office component(s) found > Installation abort"
      how can this be done with roiscan?
      thanks for any hints.
  • Doesn't find the Microsoft Store version of Excel
    1 Posts | Last post September 04, 2018
    • This script does not appear to detect the Microsoft Store version of Office that is now being used more and more. Can this be updated?
    1 Posts | Last post January 16, 2018
    • I am looking for ROISCAN for MAC systems. can you please help me?
  • Including ROIScan script version version information
    3 Posts | Last post November 08, 2017
    • Hi,
      There have been many iterations of ROIScan available from the Office Support Engineers in the past and I know the current script on display is version 1.5.2 and version 1.5.3 is due soon. But I don’t understand why this is not displayed at the top of the script !
      Jami Hossami
    • @ Jami
      Your suggestion has now been implemented starting with 1.5.3
    • I'd like to suggest that in addition to the 'Const SCRIPTBUILD = "1.9.0"' line at the top of the script a 'Const SCRIPTDATE = Date the script was updated/modified'.  This would be useful for those looking for a particular version without knowing the version number.
  • abbrievated version
    1 Posts | Last post July 16, 2017
    • This is great for trouble shooting, for a professional technician. But it is overkill for the "average user".
      Couple of suggestions:
      1. as well as version number, could you add the "last changed date" to the script.
      2a. For the "average user" all they need is:
        - Windows OS Details (abbreviated): Home/Pro/etc, SP#,  Version number, Build number, Bitness
        - Office bundle name
        - Office installation type MSI/CTR
        - Office Version number
        - Office Build numbers
        - Office Channel 
        - Office bitness
      to report to tech support .  Could you capture just that info, with appropriate labels, in the clipboard. That way you could add a message to the script telling people that they can simply already use the clipboard, <CTL><V> to paste this information immediately into any tech support request. 
      2b. OR If you can't copy that info to the clipboard, could you create a summary report of just that info, either at the top or bottom of the existing report to make it easy for users to copy all of the info in a single operation.
      2c. OR make an abbreviated version of the script that can be down loaded 
      2d. OR make an abbreviated version of the script and make it available to KB article writers so they can add it to (most) KB articles as a "fix it" tool 
      2e. Actually, after some reflection, rather than creating a separate file, just add a parameter and an IF to see if the user wants the full report or abbreviated report. That way all of the logic is maintained in one place. 
      3. I don't see an option to DOWNLOAD the file. If it is present, please make it more obvious, if not, please add to the page.  
      4. I copied the script, pasted it into Word and saved as TXT (then removed the TXT extension).  I got errors on several of the space characters.  After fixing the first 2 individually, I ended up doing a find and replace of ALL spaces .
      5. Add an option to subscribe to the page to be notified of updates to the script. 
  • Additonal information gathering
    1 Posts | Last post February 23, 2017
    • Hey there - great script.  Is it possible to have the script pull the current identity for Office 365 installations?  This information is found in HKCU\Software\Microsoft\Office\15.0 or 16.0\Common\Identity\Identities
      By doing this, you then know which Office 365 account is registered against the installation.
      Finally, is there a way to output certain parts of the gathered information to a registry key to then be imported via a RMM tool?  ie, for Office 365 installations I'd like to populate the active license Family key to HKLM\SOFTWARE\CentraStage\Custom8 and the Identity mentioned above to HKLM\SOFTWARE\CentraStage\Custom7
      For standard Office 2010-2016 installations, I'd like to populate the registry key HKLM\SOFTWARE\CentraStage\Custom7 with the "Partial Key" information
      Thanks in advance.
  • ROIScan via GPO for domain users
    2 Posts | Last post November 05, 2015
    • Hello everyone,
      Is there a way to pass credentials to the ROIScan during GPO deployment?  I am attempting to use the script to run in the background on user login, however our users do not have administrative rights.  
      Can anyone recommend another way to go about this?
    • The script will list some errors in the log but is still functional through it's fallback logic when run with user permissions.
      Run it with /q to avoid the elevation prompt
  • ROIScan over the netowrk
    1 Posts | Last post November 25, 2014
    • Hi there all,
      I have a question about running the ROIScan.vbs over the network. 
      The target would be to asset all the Office installations on my Active Directory Computer machines.
      Is this possible?
      Many Thanks in advance
  • Visio 2013 Standard not presenting KMS License status.
    1 Posts | Last post June 19, 2014
    • I am working on testing ROIScan against Visio 2013 Standard SP1 for Deutsche Bank.  I noticed that the resulting output does not display license status for this product, but works fine with Project 2013 Standard SP1 and other Office 2013 suites.  I have checked Visio product is activated using both "ospp.vbs /dstatusall" command (also shows KMS server where license was issued) and visually checking the Product Information page within Visio, and both show as activated.  I have also noticed an exception in the GetLicCnt function related to Visio, but unsure if this has anything to do with the fact that License information does not present for this product.
1 - 10 of 15 Items