With the file CBClientSetup.msi, the administrator can avoid trusting each user with installations and upgrades, or from going from machine to machine to install or upgrade. Instead you can use the tools within your existing Windows server to deploy these MSI setups throughout your organization.
You can also use the scrip file RegistryScript.vbs in the Calendar Browserserver folder to add Calendar Browser group(s) to the client installations. This file can be used individually (see below) or with Active Directory.
A detailed elaborate tutorial on this aspect is out of context in this FAQ, but there are informative resources and knowledge base articles available on the internet.
Here are some links which should give you a fair idea on how to implement such a deployment technique in your organization.
Install a COM add-in automatically using Windows Server Group Policy: https://www.add-in-express.com/creating-addins-blog/2009/01/25/automatic-installation-windows-group-policy/
How to use Group Policy to remotely install software in Windows Server 2003 https://support.microsoft.com/kb/816102
Deploying a MSI through Group Policy Object (GPO) https://www.advancedinstaller.com/user-guide/tutorial-gpo.html
Additionally, the User MSI setup can be installed silently, by running the CBClientSetup.msi with the /qn commandline parameter
Eg. CBClientSetup.msi/qn
Please contact the bizsolutions365.com Support if you have questions!