- What's new in Smart Tools
- Known issues
- About Citrix Cloud and Citrix Smart Tools
- Technical Security Overview for Citrix Smart Tools
- Open source attribution
- System Requirements
- Get Started
- Smart Tools Agent
- About blueprints and the Blueprint Designer
- About blueprint steps
- About scripts
- Add a new script
- Use named parameters in scripts
- Reference attachments in scripts
- Create a blueprint
- Provision VMs for your blueprint with the Server step
- Use Amazon EC2 APIs in your blueprint with the EC2 Generic Step
- Add conditional actions to your blueprint with the Conditional step
- Add server volumes to your blueprint with the Mount Volume step
- Register or unregister DNS subdomains
- Chain blueprint step outputs and inputs
- Create references to scripts and blueprints
- View and modify blueprints and scripts
- Publish a blueprint
- Clone a blueprint
- Share a blueprint or script
- About Smart Check
- About health checks
- Add a Site to Smart Check
- Discover a Site in Smart Check
- Perform health checks for your XenApp and XenDesktop Site
- Use custom checks and alerts with Smart Check
- View reports from health checks
- Manage Smart Check alerts and notifications
- Upload Site diagnostics to Citrix Technical Support
- View or modify a Site in Smart Check
- JSON format objects reference
- Smart Scale
- Smart Migrate
- Resource Locations
- Prepare Windows Server VM templates for deploying blueprints
- About the Checks and Blueprints catalog and Library
- About deployment profiles
- About the Pre-deployment Checklist
- Deploy a blueprint using existing machines
- Deploy a blueprint to a Citrix XenServer resource location
- Set static IP addresses for XenServer VM templates
- Deploy a blueprint to a Citrix CloudPlatform resource location
- Deploy a blueprint to a VMware vSphere resource location
- Set a static IP address for OVA files using VMware vSphere
- Deploy a blueprint to a Microsoft Hyper-V Server resource location
- Hyper-V VM prerequisite configurations
- Deploy a blueprint to Microsoft Azure Classic resource location
- Deploy a blueprint to an Amazon Web Services resource location
- Preparing Windows-based custom AMIs for Smart Tools
- Rerun a blueprint step during a deployment error
- Pause or cancel a deployment
- Deploy a script
Deploy Citrix Solutions Blueprints
- Deploy Citrix Solutions blueprints using existing machines
- Create a XenApp and XenDesktop production deployment on Microsoft Azure Classic
- Create a XenApp and XenDesktop production deployment on AWS
- Create a XenApp and XenDesktop production deployment with Provisioning Services on Citrix XenServer and VMware vSphere
- Deploy the Simple XenApp and XenDesktop Proof of Concept blueprint on Microsoft Azure Classic
- Deploy the Simple XenApp and XenDesktop Proof of Concept blueprint to AWS
- Deploy the XenApp and XenDesktop Proof of Concept blueprint on Citrix XenServer
- Deploy the XenApp and XenDesktop Proof of Concept blueprint on Microsoft Azure Classic
- Deploy the XenApp and XenDesktop Proof of Concept blueprint with NetScaler to AWS
- Deploy XenApp with the Secure Browser Service
- Deploy the XenMobile Enterprise or Advanced Edition blueprint
- Deploy the XenMobile MDM Edition blueprint
Deploy Resource Locations for Citrix Cloud
- Deploy the XenApp and XenDesktop Resource Location Setup blueprint on Citrix XenServer
- Deploy the XenApp and XenDesktop Resource Location Setup blueprint on Microsoft Azure Classic
- Deploy the XenApp and XenDesktop Resource Location Setup blueprint on AWS
- Deploy the XenApp and XenDesktop Resource Location Setup blueprint with an existing domain on AWS
- Manage Deployments
- Accounts and users
- REST API
- Troubleshoot agent connectivity issues
- Troubleshoot agent download and installation issues
- Troubleshoot blueprint creation issues
- Troubleshoot blueprint deployment issues
- Troubleshoot Site onboarding issues
- Troubleshoot removing Sites from Smart Tools
- Troubleshoot Smart Scale events
- Troubleshoot XenApp 6.x farm migration issues
Ensure you have a DHCP server in your network environment for dynamic IP and DNS address assignments. Some resource locations or blueprints do not support using static IP addresses for VMs.
Configure dynamic IP and DNS addressing for Internet Protocol Version 4 (IPv4) to obtain IP and DNS addresses automatically from the DHCP server. To do this, perform the following actions:
- Click Start > Control Panel > Network and Internet > Network and Sharing Center.
- From the left pane, click Change adapter settings, right-click the network adapter and select Properties.
- Select Internet Protocol Version 4 (IPv4) and then click Properties.
On the General tab, verify the Obtain an IP address automatically and Obtain DNS server address automatically settings are selected.
Note: Smart Tools supports Internet Protocol version 4 (IPv4) only. Internet Protocol Version 6 (IPV6) is not supported.
- On Windows systems, verify the password for the local Administrator account does not require changing: From Computer Management > System Tools > Local Users and Groups, under Administrator Properties, ensure that the User must change password at next logon option is not selected.
- Ensure that the machines in your resource location are connected to the Internet. Some blueprints need to download ISO images, support files, or other software during the deployment process.
The Citrix Smart Tools Agent requires access over port 443 (outbound HTTPS) across the Internet to the following domains:
Alternatively, you can allow access to the following public IP addresses:
- 126.96.36.199/24 subnet (or 188.8.131.52 to 184.108.40.206)
Important: Citrix recommends using the domains listed above as public IPs are subject to change. If you choose to use the public IP addresses instead, visit status.cloud.com and subscribe to Citrix Cloud notifications to stay informed of future updates to these IP addresses.
Ensure the machines hosting the Smart Tools Agent are able to resolve external DNS names. Communication between your server and Citrix Smart Tools occurs over port 443 (outbound HTTPS) only.
On Windows, ensure that the Remote Desktop Protocol (RDP) service is enabled and TCP 3389 port is not blocked by a firewall.
Port requirement for agent installation
Citrix Smart Tools includes a function that can install the agent automatically on new servers in your resource location. To do this on Linux servers, inbound access over port 22 (SSH) is required. On Windows servers, inbound access over port 3389 (RDP) is required.
After the agent is installed, you can shut down these ports if needed as further communication between your servers and Citrix Smart Tools occurs over port 443 (outbound HTTPS) only. For more information, see About agents in Smart Tools.
For Citrix XenServer resource locations: If a Windows machine acts as a connector, ensure that Windows Management Instrumentation (WMI) and inbound connections on TCP port 135 (DCOM port) are enabled on your Windows VM template. If a Linux machine acts as a connector, ensure that Remote Desktop Services and inbound connections on TCP port 3389 are enabled on your Windows VM template. For more information, see the section “Automatic Agent installation on Citrix XenServer provisioned VMs” in Install or remove the Smart Tools Agent
Ensure that the firewall allows SSL traffic from your servers to the Citrix Smart Tools domains (specified in the Port requirements section) over port 443 (outbound HTTPS).
If your resource location is behind a proxy, the Smart Tools Agent requires a pass-through connection to the proxy server. For more information about configuring proxy settings for the Smart Tools Agent, see Use the Citrix Smart Tools Agent behind a proxy.
Note: The agent does not work with HTTPS proxy content inspection on the SSL session. If the proxy has content inspection, set up a rule on the proxy to pass traffic from the servers where the agent is installed.
If your servers do not appear in the Citrix Smart Tools user interface (UI) after installing the agent, contact Citrix customer support. The Citrix customer support team may request a copy of the agent log files to debug the problem.
- Log in to the server that is unable to connect to Citrix Smart Tools.
- Navigate to the log file location:
- On Linux: /opt/citrix/lifecycle-management
- On Windows: C:\Program Files (x86)\Citrix\LifecycleManagement
- Copy the connector.logfile to your local machine:
- On Linux: cp connector.log log.txt
- On Windows: copy connector.log log.txt
- Send the log.txt file to