VDAs 7. The name of the monitoring database must not have any spaces in it. No lesser SQL role will work. In that case, the person running the scripts only needs the dbcreator and securityadmin roles. It is possible to create the three databases in advance. Each Basic Availability Group has its own Listener.
Assign a service account to the role at the Datacenter or higher level. Add two cores for LHC. Add at least three more Gigs of RAM and watch the memory consumption. Configure the Delivery Controller VM with four cores per socket. The only difference is the product name displayed in the installation wizard.
On the top left, click Delivery Controller. In the Core Components page, you can install all components on one server, or on separate servers. Splitting them out is usually recommended for the following reasons: large environments; or if you have multiple farms, and want to share the Licensing, and Director components across those farms.
In CU6 and later, StoreFront is no longer an option in this metainstaller, but it can be installed separately. This will take several minutes. Studio will automatically launch. Ensure the two Controller VMs do not run on the same hypervisor host. Create an anti-affinity rule.
After it loads, click Deliver applications and desktops to your users. In the Introduction page, select An empty, unconfigured site. This reduces the number of pages in this Setup wizard. The other pages will be configured later. Enter a Site Name aka farm name , and click Next. Only administrators see the farm name. In the Databases page, if you are building two Controllers, click Select near the bottom of the same page.
Click Add. Note: the Delivery Controller software must already be installed on that second machine. Then click Save. If you installed Licensing with your Delivery Controller, then simply enter localhost. If the Certificate Authentication appears, select Connect me , and click Confirm.
Then select your license, and click Next. In the Summary page, if your databases are mirrored or in an Availability Group, each database will show high availability servers , and the name of the Mirror server. Click Finish. It will take some time for the site to be created. Change the database names if desired, and click Next.
In the Summary page, click Generate scripts. A folder will open with six scripts. Edit each of the scripts. Near the top of each script are two lines to create the database. Uncomment both lines including the go line. Then save and close the file. Once all of the scripts are edited, you can send them to your DBA.
Then execute the script. Back in Citrix Studio, click the Continue database configuration and Site setup button. In the Summary page, if your databases are mirrored, each database will show high availability servers , and the name of the Mirror server. Verify Database Mirroring If your database is mirrored, when you run asnp citrix.
Second Controller When building the first Delivery Controller, the scripts might have already included the second Delivery Controller. On the second Delivery Controller, install XenDesktop as detailed earlier. Enter the name of the first Delivery Controller, and click OK.
Click Generate scripts. If not mirroring, then the top three scripts need to be sent to a DBA. If mirroring, send all six. On the SQL Server, open one of the.
Then execute the XenDesktop script. Back in Citrix Studio, click OK. You can also test the site again if desired. This can be an internally-signed certificate if the StoreFront server trusts internally-signed certificates. Open a command prompt as administrator. Double-click the certificate you want to bind.
On the Details tab, scroll down to Thumbprint and copy the thumbprint. Remove the special character at the beginning of the thumbprint. Remove the spaces. Make sure the GUID has curly braces on both sides with no space between appid and the left curly brace. If you entered everything correctly, then it should say SSL Certificate successfully added. The Docs article has scripts for monitoring LHC performance. Site will sort itself out and all will work.
If the rebooted DDC is not the elected one, it will not impact any functionality. In that scenario it will take control, however not start LHC and resources would not be available.
The Site database has many more roles than the Logging and Monitoring databases. This script contains common functions that the other scripts use.
This script prompts for the failover partner location FQDN for each database. Providing a blank failover partner removes the failover partner. You can also use the ClearPartner option to remove a partner. Do not set the failover partner to the same location as the principal database server. This script ensures that certain Citrix services are up and running, and then updates those services in the correct order on all Controllers in the site.
Enclose connection string information for each database in quotes. This option speeds up recovery when a high availability event occurs, and is recommended for both single and multi-subnet environments.
Run this script once to add the option. Run the script again to remove it. This is useful if something has gone wrong and a reset is needed. After the reset, you can try again to set the connection strings. Remove the existing Database connections At the Delivery Controller, open PowerShell as Administrator and run the following commands to clear the existing database connections.
Load the Citrix snap-ins asnp Citrix. Run Set-MonitorConfiguration to change the grooming settings. On the Administrators tab, right-click, and click Create Administrator.
In the Administrator and Scope page, Browse to a group e. Citrix Admins that will have permissions to Studio and Director. These groups typically have access to all objects, so select the All scope. Alternatively, you can create a Scope to limit the objects. On the Role page, select a role, and then click Next. Select the All scope.
And click Next. In the Summary page, click Finish. When administrators in the Help Desk role log into Director, all they see is this. To jazz it up a little, add the Help Desk group to the read-only role. In the Scope page, select a scope, and click Next. Then click OK. Now Director will display the dashboard. If desired, you can disable it in Citrix Studio: On the left, go to the Configuration node.
On the right, switch to the Product Support tab. Click End. Click Yes. On the bottom right, click Download trusted root CA certificates.
Extract the downloaded files. Sort the files by date, and double-click the newest. On the General tab, click Install Certificate. In the Certificate Store page, click Browse. If you close your browser and reopen it, and then go to the vCenter URL, there should no longer be any certificate errors. Skip to the Hosting Resource section.
Import vCenter Certificate If the vCenter certificate is valid and trusted, then you can skip to the Hosting Resource section. Get the vCenter certificate. Open a browser and point it to the vCenter URL. On the top right, click the two right arrows to show more tabs, and click Security. On the Security tab, click View certificate. On the Details tab, click Copy to File. In the Export File Format page, either format will work. In the File to Export page, browse to a new file, and click Next.
If your Delivery Controller is Windows R2 or newer, then simply run certlm. For Windows R2, run mmc. Move the Certificates snap-in to the right by highlighting it, and clicking Add.
Select Computer account , and click Next. Select Local computer , and click Finish. Click OK. In the File to Import page, browse to the certificate you saved earlier, and click Next. In the Certificate Store page, click Next. Click OK to acknowledge that the import was successful. Repeat these steps on the second Controller. It is important that you import the certificate on both Controllers before adding the Hosting Resource.
If you open Internet Explorer and browse to the vCenter Server, there should be no certificate errors. Hosting Resources 7. In Studio, expand Configuration and click Hosting. Right-click it, and click Add Connection and Resources. Enter credentials of a service account that can log into vCenter. In the Connection name field, give the connection a name. Typically, this matches the name of the vCenter server. If you are not using Machine Creation Services, and instead only need the vCenter connection for machine power management, change the Create virtual machines using selection to Other Tools.
If you see a message about the vCenter certificate, check the box next to Trust certificate , and click OK. Note: this vCenter certificate thumbprint is stored in the XenDesktop database, and is not updated when the vCenter certificate changes. See CTX Cannot connect to the VCenter server due to a certificate error for instructions on manually updating the database with the new certificate thumbprint. Also see CTX Xendesktop 7. Alternatively, you can import the vCenter certificate to Trusted People on every Controller.
In the Storage Management page, click Browse , and select a vSphere cluster. Select Use storage shared by hypervisors.
If you have sufficient disk space on each ESXi host, also select Optimize temporary data on available local storage. From Mark Syms at XA 7. For maximum flexibility, only select one datastore. To select additional datastores, run this wizard again to create a separate Hosting Resource. If you selected the temporary data on local storage option, on the bottom, click Select , and choose the datastores you want to use for disk caching. By default, all local datastores are selected. Click Next when done.
In the Network page, enter a name for the hosting resource. Since each hosting resource is a combination of vCenter, Cluster, Network, and Datastores, include those names in this field e. Select a network and click Next. If you have multiple datastores for your VDAs, run the wizard again. You can use the existing vCenter connection. This time, select a different datastore. Give it a name that indicates the chosen datastore. Create additional Catalogs for each datastore. You can then combine the Catalogs into a single Delivery Group.
You can cancel the wizard. Go to the downloaded Citrix Licensing If you see the Subscription Advantage Renewal page, make a selection, and click Next. In the Upgrade page, click Upgrade.
If you go to Programs and Features , it should now show version Citrix Licensing On the right, click Authenticate Certificate. Change the selection to Connect me , and click Confirm. Licensing Manager might prompt you to register with Citrix Cloud.
Click the Copy button and then click Register to be take to Citrix Cloud. Click the blue Register button in the middle of the page. Paste in the copied code and then click Continue.
Click Register. Back in the on-premises Licensing Manager, it will eventually show as Registered. Click the arrow next to a license to see when it expires and the number of licenses in use.
If you click the gear icon on the top right… On the Account tab, you can add License Server Administrators. The Update Licenses tab lets you check for license renewals and download them. Enter the LA- license code, and click Show.
Then click Allocate licenses. After licenses are installed, right-click the Licensing node, and click Edit Product Edition Change the edition to match your licenses. Click OK when done. Multi-type licensing at Citrix Docs. Switch to the Usage and Statistics tab and make a selection in the Share usage statistics with Citrix section.
Citrix License Management Service Version At the bottom of this page is a link to change the retention period. In the Installation Type page, select Role-based or feature-based installation. Click Next until you get to the Server Roles page. Check the box next to Remote Desktop Services , and click Next. Click Next until you get to the Role Services page. Check the box next to Remote Desktop Licensing , and click Next.
Click Add Features if prompted. Then finish the wizard to install the role service. The tool should find the local server. If it does not, right-click All servers , click Connect , and type in the name of the local server. Once the local server can be seen in the list, right-click the server and click Activate Server. In the Connection Method page, click Next. In the Company Information page, enter the required information, and click Next.
All of the fields on the Company Information page are optional, so you do not have to enter anything. Since the session hosts will be configured to pull Per User licenses, there is no need to install licenses on the RD Licensing Server.
Ensure you have green check marks. If the person installing Remote Desktop Licensing does not have permissions to add the server to the Terminal Server License Servers group in Active Directory, ask a domain admin to do it manually. If you have the proper permissions, click Add to Group. Click Continue when prompted that you must have Domain Admins privileges. Click OK when prompted that the computer account has been added. Click OK to close the window.
For a list of checks, see About health checks at Citrix Docs. Click Smart Check. If you enabled Smart Tools during the installation of XenDesktop 7. Click Complete Setup. In step 1, click Download Agent. Step 2 indicates it is waiting for you to install the Agent. Check the box next to I accept the terms in the License Agreement , and click Install. Step 2 now shows that the Agent was installed successfully.
Or, if the site is already added to your list of sites, click View Report next to the site. You can add a Custom Check that targets those machines.
At the top right, if you click Perform Check , you can run one of the checks. If you click Configure. You can schedule the checks to automatically run periodically. To view the alerts, click one of the alert badges in the component category. Also see Smart Check alerts reference at Citrix Docs. Expand a component, and click an alert. To view the hidden alerts, at the top right, click the menu icon, and click Show Hidden Alerts.
The hidden alert is grayed out. If you click the alert, you can restore it. Citrix Scout XenDesktop 7. Database Connections. Broker Service.
Core Services. Hypervisor Connections. No special instructions. Ensure the installed licenses a non-expired Subscription Advantage date. In-place upgrade the WEM Server. This is no longer required in WEM and newer.
If the settings are still there, then just click Save Configuration. In-place upgrade the WEM Console. In-place upgrade the WEM Agents. Boost Productivity Support employee well-being Enable a hybrid workforce Transform employee experience. Small business. What is Citrix Workspace? Citrix 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.
Empower every worker with one intelligent, flexible workspace. Support Downloads Community. Success Center Get expert guidance, resources, and step-by-step instructions to navigate your path to the cloud. Cloud Learning Series Learn about cloud planning, deployment, and management so you can get the most from your Citrix Cloud services. Born Digital Lessons for the C-Suite from the next generation of leaders.
Contact us. Sign in. 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. Load management policy settings. Profile management policy settings. Receiver policy settings. Virtual Delivery Agent policy settings.
Virtual IP policy settings. Connector for Configuration Manager policy settings. Multi-type licensing. Universal Windows Platform Apps.
Connections and resources. Local Host Cache. Manage security keys. Connection leasing. Virtual IP and virtual loopback. Delivery Controllers. VDA registration. Use Search in Studio.
User profiles. Citrix Insight Services. Citrix Scout. Session Recording. Get started with Session Recording. Install, upgrade, and uninstall Session Recording. Configure Session Recording. Grant access rights to users. Create and activate recording policies. Create notification messages. Disable or enable recording. Enable or disable live session playback and playback protection. Enable and disable digital signing. Specify where recordings are stored.
Specify file size for recordings. Log administration activities. Install Session Recording with database high availability. View recordings. Troubleshoot Session Recording.
Manage your database records. Configuration Logging. Event logs. Advanced configuration. Monitor deployments. Alerts and notifications. Delegated Administration and Director. Secure Director deployment. Configure network analysis. Troubleshoot user issues. Send messages to users. Restore sessions. Reset a Personal vDisk. Run HDX channel system reports.
Shadow users.
0コメント