Virtual Delivery Agent VDA 7. LTSR Carl Stalhood. Navigation Recently Updated. Hardware. Hypervisor Host Hardware. Citrix Blog Post Citrix Scalability The Rule of 5 and 1. Webopedias list of Data File Formats and File Extensions makes it easy to look through thousands of extensions and file formats to find what you need. WI-image-better-15.png' alt='Ica File Creator' title='Ica File Creator' />Simply take the number of physical cores in a hypervisor host, multiply it by 5 or 1. Single Server Scalability. Use 5 if youre looking for the number of Xen. Desktop VMs you can host on a box, and use 1. Xen. App user sessions you can host on a box. Virtual Machine Hardware. VDA virtual machine sizing. Ica File Creator' title='Ica File Creator' />For virtual desktops, give the virtual machine 2 v. CPU and 2 GB of RAMFor Windows 2. R2 RDSH, give the virtual machine 4 v. CPU and 1. 2 2. 4 GB of RAMFor Windows 2. R2 RDSH, give the virtual machine 8 v. CPU, and 2. 4 4. GB of RAMSee Daniel Feller Sizing Windows 2. Windows 2. 01. 2 And Windows 1. Virtual Machines. The number of Native Americans living in urban areas has grown substantially in recent decades. Urban and rural life each has its advantages and disadvantages. If using RAM caching MCSIO or Pv. S, add more RAM for the cache. Remove the floppy drive. Remove any serial or LPT ports. If v. Sphere. To reduce disk space, reserve memory. Memory reservations reduce or eliminate the virtual machine. The NIC should be VMXNET3. If this VDA will boot from Provisioning Services. For v. Sphere, the NIC must be VMXNET3. For v. Sphere, configure the CD ROM to boot from IDE instead of SATA. SATA comes with VM hardware version 1. SATA wont work with Pv. S. For Windows 1. CTX2. 24. 84. 3 Windows 1. Citrix Xen. Desktop . Citrix provides partial support for Semi Annual Channel Targeted aka Current Branch versions of Windows 1. Citrix provides full support for Semi Annual Channel Broad aka Current Branch for Business versions of Windows 1. VDA version released after a Windows 1. Broad typically 4 months and 4 patches after initial release. Windows 1. 0 1. 70. Broad is supported by VDA 7. VDA 7. 1. 5 was released after Windows 1. Broad after four monthly Windows patches. Windows 1. 0 1. 70. Targeted Citrix Product Manager in the comments mentioned that 7. Citrix has a live article about all this CTX2. The Microsoft patches required for 1. Nov 1. 4th Patch Tuesday KB4. VDA already installed, to 1. D patch last week of November via Microsoft Update Catalogue will allow you to do a fresh new VDA install on top of 1. Install the latest version of hypervisor drivers e. VMware Tools. If Windows 7 on v. Sphere, dont install the VMware SVGA driver. For more details, see Citrix CTX2. Intermittent Connection FailuresBlack Screen Issues When Connecting from Multi Monitor Client Machines to Windows 7 VDA with VDA 7. SphereESXi. The v. Sphere Activity Monitoring Feature with NSX Guest Introspection feature uses a TDI driver vnetflt. Connection Interrupted message when users log off of Citrix. See VMware 2. 12. Windows virtual machines using the v. Shield Endpoint TDI Manager or NSX Network Introspection Driver vnetflt. Xen. Desktop 7. 1. Connection interrupted at Citrix Discussions. If v. Sphere, disable NIC Hotplug. Users could use the systray icon to Eject the Ethernet Controller. Obviously this is bad. To disable this functionality, power off the virtual machine. Once powered off, right click the virtual machine, and click Edit. Settings. On the VM Options tab, expand Advanced, and then click Edit Configuration. On the bottom left, enter devices. On the right, enter false. Then click Add. Then click OK a couple times to close the windows. The VM can then be powered on. Windows Preparation. Computer Group Policy Make sure the Master VM is in the same OU as the Linked Clones so the Master VM will get the computer level GPO settings in its registry. Run gpupdate on the master after moving the VM to the correct OU. When Clones are created from the Master, the computer level GPO settings will already be applied, thus eliminating a timing issue. If RDSH Server OS, disable IE Enhanced Security Configuration in Server Manager Local Server. Optionally, go to Action Center Windows 8. R2 or Control Panel  Security and Maintenance Windows 1. User Account Control, and enable Smart. Screen. In Windows 1. Settings app for Change User Account Control settings. Smart. Screen is configured in Windows Defender Security Center App browser control. Run Windows Update. Add your Citrix Administrators group to the local Administrators group on the VDA. Computer Management. The Remote Desktop Services Prompt for Password policy prevents Single Sign on to the Virtual Delivery Agent. Check registry key HKEYLOCALMACHINESOFTWAREPoliciesMicrosoftWindows NTTerminal Services. If f. Prompt. For. Password 1 then you need to fix group policy. The following GPO setting will prevent Single Sign on from working. Computer Configuration Policies Administrative Templates Windows Components Remote Desktop Services Remote Desktop Session Host Security Always prompt for password upon connection. Or set the registry value HKEYLOCALMACHINESOFTWARECitrixPortica. Auto. Logon DWORD 0x. For Windows 72. 00. R2 VDAs that will use Personal v. Disk, or App. Disk, or any other layering technology, install Microsoft hotfix 2. Cisco Catalyst 3500 Xl Ios. A computer stops responding because of a deadlock situation in the Mountmgr. This hotfix solved a Personal v. Disk Image update issue detailed at Citrix Discussions. If this VDA is Windows Server 2. R2, see http www. To remove the built in apps in Windows 1. Robin Hobo How to remove built in apps in Windows 1. Enterprise. For Remote Assistance in Citrix Director, configure the GPO setting Computer Configuration Policies Administrative Templates System Remote Assistance Offer Remote Assistance. See Jason Samuel How to setup Citrix Director Shadowing with Remote Assistance using Group Policy for more details. If you intend to use Citrixs SCOM Management Packs for Xen. AppXen. Desktop, make sure Win. RM is enabled on the VDA by running winrm quickconfig. Or you can enable Win. RM using Group Policy. Install Virtual Delivery Agent 7. LTSRFor virtual desktops, make sure you are logged into the console. The VDA wont install if you are connected using RDP. Bve Train Simulator Game. Make sure. NET Framework 4. CLI Install Command Line Install Options are detailed at Install using the command line at Citrix Docs. The Citrix Telemetry Service seems to cause problems. You can use the Command Line Installer to exclude Telemetry Service as detailed at VDA upgrade cmdlet at Citrix Discussions. Xen. Desktop. VDASetup. EnableHDXPORTS enableframehawkport EnableREALTIMETRANSPORT optimize controllers xdc. Exclude Citrix Telemetry ServiceGUI Install Mount the downloaded Xen. Desktop 7. 1. 5 LTSR ISO, and and run Auto. Select. exe. Alternatively, you can download the standalone VDA package and run that instead. Go the main Xen. Desktop 7. Expand the section labelled Components that are on the product ISO but also packaged separately to download the Standalone VDA installers. VDA installer called Desktop OS Core Services that is designed for Remote PC deployments. Click Start next to either Xen. App or Xen. Desktop. The only difference is the product name displayed in the installation wizard. On the top right, click Virtual Delivery Agent for Windows Desktop OS, or Windows Server OS, depending on which type of VDA you are building. In the Environment page, select Create a Master Image, and click Next. For virtual desktops, in the HDX 3. D Pro page, click Next. In the Core Components page, if you dont need Citrix Receiver installed on your VDA, then uncheck the box. Receiver is usually only needed for double hop connections connect to first VDA, and then from there, connect to second VDA. Receiver for Windows 4. Carl Stalhood. Navigation. This post applies to all Receiver versions 4. Recently Updated. Receiver Modules. Female War The Pottery. The Receiver installer deploys multiple modules. Here are the important ones ICA Engine wfica. ICA protocol to connect to published apps and desktops. Self Service selfservice. GUI that gets icons from Store. Front. When icon is clicked, ICA Engine performs the connection. Single Sign on SSON for ICA ssonsvr. VDAs. Receiver Auto Update Citrix. Receiver. Updater. Receiver 4. 8 and newer Notifies users of Receiver updates. The PNAgent module is no longer included in Receiver 4. The older Receiver Enterprise includes the PNAgent module, but does not include Self Service. The last version of Receiver Enterprise is 3. Custom ICA files are no longer supported. However, Ryan Butler has created a script that asks Store. Front for an ICA file. Explicit credentials are supported. Find the script at Github. Receiver Discovery and Beacon Process. If you are using Receivers built in user interface instead of  a web browser, then Receiver first prompts you to perform discovery, which is also called Add Account. Enter either a Store. Front FQDN, or a Net. Scaler Gateway FQDN. Just enter the FQDN. Theres no need to enter https or a path. Receiver will contact the FQDN and request download of the Store. Front Provisioning File. If your Store. Front server is configured with multiple stores, then the user will be prompted to select a store. Unfortunately, theres no configuration option in Net. Scaler Gateway to force a particular store. The Provisioning File downloaded from Store. Front is an XML document containing values for several items configured in the Store. Front console. You can export the Provisioning File from the Store. Front console by right clicking a Store. The Receiver. Config. Provisioning File looks something like this Here are the values in the Provisioning File Receiver reads the Provisioning File, and configures itself by inserting the files contents into the users registry. The values are located under HKCUSoftwareCitrixDazzleSites and HKCUSoftwareCitrixReceiverSR. If you performed discovery through Net. Scaler Gateway, notice that the internal Base URL is added to the users registry. Once Receiver is configured, it then performs the following steps Attempt to connect to the Internal Beacon. If the Internal Beacon is reachable, connect directly to the Store. Front Base URL Address. If the Internal Beacon is not reachable. Attempt to connect to the External Beacons. 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. Here are some interesting notes on this connection process In Store. Front Console, if any configuration changes are performed that affect the Provisioning File, do the Receivers reconfigure themselves automaticallyOr do users have to remove Accounts and re add so the updated Provisioning File is imported Here are some additional methods of performing Receiver Discovery Uninstall Old Clients. Receiver 4. 4 and newer includes Receiver Clean Up, so, in theory, its not necessary to uninstall old clients first. For more details, see Citrix CTX1. Upgrading to Citrix Receiver for Windows. To run it silently, run Citrix. Receiver. exe RCU Silent For a reliable upgrade experience, write a script to remove the old clients, clean up the registry and file system, and then deploy the new Receiver. Citrix Blog Post Cookbook to Upgrade from Receiver 3. Windows to Receiver 4. Citrix Article CTX1. Upgrading to Citrix Receiver for Windows contains step by step procedure to use Group Policy to uninstall Receiver Enterprise 3. Receiver 4. x. The Receiver Clean Up utility is designed to assist with the following scenarios When errors occur during upgrade from an earlier version of Receiver or Online Plug in. When unexpected behavior or performance is experienced after upgrade from an earlier Receiver or Online Plug in. If Receiver upgrade is not possible due to feature incompatibility andor a clean uninstall is required. The Receiver Clean Up Utility removes components, files, and registry values of Online Plug in 1. Receiver for Windows 3. Online Plugin in 1. This includes the Offline Plug in component if installed. Citrix CTX3. 25. 14. How to Remove Client Files Remaining on System after Uninstalling Receiver for Windows. Blog posts from Shaun Ritchie Installation and Configuration. This section contains a summary of all common command line switches, registry keys, and policy settings for Receiver. Links Citrix. Receiver. LTSR, or version 4. LTSR, can be installed by simply double clicking it. Administrator vs non administrator. Non administrator If a non administrator installs Receiver, then each non administrator that logs in to the workstation will have to reinstall Receiver. Non administrator installations are installed to USERPROFILEApp. DataLocalCitrixICA Client for each user. Administrator If Citrix. Receiver. exe is installed using an administrator account. Receiver only needs to be installed once. Administrator installations are installed to C Program Files x. CitrixICA Client. Administrator installations cannot be upgraded by non administrators. Conflicts If an administrator install of Receiver is performed on a machine that has non administrator installs of Receiver, then the two Receivers will conflict. Best option is to uninstall non admin Receiver before installing admin Receiver. Otherwise, the users profile probably has to be reset before Receiver is functional again. Auto Update. Receiver 4. Some notes To troubleshoot Auto update, see Citrix CTX2. Troubleshooting Citrix Receiver Updates. Add Account Wizard. From Citrix CTX1. How to Suppress the Add Account Window in Citrix Receiver for Windows After installation, Receiver will launch and ask you to add an account. If Receiver 4. 4. Do not show this window automatically at logon. For Receiver 4. 4 and newer, FTU First Time Use aka Add Account Wizard will be displayed only if a store is not configured. If a store is already configured via command line, GPO, or Citrix Studio, then FTU screen will not be available after installation. Otherwise, FTU can be suppressed by doing one of the following  Note Receiver 4. Add Account wizardDiscover Hidden Stores. When Receiver is first launched, it must perform Discovery, which is the process of downloading the. Store. Front. Discovery is performed by entering a Store. Front FQDN or Gateway FQDN. To discover a hidden store a store thats not advertised, add Store. Name to the end of the FQDN. CTX2. Unable to add account from Receiver dialog If the store is hidden in storefront. Citrix. Receiver. Command line switches. Citrix Blog Post Citrix Receiver Command Line Helper Tool contains a GUI tool to build your installer command line. Installer Command Line Switches are detailed at Configure and install Receiver for Windows using command line parameters at Citrix Docs. Common Command line switches include the following silentinclude. SSON enables pass through authentication. GPO configuration is also required as detailed below. Citrix. Receiver. SSONALLOWADDSTOREA by default, only SSL HTTPS stores are accepted. To allow non SSL stores. Citrix. Receiver. ALLOWADDSTOREASTORE0 To add a store from the installation command line. Citrix. Receiver.