Office 365 Click-to-Run Build

Display Office 365 Click-to-Run Build


Show which Office 365 Click-to-Run build to a custom field. I created an agent procedure that pulls the release number from the registry, and stores the value in a custom field on the Audit > Individual Data > Machine Summary page. You can also use that custom field as an "Culomn" in Agents > Manage Agents

1. In Kaseya go to "Audit --> View Individual Data --> Machine Summary"
2. Click on "New Custom Field" in the summary tab
3. Name it to "Office Click-to-Run Version" or else you need to edit the procedure
4. Import the XML file from "System --> Server Managment --> Import Center"
5. Run the procedure "Add - Office Click-to-Run Version to Custom Field"

Version and build numbers of update channel releases:

  • Name: Tobias Nilsson
  • Company: B2B IT-Partner
  • Website: http://www.b2bitpartner.se
  • Contact Developer
  • Summary
  • Office 365 Click-to-Run Build
  • Initially Released December 11th, 2017
  • Reviews
    Gravatar for Derek Harlan
    by Derek Harlan on August 21st, 2020

    Initially couldn't get it to work but creating my custom field as a string data type instead of a number resulted in procedure working. Thank you!

    Gravatar for Nick
    by Nick on November 12th, 2019

    does exactly what it says. thanks!

    Gravatar for samuel@finkeltron.com
    samuel@finkeltron.com over 3 years ago

    Instructions are unclear? Do I make a custom field? Instructions for that?

    Gravatar for Tobias Nilsson
    Tobias Nilsson over 3 years ago

    Thx for the input. Updated instructions!

    Gravatar for Lane Boudreaux
    Lane Boudreaux about 2 years ago

    Custom field not being populated. Procedure runs successfully. Verified the registry key does exist. Any suggestions? FYI Majority of clients are 64bit OS and 32bit Office. Will be very useful going forward

    Gravatar for Derek Harlan
    Derek Harlan 8 months ago

    Could not get custom field to populate after running procedure. Verified value exists in registry.

    Gravatar for Derek Harlan
    Derek Harlan 8 months ago

    When choosing the custom field data type, initially chose number but when I created another custom field to test and created as a string (modified the procedure to use this test field) it populated successfully. For it worked after making it a string data type instead of a number data type.