Looking for:
Citrix receiver remote access |
.Citrix receiver remote access
Citrix Workspace. What's New. Get started with Citrix Workspace. Deliver DaaS with Citrix Workspace. Access and share files with Content Collaboration in Citrix Workspace. Prepare for Citrix Workspace. Secure workspaces. Integrate services into workspaces. Manage your workspace experience. Customize workspace notifications. Customize the appearance of workspaces. Customize workspace interactions. Customize security and privacy policies. Customize Citrix Workspace app settings.
Optimize DaaS in Citrix Workspace. Aggregate on-premises virtual apps and desktops in workspaces. Optimize connectivity with Direct Workload Connection. Service continuity. Optimize workflows.
IT Self-Service. HR Self-Service. Sales Productivity. Employee Well-being. Document History. Aviso legal. Este texto foi traduzido automaticamente. Este artigo foi traduzido automaticamente. Citrix recommends using the latest version of Citrix Workspace app to access workspaces. Citrix Workspace app replaces Citrix Receiver. The Workspace URL is customizable and is enabled by default.
Citrix Workspace app replaces Citrix Receiver as the natively installed app that provides access to the Workspace user interface UI. For information about the Citrix Workspace app and transitioning from Citrix Receiver, see Citrix Workspace app formerly Citrix Receiver in this article. Remote subscribers can gain external access to their workspaces if you configure external connectivity with Citrix Gateway or the Citrix Gateway service.
For information on enabling remote access to workspaces, see External connectivity in this article. Alternatively, for internal connectivity only, you can use Citrix Workspace on its own or host StoreFront on-premises.
Citrix Workspace supports a growing list of identity providers that you connect to Citrix Cloud and then enable in Workspace Configuration to authenticate subscribers to their workspaces. For information on configuring authentication for Workspace subscribers, see Authentication to workspaces in this article. The first part of the Workspace URL is customizable. If the URL is disabled, you must re-enable it first. Re-enabling the Workspace URL can take up to 10 minutes to take effect.
Misuse of third party intellectual property rights, including trademarks, might result in revocation and reassignment of the URL or suspension of the Citrix Cloud account. The customizable part of the URL:. For example, you might want subscribers to use an on-premises StoreFront URL to access resources, or you might want to prevent access during maintenance.
If you continue to use Citrix Receiver, technical support is limited to the options described in Lifecycle Milestones and Definitions. Citrix Workspace app is a natively installed app that replaces Citrix Receiver for accessing workspaces. The following table shows the authentication methods supported by Citrix Workspace app. The table includes authentication methods relevant to specific versions of Citrix Receiver, which Citrix Workspace app replaces.
For more information about supported features in Citrix Workspace app by platform, refer to the Citrix Workspace app feature matrix. For information on single sign-on for workspace subscribers, see Enable single sign-on for workspaces with Citrix Federated Authentication Service. Once they upgrade to Citrix Workspace app, they can access their workspaces.
For more information on what the subscriber experience of this UI is, visit Manage your workspace experience. If you have a StoreFront on-premises deployment, upgrading from Citrix Receiver to Citrix Workspace app only changes the icon to open Citrix Workspace app. Provide secure access for remote subscribers by adding Citrix Gateways or the Citrix Gateway service to resource locations. The Citrix Virtual Apps Essentials service uses the Citrix Gateway service, which requires no additional configuration.
Configuring more identity providers in Identity and Access Management gives you more options to choose from in Workspace Configuration for how subscribers sign into their workspaces. For more information on supported methods for subscriber authentication to workspaces, visit Secure workspaces. AD plus Token is the default identity provider used to authenticate subscribers to workspaces.
For information on setting up token-based two-factor authentication, see Two-factor authentication. You choose an identity provider as your primary authentication method for Citrix Workspace in Workspace Configuration. The identity provider you choose must first be configured in Identity and Access Management.
To change the primary authentication method for signing into Citrix Workspace you must:. You can configure and change your primary authentication method for Citrix Workspace without breaking your production environment.
Citrix Workspace offers a seamless experience by providing single sign-on SSO to secondary resources once the subscriber has signed in to their workspace. Beyond SSO capabilities, Citrix Secure Private Access allows you to set enhanced security policies, configure contextual access, and collect analytics. 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. View PDF. This content has been machine translated dynamically. Give feedback here. Thank you for the feedback. Translation failed!
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.
Citrix will not be held responsible for any damage or issues that may arise from using machine-translated content. Was this helpful. Send us your feedback. Instructions for Contributors. November 16, Contributed by: J C M. Citrix Preview Documentation. This Preview product documentation is Citrix Confidential.
If you do not agree, select Do Not Agree to exit. Machine Translation Feedback Form. Write something?
Citrix receiver remote access.
The first part of the Workspace URL is customizable. If the URL is disabled, you must re-enable it first. Re-enabling the Workspace URL can take up to 10 minutes to take effect. Misuse of third party intellectual property rights, including trademarks, might result in revocation and reassignment of the URL or suspension of the Citrix Cloud account.
The customizable part of the URL:. For example, you might want subscribers to use an on-premises StoreFront URL to access resources, or you might want to prevent access during maintenance. If you continue to use Citrix Receiver, technical support is limited to the options described in Lifecycle Milestones and Definitions. Citrix Workspace app is a natively installed app that replaces Citrix Receiver for accessing workspaces.
The following table shows the authentication methods supported by Citrix Workspace app. The table includes authentication methods relevant to specific versions of Citrix Receiver, which Citrix Workspace app replaces. For more information about supported features in Citrix Workspace app by platform, refer to the Citrix Workspace app feature matrix.
For information on single sign-on for workspace subscribers, see Enable single sign-on for workspaces with Citrix Federated Authentication Service. Once they upgrade to Citrix Workspace app, they can access their workspaces.
For more information on what the subscriber experience of this UI is, visit Manage your workspace experience. If you have a StoreFront on-premises deployment, upgrading from Citrix Receiver to Citrix Workspace app only changes the icon to open Citrix Workspace app. Provide secure access for remote subscribers by adding Citrix Gateways or the Citrix Gateway service to resource locations.
The Citrix Virtual Apps Essentials service uses the Citrix Gateway service, which requires no additional configuration. Configuring more identity providers in Identity and Access Management gives you more options to choose from in Workspace Configuration for how subscribers sign into their workspaces.
For more information on supported methods for subscriber authentication to workspaces, visit Secure workspaces. AD plus Token is the default identity provider used to authenticate subscribers to workspaces.
For information on setting up token-based two-factor authentication, see Two-factor authentication. You choose an identity provider as your primary authentication method for Citrix Workspace in Workspace Configuration.
The identity provider you choose must first be configured in Identity and Access Management. To change the primary authentication method for signing into Citrix Workspace you must:.
You can configure and change your primary authentication method for Citrix Workspace without breaking your production environment. Citrix Workspace offers a seamless experience by providing single sign-on SSO to secondary resources once the subscriber has signed in to their workspace.
Beyond SSO capabilities, Citrix Secure Private Access allows you to set enhanced security policies, configure contextual access, and collect analytics. 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. View PDF. This content has been machine translated dynamically.
Give feedback here. Thank you for the feedback. Translation failed! 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.
Citrix will not be held responsible for any damage or issues that may arise from using machine-translated content. Was this helpful. Send us your feedback.
Instructions for Contributors. Install using the command line. Install VDAs using scripts. Create a site. Create machine catalogs. Manage machine catalogs. Create delivery groups. Manage delivery groups. Create application groups. Manage application groups. Publish content. Server VDI. User personalization layer. Remove components. Upgrade and migrate.
Upgrade a deployment. App protection. Contextual App Protection for StoreFront. Contextual App Protection for Workspace. App Protection for hybrid launch for Workspace. App Protection for hybrid launch for StoreFront. Delegated administration. Federated Authentication Service. FIDO2 authentication. Manage security keys. Security considerations and best practices. Smart cards. Smart card deployments. Pass-through authentication and single sign-on with smart cards.
Virtual channel security. Generic USB devices. Mobile and touch screen devices. Serial ports. Specialty keyboards. TWAIN devices. WIA devices. HDX 3D Pro. Text-based session watermark. Screen sharing.
Virtual display layout. Audio features. Browser content redirection. HDX video conferencing and webcam video compression. HTML5 multimedia redirection. Optimization for Microsoft Teams. Monitor, troubleshoot, and support Microsoft Teams. Windows Media redirection. General content redirection. Client folder redirection. Host to client redirection. Bidirectional content redirection. Generic USB redirection and client drive considerations.
Printing configuration example. Best practices, security considerations, and default operations. Printing policies and preferences. Provision printers.
Maintain the printing environment. Work with policies. Policy templates. Create policies. Compare, prioritize, model, and troubleshoot policies. Default policy settings. Policy settings reference. ICA policy settings. HDX features managed through the registry. Load management policy settings. Profile management policy settings. User personalization policy settings.
Virtual Delivery Agent policy settings. Virtual IP policy settings. Connector for Configuration Manager policy settings. Multi-type licensing. FAQ for licensing. App packages. Universal Windows Platform Apps. Connections and resources. Local Host Cache. Virtual IP and virtual loopback. Delivery Controllers. VDA registration. Use Search in Studio. User profiles. Citrix Insight Services. Citrix Scout. Configuration logging. Event logs. Advanced configuration. PIV smart card authentication.
Network analysis. Delegated Administration and Director. Secure Director deployment. Configure with Citrix Analytics for Performance. Site analytics. Alerts and notifications. Filters data. Historical trends. Troubleshoot deployments.
User issues. Feature compatibility matrix. Data granularity and retention. Troubleshoot Director failure reasons. Third party notices. Document History.
Citrix receiver remote access.Remote PC Access
Aggregate on-premises virtual apps and desktops in workspaces. Optimize connectivity with Direct Workload Connection. Service continuity. Optimize workflows. IT Self-Service. HR Self-Service. Sales Productivity. Employee Well-being. Document History. Aviso legal. Este texto foi traduzido automaticamente. Este artigo foi traduzido automaticamente. Citrix recommends using the latest version of Citrix Workspace app to access workspaces. Citrix Workspace app replaces Citrix Receiver. The Workspace URL is customizable and is enabled by default.
Citrix Workspace app replaces Citrix Receiver as the natively installed app that provides access to the Workspace user interface UI. For information about the Citrix Workspace app and transitioning from Citrix Receiver, see Citrix Workspace app formerly Citrix Receiver in this article.
Remote subscribers can gain external access to their workspaces if you configure external connectivity with Citrix Gateway or the Citrix Gateway service. For information on enabling remote access to workspaces, see External connectivity in this article. Alternatively, for internal connectivity only, you can use Citrix Workspace on its own or host StoreFront on-premises.
Citrix Workspace supports a growing list of identity providers that you connect to Citrix Cloud and then enable in Workspace Configuration to authenticate subscribers to their workspaces. For information on configuring authentication for Workspace subscribers, see Authentication to workspaces in this article.
The first part of the Workspace URL is customizable. If the URL is disabled, you must re-enable it first. Re-enabling the Workspace URL can take up to 10 minutes to take effect. Misuse of third party intellectual property rights, including trademarks, might result in revocation and reassignment of the URL or suspension of the Citrix Cloud account.
The customizable part of the URL:. For example, you might want subscribers to use an on-premises StoreFront URL to access resources, or you might want to prevent access during maintenance.
If you continue to use Citrix Receiver, technical support is limited to the options described in Lifecycle Milestones and Definitions. Citrix Workspace app is a natively installed app that replaces Citrix Receiver for accessing workspaces. The following table shows the authentication methods supported by Citrix Workspace app. The table includes authentication methods relevant to specific versions of Citrix Receiver, which Citrix Workspace app replaces.
For more information about supported features in Citrix Workspace app by platform, refer to the Citrix Workspace app feature matrix.
For information on single sign-on for workspace subscribers, see Enable single sign-on for workspaces with Citrix Federated Authentication Service. Once they upgrade to Citrix Workspace app, they can access their workspaces. For more information on what the subscriber experience of this UI is, visit Manage your workspace experience. If you have a StoreFront on-premises deployment, upgrading from Citrix Receiver to Citrix Workspace app only changes the icon to open Citrix Workspace app.
Provide secure access for remote subscribers by adding Citrix Gateways or the Citrix Gateway service to resource locations. The Citrix Virtual Apps Essentials service uses the Citrix Gateway service, which requires no additional configuration.
Configuring more identity providers in Identity and Access Management gives you more options to choose from in Workspace Configuration for how subscribers sign into their workspaces. For more information on supported methods for subscriber authentication to workspaces, visit Secure workspaces.
AD plus Token is the default identity provider used to authenticate subscribers to workspaces. Compare, prioritize, model, and troubleshoot policies. Default policy settings. Policy settings reference. ICA policy settings. HDX features managed through the registry. Load management policy settings. Profile management policy settings. User personalization policy settings. Virtual Delivery Agent policy settings. Virtual IP policy settings. Connector for Configuration Manager policy settings. Multi-type licensing.
FAQ for licensing. App packages. Universal Windows Platform Apps. Connections and resources. Local Host Cache. Virtual IP and virtual loopback. Delivery Controllers. VDA registration. Use Search in Studio. User profiles. Citrix Insight Services. Citrix Scout. Configuration logging. Event logs. Advanced configuration. PIV smart card authentication. Network analysis. Delegated Administration and Director.
Secure Director deployment. Configure with Citrix Analytics for Performance. Site analytics. Alerts and notifications. Filters data. Historical trends. Troubleshoot deployments. User issues. Feature compatibility matrix. Data granularity and retention. Troubleshoot Director failure reasons. Third party notices.
Document History. Aviso legal. Este texto foi traduzido automaticamente. Este artigo foi traduzido automaticamente. Remote PC Access is a feature of Citrix Virtual Apps and Desktops that enables organizations to easily allow their employees to access corporate resources remotely in a secure manner. The Citrix platform makes this secure access possible by giving users access to their physical office PCs. If users can access their office PCs, they can access all the applications, data, and resources they need to do their work.
Remote PC Access eliminates the need to introduce and provide other tools to accommodate teleworking. For example, virtual desktops or applications and their associated infrastructure. As a result, the requirements and process of deploying and configuring Remote PC Access are the same as those required for deploying Citrix Virtual Apps and Desktops for the delivery of virtual resources. This uniformity provides a consistent and unified administrative experience. The feature consists of a machine catalog of type Remote PC Access that provides this functionality:.
Citrix Virtual Apps and Desktops can accommodate more use cases for physical PCs by using other types of machine catalogs. These use cases include:. Sessions consume licenses in the same way as other Citrix Virtual Desktops sessions. While all the technical requirements and considerations that apply to Citrix Virtual Apps and Desktops in general also apply to Remote PC Access, some might be more relevant or exclusive to the physical PC use case.
Showing this screen is a security risk. If using a docking station, you can undock and redock laptops. Some devices provide built-in functionality to disconnect the wireless adapter upon establishing a wired connection. The other devices require custom solutions or third-party utilities to disconnect the wireless adapter. Review the Wi-Fi considerations mentioned previously. For information on how to create other types of machine catalogs, see the Create machine catalogs.
After you successfully complete steps 2—4, users are automatically assigned to their own machines when they log in locally on the PCs. Instruct users to download and install Citrix Workspace app on each client device that they use to access the office PC remotely. Editing the registry incorrectly can cause serious problems that might 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. After the restart, the operating system power saving settings are respected. The machine goes into sleep mode after the preconfigured idle timer passes. After the machine wakes up, it reregisters with the Delivery Controller.
To prevent this automatic action, add the following registry entry on the office PC, and then restart the machine. By default, the remote user has preference over the local user when the connection message is not acknowledged within the timeout period. To configure the behavior, use this setting:. The timeout for enforcing the Remote PC Access mode is 30 seconds by default. You can configure this timeout but do not set it lower than 30 seconds.
To configure the timeout, use this registry setting:. This allows you to monitor your environment for unwanted or unexpected activity and be able to audit such events if you need to investigate any incidents. This event ID appears when the SasNotification registry value does not exist or when the SasNotification registry value is 0.
This event ID appears when the remote session has been disconnected and when the SasNotification registry value does not exist or the SasNotification registry value is 0. This event ID appears when the remote user agrees to disconnect the session and when the SasNotification registry value is 1 and the RpcaMode registry value is 1 or the RpcaMode registry value is 2 or the RpcaMode registry value does not exist.
This event ID appears when the remote user does not decline the disconnect request within the specific timeout period and when the SasNotification registry value is 1 and the RpcaMode registry value is 2. This feature enables users to keep their office PCs turned off when not in use to save energy costs. It also enables remote access when a machine has been turned off inadvertently. This allows the feature to work without dependencies on extra infrastructure components or third-party solutions for delivery of magic packets.
After you address the prerequisites, complete the following steps to allow the Delivery Controller to communicate with SCCM:. For more details about display adapter priorities and monitor creation, see the Knowledge Center article CTX If the physical PC has the Hyper-V role or any virtualization-based security features enabled, the PC reports as a virtual machine.
To enable Remote PC Access mode, add the following registry value:. Informational messages are not throttled. Error messages are throttled by discarding duplicate messages. If power management for Remote PC Access is enabled, subnet-directed broadcasts might fail to start machines that are on a different subnet from the Controller.
If you need power management across subnets using subnet-directed broadcasts, and AMT support is not available, try the Wake-up proxy or Unicast method.
Ensure those settings are enabled in the advanced properties for the power management connection. To enable Remote PC Access mode, add the following registry setting:. 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.
No comments:
Post a Comment