Citrix receiver 4.9 for windows 10 64 bit free
Receiver for Windows, LTSR Cumulative Update 9. Release Date: Jun 22, Compatible with. Windows 10, , 7, R2, Thin PC as well as Windows. Downloads / Citrix Receiver / Receiver for Windows LTSR. Find. Filter [on]. Find Downloads. Select a product Citrix ADC, Citrix Analytics.
Download Receiver for Windows LTSR – Citrix – Download Receiver for Windows – Citrix.
Windows 10, , 7, R2, Thin PC as well as Windows Server , , and R2. Download Receiver for Windows Download Receiver for Windows. Location: HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\ICA Client Name: VdLoadUnLoadTimeOut. Type: REG_DWORD Data: Any value in seconds (Decimal). On bit Windows. bit Windows Location: HKLM\Software\WowNode\Citrix\Dazzle Name: RefreshMs. Type: REG_SZ Value: Name: InitialRefreshMinMs.
Citrix receiver 4.9 for windows 10 64 bit free
View all products. Buy Citrix products, request a quote, or learn more about our products and subscriptions. Citrix Workspace app is the easy-to-install client software that provides seamless secure access to everything you need to get work done. View all resources. Get the white paper. Get the report.
Get expert guidance, resources, and step-by-step instructions to navigate your path to the cloud. Learn about planning, deployment, and management of Citrix solutions, so you can maximize the value of your investment. Read the article. Manage licenses Renew maintenance. Compatible with Windows 10, 8. Open the web. Please review the product documentation for the complete list of fixed issues and known issues.
High performance access to Windows virtual apps and desktops, anywhere access from your desktop, start menu, Receiver UI or web access with Chrome, Internet Explorer or Firefox. Citrix Receiver can be used on domain and non-domain joined PCs, tablets, and thin clients. Provides high performance use of virtualized Skype for Business, line of business and HDX 3D Pro engineering apps, multimedia, local app access. It is an optional download, provided on an as-is basis by Citrix to serve as an example.
Before use, IT administrators must customize the scripts to suit their environment. Please see the product documentation for instructions on using this admin tool. Please see the product documentation for instructions on using this admin tool. The uninstall and install scripts may be used as noted in the upgrade guide for Citrix Receiver for Windows CTX It is an optional download, to be used by IT administrators, and not meant for use by end-users.
Yes, I accept No. Your download will start immediately upon accepting this agreement. You may close this window once your download begins. Solutions Solutions. Digital Workspaces. DaaS and VDI. Secure Access. Application Delivery.
Content Collaboration. Boost Productivity Enable remote work Collaborate securely Enhance user experience. Build your own digital workspace.
Download Citrix Workspace app Citrix Workspace app is the easy-to-install client software that provides seamless secure access to everything you need to get work done. Support Downloads Community. Profile streaming is enabled — speeds up logons. Active Write Back is disabled — places extra load on file servers for not much benefit.
No Start Menu roaming issues — might need ResetCache registry value. No AppData redirection — slows down applications. Folder Redirection file share: File share is highly available. Antivirus is not slowing down folder redirection performance. Antivirus is not slowing down file transfer performance — time how long it takes to copy a Home Directory folder to the local machine. ThinKiosk can lock down Windows 10 endpoints. Browser Content Redirection offloads video e.
Workspace app is periodically e. Workspace app LTSR Receiver 4. EDT protocol aka Adaptive Transport is enabled. In ADC license does not expire any time soon. LOM nsroot password is changed from the default. No VLAN is connected to multiple active interfaces unless those interfaces are in a port channel. ADC nsroot password is not nsroot. Policies are Advanced Expressions instead of Classic Expressions.
LDAP Bind account is a service account — not a regular user whose password expires. No local ADC accounts except nsroot. NTP and Time Zone are configured. Thresholds are configured for CPU and Memory alarms. Management certificate has no certificate errors. Unused network interfaces are disabled. ADC instance is connected to only one security zone — if connected to multiple security zones, then a firewall is bypassed.
Only one default route — extra default routes can come from HA pairing or hardware migration. Installed Licenses are identical on both nodes. Unused interfaces are disabled. HA is synchronizing without error. Fail-safe mode is enabled.
LOM nsroot password is not nsroot. Management authentication is configured for external authentication server, typically LDAP. No local accounts except nsroot. No certificate errors when accessing SVM management using htttps.
NTP is configured and enabled. Syslog is configured. Production instances typically have Dedicated CPU cores. No VMACs in instance interface settings. Monitors do more than just telnet — e. LDAP monitor bind account uses service account, not domain admin.
Horizon Load Balancing. Rewrite policies remove web server header information Server, X-Powered-By, etc. Root certificate is not linked to intermediate certificate. Certificates are not expired. ADM Web Insight is viewed. Bot Management ADM Security Insight is enabled and viewed. ADM firmware version is Every High Availability node and DR node has same disk size. ADM nsroot password is not nsroot. ADM Agent nsrecover password has been changed from the default.
No certificate errors when accessing ADM management using htttps. ADM Database is not full. Sufficient disk space. ADC Restore process is documented and tested. Licenses are assigned to Virtual Servers that need Analytics e.
HDX Insight or Applications tab. License expiration notifications are enabled. Analytics Thresholds are configured — e. ICA Latency threshold. Gateway Virtual Server Maximum Users is 0, which means unlimited. Gateway communication to StoreFront is https protocol, not http. Both factors are required to login.
ADC administrators know how to update the Signing certificate. If Static Proximity: Static Proximity database is current. GSLB Services show correct geo location. Custom Entries are added for internal subnets. This post lists all minor and major changes made to carlstalhood. Some GPO settings e. Blast Clipboard were moved in Horizon 8. Horizon Client Software Updates can now automatically popup an upgrade message when new client is available.
Navigation Workspace app is the new name for Receiver. The newest Workspace app versions contain many Teams optimization enhancements.
Workspace app Modules The Workspace app installer deploys multiple modules. Here are the important ones: ICA Engine wfica. Self-Service selfservice. The most recent name for this component is Citrix Workspace Update. After authentication, Gateway will connect to its configured Account Services address, and download the Provisioning File from StoreFront. See How to configure Receiver to a Store that is not advertised for special syntax. An important value to consider for multi-datacenter configurations.
Once Workspace app is configured, it then performs the following steps: Attempt to connect to the Internal Beacon. If the External Beacons are not reachable, then stop attempting to connect. Connect to the Gateway address configured in the Provisioning File. If there is more than one Gateway, connect to the Gateway that is marked as the Default. The actual connection process is controlled by the contents of the Provisioning File, not the Discovery address.
Here are some additional methods of performing Workspace app Discovery: After exporting the Provisioning File from StoreFront Console, distribute it to users, and ask them to double-click it. After logging in to Receiver for Web StoreFront , at the top right, click the user name, and click Activate. This downloads the receiverconfig. The user then must run the downloaded file. Virtual Monitors In Workspace app and newer, when connected to a published desktop on a single monitor, you can split the screen into virtual monitors.
In the desktop toolbar at the top of the screen, click Preferences. Switch to the Monitor Layout tab. On the bottom, select Horizontal or Vertical , then click somewhere in the blue box to draw a line.
The single monitor will be split along this line. You can set different DPI for each portion of the virtual display. Right-clicking one of the split sections changes that section to the primary display. Click OK when done. In the toolbar, click Window to resize it to a window, and then click Full Screen to cause your virtual monitor configuration to take effect.
Uninstall Old Clients Workspace app and Receiver 4. This includes the Offline Plug-in component if installed. Workspace app and newer do not support Windows 7. Workspace app and newer enable DPI Matching by default. DPI Matching can be disabled through client-side group policy, or in the Advanced Preferences in Workspace app and newer. See CTX for details. Administrator vs non-administrator Non-administrator — If a non-administrator installs Workspace app, then each non-administrator that logs in to the same workstation will have to reinstall Workspace app.
Administrator — If CitrixWorkspaceApp. Administrator installations of Workspace app and newer can be manually upgraded by non-administrators by clicking Check for Updates. Older versions cannot be upgraded by non-administrators. Conflicts — If an administrator install of Workspace app is performed on a machine that has non-administrator installs of Workspace app, then the two installations will conflict.
Best option is to uninstall non-admin Workspace app and Receiver before installing admin Workspace app. Auto-Update Workspace app supports auto-update. Some notes: If Workspace app or newer is installed as administrator, then non-administrators can click Check for Updates to manually update Workspace app. To prevent this, use group policy to disable Citrix Workspace Updates. Older versions of Workspace app cannot be upgraded by non-administrators.
If Workspace app is installed on a VDA, auto-update is automatically disabled. This includes Remote PC. Auto-update can be limited to LTSR updates only. Auto-update is configurable through several mechanisms: group policy, StoreFront, Workspace app GUI, installer command line.
Workspace app and later let users select an Update channel. Rename CitrixWorkspaceApp. Install using a command line switch: CitrixWorkspaceApp. Change Registry values post installation to suppress the Add Account window.
Discover Hidden Stores When Receiver is first launched, it must perform Discovery, which is the process of downloading the. GPO configuration is also required as detailed below. AutoUpdateCheck can also be set to manual or disabled.
AutoUpdateStream can also be set to Current. Give the shortcuts a short name. Set this to create. See the link for details. Local Username and Password — Check the top two boxes. This causes all icons to be placed on the Start Menu. Enable Manage App Shortcut and configure it as desired. To allow the Self-Service window, but prevent it from automatically opening reside in systray , tick Prevent Citrix Workspace or Receiver performing a refresh of the application list when opened.
Source Enable Control when Workspace or Receiver attempts to reconnect to existing sessions. If this is a VDA published desktop, set it to Disabled. Otherwise configure it as desired. Enable automatic client drive and client microphone mapping. See Below for details. Configure the FileSecurityPermission setting in one or more of the regions. From a machine that has Workspace app installed, find the. You can also download the ADMX files from one of the Workspace app download pages Workspace app current release version Copy the CitrixBase.
Also copy the en-US folder. In Workspace app, the files are still named receiver. If one exists, paste the. Workspace app and newer has a setting to Disable sending data to 3rd party e. Google Analytics. Workspace app and newer let you disable embedded browser caching. Citrix Workspace Updates , aka AutoUpdate can be configured using group policy. Workspace app and newer can be configured to require in-memory ICA files only.
Workspace app 4. In XenApp 6. Login to the PC as an administrator. If installing Workspace app , as an administrator, during installation, on the Enable Single Sign-on page, check the box next to Enable Single Sign-on. Then finish the installation. If installing an older version of Receiver: Go to the downloaded Citrix Receiver. Shift-right-click CitrixReceiver.
Open a command prompt. Click Install when prompted. Install the receiver. Expand Citrix Workspace and click User authentication. On the right, double-click Local user name and password.
Select Enabled and then check the box next to Allow pass-through authentication for all ICA connections. Click OK. You can use a GPO to configure this on the client side. Local Intranet zone should have Automatic logon only in Intranet zone enabled. Logoff Windows and log back on. In Task Manager you should now see ssonsvr. Right-click the Workspace app icon and click Advanced Preferences. Click Configuration Checker. The lines with red x will indicate the issue and corrective action.
Select Enabled , and then click Show. Enter a store path based on the example shown in the Help box. Workspace app lets you enter a Gateway path. Then click OK. From Citrix Docs Configuring application delivery: There are several methods of controlling how Workspace app displays shortcuts on the Start Menu and Desktop as detailed below: Workspace app Registry values receiver.
This only works if the app is a Favorite, or if Favorites are disabled, or Mandatory Store. More details in Configuring application delivery at Citrix Docs. StartMenuDir — If there is potentially a conflict between local apps and remote apps, then you should place the Start Menu shortcuts in a folder.
Receiver for Windows, LTSR Cumulative Update 4 – Citrix.Citrix Receiver for Windows LTSR – PDF Free Download
Note: A first-time user is one who does not have Citrix Receiver for Windows installed on the device. If your site requires configuration of Citrix Receiver for Windows, use an alternate deployment method. Automatically from Receiver for Web or from a Web Interface logon screen.
A first-time user can set up an account by entering a server URL or downloading a provisioning CR file.
Citrix Receiver for Windows does not require administrator rights to install unless you are using passthrough authentication. When installing Citrix Receiver by using the executable file. Note Installing the latest version of Citrix Receiver with integrated RTME support requires administrative privileges on the host machine.
Previously installed versions of RTME are overwritten with the latest version; upgrading from the same Citrix Receiver for Windows version to the latest bundled version for example, Receiver 4.
If a more recent version of RTME is present, the installer retains the latest version. Attach the provisioning file created by StoreFront to an and inform users how to upgrade and to open the provisioning file after installing Citrix Receiver for Windows. Or, if you configured -based account discovery as described in the StoreFront documentation, inform users to enter their address. Inform users how to upgrade Citrix Receiver for Windows, access the Citrix Receiver for Web site, and download the provisioning file from Citrix Receiver for Web click the user name and click Activate.
Let your users know how to upgrade Citrix Receiver for Windows. You can, for example, create a download site where users can obtain the renamed Citrix Receiver installer Citrix Systems, Inc.
If Citrix Receiver for Windows 3. Install and uninstall Citrix Receiver for Windows manually August 6, You can install Citrix Receiver for Windows from the installation media, a network share, Windows Explorer, or a command line by manually running the CitrixReceiver.
For command line installation parameters and space requirements, see Configure and install Receiver for Windows using command-line parameters. Validating free disk space Citrix Receiver for Windows performs a check to verify whether there is enough available disk space to complete the installation.
The verification is performed both during a fresh installation and an upgrade. During a fresh installation, the installation ends when there is insufficient disk space and the following dialog appears. When you are upgrading Citrix Receiver for Windows, the installation ends when there is insufficient disk space and the following dialog appears Citrix Systems, Inc. Installation type Fresh installation Upgrade of Citrix Receiver Required disk space MB MB Note The installer performs the check on the disk space only after extracting the installation package.
When you reinstall Citrix Receiver for Window, these policies might be enforced, possibly causing unexpected behavior. To remove the customizations, delete them manually. Configure and install using command-line parameters March 19, Customize Citrix Receiver for Windows installer by specifying command line options.
The installer package self-extracts to the user s temp directory before launching the setup program. The space requirement includes program files, user data, and temp directories after launching several applications. For more information space requirements, see System requirements. Check for updates manually; Disabled Disable auto-update CitrixReceiver. For example, if you set the value to 10, the Remind me later option is displayed 10 times.
The feature, however, must be configured both on the server and the client. Administrator-level privileges are required to perform these steps. This option is not necessary for silent installs.
If you suppress reboot prompts, the USB devices that are in suspended state when Citrix Receiver for Windows installs is not recognized by Citrix Receiver for Windows until after the user device is restarted. Note: Smart card, Kerberos and Local user name and password policies are inter-dependent.
The order of configuration is important. We recommend to first disable unwanted policies, and then enable the policies you require. Carefully validate the result. The default value is Yes. This property is required for smart card Single sign-on. Note that users must log off and log in to their devices after an installation with Single sign-on authentication enabled.
Requires administrator rights. Use this property to explicitly enable or disable the always-on tracing feature. Always-on tracing helps collect critical logs around connection time.
These logs can prove useful when troubleshooting intermittent connectivity issues. The Always-on tracing policy overrides this setting. Dynamic client name Citrix Systems, Inc. When users change their computer name, the client name changes to match. Defaults to Yes.
When specifying multiple parameters, separate each parameter with a comma and without spaces. The names are case sensitive. If you do not specify this parameter, all components are installed by default. WebHelper Installs the WebHelper component.
The AM value must be specified on the command line and. Defaults to S. Specifies whether users can save the credentials for stores locally on their computers and apply only to stores using the PNAgent protocol. Change this property to choose the default certificate per the smart card provider or the certificate with the latest expiry date.
If there are no valid logon certificates, the user is notified, and given the option to use an alternate logon method if available. Use this option to select a certificate. Specifies whether the HDX engine should use Kerberos authentication and applies only when single sign-on pass-through authentication is enabled.
For more information, see Configure domain pass-through authentication with Kerberos. The default value is False. Specifies whether or not application icons are displayed for documents that have file type associations with subscribed applications.
When the argument is set to false, Windows generates icons for documents that do not have a specific icon assigned to them. The icons generated by Windows consist of a generic document icon overlaid with a smaller version of the application icon.
Citrix recommends enabling this option if you plan to deliver Microsoft Office applications to users running Windows 7.
For information about session pre-launch, see Reduce application launch time. You can specify the relative path under the programs folder to contain the shortcuts to subscribed applications. Users can change the folder name or move the folder at any time. Use the same registry locations as noted above. Applications will be displayed individually or under the root folder but not within Category sub folders defined with XenApp.
To move shortcuts, you must uninstall and re-install the applications Citrix Systems, Inc. Specifies up to 10 stores to use with Citrix Receiver. Values: x and y Integers 0 through 9; storename Defaults to store. This must match the name configured on the StoreFront Server; servername. On Off The optional Off configuration setting enables you to deliver disabled stores, giving users the choice of whether or not they access them.
Requires that Citrix Receiver is installed for All Users. CategoryPath is supported for desktop shortcuts. You can use a stub application to launch a virtual desktop or application from the command line.
The file name for a stub application is the Display Name of the application, with the spaces removed. For example, the stub application file name for Internet Explorer is InternetExplorer. Citrix recommends using the scripts rather than extracting the. For general information about startup scripts, see Microsoft documentation. Citrix includes sample per-computer startup scripts to install and uninstall CitrixReceiver.
The scripts are located on the Citrix Receiver for Windows Download page. If not removed, these configuration files can prevent some users from accessing the Receiver logs directory. The Citrix sample scripts include functionality to properly remove these configuration files. To use the startup scripts to deploy Receiver with Active Directory: 1. Create the Organizational Unit OU for each script. Modify sample scripts Modify the scripts by editing these parameters in the header section of each file: Current Version of package.
The specified version number is validated and if it is not present the deployment proceeds. If you specify a partial version, for example, 3. This specifies the network share containing the packages and is not authenticated by the script. Script Logging Directory. This specifies the network share where the install logs are copied and is not authenticated by the script. Package Installer Command Line Options. These command line options are passed to the installer.
For the command line syntax, see Configure and install Receiver for Windows using command-line parameters. To add the per-computer startup scripts 1. Open the Group Policy Management Console. In the Properties menu, click Show Files, copy the appropriate script to the folder displayed, and then close the window. In the Properties menu, click Add and use Browse to find and add the newly created script.
To deploy Citrix Receiver for Windows per-computer 1. Move the user devices designated to receive this deployment to the OU you created. Reboot the user device and log on as any user Citrix Systems, Inc. To remove Citrix Receiver for Windows per-computer 1. Move the user devices designated for the removal to the OU you created. Reboot the user device and log on as any user.
Use the per-user sample startup scripts Citrix recommends using per-computer startup scripts. In the Logon Properties menu, click Show Files, copy the appropriate script to the folder displayed, and then close the window.
In the Logon Properties menu, click Add and use Browse to find and add the newly created script. To deploy Citrix Receiver for Windows per-user 1. Move the users designated to receive this deployment to the OU you created. Reboot the user device and log on as the specified user. Move the users designated for the removal to the OU you created. Citrix Receiver for Web site enable you to access StoreFront stores through a web page. If the Citrix Receiver for Web site detects that a user does not have a compatible version of Citrix Receiver for Windows, you are prompted to download and install Citrix Receiver for Windows.
If -based account discovery is configured and a first-time user installs Citrix Receiver for Windows from Citrix. Entering an address results in the error message Your cannot be used to add an account. Use the following configuration to prompt for the server address only. Download CitrixReceiver. Rename CitrixReceiver. Deploy the renamed executable using your regular deployment method. The Web Interface provides a client detection and deployment process that detects which Citrix clients can be deployed within the user s environment and then guides them through the deployment procedure.
You can configure the client detection and deployment process to run automatically when users access a XenApp website. If the Web Interface detects that a user does not have compatible version of Citrix Receiver for Windows, the user is prompted to download and install Citrix Receiver for Windows. Use the following configuration to prompt for the server address only: 1. Specify the changed filename in the ClientIcaWin32 parameter in the configuration files for your XenApp websites.
To use the client detection and deployment process, the Citrix Receiver for Windows installation files must be available on the Web Interface server. By default, the Web Interface assumes that the file names of the Citrix Receiver for Windows installation files are the same as the files supplied on the XenApp or XenDesktop installation media.
Add the sites from which the CitrixReceiverWeb. Adding distribution points 3. Deploying the Receiver software to the software center 4.
Copy the downloaded Citrix Receiver to a folder on the Configuration Manager server and launch the Configuration Manager console. Right-click Application and click Create Application. The Create Application wizard appears. In the General pane, select Manually specify the application information and click Next.
In the General Information pane, specify information about the application such as Name, Manufacturer, Software version, and so on. In the Application Catalog wizard, specify additional information such as Language, Application name, User category and so on and click Next. Note: Users can see the information you specify here.
In the Content pane: a Provide the path where the Citrix Receiver setup file is present. In the Detection Method pane: Select Configure rules to detect the presence of this deployment type and click Add Clause.
Set Setting Type to File System. Under Specify the file or folder to detect the application, set the following: Type From the drop-down menu, select File. Click Next. Note: Do not specify any requirements and dependencies for this deployment type. In the Summary pane, verify the settings for this deployment type. A success message appears. In the Completion pane, a new deployment type Receiver Deployment is listed under the Deployment types. Click Next and click Close. Add distribution points 1.
The Distribute Content wizard appears. The Add Distribution Points dialog appears. In the Completion pane, a success message appears 4. Click Close Citrix Systems, Inc. The Deploy Software wizard appears. In the Scheduling pane, specify the schedule to deploy the software on target devices Citrix Systems, Inc.
In the User Experience pane, set the User notifications behavior; select Commit changes at deadline or during a maintenance window requires restart and click Next to complete the Deploy Software wizard. In the Completion pane, a success message appears. Reboot the target endpoint devices required only to start installation immediately. Installation is triggered automatically based on the schedule you configure.
Alternatively, you can also schedule or install on demand. The installation status is displayed in the Software Center after the installation starts.
Creating device collections 1. The Create Device Collection wizard appears. In the General pane, type the name for the device and click Browse for Limiting collection. In the Membership Rules pane, click Add Rule for filtering the devices. The Create Direct Membership Rule wizard appears. In the Search for Resources pane, select the Attribute name based on the devices you want to filter and provide the Value for Attribute name to select the devices.
In the Select Resources pane, select the devices that are required to be part of device collection. In the Completion pane a success message appears. Click Close. In the Membership rules pane, a new rule is listed. Click Close to complete the Create Device Collection wizard. The new device collection is listed in Device Collections. Also, retrying might yield successful deployment.
Configure October 26, Citrix Systems, Inc. Ensure your XenApp environment is configured correctly. Understand your options and provide meaningful application descriptions for your users.
This mode allows users to subscribe to applications from the Citrix Receiver for Windows user interface. Configure with the Group Policy Object administrative template Provide users with account information. Provide users with the information they need to set up access to accounts hosting their virtual desktops and applications. In some environments, users must manually set up access to those accounts. If you have users who connect from outside the internal network for example, users who connect from the Internet or from remote locations , configure authentication through NetScaler Gateway.
Configuring application delivery March 19, When delivering applications with XenDesktop or XenApp, consider the following options to enhance the user experience: Web Access Mode – Without any configuration, Citrix Receiver for Windows provides browserbased access to applications and desktops.
You can open a browser to a Receiver for Web or Web Interface site to select and use the applications you want. In this mode, no shortcuts are placed on the user s desktop. Self Service Mode – By adding a StoreFront account to Citrix Receiver for Windows or configuring Citrix Receiver for Windows to point to a StoreFront site, you can configure self-service mode, which allows you to subscribe to applications from the Citrix Receiver for Windows user interface.
This enhanced user experience is similar to that of a mobile app store. In a self-service mode, you can configure mandatory, auto-provisioned and featured app keyword settings as required. Note: By default, Citrix Receiver for Windows allows you to select the applications to display in the Start menu.
App shortcut-only mode – As a Citrix Receiver for Windows administrator, you can configure Citrix Receiver for Windows to automatically place application and desktop shortcuts directly in the Start menu or on the desktop in a similar way that Citrix Receiver for Windows Enterprise Citrix Systems, Inc.
The new shortcut only mode allows you to find all the published apps within the familiar Windows navigation schema where you would expect to find them. Note: Include meaningful descriptions for applications in a Delivery Group. Descriptions are visible to Citrix Receiver for Windows users when using Web access or self-service mode. Configuring NetScaler Gateway Store Citrix recommends using the Group Policy Object administrative template to configure rules for network routing, proxy servers, trusted server configuration, user routing, remote user devices, and user experience.
You can use the receiver. For domain policies, import the template file using the Group Policy Management console. This is especially useful for applying Citrix Receiver for Windows settings to a number of different user devices throughout the enterprise. To affect a single user device, import the template file using the local Group Policy Editor on the device.
As an administrator, open the Citrix Receiver Group Policy Object administrative template by running gpedit. If applying the policy on a single computer, launch it from the Start menu.
If applying on domain policies, launch it by using the Group Policy Management console 2. Edit the settings. Limitations: 1. Configure self-service mode By simply adding a StoreFront account to Citrix Receiver or configuring Citrix Receiver to point to a StoreFront site, you can configure self-service mode, which allows users to subscribe to applications from the Receiver user interface.
Note: By default, Citrix Receiver for Windows allows users to select the applications they want to display in their Start menu. In self-service mode, you can configure mandatory, auto-provisioned and featured app keyword settings as needed. Append keywords to the descriptions you provide for delivery group applications: To make an individual app mandatory, so that it cannot be removed from Citrix Receiver for Windows, append the string KEYWORDS:Mandatory to the application description.
There is no Remove option for users to unsubscribe to mandatory apps Citrix Systems, Inc. When users log on to the store, the application is automatically provisioned without users needing to manually subscribe to the application. Customize the app shortcut location using the Group Policy Object template Note You should make changes to group policy before configuring a store.
If at any time you want to customize the group policies, reset Citrix Receiver, configure the group policy, and then reconfigure the store. As an administrator, you can configure shortcuts using group policy. Open the Local Group Policy Editor by running the command gpedit. Choose Add, browse to the Receiver Configuration folder and then select receiver. The following settings can be added in the web.
Settings: true or false default is false. Settings: true or false default is true. To set a single directory for all shortcuts in the Start menu, use StartMenuDir. Setting: String value, being the name of the folder into which shortcuts are written. To reinstall modified apps, use AutoReinstallModifiedApps. To show a single directory for all shortcuts on the desktop, use DesktopDir. To remove shortcuts and Receiver icon for an application that was previously available from the Store but now is not available, use SilentlyUninstallRemovedResources.
In the web. Ensure that the Citrix StoreFront management console is not running on any of the other servers in the deployment. Once complete, propagate your configuration changes to the server group, so that the other servers in the deployment are updated.
Using per app settings in XenApp and XenDesktop 7. This functionality was similar to previously released versions of Citrix Receiver, however, release introduced the ability to control app shortcut placement using XenApp per app settings.
This functionality is useful in environments with a handful of applications that need to be displayed in consistent locations. Note: This setting applies to the Web interface site only.
Using per app settings in XenApp 7. In Citrix Studio, locate the Application Settings screen. In the Application Settings screen, select Delivery. Using this screen, you can specify how applications are delivered to users Citrix Systems, Inc. Select the appropriate icon for the application.
Click Change to browse to the location of the desired icon. In the Application category field, optionally specify the category in Receiver where the application appears.
For example, if you are adding shortcuts to Microsoft Office applications, enter Microsoft Office. Select the Add shortcut to user s desktop checkbox. Click OK.
Reducing enumeration delays or digitally signing application stubs If users experience delays in app enumeration at each logon, or if there is a need to digitally sign application stubs, Receiver provides functionality to copy the. This functionality involves a number of steps: 1. Create the application stubs on the client machine. Copy the application stubs to a common location accessible from a network share. If necessary, prepare a white list or, sign the stubs with an Enterprise certificate.
Add a registry key to enable Receiver to create the stubs by copying them from the network share. If RemoveappsOnLogoff and RemoveAppsonExit are enabled, and users are experiencing delays in app enumeration at every logon, use the following workaround to reduce the delays: 1.
Caution: Editing the Registry incorrectly can cause serious problems that may require you to reinstall your operating system. Citrix cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. Be sure to back up the registry before you edit it.
Enable a machine to use pre-created stub executables that are stored on a network share: 1. On a client machine, create stub executables for all of the apps. To accomplish this, add all the applications to the machine using Receiver; Receiver generates the executables Citrix Systems, Inc.
You only need the. Copy the executables to a network share. It s also possible to configure these settings on HKCU if you prefer.
Example use cases This topic provides use cases for app shortcuts. Allowing users to choose what they want in the Start Menu Self-Service If you have dozens or even hundreds of apps, it s best to allow users to select which applications they want to favorite and add to the Start Menu: If you want the user to choose the applications they want in their Start Menu If you want the user to choose the applications they want in their Start Menu but also want specific app shortcuts on the desktop configure Citrix Receiver in self-service mode.
In this mode you also configure auto-provisioned and mandatory app keyword settings as needed. Use auto provisioned and mandatory apps as needed. No app shortcuts in the Start Menu If a user has a family computer, you might not need or want app shortcuts at all. In such scenarios, the simplest approach is browser access; install Citrix Receiver without any configuration and browse to Citrix Receiver for Web and Web interface.
You can also configure Citrix Receiver for self-service access without putting shortcuts anywhere Citrix Systems, Inc. Citrix Receiver will not put apps in the Start Menu even in self-service mode unless you put them there using per app settings.
All app shortcuts in the Start Menu or on the Desktop If the user has only a few apps, you can put them all in the Start Menu or all on the desktop, or in a folder on the desktop. All available apps will appear in the Start Menu.
All available apps will appear in the desktop. Per app settings in XenApp 6. This feature is referred to as Local App Access. Before installing an application on a user s computer, Citrix Receiver searches for the specified patterns to determine if the application is installed locally. When the user starts the application from the Citrix Receiver window, Citrix Receiver starts the locally installed preferred application. If a user uninstalls a preferred application outside of Citrix Receiver, the application is unsubscribed during the next Citrix Receiver refresh.
If a user uninstalls a preferred application from the Citrix Receiver window, Citrix Receiver unsubscribes the application but does not uninstall it. Note: The keyword prefer is applied when Citrix Receiver subscribes an application. Adding the keyword after the application is subscribed has no effect.
You can specify the prefer keyword multiple times for an application. Only one match is needed to apply the keyword to an application. If it is, Citrix Receiver subscribes the application and does not create a shortcut. The application name can be a word or a phrase. Quotation marks are required for phrases. Matching is not allowed on partial words or file paths and is case-insensitive. The application name matching pattern is useful for overrides performed manually by an administrator.
The Programs folder is a sub folder of the Start menu directory, so you must include it in the absolute path to target an application in that folder.
Quotation marks are required if the path contains spaces. The matching is case-sensitive. The absolute path matching pattern is useful for overrides implemented programmatically in XenDesktop.
The relative path provided must contain the application name and can optionally include the folders where the shortcut resides. Matching is successful if the shortcut file path ends with the relative path provided.
The relative path matching pattern is useful for overrides implemented programmatically. Configuring your XenDesktop environment October 26, After the Citrix Receiver for Windows is installed, the following configuration steps allow users to access their hosted applications and desktops: Adaptive transport – Adaptive transport optimizes data transport by applying a new Citrix protocol called Enlightened Data Transport EDT in preference to TCP whenever possible.
For more information about configuring adaptive transport, see Configuring adaptive transport. For more information about configuring auto-update, see Configuring auto-update. Bidirectional content redirection – The bidirectional content redirection allows you to enable or disable client to host and host to client URL redirection. For more information on configuring bidirectional content redirection, see Configuring bidirectional content redirection.
For information on configuring Bloomberg keyboards, see Configure Bloomberg keyboards. This is accomplished by exposing each of those functions using different interfaces. StoreFront 3.
IPv4 VDAs only. However, UDP ports and are not automatically opened. You must enable them. By default, the adaptive transport is allowed in Citrix Receiver for Windows. However, also by default, the client attempts to use adaptive transport only if the VDA is configured to Preferred in the Citrix Studio policy and if the setting has been applied on the VDA.
Set the new policy to Preferred to use adaptive transport when possible, with fallback to TCP. To disable adaptive transport on a specific client, set the EDT options appropriately using the Citrix Receiver Group Policy Object administrative template.
To configure adaptive transport using the Citrix Receiver Group Policy Object administrative template optional The following are optional configuration steps to customize your environment. For example, you may choose to disable the feature for a particular client for security reasons.
If you are applying the policy on a single computer, launch it from the Start menu. If you are applying the policy on a domain, launch it by using the Group Policy Management console Citrix Systems, Inc. Set the Transport protocol for Receiver policy to Enabled.
Select Communication Protocol for Citrix Receiver as required. Off: Indicates that TCP is used for data transfer. There is no fallback to TCP with this option. Additionally, for the adaptive transport configuration to take effect, the user is required to add the Citrix Receiver Windows template files to the Policy Definitions folder. Configuring auto-update March 19, When you configure auto-update from Citrix Receiver for Windows, follow the methods below in the order of priority: 1.
Group Policy Object administrative template 2. Command line interface 3. If you are applying the policy on a single computer, launch the Citrix Receiver Group Policy Object administrative template from the Start menu.
If you are applying the policy on a domain, launch the Citrix Receiver Group Policy Object administrative template by using the Group Policy Management console. Select the Set the Delay in Checking for Update policy. This policy allows you to stage the rollout for a period Citrix Systems, Inc. Select Enabled, and from the Delay Group drop-down, select one of the following options: Fast Update rollout happens at the beginning of the delivery period. Medium Update rollout happens at the mid-delivery period.
Slow Update rollout happens at the end of the delivery period. Click Apply and OK to save the Policy. Select Enabled and set the values as required: From the Enable AutoUpdate Policy drop-down, select one of the following options: Auto You are notified when an update is available default. Manual You are not notified when updates are available. Check for updates manually.
Any other number indicates that the Remind me later option is displayed in that count. For example, if you set the value to 10, the Remind me later option is displayed 10 times Citrix Systems, Inc. Click Apply and OK to save the policy. Typically, CitrixReceiverUpdater. Or, set AllowSavePwd value to A to allow users to save their passwords for non-secure stores. The default is the value specified from the PNAgent server at run time.
It specifies whether users can save credentials for stores locally on their computer and applies only to stores using the PNAgent protocol. Failed to load featured products content, Please try again. Customers who viewed this article also viewed. Log in to Verify Download Permissions. N : Prevents users from saving their passwords.
Receiver 4. Using Registry Editor incorrectly can cause serious problems that might require you to reinstall your operating system. Citrix Receiver can be used on domain and non-domain joined PCs, tablets, and thin clients. Provides high performance use of virtualized Skype for Business, line of business and HDX 3D Pro engineering apps, multimedia, local app access. It is an optional download, provided on an as-is basis by Citrix to serve as an example.
Before use, IT administrators must customize the scripts to suit their environment. The uninstall and install scripts may be used as noted in the upgrade guide for Citrix Receiver for Windows CTX It is an optional download, to be used by IT administrators, and not meant for use by end-users. Yes, I accept No. Your download will start immediately upon accepting this agreement.
You may close this window once your download begins. Solutions Solutions. Digital Workspaces. DaaS and VDI. Secure Access. Application Delivery. Content Collaboration. Boost Productivity Enable remote work Collaborate securely Enhance user experience.