- Active Directory OUベースのController検出
|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.
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.
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.
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.
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.