Looking for:
Remote access citrix receiver |
Remote access citrix receiver
Customers who viewed this article also viewed. Log in to Verify Download Permissions. These connections are not brokered by XenDesktop and not started through the Web Interface. They are initiated using the Remote Desktops Connection client built into Windows client operating systems. See Web Interface documentation for further information. Select a desktop group and access the Properties page. Either the bit or the bit version works. Troubleshooting If the virtual desktop has a firewall on it, the firewall might have to be configured to allow connections on the RDP port The path to RdpPlugIn.
For example, in gpedit. Verify that the Web Interface site has Remote Desktop Connection selected when attempting connection; rather than Native client for example.
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.
The download begins. Run the following command. Replace the name of the executable with the one you downloaded and the cloud connector FQDN. Once the trial is approved, Log in to Citrix Cloud from your local machine. Select I want users to connect to same static desktop each time they login. Click Next. In our example we are adding a machine. In the Select Computers pop up, enter the first few characters of the machine hostname you want to add.
Click Check Names. If the search returns more than one machine names, choose the ones you want to add hold down the CTRL key to choose more than one. Once you have selected all the machines. Click OK. Repeat the last 2 steps to add all the machines you want to add to the catalog. Then click Save in the Select Computers dialog. From the Select the Zone and minimum functional level for this catalog drop-down list, select or newer. Enter a name for the machine catalog.
Click Finish. You will be returned to the Machine Catalogs page. From the left side menu click Delivery Groups to start creating your delivery group. Specify which users can access these desktops. For our example we assign the desktops to a group of users, that have a mapping for each of the machines in the delivery group for enhanced security.
Click Add. You can check their names by clicking Check Names. Once you are done click OK. If the search returns more than one user name, choose the ones you want to add hold down the CTRL key to choose more than one.
Once you have selected all the users you want to add. Repeat the last 2 steps for all the users you want to add to the delivery group. Then click Save in the Select Users or Groups dialog. Click Next in the Create Delivery group dialog. In the Add Desktops Assignment Rule dialog. Enter Display Name for the delivery group.
Click Add and add the same or a subset of the users you chose earlier again. Ensure Enable desktop assignment rule check box is checked. Once the delivery group is created, the Delivery Group Manage link looks like this. Click the Desktops tab in the Details section.
Select the machine you want to assign to a user. Click Change User from the Action menu. Search for the user you want to assign to the machine using the Check Names button.
Once found, click OK. Click Save. Note : The last 4 steps are needed, if you want to assign specific users to specific desktops, else the users will be auto assigned to next available desktop in the delivery group or you can use PowerShell scripts to perform the assignment. Log in as a domain user you have assigned the remote desktop to. If this is the first time you are launching a session from the browser, you may get the following pop up. Click View All Desktops. Click the Remote PC Access delivery group.
The guide walked you through connecting your physical desktops in your office to the Citrix DaaS, so users access them remotely. You learned how use Citrix DaaS to allow users to access their desktops on any device from any location.
No comments:
Post a Comment