Product Documentation

Smart Tools concepts

Important: This topic describes deprecated functions or concepts and will be removed from the documentation. For more information about deprecated functions in Smart Tools, see What’s New in Citrix Smart Tools.


A basic billing entity that contains users. For example, an account may be in the name of an organization and authorized employees may be added as users of the account.


A description of how to deploy and manage an application or service. A blueprint captures deployment topology, software, platform components, configuration, and workflow of the deployment process. It also captures how to recover from failure and the process to tear down a deployment. A blueprint can contain built-in steps, scripts, and other blueprints. Additionally, blueprints can include configuration options that prompt users to make choices (for example, add a StoreFront server to a XenDesktop deployment) or supply additional information (for example, domain credentials) which Smart Tools uses when the blueprint is deployed.

Blueprint Catalog

Contains blueprints that are available to all Smart Tools users. To deploy or modify a blueprint, users first add the blueprint from the catalog to their account.

Blueprint Designer

The user interface for creating and editing blueprints. In the Blueprint Designer, a blueprint is displayed as a series of steps that Smart Tools will execute in sequence when the blueprint is deployed. The Blueprint Designer displays tools for creating a new blueprint such as built-in steps and any blueprints or scripts that are stored or shared in the Library. The Blueprint Designer also provides options for adding information in tooltips, specifying recommended configurations for provisioned VMs, and specifying user-supplied information that Smart Tools uses when the blueprint is deployed (for example, file locations for installation media).

built-in step

An out-of-the-box automation step that can be included in blueprints to perform specific functions such as provisioning a server, rebooting a server, or creating a snapshot. Built-in steps are added to a blueprint using the Blueprint Designer.

Citrix Smart Tools Agent

A lightweight software package that is installed on servers that Smart Tools monitors and manages. Smart Tools installs the agent automatically when it deploys new VMs for a blueprint. Users can install the agent manually on existing machines to add them to Smart Tools. The agent is installed on Linux servers over inbound port 22 (SSH) and on Windows servers over inbound port 3389 (RDP). After installation, communication between the servers and Smart Tools occurs over outbound port 443 (HTTPS).


A server that communicates with Smart Tools and also has access to a virtualization instance or cloud resource location behind a firewall. The machine acting as a connector is only needed if the virtualization instance or cloud resource location cannot be accessed over the Internet. To configure a server to act as a connector, install the Citrix Smart Tools Agent on the server. After the agent is installed, the server can be selected and promoted to act as a connector during the process of configuring a new resource location.

deployment profile

Blueprint configuration settings that are saved from a previous blueprint deployment. Deployment profiles enable you to reuse your current deployment settings in the event you want to deploy the blueprint again to the same resource location.


A user’s personal space for storing blueprints and scripts that the user creates, adds from a catalog, or that are shared by other users. Users must add blueprints to their library before those blueprints can be deployed.

resource location

An instance of a virtualization platform, a private cloud, or a public cloud that serves as the location for deploying blueprints. Smart Tools supports several types of resource locations; see Resource location requirements.


A member of one or more accounts. When a user is a member of multiple accounts, the user can be assigned a different role in each account. For example, a user with an Administrator role on Account A might have the Architect role when logging on to Account B.