- 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
Deploy a blueprint using existing machines
When deploying blueprints, Smart Tools can either provision and configure new machines or use existing machines that you specify. This topic describes how to deploy a Smart Tools blueprint using existing machines in your environment.
You might need to deploy blueprints with existing machines if:
- You want to use machines in a resource location that Smart Tools does not support such as Microsoft Azure Resource Manager or Nutanix Acropolis.
- You want to use a supported resource location such as AWS or Citrix XenServer, but don’t want to supply credentials or keys to Smart Tools.
- You want to use physical machines in your environment with a blueprint.
Before you can use existing machines with Smart Tools, you must first install the Smart Tools Agent on each machine you want to use with the blueprint you want to deploy. The agent communicates with Smart Tools on port 443, enabling Smart Tools to locate and configure each machine during the blueprint deployment process. Ensure each machine hosting the agent has outbound communication on port 443 enabled.
To install the Smart Tools Agent
- Log on as an administrator user of the machine on which you want to install the agent.
- Log on to the Smart Tools web site using your account credentials.
- From the home page, click Resources & Settings.
- From the Resource Locations page, click Add Resource Location.
- Select Citrix XenServer and click Next. Selecting this option is required only to download the agent; not to specify your resource location.
- Select the machine operating system and bitness (32-bit or 64-bit), if applicable, and click Download Agent. When prompted, save the package.
- Locate the Smart Tools Agent package and launch the installation. During installation, the agent registers the machine with Smart Tools. This can take a few minutes. When the machine is successfully registered, a green check mark appears.
- Click Cancel to close the Add Resource Location dialog.
To use existing machines with a blueprint, the blueprint must include Server steps. These steps appear as machine tiers when you configure the blueprint deployment. For each machine tier, you specify an existing machine. When the blueprint is deployed, Smart Tools uses the specified machines as targets for the other steps in the blueprint, such as installing software or configuring a server role. For more information about Server steps, see the “Server Step” section of About blueprint steps
- From the menu bar, click Smart Build and then point to the blueprint you want to deploy.
- Under Actions, click Actions > Deploy. The blueprint description page appears.
- Click Start deployment setup. The Overview page appears.
- In Deployment Name, enter a friendly name for your deployment and click Next. The Resource Location page appears.
- In Resource Location, select All Existing Machines and then click Next.
- On the Architecture page, select any applicable deployment options and click Next.
- Review the Pre-deployment Checklist to ensure you have the information or resources that will be needed to configure and deploy the blueprint. Click Continue. For more information, see About the pre-deployment checklist.
On the Size page, perform the following actions:
- Select Use existing machines.
- In each machine tier, select a machine from the list. Repeat this step for all machine tiers in the blueprint. Click Next.
- On the Configuration page, enter the configuration parameters for the deployment. For more information about each parameter, click its Help icon. Click Next.
(Optional) Create a deployment profile:
- Enter a friendly name for the profile.
- (Optional) Enter a description.
- Click Save. If you do not want to create a profile, click Cancel.
- On the Summary page, review the options you’ve configured.
- Click Deploy.
After the deployment begins, Smart Tools displays the status of the deployment in the Deployment Details page. The Deployment Details page includes the real-time progress of each step in your blueprint. Depending on machine availability and the complexity of the blueprint, the deployment might take some time to complete, and some blueprint steps might take longer than others.