Deploying Wildix Native Legacy Collaboration App and WIService using Microsoft Intune
This document provides all the necessary information for deploying Wildix Native Legacy Collaboration App and WIService using Microsoft Intune.
Created: January 2025
Permalink: https://wildix.atlassian.net/wiki/x/AgDPOg
Introduction
At Wildix we offer a .msi file to enable large-scale Microsoft deployments, utilising tools such as Intune and System Centre Configuration Manager. Below are some steps on how to deploy Wildix Intune.
Requirements
Windows 10 (64-bit) or higher
Microsoft .NET Framework v.4.0
Preparation
To use the .msi file in Intune, you need to prepare it. To do so, follow the steps described below:
Download the MSI files from the links below:
Legacy Collaboration Native App: https://files.wildix.com/integrations/win/collaboration/Collaboration-x64.msi
WIService: https://files.wildix.com/integrations/win/wiservice/WIService.msi
Current limitations: No support for text-to-speech in live search, chat & no possibility to change default webcam in case more than one is available.
Then download the Win32 Content prep tool from this link: https://github.com/microsoft/Microsoft-Win32-Content-Prep-Tool (download link is Version 1.8.6)
Once it’s downloaded, unzip the folder and open up the IntuneWinAppUtil Application
That will open up a terminal window, and ask you to specify the source folder of the application you want to convert. If you go to the application, right-click and open up properties, you can copy the Collaboration-x64.msi file location
Once you press Enter, you will be asked to specify the set-up file, which you do
Once you hit Enter again, you will be asked to specify where you want the new file to be outputted to
The final step is to be asked if you want to specify catalog folder (Y/N), you should enter N
The program will then run and create a Win32 app that you can upload to InTune. You can do this for the WIService.msi file as well
After you’ve converted the .msi files into Win32 Apps, you can upload them to InTune. If you have not already installed WIService, we recommend starting with there, as you can set up WIService as a dependency when installing the Native App.
WIService Installation
To start, proceed to your Intune page. Log in, go to Apps, All apps (1), and select Add (2). Then from the App type menu, go to Windows app (Win32), which is under “Other”. (3), then click Select (4)
Then open the converted app and press OK
Now you follow the process and specify how you want the app configured. Firstly, fill out the Publisher name as Wildix. You can choose this time to add any category that you may have in your company. When ready, select Next at the bottom to move on
The next page is where you specify how you want it installed and with what settings
WIService Custom App Parameters that can be used within the install command:
enableAutoupdate=true (enabled) / false (disabled) - auto upgrade option
wiserviceSilentmode=true (enabled) / false (disabled) - install in silent mode. Note that you can not have wiserviceSilentmode=true if you’re using auto upgrade. It needs to be set to false
launchAtStartup=1 - once opened for the first time, it will automatically start on start-up
Once you’re happy with the configuration, select Next.
On the next page, you select the requirements, the operating system architecture (64-bit) and then the min operating system (min. Windows 10). Then select Next
Then set the detection. Use the drop-down to select manually configure detection rule. Then select Add. A new sidebar will open, use the drop-down to select MSI and it will auto-populate
After setting the detection, select Next. The next two pages are Dependencies and Dupersedence, you do not need to set anything here, so can select Next on both pages until you get to the section where you can choose the groups to deploy this to
Once you have selected the groups to deploy the app to, proceed to the summary section
Once you’re happy with the configuration, select Create at the bottom of the page and it will create the app within Intune
Native App Installation
To install the Legacy Collaboration Native App, you will need to follow similar steps to WIService. To start:
Add a new Win32 app and select the Legacy Collaboration app
Now you follow the process and specify how you want the app configured. Firstly, fill out the Publisher name as Wildix. You can choose this time to add any category that you may have in your company. When ready, select Next at the bottom to move on
The next page is where you specify how you want it installed and with what settings
The install command gives you an opportunity to configure the installation. Please see the details of each option below, but the main details are the host=yourhostname.wildixin.com, where you need to change yourhostname to the PBX name
Native App Custom App Parameters:
host - host installation for all users on the computer
hidePreferences (optional) - disable the settings menu for all users
secondaryHost (optional) - failover custom domain host
callControlMode (optional) - login to Legacy Collaboration in call control mode
callBringToFrontMode (optional) - open minimised or closed in system tray/ menu bar Legacy Collaboration on incoming calls
allowInsecureConnections (optional) - allow non-secure connections in case of invalid SSL/TLS certificates
An example of the custom code would be:
/qn host=yourhostname.wildixin.com hidePreferences=0 secondaryHost=yourhostname2.wildixin.com callControlMode=0 callBringToFrontMode=1 allowInsecureConnections=1Once you’re happy with the configuration, select Next
On the next page, you select the requirements, the operating system architecture (64-bit) and then the min operating system (min. Windows 10). Then select Next
Then set the detection rules. Set the rule format to manually configure, then select Add. That will give you the option to add a rule type as MSI and it will auto-populate the code. Select OK and then Next
The next step will allow you to set it so that the WIService is installed first. You can do this by setting it as a dependency. On the dependencies page, select Add, a new sidebar will open, and you should be able to select the WIService app
Then select Next to go through the Supersedence option and then you can assign the app to the relevant users and groups
Once you’ve assigned it, you can select Next to review and create the app deployment
Check over the settings and if you’re happy, you can proceed and it will create the application and then upload the software ready for the devices to be synced
Below is a screenshot of the summary:
A note regarding the Auto Upgrade of the WIService. If enabled, it will create a Windows Task Scheduler, to check for updates every day at 0100-0600 or after starting PC. The task is set to run with the highest privileges and whether the admin user is logged in or not, which will install the latest update in silent mode. Please see the screenshot below: