Intune deployment guidelines

Avatar
Written by Jérôme | Updated

This guide explains how to deploy UpSlide software using Microsoft Intune MDM.

Note:

If you've received a new installer from our team, make sure to update the version number of the detection rule described in the UpSilde packaging section of this article.

Create an Intunewin app

You can deploy your customized Win32 apps via Microsoft Intune using the Intune-Win32-App-Packaging-Tool. You can find the tool here.

Then, create 2 folders: IntuneApps, where you can find the .exe you want to deploy, and Intunewin, where the tool will stock the .intunewin file.

Then, launch the tool and fill in the information on the screen using your specific names of files and locations. Example:

Screenshot_2021-09-29_092940.png

The .intunewin file will be generated. This process can take up to 5 Minutes.

Pre-Requisites packaging

Using the same Win32-App-Packaging tool, you'll need to package both pre-requisites:

Then, on the Intune Portal, create two new Win32 Apps as follows:

vsto.pngmceclip4.png

For VSTO dependency, the detection rules are as follows:

  • Key path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VSTO Runtime Setup\v4R
  • Value name: VSTORFeature_CLR40
  • Detection method: Integer comparison
  • Operator: Equals
  • Value: 1

 

Dependencies are now ready. The last part will consist of packaging UpSlide.

UpSlide Packaging

Go back to the Intune Portal and create a new Win32 Application to put the UpSlide .intunewin file that was previously generated. 

enhanced_install_-1.png

You can save the logo and add it so your software centre is clearer for your users. Then, go to the Program Tab to set your installation command line.

UpSlide_logo.png

 

Note:
You can find all the command line switches in this article.

 

installationcommand_enhanced.png

Next, go to the Detection Rules tab to set two detection rules as follows:

One to detect the installation:

  • Rules format: Manually configure detection rules.
  • Rule type: File
  • ​Path: C:\ProgramData\UpSlide\Binaries\
  • File: Finance3point1.UpSlide.Engine.dll
  • Detection method: File or folder exists

detection_rule_upslide_enhanced.png

And the second one is to detect the setup installation version, which is necessary if our team sends you an updated version of the setup:

  • Add a new rule in the same menu
  • Rule type: Registry
  • Key ​Path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Excel\Addins\Finance3point1.UpSlide.Excel
  • Value name: SetupVersion
  • Detection method: Version comparison
  • Operator:  Equals
  • Value: Your targeted version (it will be in your exe file name furnished by your consultant)

intuneequals.png

Important
Set the detection rule on the SetupVersion, and ensure the value has four digits.
For example, 6.9.23.5 (and not 6.9.23)

 Next, go to the Dependencies tab and select the pre-requisite apps packaged earlier:

mceclip2.png

That's it! Finish the package creation and assign the app to your users.

For all-user installs
The registry keys for an all-user install are inserted into the local machine hive HKEY_LOCAL_MACHINE.
Please beware of two specific requirements:
• If the installation is carried out on an x64 machine with an x32 version of Office, the keys are inserted in HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node.
• An additional key value is needed in HKEY_LOCAL_MACHINE\SOFTWARE\Office\12.0\Common\General: EnableLocalMachineVSTO (Dword) set to 1.