Deploying Windows MSI Applications via Mobile Guardian
This guide covers the deployment of Windows .msi installers to managed Windows devices using the Mobile Guardian dashboard.
Prerequisites
Before starting, ensure you have the following information and resources ready:
- Direct Download URL: An HTTP/HTTPS direct link pointing to the hosted .msi file. The URL must download the file directly without intermediate landing pages or interactive sign-in screens.
- Installer Properties (Product Code & Upgrade Code):
- Extract the ProductCode GUID (unique to this release) and UpgradeCode GUID (identifying the general software family) from the MSI file's Property table using a tool like Orca or PowerShell.
- SHA-256 Hash: The checksum generated from the .msi file. Windows enforces this hash check to verify integrity before installing.
Step 1: Access Hosted Applications
- Sign in to your Mobile Guardian Dashboard.
- From the main sidebar, select Applications.
- Click on the Windows tab.
- Click New Hosted Application.
Step 2: Configure Details. Fill out the initial metadata fields:
Fill out the initial metadata fields:
| Field | Configuration Guidance |
| Title | The display name of the software (e.g., 7-Zip 64-bit). |
| Description | Notes or internal details regarding the purpose or version of the deployment. |
| Vendor | The software publisher or developer (e.g., Igor Pavlov). |
| Install Type | Select Hosted MSI. |
| Upgrade Code | Enter the package's UpgradeCode GUID. This ensures Windows recognises the application family during subsequent version updates. |
| Product Code | Enter the exact ProductCode GUID for this version. Windows uses this value to confirm installation success. |
| Version | Enter the exact software version number (e.g., 23.01.00.0). |
Step 3: Manual Configuration (MSI Package Specifics)
Configure the package download source and silent execution parameters:
- Package URL: Paste the direct HTTPS URL where the .msi is hosted.
- File Hash: Paste the SHA-256 hash. If the downloaded file differs by even one byte, Windows will abort the installation.
- Install Arguments: Command-line parameters passed directly to msiexec.
- Install Timeout (minutes): Maximum allowable time for the installer to finish execution before Mobile Guardian marks the task as failed. Leave blank to rely on the standard operating system default.
Step 4: Device Assignment & Settings
Choose how devices receive and install the MSI package.
Auto-Install Settings
Use this section to silently push the software automatically:
- Assignment Scope:
- Assign to all school-owned devices: Targets institutional equipment.
- Deployment Flags:
- Honour install window: Defines when the installation can take place (set to Immediately by default, or scheduled for off-hours).
- Version:
- Add the version of the application, same as you have added above.
Step 5: Application Policy & Installation Verification
To verify that the application policy has successfully deployed and installed the software on the target device:
- Navigate to the Device Settings: Navigate to the specific device's settings and select Policies
- Review Applied Policies: Go to Policies > Applied.
Verification: Confirm the policy assigned to install the newly added application appears in the active policy list.
Check Installed Applications: Select Installed Applications from the device menu.
Verification: Confirm the newly added application appears in the list of installed software with its corresponding version.