Metalogix ControlPoint is installed and runs as a .NET application. It is installed into an existing Web application, and it creates a separate Service database (xcAdmin) for configuration information and analysis data. This Service database may be installed either on the same database server as all other SharePoint databases or on a separate server.
NOTE: You can install ControlPoint on any Web front-end server machine in your farm. It is recommended, however, that you install ControlPoint on the machine on which you want to run the most resource-intensive ControlPoint processes. The machine name of the server on which you install ControlPoint is the name that ControlPoint will use by default as the farm name in the ControlPoint application interface. You can, however, change the display name of the farm at a later time.
Native Kit Components
The Native Kit consists of the following three folders:
·Release Documents - Contains the set of installation and user documentation for ControlPoint.
·Solutions Artifacts - Contains the solution (.wsp) files that contain the core functionality of ControlPoint; it may also include the Visual Studios symbol (.pdb) files that are used by the MSOCAF code analysis framework.
·Installation Scripts - Contains the command files, parameter files, executables, and dlls necessary to support the installation process itself. The two most critical components in this folder are the following file :
§ManualDeploymentParams.cmd, which contains the parameters that configure the installation
§ManualDeployment.cmd, which contains the script that carries out the installation.
Before You Begin
·For the first farm on which you are installing ControlPoint, make sure the machine on which you are installing ControlPoint has access to the Internet, which is necessary to permit activation of your ControlPoint license.
NOTE: If the machine on which ControlPoint is installed does not have Internet access, you can request a license file from Metalogix.
Have the following information ready (you may wish to record it in the spaces provided):
·The URL of the Web Application into which ControlPoint will be installed (For example, if a load balancer is used, the load balancer URL should be entered; if the load balancer performs SSL decryption, the SSL version of the URL should be entered.)
Web App URL _______________________________________________________________________
·The managed path where you want to create the ControlPoint Configuration Site Collection to be created (most Web applications have /sites available, and that is the default value for this parameter.)
Web Application Managed Path ______________________________________________________
·The email address of the primary ControlPoint Administrator. (This will act as the "from" account for email correspondence sent on behalf of ControlPoint)
ControlPoint Administrator Account Email Address ______________________________________
·The domain account that will become the Site Collection Administrator for the ControlPoint Configuration Site Collection.
It is recommended that you use an Active Directory-based name and allow the initial script to add the Windows-Claims prefix for that account. You can add FBA-based or other Claims-based identities to the Site Collection Administrator's list later.
Site Collection Administrator Account _______________________________________________
·The domain account to be used to install ControlPoint
ControlPoint Installation Account ___________________________________________________
The application pool account for the Web application where the ControlPoint Configuration Site Collection will be installed
·Web App Application Pool Account _______________________________________________
The Name of the SQL server that will host the ControlPoint Service database, as well as the authentication method to be used
·Database Server Name: __________________________
·SQL Server ID ___________________________ Password _______________________________