To offer TADDM WMI extention update as a .msi file to simplify automating deployment in environments where the autodeploy feature is not an option

With each TADDM Fixpack, an updated TADDM WMI extention is offered. This WMI extention has to be installed on all Windows systems  to ensure the Session and Windows Computer Sensors continue to work properly.

One can use the WMI Autodeploy feature in TADDM to update the Windows target systems during discovery, however this only works if the discovery credentials being used also have administrator privileges on each Windows system. 

In many customer evironments, only the minimal permissions needed to perform the individual TADDM discoveries for each particular sensor are allowed, so more often than not the WMI Autodeploy is not a viable option to update the TADDM WMI extention locally on each Windows system. 

TADDM Support has made a powershell script available to install the WMI update for non-admin accounts. This also works but the standard format for most automation tools in customer environments is a .msi file.

My request for enhancement is as follows:

Could TADDM Development create an officially supported  .msi file that installs the WMI extention updates as in the script or the WMI-Autodeploy? Customers are asking for this in a .msi format, the most common format for Windows Automation Tools (SCCM or GPO update policies in Active Directory).

This would make the rollout of new TADDM versions easier as the WMI updates would be installed faster in environments where the WMI Autodeploy is not a viable option.