Brief Overview

Mass deployment installs the WalkMe User Extension on every computer in your organization from the backend, with no action needed from end users. This minimizes the chance that anyone ends up without WalkMe.

Deployment uses MSI/PKG/mobile config files, configuration settings, and your software management system. GPO and SCCM are the most common, but WalkMe also supports G-suite, Intune, Jamf, Altiris, and others (see the supported management tools below).

Every deployment completes three stages. Most issues in the troubleshooting sections below trace back to one of them being incomplete:

1. Installation: The extension package is deployed, placing the extension in the browser
2. Configuration: The extension is pointed to your WalkMe account, using registry keys, browser profile settings, or configuration files. On 64-bit Windows machines, configure the registry key for both 32-bit and 64-bit. On 32-bit machines, only the 32-bit MSI and registry key are needed. This stage is required without it, the extension appears in the browser but doesn't load WalkMe.
3. Enabling: The extension is enabled in the browser. If a WalkMe extension already exists on the machine, uninstall it before deploying the new one

Access

To access Mass Deployment Wizard in the console:

1. Open the WalkMe Console:
   • US-Rechenzentrum
   • EU-Datenzentrum
   • SAP US Data Center
   • SAP EU Data Center
   • FedRAMP-Rechenzentrum
   • Kanada-Rechenzentrum
2. Select Admin category
3. Select My Account
4. Go to Extension Installation
5. Choose the Mass Deployment Wizard tab

How It Works

From the Mass Deployment Wizard tab follow these instructions:

1. Select the operating system (Windows, macOS, or Linux)
2. Select the browser to install the extension on
3. Select the engine, for example GPO, SCCM, G-suite, or Intune
4. Complete any extra options for that engine. For example, Windows + Chrome + Intune asks for the Intune installation type, and macOS + Safari + Jamf (macOS 11 or newer) asks for the installation method
5. If your extension is set up as a Unique Extension, answer Remove WalkMe store extension:
   • Yes: A Store version of the User Extension is already installed. The guide includes steps to remove it before installing the new extension
   • No: No User Extension is installed (neither Store nor Unique). The guide includes installation steps only
6. Select Generate Mass Deployment Guide and follow the step-by-step instructions.
   

Which operating systems, browsers, and management tools are supported?

Mass deployment supports Chrome, Edge (Chromium), Firefox, Safari, and Internet Explorer 11 across five operating systems:

• Google Chrome
  • Windows - Yes
  • MacOs - Yes
  • Linux - Yes
  • iOS - No
  • Android - No
• Microsoft Edge (Chromium)
  • Windows - Yes
  • MacOs - Yes
  • Linux - No
  • iOS - Yes
  • Android - Yes
• Mozilla Firefox
  • Windows - Yes
  • MacOs - Yes
  • Linux - No
  • iOS - No
  • Android - No
• Apple Safari
  • Windows - No
  • MacOs - Yes
  • Linux - No
  • iOS - Yes
  • Android - No
• Internet Explorer 11
  • Windows - No
  • MacOs - No
  • Linux - No
  • iOS - No
  • Android - No

Supported management tools (MDMs)

• Windows:
  • GPO
  • SCCM
  • G-suite
  • Intune (Extension Force Install List, Extension Settings, Devices)
• MacOS:
  • Altiris
  • Jamf
  • G-suite
  • Intune (Devices)
  • Legacy
• Linux:
  • CF-engine
  • G-suite
• iOS:
  • Intune
  • Jamf
• Android:
  • Intune

Test Your Deployment

Force the policy to apply, then confirm WalkMe loads with a quick console check.

Step 1: Apply the policy right away (Windows with GPO)

Policies can take time to reach machines. To apply them immediately on a test machine:

1. Open Command Prompt as an administrator
2. Run gpupdate /force
3. Wait for confirmation that a new policy was found and enforced
4. Restart the machine

After the restart, the extension should appear in every browser you deployed to.

Step 2: Check that WalkMe loads

If your WalkMe content doesn't appear on your website after deployment, run this quick test:

1. On a machine the extension was deployed to, open the website where WalkMe content should play
2. Press F12 to open the browser developer tools
3. Go to the Console tab
4. Type the following into the Console input:

   • _walkmeInternals

5. Press Enter

What the results mean:

• ✅No error: The extension deployment is working correctly, as long as WalkMe wasn't already on the site without the extension. Any remaining issue is unrelated to the deployment itself.
• ❌Red error: The extension isn't working properly. Use the troubleshooting sections below for your operating system and browser. If they don't resolve it, contact WalkMe Support.

Troubleshooting on Windows

Most Windows issues come from an incomplete Installation or Configuration stage, a registry conflict with another extension, or blocked network domains

Chrome

The extension does not show in the browser.

1. Confirm that the Installation step in the guide has been completed. Both the GPO and SCCM methods result in a registry key being placed in the HKEY_LOCAL_MACHINE → SOFTWARE → Policies → Google → Chrome → ExtensionInstallForcelist 
2. Open Regedit on the affected user's machine and look for the WalkMe entry in that location  
3. Check for a conflict with another force-installed Chrome extension. If another extension's entry in the same ExtensionInstallForcelist key has the same name (for example, both are named "1" or "2"), only one extension will show. Rename one of the entries so each name is unique.
4. If another Chrome extension was mass deployed in the HKEY_CURRENT_USER hive, deploy both WalkMe registry keys (Installation and Configuration) in HKEY_CURRENT_USER as well.

The extension shows in the browser, but WalkMe doesn't load on the site.

1. Confirm the Configuration step has been completed - this step is required the extension cant work without it.
2. In Regedit, go to:
   • HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftEdge3rdpartyextensionsiffnipbkkgbgeffippbaldmgdpealpddpolicy and confirm the wmExtConfig value and data match the Mass Deployment Guide exactly.
3. Ask your IT team to confirm the domains in WalkMe Access Requirements are allowlisted both for your network and proxy. Check www.whatismyproxy.com if you are not sure if you have a proxy.

Access Requirements for WalkMe

Edge (Chromium)

The extension does not show in the browser.

1. Confirm the Installation step in the guide is complete. Both GPO and SCCM place a registry key in HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftEdgeExtensionInstallForcelist 
2. Open Regedit on the affected user's machine and look for the WalkMe entry in that location.
3. Check for a conflict with another force-installed Edge extension. If another extension's entry in the same ExtensionInstallForcelist key has the same name (for example, both are named "1" or "2"), only one extension will show. Rename one of the entries so each name is unique.
4. If another Edge extension was mass deployed in the HKEY_CURRENT_USER hive, deploy both WalkMe registry keys (Installation and Configuration) in HKEY_CURRENT_USER as well.

The extension shows in the browser, but WalkMe doesn't load on the site.

1. Confirm the Configuration step is complete. This step is required: the extension can't work without it.
2. In Regedit, go to HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftEdge3rdpartyextensionsiffnipbkkgbgeffippbaldmgdpealpddpolicy and confirm the wmExtConfig value and data match the Mass Deployment Guide exactly.
3. Ask your IT team to confirm the domains in WalkMe Access Requirements are allowlisted for both your network and your proxy. If you're not sure whether you use a proxy, check www.whatismyproxy.com.

Firefox

If any of the files below are missing, the installation script wm_firefox_enterprise_installation.bat did not run successfully.

• On all machines, check for:
  • C:Program FilesWalkMeWalkmeExtension@walkme.com.xpi
  • C:Program FilesWalkMeExtensionWalkmeExtension@walkme.com.json
  • ~AppDataRoamingMozillaFirefoxProfiles[each profile]extensionsWalkmeExtension@walkme.com.xpi
• On 64-bit machines, also check for:
  • C:Program FilesMozilla
  • FirefoxdistributionextensionsWalkmeExtension@walkme.com.xpi
  • C:Program FilesMozilla Firefoxbrowserdefaultspreferencesall-walkme.js
• On 32-bit machines, also check for:
  • C:Program Files (x86)Mozilla
  • FirefoxdistributionextensionsWalkmeExtension@walkme.com.xpi
  • C:Program Files (x86)Mozilla Firefoxbrowserdefaultspreferencesall-walkme.js

Then confirm this registry key exists at HKEY_LOCAL_MACHINESOFTWAREMozillaManagedStorageWalkmeExtension@walkme.com.json:

• Value name: Default
• Value type: REG_SZ
• Value data: C:Program FilesWalkMeExtensionWalkmeExtension@walkme.com.json

Finally, ask your IT team to confirm the domains in WalkMe Access Requirements are allowlisted for both your network and your proxy.  If you're not sure whether you use a proxy, check www.whatismyproxy.com.

Troubleshooting on Mac

On Mac, most issues come from missing extension or configuration files, or from a configuration profile that didn't install.

Safari

The extension does not show in the browser.

Confirm these folders exist. If they don't, the installation script did not run successfully:

• ~/Library/Containers/com.walkme.safariAppExtension/Data
• ~/Library/Containers/com.walkme.safariAppExtension.WalkMeExtension/Data

The extension shows in the browser, but WalkMe doesn't load on the site.

Confirm these configuration files exist:

• ~/Library/Containers/com.walkme.safariAppExtension/Data/wmExtensionConfig.json
• ~/Library/Containers/com.walkme.safariAppExtension.WalkMeExtension/Data/wmExtensionConfig.json

Firefox

Confirm these files exist. If they don't, the installation script did not run successfully.

• /Applications/Firefox.app/Contents/Resources/distribution/extensions/WalkmeExtension@walkme.com.xpi
• /Applications/Firefox.app/Contents/Resources/browser/defaults/preferences/all-walkme.js
• ~/Library/Application Support/Firefox/Profiles/[each profile]/extensions/WalkmeExtension@walkme.com.xpi
• ~/Library/Application Support/Firefox/Profiles/[each profile]/extensions/all-walkme.js
• /Library/Application Support/Mozilla/ManagedStorage/WalkmeExtension@walkme.com.json

Chrome

The extension does not show in the browser.

The Mac guide installs the extension with a mobileconfig profile placed on the device. To confirm it installed:

1. Open System Settings and go to Privacy & Security > Profiles
2. Find the mobileconfig profile you deployed. The default names are "Chrome" or "WalkMe Chrome Extension"
3. Double-click the profile and go to Details > Custom Settings > com.google.Chrome.
4. Confirm the WalkMe extension is listed as a forced extension.

Extension Corruption After Install?

If you see the error below, the extension was corrupted after installation.

• To fix it now: Uninstall the WalkMe extension and reinstall it. This resolves the issue immediately.
• To prevent it in virtual environments: Make sure %LocalAppData%GoogleChromeUser DataDefaultExtensions is backed up between user sessions.