To add, remove, or move a Delivery Controller, you need the following roles or permissions:
||Create suitable empty database
||Create all service-specific schemas and add first Controller to Site
||Add Controller (other than the first) to the Site
|Add Controller (mirror server)
||Add Controller login to the database server currently in the mirror role of a mirrored database
||Remove Controller from the Site
||Apply schema updates or hotfixes
* While technically more restrictive, in practice, the securityadmin server role should be treated as equivalent to the sysadmin server role.
When using Desktop Studio to perform these operations, the user account must explicitly be a member of the sysadmin server role.
Before adding, removing, or moving a Controller, if your deployment uses database mirroring, ensure that the principal and mirrored databases are both running. In addition, if you are using scripts with SQL Server Management Studio, enable SQLCMD mode before executing the scripts. To verify mirroring after adding, removing, or moving a Controller, run the get-configdbconnection PowerShell cmdlet to ensure that the Failover Partner has been set in the connection string to the mirror.
After you add, remove, or move a Controller:
- If auto-update is enabled, the Virtual Delivery Agents (VDAs) will receive an updated list of Controllers within 90 minutes.
- If auto-update is not enabled, ensure that the Controller policy setting or ListOfDDCs registry key are updated for all VDAs. After moving a Controller to another Site, update the policy setting or registry key on both Sites.
To add a Controller
You cannot add servers installed with an earlier version of this software to a Site that was created with this version.
- On the server you want to add, run the installer and select the Delivery Controller and any other core components you want to install.
- In Studio, click Join existing deployment and enter the Site address.
To remove a Controller
Removing a Controller does not uninstall the Citrix software or any other component; it removes the Controller from the Database so that it can no longer be used to broker connections and perform other tasks. If you remove a Controller, you can later add it back to the same Site or to another Site. A Site requires at least one Controller, so you cannot remove the last one listed in Studio.
Note: Make sure that the Controller is powered on so that Studio loads in less than one hour. Once Studio loads the Controller you want to remove, power off the Controller when prompted to do so.
When you remove a Controller from a Site, the Controller logon to the database server is not removed. This avoids potentially removing a logon that is used by other products' services on the same machine. The logon must be removed manually if it is no longer required; securityadmin server role permission is needed to remove the logon.
Important: Do not remove the Controller from Active Directory until after you remove it from the Site.
- In Studio, select Configuration > Controllers in the left pane, then select the Controller you want to remove.
- Click Remove Controller in the Actions pane. If you do not have the correct database roles and permissions, you are offered the option of generating a script that allows your database administrator to remove the Controller for you.
- You might need to remove the Controller’s machine account from the database server. Before doing this, check that another service is not using the account.
After using Studio to remove a Controller, traffic to that Controller might linger for a short amount of time to ensure proper completion of current tasks. If you want to force the removal of a Controller in a very short time, Citrix recommends you shut down the server where it was installed, or remove that server from Active Directory. Then, restart the other Controllers on the Site to ensure no further communication with the removed Controller.
To move a Controller to another Site
You cannot move a Controller to a Site that was created with an earlier version of this software.
- On the Site where the Controller is currently located (the old Site), in Studio, select Configuration > Controllers in the left pane, then select the Controller you want to move.
- Click Remove Controller in the Actions pane. If you do not have the correct database roles and permissions, you are offered the option of generating a script that allows your database administrator to remove the Controller for you. A Site requires at least one Controller, so you cannot remove the last one listed in Studio.
- On the Controller you are moving, open Studio, reset the services when prompted, click Join existing site, and enter the address of the new site.