Deploying IDmelon Kiosk Using Intune

This guide provides step-by-step instructions for deploying IDmelon Kiosk for Kiosk Mode Policy using Microsoft Intune.

Step 1: Add IDmelon Kiosk App to Intune

  1. Access the Endpoint Manager Microsoft Intune.
  2. Navigate to Apps > All apps.
  3. Add a New Microsoft Store App
    • Click on + Create at the top of the screen.
    • From the dropdown, select Microsoft Store app (new).
    • Search for IDmelon Kiosk in the Microsoft Store and select it.
    • In the App Information pane, click Search the Microsoft Store app (new).
    • A search window will appear.
    • In the search field, type IDmelon Kiosk.
    • Press Enter.
    • Locate IDmelon Kiosk from the search results.
    • Click on the app name to select it. IDmelon Kiosk from MS Store
  4. Configure App Information
    • Change the Install behavior to System
    • Click Next to continue. IDmelon Kiosk Installation Behavior
  5. Assignments:
    • Decide who gets the app.
      • Under Required, click Add Group and select the device or user groups you want to deploy the app to.
    • Click Next when done. IDmelon Kiosk Assignment
  6. Review + Create:
    • Review all the configurations you’ve made.
    • Click Create to add the app and its dependencies to Intune.

Step 2: Create a Kiosk Configuration Policy

  1. Navigate to Configuration Profiles:
    • Go to Devices > Configurations.
  2. Create a Kiosk Policy:
    • Click + Create > New Policy.
    • Platform: Choose Windows 10 and later.
    • Profile type: Select Templates > Kiosk. Create Kiosk Policy
  3. Configure Basics:
    • Name: Enter IDmelon Kiosk Configuration.
    • Description: Provide details to identify the profile (optional).
    • Click Next to proceed.
  4. Configuration Settings:
    • Kiosk mode: Select Multi-app kiosk.
    • Target devices running Windows 10/11 in S mode: Select No.
    • User logon type: Choose Autologon.
    • Browsers and Applications: Select Add by AUMID.
    • App Name: Enter IDmelon Kiosk.
    • AUMID: Enter Hellokey.45853B8ADE74A_kxcedb3gts26c!App.
    • Click OK to add the app to the kiosk profile.
    • Click Next to continue. Create Kiosk Policy
  5. Assignments:
    • Under Included groups, click Add groups.
    • Select the device groups that should receive the kiosk configuration. Create Kiosk Policy
  6. Review + Create:
    • Click Create to deploy the configuration profile.

Step 3: Configure the Kiosk Settings

Editing the configs.xml file enables you to tailor the IDmelon Kiosk app to your preferences.

  1. Navigate to the App’s Local State Folder:

    • In the File Explorer address bar, type or paste the following path and press Enter:
    %LOCALAPPDATA%\Packages\Hellokey.45853B8ADE74A_kxcedb3gts26c\LocalState

    For kiosk users, the path is:

    C:\Users\kioskUser0\AppData\Local\Packages\Hellokey.45853B8ADE74A_kxcedb3gts26c\LocalState
    • This path directs you to the LocalState folder where the configs.xml file is stored.

  2. Configuration Parameters:

    • The file contains the following parameters:
    <KioskURL>https://myapps.microsoft.com</KioskURL>
<SelfService>false</SelfService>
<MultiTabMode>true</MultiTabMode>
<ExtensionEnabled>true</ExtensionEnabled>
<EndSessionConfirmation>false</EndSessionConfirmation>
<RestartAppOnEndSession>false</RestartAppOnEndSession>
<ShowURLBar>false</ShowURLBar>
<ShowEndSessionButton>true</ShowEndSessionButton>
<ServerAddress env="prod" />
    • KioskURL: The default webpage the kiosk app loads upon startup.
    • SelfService: Set it true if the KioskURL is a custom url (e.g., self-service url).
    • MultiTabMode: Enables (true) or disables (false) multi-tab browsing. Setting this to false activates full-screen mode.
    • ExtensionEnabled: Toggles browser extensions on (true) or off (false). Note: The Browser extension is required for the automation process. (When a card taps on the reader, the login automation will start).
    • EndSessionConfirmation: Prompts users for confirmation when ending a session if set to true.
    • RestartAppOnEndSession: Restarts the Kiosk app on each end session to reload the app configs.
    • ShowURLBar: Displays (true) or hides (false) the browser’s URL bar.
    • ShowEndSessionButton: Display (true) or hides (false) the end session button.
    • ServerAddress: Target server address (for dedicated environments).

Configuring Server Address:

The IDmelon Kiosk app allows you to specify the target server address using the ServerAddress tag in the configuration file. By default, it connects to the IDmelon server. If you need to connect to a dedicated environment, follow these steps:

  • Locate the ServerAddress tag in the config file. By default, it looks like this:
<ServerAddress env="prod" />
  • To connect the app to a custom server (dedicated environments), modify the attributes as follows:
<ServerAddress env="onpremise" base-api="https://sub.domain.com/api/url" />

Weblogin Extension Configuration:

If the Weblogin Extension is enabled in the kiosk configuration, you can also save the extension configuration as a JSON file next to the configs.xml.

{
    "handlePasskeyRequests": {
        "value": true
    },
    "allowAddingNewPasswords": {
        "value": true
    },
    "allowPasswordUpdatePrompts": {
        "value": true
    },
    "useEmbeddedNumpad": {
        "value": false
    },
    "keystroking": {
        "value": true
    }
}

Save this JSON string as extension_configs.json in the following path:

    C:\Users\kioskUser0\AppData\Local\Packages\Hellokey.45853B8ADE74A_kxcedb3gts26c\LocalState

Manually using Command-Line Arguments

Follow these steps to modify the app’s settings directly through the command prompt.

  1. Access the Command Prompt You can change the app configs by entering this command in a PowerShell:

    Start-Process 'shell:appsFolder\Hellokey.45853B8ADE74A_kxcedb3gts26c!App' -ArgumentList '-arg1 value1 -arg2 value2'

  2. Available Command-Line Arguments The IDmelon Kiosk app accepts several command-line arguments that allow you to customize its behavior:

    • -url: Specifies the URL for the kiosk to load on startup.
      • Usage: -url https://example.com
    • -selfservice: Set it true if the -url is a custom url.
      • Usage: -selfservice <true|false>
    • -multitab: Enables or disables multi-tab mode.
      • Usage: -multitab <true|false>
    • -extension: Enables or disables browser extensions.
      • Usage: -extension <true|false>
    • -confirm: Enables or disables the end session confirmation prompt.
      • Usage: -confirm <true|false>
    • -urlbar: Shows or hides the URL bar in the browser.
      • Usage: -urlbar <true|false>
    • -endsession: Shows or hides the end session button.
      • Usage: -endsession <true|false>
    • -serveraddress: Target server address for dedicated environments.
      • Usage: -serveraddress https://sub.domain.com/api/url

Automatic by Intune using Configurator.exe

Follow these steps to deploy the configs.xml file on devices.

  1. Make Intune Package file

    • Download this zip file and extract it.
    • Go to IntunePackage folder, and edit the configs.xml file according to your requirements. IntunePackage ConfigsFile
    • In the root path open the package.bat file via a Command Line Prompt. PackageBat
    • If successful, a file named configurator.intunewin will be created in the root path. IntuneWinFile

  2. Deploy Intune Package

    • In the Intune panel, select Apps > All apps.

    • Click on + Create at the top of the screen.

    • From the dropdown, select Windows app (Win32).

    • Click on select app package file and upload the configurator.intunewin file.

    • Set publisher to “IDmelon” and then Next.

    • Enter the command below for both Install command and Uninstall command:

      configurator.exe /S

    • Set the Allow available uninstall to No.

    • Set the Install behavior to System.

    • Set the Device restart behavior to No specific action. Configurator - Program Settings

    • Click Next to see the Requirements tab.

    • Choose both architectures for the Operating system architecture.

    • Select the minimum Windows version required for the app to run. Configurator - Program Settings

    • Use Next to see the Detection rules tab.

    • Select the Use a custom detection script for the Rules format.

    • Click the upload button to choose detect.ps1 script file. DetectScript DetectScript

    • Click Next now and move to the Assignments tab.

    • Assign the app to same groups of users or devices that the IDmelon Kiosk App has been deployed to. DetectScript

    • Click Next to review and create the deployment.

    Note After the Configurator app is successfully deployed, you may still need to restart your PC to apply the changes. This is because the IDmelon Kiosk App loads the new configuration only when it runs for the first time.

Automatic using script

Below script can be used to copy the config.xml files to any Kiosk user profile.

# Define the source file to copy
$sourceFile = "C:\KioskProfile\configs.xml"  # Update this to the path of the file you want to copy

# Define the base path for user profiles & get all user directories that start with "kioskUser0"
$profilesPath = "C:\Users"
$kioskUserDirectories = Get-ChildItem -Path $profilesPath -Directory -Filter "kioskUser0*"

# Loop through each kioskUser0 directory
foreach ($userDir in $kioskUserDirectories) {
    # Define the target directory for this user
    $targetDirectory = Join-Path -Path $userDir.FullName -ChildPath "AppData\Local\Packages\Hellokey.45853B8ADE74A_kxcedb3gts26c\LocalState"

    # Create the target directory if it doesn't exist
    if (-not (Test-Path -Path $targetDirectory)) {
        New-Item -Path $targetDirectory -ItemType Directory | Out-Null
        Write-Host "Created directory for user $($userDir.Name) at: $targetDirectory"
    }

    # Define the target file path
    $targetFile = Join-Path -Path $targetDirectory -ChildPath (Split-Path -Path $sourceFile -Leaf)

    # Copy the file
    try {
        Copy-Item -Path $sourceFile -Destination $targetFile -Force
        Write-Host "File copied successfully for user $($userDir.Name) to: $targetFile"
    } catch {
        Write-Host "Failed to copy file for user $($userDir.Name): $_"
    }
}

Automatic using IDmelon Accesskey

Starting with Accesskey version 3.9.0, you can set the kiosk configuration in base64 format:

To convert the configs.xml to a base64 string, enter the following command in a PowerShell:

[Convert]::ToBase64String([System.Text.Encoding]::UTF8.GetBytes((Get-Content -Raw -Path "configs.xml"))) > "output.txt"

Replace the content of the file output.txt in the following command:

accesskeycli kiosk -s -c [Base64-String]

You can also do the above steps for the Weblogin Extension configs:

[Convert]::ToBase64String([System.Text.Encoding]::UTF8.GetBytes((Get-Content -Raw -Path "configs.json"))) > "output.txt"

accesskeycli kiosk -s -c [Kiosk-Configs-Base64-String] -e [Extension-Configs-Base64-String]

Step 4: Configure the Automation Workflow (Optional)

Run the below command in either Command Prompt or PowerShell to configure login-logout flow for Microsoft.

With Command Prompt:

accesskeycli workflow-automation -s -t weblogin-extension -a login-logout -u https://myapps.microsoft.com?login_hint=${UserId} -m passkey

With PowerShell:

accesskeycli workflow-automation -s -t weblogin-extension -a login-logout -u https://myapps.microsoft.com?login_hint='${UserId}' -m passkey

Note: Since the login_hint attribute is passed as a parameter, PowerShell requires the ${} syntax to be enclosed in single quotes, like ‘${UserId}’.

Step 5: Set the Self-Service URL (Optional)

If you have set up Self-Service settings in the IDmelon Admin Panel, enter the following command in a PowerShell:

accesskeycli self-service-link -s [Self-Service URL]

By executing this command, the system will automatically handle specific user scenarios.
If the user’s badge is not enrolled, they will be redirected to the designated enrollment page. Similarly, if the user exceeds the allowed number of incorrect PIN attempts, they will be automatically directed to the specified address for a PIN reset.

Edit this page on GitHub
×