Micollab desktop Client 7.3 - Mass rollout with custom config

[tixx]

Hi everyone,

Is there any way to create a uniform configuration setting for a large number of users for the desktop client? we have 200+ users and 300+ workstations that need the software installed and configured in a particular way for all.

this includes.

- auto start with windows
- auto login
- auto integrate with outlook calendar and configure custom dynamic status preset
- create a number of new statuses (under manage statuses)

Also, is there a way of easily creating these statuses on the server end for all users?
and is there a way of adding users mobile numbers as a secondary number on the server end?

Thanks

[VinceWhirlwind]

Download the "MiCollab Client Administrator Guide".
 
Turn to Page 108.
 

[VinceWhirlwind]

Actually, Release 7.3 of the Guide has it on Page122:
 
Install the MiCollab Windows Desktop Client
The MiCollab Client installer ships as a Windows Installer package. You can use a file server on
your network as a software distribution point for the MiCollab Client. When you complete the system
configuration, send the Welcome E-mail to users, which includes a link to the software location on
the server.
Software distribution point
A Software Distribution Point uses Active Directory Group Policy objects to deploy MiCollab Client
using Active Directory Group Policy objects. This enables MiCollab Client to be run from a single
location and appear to be installed on every user's desktop.
Installing MiCollab Client using a distribution point is done with an administrative install of the installer
package to a network share. The share point must be accessible to all users who will install MiCollab
Client. The command for the administrative installation is:
%>msiexec /a UnifiedCommunicatorAdvanced.msi
The administrative installation wizard prompts you to enter a location for the administrative image.
Users can be instructed to install MiCollab Client from this folder via the network share. The users
can run the installation wizard by clicking the file and entering the MiCollab Client Service FQDN
when prompted.
Alternatively, a transform file (see “Creating a transform” on page 128), or the Explorer shortcut that
includes the IP property in the command parameters, could be provided:
%>msiexec /i UnifiedCommunicatorAdvanced.msi UC_SERVER_HOSTNAME=”192.168.1.66”
In this example, UC_SERVER_HOSTNAME property is set to the IP address of the MiCollab Client
Service.
Suppressing the installation wizard dialogs can further customize the installation by using the /qn
flag. More customization options can be found in the Windows Installer SDK documentation at
http://msdn2.microsoft.com/en-us/library/aa367988.aspx.

[tixx]

Thanks everyone, will take a look at that.

We dont have on prem AD, only AzureAD so that will be difficult to push via GP.

What about the questions regarding setting mobile numbers and custom statuses for users via the micollab server GUI?

Thanks

[VinceWhirlwind]

Match an AD field to the MiCollab 2nd phone field and make sure each user's mobile is entered in the AD field.
Create a template in MiCollab which has deskphone as well as 2nd phone.
When you provision each user in MiCollab it will add in the mobile for you.
 
MiCollab statuses they will have to create themselves.

[tixx]

Thanks Vince

Much appreciated