Prerequisites for installation with Remote mdb database
- SQL client connectivity
- SQL Management Tools
- Logged on to Domain Manager with a Windows account with Local Administrator Rights on the SQL Server
- The account used in # 3 must have SQL Server Role "SYSADMIN" assigned to it
1. On the Domain Manager, install the SQL Client and the SQL Management Tools by running setup.exe from the SQL installation media.
Check the boxes next to "Client Tools Connectivity" and "Management Tools - complete" and click next and follow prompts:
You should get a message once the install completes like this
2. Verify that the account performing the install is listed in the local administrators group on the SQL server,
This is done by going to "Start -->Administrative Tools -->Computer Management-->expand "Local users and Computers" -->Groups -->
Double click on "Administrators" make sure the account running setup of CA Client Automation is listed specifically, if not add it.
3. Go to SQL Management Studio and go under "Server Roles" double click on SYSADMIN make sure that the Windows account
who is running setup of Client Automation is assigned the SQL Server Role "SYSAMDIN" if not add it.
Steps to install a CA Client Automation Domain Manager
Run Setup.exe from the root of the CA Client Automation DVD # 1 and choose to "Run this installation in English" or Applicable Language
Choose the first option - Install CA ITCM. In this scenario it is not necessary to do a separate 'Install MDB', it will be installed
automatically to the remote SQL server in the steps that follow:
Scroll down and accept the license agreement
Select the Options that are Applicable for your Environment and select Next>
Choose Custom Installation and click Next>
Select Domain Manager and any other Options that are applicable for your Environment and click Next>
Management Database Provider - Choose Microsoft SQL Server
Management Database Server - this is where MSSQL is running and you should enter the Fully Qualified Domain Name (FQDN) of the SQL Server.
MDB Username - ca_itrm is the main SQL account for CA Client Automation
MDB Password and Confirm Password - the default password for this account is NOT_changedR11 but you can specify your own as desired. Be sure the password meets the server's password complexity requirements
On the Configure Microsoft SQL Server MDB screen enter the required fields as needed
Compatibility mode- Check this if you are going to be using this as a shared mdb database with other CA Products.
This installs all tables to ensure other CA products will function correctly.
MDB Database - Leave as mdb
MDB Instance Name - If connecting to a named instance of MSSQL specify the name of that instance. If connecting to the default instance leave as "default".
DB Port Number - Specify the port utilized by SQL Server this should match what you setup in the SQL Connectivity Tools.
Import Software Signatures during installation - specify if the installation should import the signatures or not.
Click Next> after configuring this screen.
On the Configure the Scalability Server Screen enter the name of the local Domain Manager, this is usually picked up by the Installer
On the Configure Agent Screen leave Scalability Server the name of the Domain Manager and click Next>
On the Configure CA IT Client Manager
Choose to accept the default install path shown or click on Advanced and choose the desired path and or different
drive letter and click on Next>
Review the details on the Installer Summary page and click Next>
The installer will begin installing the MDB to the remote sql server followed by the manager components on the
local application server.
The Install Summary screen appears review it for possible errors and make sure all installed correctly and click Next>
The Installer will now start up the DSM Services and will complete
Post install steps to verify the installation Complete Successfully
- Run camstat to verify that CAM is running
- Open a command prompt and run CAF STATUS and verify all CAF plugins are started
- Open the DSM Explorer and make sure that it launches successfully