Controllerの追加、削除、または移動、またはVDAの移動

To add, remove, or
move a Delivery Controller, you need the following roles or permissions:

Operation

Purpose

Server role

Database role

Database creation

Create suitable empty
database

dbcreator

Schema creation

Create all service-specific
schemas and add first Controller to Site

securityadmin *

db_owner

Add Controller

Add Controller (other than
the first) to the Site

securityadmin *

db_owner

Add Controller (mirror
server)

Add Controller login to the
database server currently in the mirror role of a mirrored database

securityadmin *

Remove Controller

Remove Controller from the
Site

db_owner

Schema update

Apply schema updates or
hotfixes

db_owner

* While
technically more restrictive, in practice, the securityadmin server role should
be treated as equivalent to the sysadmin server role.

When using
Studio to perform these operations, the user account must explicitly be a
member of the sysadmin server role.

If your deployment
uses database mirroring:

Before adding,
removing, or moving a Controller, 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.

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.

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; the 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.

Select Configuration > Controllers in the Studio navigation pane, then select the Controller you want to remove.

Select 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.

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), select
Configuration > Controllers in the Studio
navigation pane, then select the Controller you want to move.

Select
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, select
Join
existing site, and enter the address of the new Site.

Move a VDA to
another Site

If a VDA was provisioned using Provisioning Services or is an existing
image, you can move a VDA to another Site (from Site 1 to Site 2) when
upgrading, or when moving a VDA image that was created in a test Site to a
production Site. VDAs provisioned using Machine Creation Services (MCS) cannot
be moved from one Site to another because MCS does not support changing the
ListOfDDCs a VDA checks to register with a Controller; VDAs provisioned using
MCS always check the ListOfDDCs associated with the Site in which they were
created.

There are two ways
to move a VDA to another site: using the installer or Citrix policies.

Installer: Run
the installer and add a Controller, specifying the FQDN (DNS entry) of a
Controller in Site 2.

Important: Specify Controllers in the installer only when the Controllers
policy setting is not used.

Group Policy
Editor: The following example moves multiple VDAs between Sites.

Create a
policy in Site 1 that contains the following settings, then filter the policy
to the Delivery Group level to initiate a staged VDA migration between the
Sites.

Controllers - containing FQDNs (DNS entries) of one
or more Controllers in Site 2.

Enable auto update of Controllers - set to disabled.

Each VDA in
the Delivery Group is alerted within 90 minutes of the new policy. The VDA
ignores the list of Controllers it receives (because auto-update is disabled);
it selects one of the Controllers specified in the policy, which lists the
Controllers in Site 2.

When the VDA
successfully registers with a Controller in Site 2, it receives the Site 2
ListOfDDCs and policy information, which has auto-update enabled by default.
Since the Controller with which the VDA was registered in Site 1 is not on the
list sent by the Controller in Site 2, the VDA re-registers, choosing among the
Controllers in the Site 2 list. From then on, the VDA is automatically updated
with information from Site 2.