Skip to main content

Deploy Via Intune

Status: Released Updated: 01 Sep 2026

Overview​

This guide describes how to deploy the MyPass Windows Client using Microsoft Intune. Intune is the cloud-based endpoint management solution for Windows devices enrolled in your organization.

Prerequisites​

  • Windows 10 or later: Devices must run Windows 10 or Windows 11
  • .NET Framework version 4.5 or later: Required on target devices
  • Device Enrollment: Devices must be enrolled in Intune (MDM)
  • Installation Package: Windows Client version 4.5.0.25074

Obtaining the Installation Package​

Download the MSI from the MyPass Download Portal or contact your deployment engineer. Extract FastPassWindowsClient-v4.5.0.25074.zip to access the .msi file.

Step-by-Step Deployment via Intune​

Step 1: Add the Application​

  1. In the Intune admin center, go to Apps > All Apps > Create
  2. Select Windows platform and Line-of-business app > Select

Step 2: Upload the MSI and Configure App Information​

  1. Upload the MSI file and complete the App information page:

    • Name: "MyPass Windows Client"
    • Description: "Enables password reset and account unlock from the Windows login screen"
    • Publisher: "MyPass" or your organization name
    • Category: Select "Productivity" or "Security"

  2. Optionally add command-line arguments:

    • /q for quiet installation (no prompts)
    • /norestart to prevent forced reboot after installation (users must restart manually, or restart can be scheduled)
    • /l*v "C:\Logs\MyPassWindowsClientInstall.log" to write verbose logs to a file for troubleshooting (useful for debugging installation issues)
    • Example: /q /norestart /l*v "C:\Logs\MyPassWindowsClientInstall.log"
    note

    The MSI may still require a restart for the Windows Client to function. If using /norestart, notify users that a restart is required before the Windows Client will be available. Log files can be reviewed on target devices at the specified path if installation issues occur.

  3. Click Next through scope tags (if applicable) to reach assignments

Step 3: Assign to Target Groups​

Required Assignment (mandatory installation):

  • Select Required and add the target groups
  • Apps install automatically on next device sync (typically within 8 hours)

Available Assignment (optional installation):

  • Select Available for enrolled devices and add target groups
  • Users can install from Company Portal at their convenience

Exclude Groups (optional):

  • Exclude specific groups if needed (e.g., test devices)

Step 4: Review and Create​

Review all settings and click Create to complete the deployment.

Step 5: Monitor Deployment Status​

Use the Monitor section to track deployment progress:

  • Overview: Chart showing overall installation status
  • Device install status: Status per device (Succeeded, Pending, Failed, Not Applicable)
  • User install status: Status by user

Intune checks for new assignments every 8 hours; devices/users can manually sync for immediate deployment.

Deployment Best Practices​

  • Pilot First: Start with a small pilot group (IT department) before full rollout
  • Staged Rollout: Deploy in phases to manage support load
  • User Groups: Most deployments should target user groups rather than device groups
  • Monitor Progress: Review deployment status regularly in the Monitor section

Troubleshooting​

Installation Fails: Check that devices have .NET Framework 4.5+ installed. Review Intune Management Extension logs on the target device. Trigger a manual device sync via Company Portal.

App Doesn't Appear in Company Portal: Verify the device is enrolled in Intune and the user is in an assigned group. Wait up to 8 hours for assignment processing or manually sync.

Installation Hangs: Add /q to command-line arguments for quiet mode. Ensure sufficient disk space. Verify Windows Installer service is running.

Post-Deployment​

After successful deployment:

  1. Users will see the Windows Client Launch Panel on the login screen after device restart
  2. Users must enroll in MyPass through the Launch Panel
  3. Configure additional settings via Windows Client Customization if needed

Additional Resources​