At one of my customers there was a question to deploy the Cloud Gateway Express unattended. To do so we first have to install the prerequisites, from the eDocs:

Before the components are installed, the .NET Framework 3.5.1 Features > .NET Framework 3.5.1 feature and the Web Server (IIS) role are deployed, and the following role services are enabled if they are not already configured on the server.

• Web Server > Common HTTP Features > Static Content, Default Document, HTTP Errors, HTTP Redirection
• Web Server > Application Development > ASP.NET, .NET Extensibility, ISAPI Extensions, ISAPI Filters
• Web Server > Health and Diagnostics > HTTP Logging
• Web Server > Security > Windows Authentication, Request Filtering
• Management Tools > IIS Management Console, IIS Management Scripts and Tools
• Management Tools > IIS 6 Management Compatibility > IIS 6 Metabase Compatibility, IIS 6 WMI Compatibility, IIS 6 Scripting Tools

These features can be installed via Powershell:

[codesyntax lang=”powershell”]

Import-Module ServerManager

Add-WindowsFeature as-net-framework

[/codesyntax]

[codesyntax lang=”powershell”]

Import-Module Servermanager

Add-WindowsFeature Web-Server

Add-WindowsFeature Web-Asp-Net

Add-WindowsFeature Web-Windows-Auth

Add-WindowsFeature Web-Metabase

Add-WindowsFeature AS-NET-Framework

Add-WindowsFeature Web-Common-Http

Add-WindowsFeature Web-Static-Content

Add-WindowsFeature Web-Default-Doc

Add-WindowsFeature Web-Dir-Browsing

Add-WindowsFeature Web-Http-Errors

Add-WindowsFeature Web-Http-Redirect

Add-WindowsFeature Web-App-Dev

Add-WindowsFeature Web-Asp-Net

Add-WindowsFeature Web-Net-Ext

Add-WindowsFeature Web-ISAPI-Ext

Add-WindowsFeature Web-ISAPI-Filter

Add-WindowsFeature Web-Health

Add-WindowsFeature Web-Http-Logging

Add-WindowsFeature Web-Security

Add-WindowsFeature Web-Basic-Auth

Add-WindowsFeature Web-Windows-Auth

Add-WindowsFeature Web-Digest-Auth

Add-WindowsFeature Web-Client-Auth

Add-WindowsFeature Web-Cert-Auth

Add-WindowsFeature Web-Url-Auth

Add-WindowsFeature Web-Filtering

Add-WindowsFeature Web-IP-Security

Add-WindowsFeature Web-Performance

Add-WindowsFeature Web-Stat-Compression

Add-WindowsFeature Web-Dyn-Compression

Add-WindowsFeature Web-Mgmt-Tools

Add-WindowsFeature Web-Mgmt-Console

Add-WindowsFeature Web-Scripting-Tools

Add-WindowsFeature Web-Mgmt-Service

Add-WindowsFeature Web-Mgmt-Compat

Add-WindowsFeature Web-Metabase

Add-WindowsFeature Web-WMI

Add-WindowsFeature Web-Lgcy-Scripting

Add-WindowsFeature Web-Lgcy-Mgmt-Console

[/codesyntax]

And the installation of the Citrix Receiver Storefront can be made unattended by using the following command line:

[codesyntax lang=”dos”]

CitrixReceiverStorefront-x64 -silent

[/codesyntax]

Next phase is to configure the Cloud Gateway Express but because I’m joining an existing Server Group I have to find a way to create an Authorization Code in order to join the existing Server Group.

To join an existing server group

1. If the Citrix Receiver Storefront management console is not already open after installation of Receiver Storefront, click Start > All Programs > Citrix > Citrix Receiver Storefront.
2. In the results pane of the Citrix Receiver Storefront management console, click Join existing server group.
3.  Log on to the primary server in the Receiver Storefront deployment that you wish to join and open the Citrix Receiver Storefront management console. Select the Server Group node in the left pane of the console and, in the Actions pane, click Add Server. Make a note of the authorization code that is displayed.
4. Return to the secondary server and specify the name of the primary server in the existing server deployment that you wish to join. Enter the authorization code obtained from that server and click Join.
5. Once the new server has joined the deployment, return to the primary server and, in the left pane of the Citrix Receiver Storefront management console, select the Server Group node. In the Actionspane, click Propagate Changes.The configurations of all the secondary servers in the deployment, including the new server you just added, are updated to match the configuration of the primary server.

The new secondary server is added to your deployment and all servers in the group are updated with details of the new server.

To manage your multiple server deployment, use only the Citrix Receiver Storefront management console on the primary server. Any configuration changes you make on the primary server must be propagated to the secondary servers to ensure a consistent configuration across the deployment.

As you can see the current eDocs don’t really mention this way of deployment so when I get more information on how to configure the Cloud Gateway Express I will add this to this blogpost.