This guide contains detailed information about configuring and managing the ControlPoint application.
The Metalogix ControlPoint Administration Guide is intended for ControlPoint Application Administrators (that is, SharePoint administrators who also have responsibilities for managing ControlPoint configuration and permissions).
Once the ControlPoint application has been installed and configured on the first Web front-end server in your SharePoint farm, you can perform the following tasks as needed:
·Configure ControlPoint for each additional Web front-end server in your farm (both when installing ControlPoint for the first time and whenever a new Web front-end server has been added to your farm).
·Set up host headers and/or alternate access mappings (for load balancing).
·If you use alternate authentication providers in your farm, configure ControlPoint to recognize them.
REMINDER: Each farm in a multi-farm installation has its own copy of the ControlPoint application. Therefore, if you have installed ControlPoint on multiple farms, you must perform the entire configuration and setup process for each farm.
If you have more than one Web front-end server in your farm, SharePoint automatically propagates the ControlPoint application to all of them. However, you must perform the following tasks manually on each additional Web front-end server:
·Install the appropriate version of the NET Framework. From the installation folder, run prerequisites.exe.
NOTE: It is important that additional Web front-end servers run with the version of prerequisites provided by Metalogix. Refer to the topic Installing and Deploying ControlPoint in the ControlPoint Installation and Upgrade Guide for more information on prerequisites.
·Create an IIS Virtual Directory, as described below.
NOTE: SharePoint automatically propagates the ControlPoint application to all Web front end servers; however, it only creates the IIS Virtual Directory on the machine on which ControlPoint was installed. Included with ControlPoint is a utility called CreateVirtDirectory.exe to help automate this process. Alternatively, you can create the IIS Virtual Directory manually. Consult your Microsoft Server documentation for details, as the procedure varies based on the version of IIS Manager you are running.
To create an IIS Virtual Directory on an additional front-end server using the Create Virtual Directory utility:
1 Open the IIS Manager on the additional Web front-end server.
2Verify that SharePoint has propagated the ControlPoint website, as indicated by its presence in the IIS of the server).
NOTE: The amount of time it takes for SharePoint to propagate the ControlPoint website to additional Web front-end servers depends on a number of factors, including the size of your farm.
3On the front end server where the ControlPoint application was initially installed, go to the following directory: C:\Program Files\Metalogix\ControlPoint\ControlPointFeature
4Copy the file CreateVirtDirectory.exe to any location on the additional front-end server, then double-click to run it.
NOTE: If you are running Windows Server 2008, it may be necessary to "Run as Administrator."
5Repeat Steps 1-4 for each additional front-end server in your farm.
Enabling Session Affinity for Load Balancing
If the ControlPoint application is to be accessed behind a load balancer, Session Affinity (Sticky Sessions) should be enabled for the ControlPoint Web Application. Otherwise, ControlPoint analyses may fail to complete. (Note that the method for enabling Site Affinity will vary, depending on your load balancer).
If you set up a host header for the Web application that hosts the ControlPoint Configuration Site collection, use the same procedure as you would any other SharePoint Web application. After setting up the host header, it is recommended that you change the Value of the ControlPoint Configuration Setting INBOUNDCONTROLURL from the default value to the host header name.