URL Content Redirection supports a custom user data directory path on Windows platform, such as the roaming application data folder %APPDATA%.
This is supported for Google Chrome and Microsoft Edge Chromium for Windows Agent and Windows Client. RDSH Application mode is also supported. For Firefox, the URL extension is already installed under the roaming application data folder by default.
User Data Directory Setting
A custom user data directory path can be configured using a Chrome/Edge GPO. If it is not configured, the extension is always installed under the local application data folder %LOCALAPPDATA% by default.
Google Chrome Setting
- Add the Chrome browser policy template:
- Download the appropriate Google Chrome policy templates file from https://chromeenterprise.google/browser/download/#manage-policies-tab and extract the contents.
- Copy the chrome.admx files to your Policy Definition template folder.
- In the admx folder, open the appropriate language folder. For example, if you’re in the U.S., open the en-US folder.
- Copy the chrome.adml file to the matching language folder in your Policy Definition folder.
- Open the Group Policy Management Editor from Windows Administrative Tools to confirm the files loaded correctly.
- Set policies:
- Open Group Policy and navigate to .
- Find and open the policy Set user data directory.
- Choose an option:
Option Description Enabled Configures the directory that Google Chrome uses for storing user data. Disabled Prevents the policy from affecting Chrome browser. Not Configured Resets the policy to its default.
Group Policy name | Set user data directory |
Group Policy path (Mandatory) | Administrative Templates/Google Chrome/ This GPO is enabled in both User and Computer Configuration, with Computer Configuration having higher priority. |
Group Policy ADMX file name | chrome.admx |
Path (Mandatory) | SOFTWARE\Policies\Google\Chrome |
Value Name | UserDataDir |
Value Type | REG_SZ |
Priority | HKLM > HKCU |
Microsoft Edge Setting
- Add the Chrome browser policy template:
- Download the appropriate Microsoft Edge policy templates file from https://www.microsoft.com/en-us/edge/business/download and extract the contents.
- Copy the msedge.admx files to your Policy Definition template folder.
- In the admx folder, open the appropriate language folder. For example, if you’re in the U.S., open the en-US folder.
- Copy the msedge.adml file to the matching language folder in your Policy Definition folder.
- Open Group Policy Management Editor from Windows Administrative Tools to confirm the files loaded correctly.
- Set policies:
- Open Group Policy and navigate to .
- Find and open the policy Set the user data directory.
- Choose an option:
Option Description Enabled Configures the directory that Microsoft Edge uses for storing user data. Disabled Prevents the policy from affecting Microsoft Edge. Not Configured Resets the policy to its default.
Group Policy unique name | UserDataDir |
Group Policy name | Set user data directory |
Group Policy path (Mandatory) | Administrative Templates/Microsoft Edge/ This GPO is enabled in both User and Computer Configuration, with Computer Configuration having higher priority. |
Group Policy ADMX file name | MSEdge.admx |
Path (Mandatory) | SOFTWARE\Policies\Microsoft\Edge |
Value Name | UserDataDir |
Value Type | REG_SZ |
Priority | HKLM > HKCU |
Supported Directory Path Variables for Windows
Variable | Description |
---|---|
${user_name} | The user who is using Google Chrome/Microsoft Edge. |
${machine_name} | The machine name, possibly including the domain name. |
${documents} | The Documents folder for the current user. |
${local_app_data} | The Application Data folder for the current user. |
${roaming_app_data} | The Roaming Application Data folder for the current user. |
${profile} | The home folder for the current user. |
${global_app_data} | The system-wide Application Data folder. |
${program_files} | The Program Files folder for the current process. This folder depends on whether it's a 32-bit or 64-bit process. |
${windows} | The Windows folder. |
${client_name} | This variable is empty if it's used from a local session. If it's used in a path, prefix it with something that's guaranteed not to be empty. |
${session_name} | The name of the active session. Use this name to distinguish among multiple simultaneously connected remote sessions that are using a single user profile. |