Workstatus Silent App Installation Through Microsoft Intune — SOP

Purpose

This document provides step-by-step instructions for installing the Workstatus Silent App on Windows systems through Microsoft Intune.
The process involves:

• Mapping the user's Machine ID in Workstatus.
• Creating the user in Microsoft Intune.
• Assigning an Intune license to the user.
• Connecting the user's Windows system to Microsoft Entra ID.
• Registering the device with the organization's MDM.
• Creating and assigning the Workstatus Silent App in Intune.
• Verifying the installation and data synchronization.

Prerequisites

Before starting the installation, ensure the following:

• Admin/IT team has access to Microsoft Intune.
• Admin/IT team has access to Microsoft Admin Center.
• User has a Windows system.
• The previous version of the Workstatus app should be uninstalled.
• User has Administrator access to the Windows system.
• Workstatus Silent App package is available.
• Workstatus custom detection script is available.
• User's Machine ID is available/mapped in Workstatus.
• Internet connectivity is available on the user's system.

1. Admin / IT Team Actions

1.1 Map User Machine ID in Workstatus

Before starting the Intune installation, map the user's Machine ID with the corresponding Workstatus user account.
Follow the Workstatus support article: How to Map a User's Machine ID in Workstatus
Steps

• Log in to the Workstatus application.
• Navigate to the appropriate user/member.
• Map the user's Machine ID to the corresponding Workstatus user account.
• Verify that the Machine ID is correctly mapped.

Important: The Machine ID is used to identify and associate the user's Windows machine with their Workstatus account during the MDM installation process.

1.2. Create User in Microsoft Intune

Step 1: Open Microsoft Intune

Open the Microsoft Intune portal: Microsoft Intune Admin Center

Step 2: Create a User

• Log in with the Admin/IT account.
• Go to Users.
• Click Create User.
• Select Create New User.
• Enter the User Principal Name.
• Enter/copy the user's email address.
• Enter the Display Name.
• Set/copy the temporary password.
• Click Review + Create.
• Review all the entered information.
• Click Create.

Note: Keep the user email address and temporary password available because they will be required when connecting the user's Windows system to Microsoft Entra ID.

1.3 Assign Microsoft Intune License to the User

After creating the user, assign an Intune license.

Step 1: Open Microsoft Admin Center

Open: Microsoft Admin Center – Users

Step 2: Assign License

• Go to Users.
• Select Active Users.
• Search for the newly created user.
• Click the three-dot (...) menu.
• Select Manage Product Licenses.
• Go to Licenses and Apps.
• Select the appropriate Microsoft Intune license.
• Enable the Intune license.
• Click Save Changes.

Verification

Verify that the Intune license is successfully assigned to the user before proceeding.

2. Action on User's Windows System

Requirement: The user must have Administrator access to the Windows system.

2.1 Open Work or School Account Settings

On the user's Windows system:

• Open Settings.
• Go to Accounts.
• Select Access work or school.
• Click Connect.

2.2 Join Device to Microsoft Entra ID

• In the account connection window, click Join this device to Microsoft Entra ID.
• Enter the user email address created in Intune.
• Enter the temporary password created during user creation.
• Click Sign in.

2.3 Update User Password

The Update Your Password screen will appear.
Enter:

• Current Password: Temporary password provided during user creation.
• New Password: Create a new password.
• Confirm Password: Enter the new password again.

Click Sign in/Submit as applicable.

2.4 Complete Device Registration

The system will display a Registering your device screen for a short period.
After registration:

• The Account Added to this device confirmation screen will appear.
• Click Done.
• If a confirmation pop-up appears, click Join.
• Wait for the registration process to complete.
• When You're all set appears, click Done.

The Windows user account is now connected to Microsoft Entra ID.

2.5. Connect the Device to Company MDM

After joining the device to Microsoft Entra ID:

• Go back to Settings → Accounts → Access work or school.
• Click Connect.
• Enter the user's company email address.
• Enter the user's password.
• Complete the connection process.

After successful connection, the Connected to company MDM option should be displayed.

2.6 Verify MDM Connection

• Click MDM.
• Click the Info button.
• The Managed by Vinove screen will open.
• Scroll to the bottom of the page.
• Click Sync.

Important: Syncing the device ensures that the latest Intune policies and application assignments are received by the user's Windows system.

3. Admin / IT Team — Create Workstatus Silent App in Intune

After the user's device is registered with Intune/MDM, the Admin/IT team can create the Workstatus Silent App deployment.

3.1 Open Windows Apps

• Log in to Microsoft Intune.
• Go to Apps.
• Select Windows.
• Click Create.

3.2. App Information

• Select Windows app (Win32).
• Click Select.
• Click Select package file.
• Upload the Workstatus Silent App package provided by the Workstatus team.
• Enter the required Publisher Name.
• Enter app version
• Click Next.

3.3. Program Configuration

Configure the installation commands.
Install Command :

• powershell.exe -NoProfile -ExecutionPolicy Bypass -File ".\install.ps1"

Uninstall Command :

• powershell.exe -NoProfile -ExecutionPolicy Bypass -File ".\uninstall.ps1"

After entering the commands:

• Verify the commands carefully.
• Click Next.

3.3. Requirements

Configure the application requirements.
Operating System Architecture

• Check Operating System Architecture.
• Select No for the applicable architecture requirement as per the Workstatus package configuration.

Minimum Operating System

Select: Windows 10 1607
Click Next.

Note: Keep the minimum OS version aligned with the Workstatus application's supported Windows version if the package requirements are updated.

3.4. Detection Rules

Detection rules allow Intune to determine whether the Workstatus Silent App is already installed.

• Select Custom Detection Script.
• Upload the Workstatus detection script provided by the Workstatus team.
• Set:

2. • Run script as 32-bit process on 64-bit clients: No
   • Enforce script signature check: No
   • Run script silently: No

• Click Next.

Important: Use the exact detection script provided by the Workstatus team. Do not modify the script unless instructed.

3.5. Dependencies

On the Dependencies page:

• Review the configuration.
• No additional dependency is required unless specified by the Workstatus team.
• Click Next.

3.6. Supersedence

On the Supersedence page:

• Review the configuration.
• No supersedence configuration is required unless replacing an existing Workstatus application version.
• Click Next.

3.7. Assignments

Assign the Workstatus Silent App to the required users or devices.
The following options are available:

• Add Group
• Add All Users
• Add All Devices

Select the appropriate assignment based on the deployment requirement.
For a user-based deployment, select Add All Users or the appropriate user group.
For a device-based deployment, select Add All Devices or the appropriate device group.
Click Next.

Recommendation: For production deployment, use a specific user/device group instead of assigning the application to all users or all devices unless the deployment is intentionally organization-wide.

3.8. Review + Create

1. Review all application configuration details.
2. Verify:
3. • App package
   • Install command
   • Uninstall command
   • Requirements
   • Detection script
   • Dependencies
   • Assignments
3. Click Create.

The Workstatus Silent App package will begin uploading to Microsoft Intune.

Note: Application upload may take several minutes depending on the package size and internet connection.

4. Verify App Installation Status in Intune

After assigning the Workstatus Silent App, Admin/IT can verify the deployment status from Microsoft Intune.

• Log in to Microsoft Intune.
• Go to Apps → Windows.
• Search for and open the Workstatus Silent App.
• Open the Overview or Monitor section.
• Check the application installation status.

Intune displays the installation status for the assigned users/devices.

Installation Status

5.App Installation on User System

After the application is successfully uploaded and assigned:

• Intune will deploy the Workstatus Silent App to the assigned Windows system.
• The user's Windows system must be connected to the Internet.
• The device must be successfully enrolled with Intune/MDM.
• The device should perform an Intune sync.
• Intune will download and install the Workstatus Silent App silently.

Expected Result

The Workstatus Silent App should be installed on the user's Windows system without requiring normal user interaction.

6. Data Synchronization

After successful installation:

• Workstatus services will start running on the user's system.
• The application will communicate with the Workstatus backend.
• User activity/tracking data should begin synchronizing.
• Initial data synchronization may take approximately 10–15 minutes.
• Note: The exact synchronization time can vary depending on network connectivity, device performance, Intune policy sync, and Workstatus service status.

7. Troubleshooting

Workstatus App is not installing

Check:

• Device is connected to the Internet.
• Device is connected to company MDM.
• Intune license is assigned to the user.
• User/device is included in the application assignment.
• Intune has successfully synced.
• Installation command is configured correctly.
• Workstatus package was uploaded successfully.
• Detection script is configured correctly.

App is installed but data is not syncing

Check:

• Machine ID is correctly mapped to the Workstatus user.
• Internet connection is available.
• Workstatus services/processes are running.
• Wait approximately 10–15 minutes for initial synchronization.
• Verify the user/device association in Workstatus.
• Check application logs if data still does not appear.

Updated on: 08/10/2026