Mass Deployment FAQ

Updated on July 3, 2019 Download PDFDownload as PDF
Download PDF

Please note: This FAQ should be used by IT admins who are in the process of deploying the WalkMe extension using the Mass Deployment guide provided to them by their WalkMe contact. Please ensure you’ve reviewed the Mass Deployment Project Scope before proceeding.

Brief Overview

After deployment, you may run into issues getting your WalkMe content to appear on your website. As a very quick test, try following these steps:

  1. On a machine you’ve deployed the extension to, go to the website that should be showing the WalkMe content
  2. Hit F12 to open the browser developer tools
  3. Go to the Console tab
  4. Type this into the Console input and hit enter: _walkmeInternals

If you do not receive a red error in the console, (and WalkMe didn’t already exist on the page without the extension) this means the extension deployment is working correctly, and any other issues seeing the WalkMe content are unrelated to the actual deployment.

If a red error did occur, it means the extension is not functioning properly. Here are a few common suggestions that can fix a problem with your deployment. If trying the below does not result in your WalkMe content showing, please open a ticket to support@walkme.com

Windows

Chrome

  1. The extension does not show in the browser
    1. Confirm that the Installation step in the guide has been completed
    2. Both the GPO and SCCM methods result in a registry key being placed in the HKEY_LOCAL_MACHINE→SOFTWARE→Policies→Google→Chrome→ExtensionInstallForcelist location. This can be confirmed by opening Regedit on the affected user’s machine and looking for an entry like this: 
    3. It’s possible a different Chrome extension has already been deployed by your organization in this manner. If the entry for this other extension is in the same  ExtensionInstallForcelist registry key and has the same Name (for example, both named “1” or “2”) the extensions will conflict and only one of them will show. If this happens, make sure to change the Name for one of the extensions, as they must be unique.
    4. It’s possible a different Chrome extension was already mass deployed in the HKEY_CURRENT_USER hive. If this is the case, try deploying both registry keys for the WalkMe extension (for the Installation and Configuration steps) in the HKEY_CURRENT_USER hive as well.
  2. The extension shows in the browser but is not loading WalkMe on the relevant site
    1. Confirm the Configuration step has been completed – this is not optional and will prevent the extension from functioning if not completed.
    2. In Regedit, go to this location, and confirm the wmExtConfig value and data are there exactly as they appear in the mass deployment guide (this is the Configuration step): HKEY_LOCAL_MACHINE→SOFTWARE→Policies→Google→Chrome→3rdparty→extensions→iffnipbkkgbgeffippbaldmgdpealpdd→policy
    3. Check with your IT team and confirm the domains listed here are whitelisted both for your network and proxy. Check www.whatismyproxy.com if you are not sure if you have a proxy.

Firefox

  1. Make sure the following locations contain these files. If they’re not there, the installation script wm_firefox_enterprise_installation.bat did not run successfully:
    1. C:→Program Files→Walkme – WalkmeExtension@walkme.com.xpi
    2. C:→Program Files→WalkMe→Extension – WalkmeExtension@walkme.com.json
    3. ~→AppData→Roaming→Mozilla→Firefox→Profiles→[every profile in this directory]→Extensions – WalkmeExtension@walkme.com.xpi
    4. For 64-bit machines:
      1. C:→Program Files→Mozilla Firefox→distribution→extensions – WalkmeExtension@walkme.com.xpi
      2. C:→Program Files→Mozilla Firefox→browser→defaults→preferences – all-walkme.js
    5. For 32-bit machines:
      1. C:→Program Files (x86)→Mozilla Firefox→distribution→extensions – WalkmeExtension@walkme.com.xpi
      2. C:→Program Files (x86)→Mozilla Firefox→browser→defaults→preferences – all-walkme.js
  2. Verify that this registry key is present:
    1. HKEY_LOCAL_MACHINE→SOFTWARE→Mozilla→ManagedStorage→WalkmeExtension@walkme.com.json
    2. Value Name: Default
    3. Value Type: REG_SZ
    4. Value Data: C:→Program Files→WalkMe→Extension→WalkmeExtension@walkme.com.json
  3. Check with your IT team and confirm the domains listed here are whitelisted both for your network and proxy. Check www.whatismyproxy.com if you are not sure if you have a proxy.

IE

  1. The extension does not show in IE’s Manage add-ons section:
    1. Confirm that the relevant MSI file(s) has been deployed and installed on the machines (just the 32 file for 32-bit machines, both 32 and 64 files for 64-bit machines):
      1. https://cdn.walkme.com/extension/atl/Walkme_Extension.x32.msi
      2. https://cdn.walkme.com/extension/atl/Walkme_Extension.x64.msi
  2. The extension shows in Manage add-ons, but WalkMe content does not show on site:
    1. Verify that both registry keys in the Config page of the mass deployment guide are in the machine’s registry – this is not optional and will prevent the extension from functioning if not completed.
    2. On the customer’s machine, open regedit, go to these locations inside either HKEY_LOCAL_MACHINE or HKEY_CURRENT_USER (whichever one the deployment has been set for), and confirm the wmExtConfig value and data are there exactly as they appear in the mass deployment guide (this is the Config step):
      1. SOFTWARE→WalkMe→WalkMeExtension
      2. SOFTWARE→Wow6432Node→WalkMe→WalkMeExtension
    3. If you are installing the registry keys via the SCCM .reg files, ensure that once the keys are in the registry that the values do not have backslashes before the quotation marks – these should only exist in the .reg files themselves, but not in the actual keys themselves once they’ve been deployed
    4. Make sure that the Enable third-party browser extensions setting in IE’s Internet Options Advanced tab are checked.
    5. Check with your IT team and confirm the domains listed here are whitelisted both for your network and proxy. Check www.whatismyproxy.com if you are not sure if you have a proxy.

Was this article helpful?

Related Articles