Deploy the desktop app (admin)

View summary

To prevent users from installing applications, make the appropriate security changes to user workstations. 

To remove Check for Updates from the desktop app menu and prevent users from receiving desktop app update notifications, make the following registry/preference value changes.

Windows

You can change either of the following registry keys:

• HKEY_CURRENT_USER\Software\Interactive Intelligence\Purecloud\Directory
• HKEY_LOCAL_MACHINE\Software\Interactive Intelligence\Purecloud\Directory

Add a new DWORD value called DisableUpdates, and set to 1 to prevent all updates.

Example: 

"DisableUpdates"=dword:00000001

Mac

In the preferences file ~/Library/Preferences/com.inin.purecloud.directory.plist, add a new Boolean value called “DisableUpdates”, and set to true to prevent all updates. 

Example: 

<key>DisableUpdates</key>

<true/>

Routinely use a third-party tool to check the appcast XML file and notify you when an updated desktop app release version is available.

Windows

https://apps.mypurecloud.com/directory-windows/appcast.xml

Mac

https://apps.mypurecloud.com/directory-mac/appcast.xml

To push out the desktop app installation and updates, use a third-party software deployment tool such as Microsoft System Center Configuration Manager (SCCM). This tool can deploy the app to users on specified days and times.

To preconfigure a default region, apply the region key and URL from the following table:

Windows

Preconfigure these registry entries to a particular region using the previous table:

• HKEY_CURRENT_USER\Software\Interactive Intelligence\Purecloud\Directory\Region
• HKEY_CURRENT_USER\Software\Interactive Intelligence\Purecloud\Directory\RegionURL

For example, to preconfigure the Frankfurt region, add a registry entry for key HKEY_CURRENT_USER\Software\Interactive Intelligence\Purecloud\Directory\Region and set it to the string de, and add a registry entry for key HKEY_CURRENT_USER\Software\Interactive Intelligence\Purecloud\Directory\RegionURL and set it to the string https://apps.mypurecloud.de/directory.

Mac

Use the following default commands:

• > defaults write com.inin.purecloud.directory region 
• > defaults write com.inin.purecloud.directory regionURL

Example:

C:\Users\Administrator\Desktop>genesys-cloud-windows-2.1.582.exe /quiet

On September 30, 2020, the desktop app name changed from PureCloud to Genesys Cloud. The installation path and executable names have changed. Registry locations and keys have not changed.

Old: C:\Program Files (x86)\Interactive Intelligence\PureCloud\PureCloud.exe

New: C:\Program Files (x86)\Genesys\GenesysCloud\GenesysCloud.exe

To force the desktop app client to run as a WebRTC Media Helper, make the following registry/preference value changes.

Windows

In the registry key HKEY_CURRENT_USER\Software\Interactive Intelligence\Purecloud\Directory, add a new DWORD value called “RunAsMediaHelper”, and set to 1 to make active. 

Example: 

"RunAsMediaHelper"=dword:00000001

Mac

In the preferences file ~/Library/Preferences/com.inin.purecloud.directory.plist, add a new Boolean value called “runAsMediaHelper”, and set to true to make it active. 

Example: 

<key>runAsMediaHelper</key>

<true/>

For more information, see About WebRTC Media Helper.

To force the installation to ignore WebRTC softphone events, make the following registry/preference value changes:

Windows

You can change either of the following registry keys:

• HKEY_CURRENT_USER\Software\Interactive Intelligence\Purecloud\Directory
• HKEY_LOCAL_MACHINE\Software\Interactive Intelligence\Purecloud\Directory

Add a new REG_SZ value called “DevUrl”, and set to “https://apps.mypurecloud.com/directory/?disableSoftphone=true” where apps.mypurecloud.com is your org’s home region.

The Windows desktop app, by default, includes functionality based on Microsoft’s CloudAP feature to streamline authentication in some SSO configurations. If your organization does not want to enable this functionality, you can change either of the following registry keys:

• HKEY_CURRENT_USER\Software\Interactive Intelligence\Purecloud\Directory
• HKEY_LOCAL_MACHINE\Software\Interactive Intelligence\Purecloud\Directory

Add a new DWORD value called “DisableMicrosoftCloudAP”, and set to 1 to disable the feature.

The desktop app uses the browser’s Local Network Access (LNA) rules: pages from a given origin can only reach private or local addresses (e.g., localhost, RFC 1918) if the origin is allowed. Genesys Cloud origins (e.g. https://apps.mypurecloud.com, your region’s apps URL) are always allowed. For any other origin, the app checks an administrator-defined allow list. If the requesting origin matches a pattern in the allow list, local network access is granted; otherwise it is denied.

Typical use case

SSO or device-trust solutions (e.g., Okta Fastpass, device binding) load content from a public origin (for example, https://your-org.okta.com) and must talk to a local endpoint (localhost or private IP). Adding the origin, or a pattern, to the allowlist allows the request to continue. If not in the allowlist, the request is blocked.

Patterns follow Chrome Enterprise URL pattern syntax. For more information about Chrome Enterprise URL pattern syntax, see Chrome URL patterns.

Examples:

• *: Allow all. Use with caution.
• [*.]okta.com: Allow okta.com and any subdomains.
• https://your-org.okta.com:*: Allow this host with any port.
• https://your-org.okta.com:443: Allow this host and this port.
  Notes:

  • Scheme and host are compared case-insensitively.
  • Omitted port in a pattern means default port only.
  • An asterisk (*) means any port.
  • The policy is read once at first use; restart the desktop app after you change the allowlist.

Windows

Use the same key as other desktop app settings:

• HKEY_LOCAL_MACHINE or HKEY_CURRENT_USER
Software\Policies\Genesys\GenesysCloud\LocalNetworkAccessAllowedForUrls

Create REG_SZ values whose names are integers (1, 2, 3, …). The data of each value is one URL pattern.

Example (Okta Fastpass):

Name: 1 → Data: "[*.]okta.com"
Name: 2 → Data: "https://your-org.okta.com"

Mac

Domain: com.inin.purecloud.directory
Key: LocalNetworkAccessAllowedForUrls (array of strings)

Example using defaults write (patterns with [or] need single quotes inside double quotes so that the shell does not interpret them):

defaults write com.inin.purecloud.directory LocalNetworkAccessAllowedForUrls -array "'[*.]okta.com'" "https://your-org.okta.com"

Single pattern:

defaults write com.inin.purecloud.directory LocalNetworkAccessAllowedForUrls -array "'[*.]okta.com'"

If the key exists and you want to add more patterns, use PlistBuddy or edit the plist directly; defaults write replaces the entire array. Restart the desktop app after changing the allow list.

The desktop app uses the Chromium Embedded Framework (CEF), which can run with the GPU process enabled or disabled. By default, the app starts with the GPU disabled (software rendering). On some computers, enabling the GPU can improve performance or fix display issues; on others, disabling it avoids GPU-related crashes or compatibility problems.

You can override the default by adding a registry value so that the app either keeps the GPU disabled (default) or enables it.

Windows

Use the same key as other desktop app settings:

• HKEY_LOCAL_MACHINE or HKEY_CURRENT_USER
Software\Interactive Intelligence\Purecloud\Directory

Add a DWORD value named DisableGpu:

• DisableGpu = 1: GPU is disabled. The app passes Chromium the flags --disable-gpu and --disable-software-rasterizer. This value is the default if the value is missing.
• DisableGpu = 0: GPU is enabled. The app does not add the flags mentioned previously; thus Chromium may use the GPU process.

If the value exists in both HKLM and HKCU, the app follows the same precedence as other settings, typically HKLM over HKCU for machine-wide policy.

Example (enable the GPU):

"DisableGpu"=dword:00000000

Example (disable the GPU explicitly):

"DisableGpu"=dword:00000001

For changes to take effect, restart the desktop app.

The desktop app uses Chromium’s WebRTC stack, which can apply automatic gain control (AGC) to the microphone input. In some environments this feature can lower the mic level inappropriately (e.g., quiet or inconsistent volume). Administrators can disable this behavior so that the app does not automatically adjust input volume.

Windows

Use the same key as other desktop app settings:

• HKEY_LOCAL_MACHINE or HKEY_CURRENT_USER
Software\Interactive Intelligence\Purecloud\Directory

Add a DWORD value named DisableInputVolumeAdjustment:

• DisableInputVolumeAdjustment = 0: Automatic input volume adjustment is enabled (normal WebRTC AGC behavior). This value is the default if the value is missing.
• DisableInputVolumeAdjustment = 1: Automatic input volume adjustment is disabled. The app passes Chromium the flag to disable the WebRtcAllowInputVolumeAdjustment feature so that the mic level is not automatically lowered.

If the value exists in both HKLM and HKCU, the app follows the same precedence as other settings, typically HKLM over HKCU for machine-wide policy.

Example (disable automatic mic gain control):

"DisableInputVolumeAdjustment"=dword:00000001

Example (re-enable, use default behavior):

"DisableInputVolumeAdjustment"=dword:00000000

For changes to take effect, restart the desktop app.