- General requirements
- Port requirements
- Firewall requirements
- Proxy requirements
- Share debug log files with Citrix Support
- 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:
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 auto-install
Citrix Smart Tools includes an auto-install function that automatically installs the agent on new and existing servers in your resource location. On Linux, inbound access over port 22 (SSH) is required for agent auto-install. On Windows, inbound access over port 3389 (RDP) is required for agent auto-install.
After the agent is installed, you can shut down these ports (if required) as further communication between your servers and Citrix Smart Tools occurs over port 443 (outbound HTTPS) only. For more information, see the Smart Tools Agent section.
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 Automatic Agent installation on Citrix XenServer provisioned VMs
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.
Share debug log files with Citrix Support
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.
To send the agent log files to Citrix Support:
- Log in to the server that is unable to connect to Citrix Smart Tools.
- On Linux, go to: /opt/citrix/lifecycle-management
On Windows, go to: C:\Program Files (x86)\Citrix\LifecycleManagement
- Copy the connector.log file to your local machine, for example:
cp connector.log log.txt
copy connector.log log.txt
- Send the log.txt file to firstname.lastname@example.org.