Adding a policy to exclude the redirected or unwanted folders from roaming or synchronization is a common thing that is often overlooked. When using Citrix Profile Management, there is a GPO that can be specifically configured to block folders from profile synchronization. You should be adding all of the redirected folders to the folder exclusion list and you should also at a minimum add the following additional folders to the exclusion list:. Create a plan to upgrade the vDisk periodically using manual or Automatic vDisk updates.
This can significantly reduce network bandwidth and overall performance. Avoid scanning the vDisk Write Cache file and streaming disk IO that makes up the operating system for a given Target. Disk IO that has been altered, tampered, or corrupted should cause an application or operating system to fail immediately.
General questions, technical, sales, and product-related issues submitted through this form will not be answered. If you need additional help, you may try to contact the support team.
Contact Support. For optimal experience, we recommend using Chrome or Firefox. If you still wish to proceed with IE, please complete setting the following IE Security Configurations and select your region:. This website uses cookies for website functionality and traffic analytics. Our Cookie Notice provides more information and explains how to amend your cookie settings. Sign In with your Trend Micro Account. Sign in to MySupport. Need More Help? The following process recommended by Citrix articles is already excluded in Deep Security by default.
Citrix Consolidated List of Antivirus Exclusions. Provisioning Server recommended exclusions. Provisioning Services Antivirus Best Practices. Microsoft Windows privileges continue to be applied to desktops in the usual way: configure privileges through User Rights Assignment and group memberships through Group Policy.
One advantage of this release is that it is possible to grant a user administrative rights to a desktop without also granting physical control over the computer on which the desktop is stored. Logon rights are required for both user accounts and computer accounts. As with Microsoft Windows privileges, logon rights continue to be applied to desktops in the usual way: configure logon rights through User Rights Assignment and group memberships through Group Policy.
The Windows logon rights are: log on locally, log on through Remote Desktop Services, log on over the network access this computer from the network , log on as a batch job, and log on as a service. For computer accounts, grant computers only the logon rights they require. Consider the following approach:.
Refer to Microsoft documentation for more information. Delivery Controller installation also creates the following Windows services.
These are also created when installed with other Citrix components:. Delivery Controller installation also creates the following Windows service. This is not currently used. If it has been enabled, disable it. Delivery Controller installation also creates these following Windows services. These are not currently used, but must be enabled. Do not disable them.
Except for the Citrix Storefront Privileged Administration Service, these services are granted the logon right Log on as a service and the privileges Adjust memory quotas for a process, Generate security audits, and Replace a process level token. You do not need to change these user rights. These privileges are not used by the Delivery Controller and are automatically disabled.
Do not alter these service settings. This allows Local Host Cache to work correctly. Do not alter its service settings.
You can disable the Citrix Telemetry Service. Apart from this service, and services that are already disabled, do not disable any other of these Delivery Controller Windows services. It is no longer necessary to enable creation of 8. The registry key NtfsDisable8dot3NameCreation can be configured to disable creation of 8. You can also configure this using the fsutil. Your user environment can contain either user devices that are unmanaged by your organization and completely under the control of the user, or user devices that are managed and administered by your organization.
The security considerations for these two environments are generally different. Managed user devices are under administrative control; they are either under your own control, or the control of another organization that you trust. You may configure and supply user devices directly to users; alternatively, you may provide terminals on which a single desktop runs in full-screen-only mode. Follow the general security best practices described above for all managed user devices. This release has the advantage that minimal software is required on a user device.
User devices that are not managed and administered by a trusted organization cannot be assumed to be under administrative control. For example, you might permit users to obtain and configure their own devices, but users might not follow the general security best practices described above. This release has the advantage that it is possible to deliver desktops securely to unmanaged user devices. These devices should still have basic antivirus protection that will defeat keylogger and similar input attacks.
When using this release, you can prevent users from storing data on user devices that are under their physical control. However, you must still consider the implications of users storing data on desktops.
It is not good practice for users to store data on desktops; data should be held on file servers, database servers, or other repositories where it can be appropriately protected. Your desktop environment may consist of various types of desktops, such as pooled and dedicated desktops. Users should never store data on desktops that are shared amongst users, such as pooled desktops. If users store data on dedicated desktops, that data should be removed if the desktop is later made available to other users.
Mixed-version environments are inevitable during some upgrades. Follow best-practice and minimize the time that Citrix components of different versions co-exist. In mixed-version environments, security policy, for example, may not be uniformly enforced. This is typical of other software products; the use of an earlier version of Active Directory only partially enforces Group Policy with later versions of Windows.
The following scenario describes a security issue that can occur in a specific mixed-version Citrix environment. When Citrix Receiver 1. It does not recognize the policy setting, which was released in the later version of the product. This policy setting allows users to upload and download files to their virtual desktop, which is the security issue.
To work around this, upgrade the Delivery Controller or a standalone instance of Studio to version 7. Alternatively, use local policy on all affected virtual desktops. In XenDesktop 5. This release uses a registry entry to allow or prohibit multiple automatic remote PC assignments; this setting applies to the entire Site.
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. If there are any existing user assignments, remove them using SDK commands for the VDA to subsequently be eligible for a single automatic assignment.
Enabling the XML trust setting allows users to successfully authenticate and then start applications. The Delivery Controller trusts the credentials sent from StoreFront. Enable this setting only when you have secured communications between your Delivery Controllers and StoreFront using firewalls, IPsec, or other security recommendations.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation. The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
Citrix Virtual Apps and Desktops. View PDF. This content has been machine translated dynamically. Give feedback here. Thank you for the feedback. Translation failed! Security considerations and best practices November 3, Contributed by: C L.
The official version of this content is in English. Some of the Citrix documentation content is machine translated for your convenience only. Citrix has no control over machine-translated content, which may contain errors, inaccuracies or unsuitable language. No warranty of any kind, either expressed or implied, is made as to the accuracy, reliability, suitability, or correctness of any translations made from the English original into any other language, or that your Citrix product or service conforms to any machine translated content, and any warranty provided under the applicable end user license agreement or terms of service, or any other agreement with Citrix, that the product or service conforms with any documentation shall not apply to the extent that such documentation has been machine translated.
Log in to Verify Download Permissions. Information This article provides guidelines for configuring antivirus software in Citrix XenApp environments and resources for configuring antivirus software on other Citrix technologies and features EdgeSight, Provisioning Services, and so on.
General Antivirus Recommendations The following list contains general antivirus recommendations that should be reviewed prior to implementing any type of exclusions or optimizations: If organizations choose to exclude particular files or folders as part of real-time or on-access scanning, Citrix recommends scanning the excluded files and folders on a regular basis using scheduled scans. Was this page helpful? Thank you!
Sorry to hear that. Name Name is required. Email Email address is required. Close Submit. Featured Products. Need more help? Product issues. Open or view cases Chat live. Other support options.
0コメント