For a secondary site, the wizard performs a smaller set of tasks than is performed for a primary site, including establishing a connection to the primary site and creating the IIS virtual directory for the secondary site.
-
The authorization server information you use for this secondary site must match what you used for the primary site.
-
You must ensure the secondary scheduler server is set to use the same Config Service as the primary server. For example, SDxConfigService.
-
The application pool identity for the secondary site must be a valid user on the computer that hosts the Config Service. This could either be a domain account or a common local user. Use Internet Information Services (IIS) Manager to update the application pool identity, if necessary.
-
If you use a domain service account as the identity to run the application pool for the secondary site, you must set the UseSPNIdentityForWCF property on the site's Settings node in Server Manager to True. (For sites on Update 21 and earlier, you must edit the Server Manager web.config file for the site and set the UseSPNIdentityForWCF key to the value True. By default, this file is located in the Server folder within the site's directory structure.) If you do not use a domain service account as the identity for the application pool, you can leave this value False.