Intune Silent Installation

Overview

BuzzBID can remain packaged as an MSIX application. You do not need a separate MSI package simply to support silent deployment through Microsoft Intune. Keeping the application deployment and the per-user AutoLogout configuration separate simplifies application updates while preserving user-level configuration control.

• BuzzBID application: Deploy as an MSIX Line-of-Business app for silent installation and version updates.
• AutoLogout setting: Deploy with a PowerShell script running in user context so the setting is created or updated in the correct Windows user profile.

1. Deploy BuzzBID as an MSIX Line-of-Business app

1. In the Microsoft Intune admin center, add BuzzBID as a Line-of-Business app.
2. Upload the signed BuzzBID MSIX package.
3. Assign the application as Required to the appropriate BuzzBID user or device group.

Intune can then install BuzzBID without requiring end-user interaction.

For future BuzzBID releases, publish a newer MSIX package with the correct package identity and a higher package version. This allows Windows and Intune to treat the package as an update to the existing application.

2. Deploy the AutoLogout setting separately

The AutoLogout setting is stored under the signed-in user's profile and should be deployed separately from the system-level application package.

Target file:
%LOCALAPPDATA%\BuzzBID\settings\autologout

Configure the Intune PowerShell script to run using the logged-on user's credentials. This ensures that %LOCALAPPDATA% resolves to the actual BuzzBID user's profile instead of the Windows SYSTEM profile.

AutoLogout file content

Create the autologout file with this exact JSON content:

{"a":1,"b":false}

The values mean:

• a = 1 sets the AutoLogout period to one hour.
• b = false indicates that the setting was configured by an administrative script such as Microsoft Intune.
• b = true indicates that the setting was configured through the BuzzBID user interface.

For an Intune deployment, use b = false so BuzzBID can distinguish centrally managed configuration from a value selected by the user in the application.

Example PowerShell script

$settingsFolder = Join-Path $env:LOCALAPPDATA "BuzzBID\settings"
$settingsFile = Join-Path $settingsFolder "autologout"

New-Item -ItemType Directory -Path $settingsFolder -Force | Out-Null

$content = '{"a":1,"b":false}'
Set-Content -Path $settingsFile -Value $content -Encoding UTF8

Recommended Intune script settings

• Run this script using the logged-on credentials: Yes. This is required so the file is written to the actual user's profile.
• Enforce script signature check: Follow your organization's policy. Enable this option if your organization requires signed PowerShell scripts.
• Run script in 64-bit PowerShell host: Yes, unless there is a specific reason not to. This is recommended for modern Windows endpoints.

Installation and upgrade flow

1. Intune deploys the BuzzBID MSIX package as a required LOB application.
2. Windows installs BuzzBID silently for the targeted users or devices.
3. The separate Intune PowerShell policy runs in user context and creates or updates the AutoLogout file with {"a":1,"b":false}.
4. When a new BuzzBID version is released, publish the newer MSIX package through Intune.
5. Continue managing the AutoLogout configuration independently; it does not need to be embedded in the BuzzBID installer.

Uninstall considerations

Because BuzzBID is deployed as an MSIX package, there is normally no traditional BuzzBID uninstall executable path. Intune and Windows manage BuzzBID as an app package.

Treat the AutoLogout setting separately from application removal. Removing BuzzBID does not necessarily require deleting the user-specific setting file. Keeping the file can preserve the customer's configuration if BuzzBID is reinstalled later.

Final recommendation

Deploy the BuzzBID MSIX as a required Line-of-Business app and deploy the AutoLogout setting as a separate PowerShell script running in user context. This keeps application lifecycle management simple while preserving per-user configuration control.