XenDesktop 7, the unattended installation..

XenDesktop 7As an IT Consultant I’m all about automation and orchestration so with the Release To Web of XenDesktop 7 we have a new installation to automate. Luckily the installation of XenDesktop is improved, it’s 7 clicks from start to finish as Stephane has blogged about on Archy.net.

The first thing I opened was the eDocs page to find the unattended installation command lines for XenDesktop 7. The eDocs give a pretty good explanation of the command line switches to be used:

To install core components using the command line From the \x64\XenDesktop Setup directory on the media, run the XenDesktopServerSetup.exe command. The following table describes command options.

Option Description
/help or /h Displays command help.
/quiet No user interface appears during the installation. The only evidence of the installation process is in Windows Task Manager. If this option is omitted, the graphical interface launches.
/noreboot Prevents a restart after installation. (For most core components, a restart is not enabled by default.)
/remove Removes the core components specified with the /components option. For more information about removing components, see Remove components.
/removeall Removes all installed core components. For more information about removing components, see Remove components.
/configure_firewall Opens all ports in the Windows firewall needed by components being installed, if the Windows Firewall Service is running, even if the firewall is not enabled. If you are using a third-party firewall or no firewall, you must manually open the ports.
Controller: TCP 80, 443
Director: TCP 80, 443
License Server: TCP 7279, 8082, 8083, 27000
StoreFront: TCP 80, 443
For complete port information, see CTX101810.
/components component [,component] … (Required.) Comma-separated list of components to install or remove. Valid values are:
CONTROLLER – Controller
LICENSESERVER – Citrix Licensing
If this option is omitted, all components are installed (or removed, if the /remove option is also specified).
/installdir directory Existing empty directory where components will be installed. Default = c:\Program Files\Citrix.
/tempdir directory Directory that holds temporary files during installation. Default = c:\Wndows\Temp.
/nosql Prevents installation of Microsoft SQL Server Express on the server where you are installing the Controller. If this option is omitted, SQL Server Express will be installed.
/enableremoteassistance (Valid only when installing Director.) Enables the Windows Remote Assistance feature. Windows Remote Assistance is always installed when you install Director; you enable or disable the feature by including or omitting this option in the command line.

And there are a couple of examples how to use these switches:



Basically I’ve got the following commands:

License Server

“x64\XenDesktop Setup\XenDesktopServerSetup.exe” /components LICENSESERVER /quiet /noreboot /configure_firewall


“x64\XenDesktop Setup\XenDesktopServerSetup.exe”/components STOREFRONT /quiet /noreboot /configure_firewall

XenDesktop 7 Controller

“x64\XenDesktop Setup\XenDesktopServerSetup.exe”/components CONTROLLER /quiet /noreboot /configure_firewall /nosql

XenDesktop 7 Director

“x64\XenDesktop Setup\XenDesktopServerSetup.exe”/components DESKTOPDIRECTOR /quiet /noreboot /configure_firewall

XenDesktop 7 Studio

“x64\XenDesktop Setup\XenDesktopServerSetup.exe”/components DESKTOPSTUDIO /quiet /noreboot /configure_firewall


I’ve tested these command lines and they worked in my lab environment, of course the components will need some additional configuration but this will give you a good start in automating your XenDesktop 7 deployment.

For example, I’ve searched for the configuration of SF2.0 but there’s only a description for the installation on the eDocs so Citrix is documenting the installation.

Citrix will probably add some powershell commandlets to configure the rest of the stack. The XenDesktop 7 SDK is already released and if you need to script tasks you can create the tasks in Studio and collect the script from the Studio console.


The following two tabs change content below.

Kees Baggerman

Kees Baggerman is a Staff Solutions Architect for End User Computing at Nutanix. Kees has driven numerous Microsoft and Citrix, and RES infrastructures functional/technical designs, migrations, implementations engagements over the years.

Leave a Reply