When using the Service Desk Remote Components Installer to create the MS SQL Server MDB, what is actually installed on the Server?
search cancel

When using the Service Desk Remote Components Installer to create the MS SQL Server MDB, what is actually installed on the Server?


Article ID: 54571


Updated On:


CA IT Asset Manager CA Software Asset Manager (CA SAM) ASSET PORTFOLIO MGMT- SERVER SUPPORT AUTOMATION- SERVER CA Service Desk Manager - Unified Self Service CA Service Desk Manager CA Service Management - Asset Portfolio Management CA Service Management - Service Desk Manager


This article has information on how the Remote Components Install does on the DBMS Server.


Release: ALL
Component: CA Service Desk


When you click "Install Remote Components" from the Remote Components Install Wizard, a Javaw.exe process would be launched from JAVA_HOME\bin.

A Log for service desk remote MDB installation is created in %temp%\ca_service_desk_remote_setup_XXXXXX.log

Initialization steps:

  1. Remote components will check the source of its installation.

  2. It will use the Java components from the install media to launch the java interface of remote components and hence use this path as root directory.

  3. Check the existence of EIAM on the server.

Database Queries:

  1. Windows will search for osql.exe. This query to search for osql.exe would happen in all the paths defined in <path>

  2. It will use the one defined in the installation directory of sql
    ...\Program Files\Microsoft SQL Server\80\Tools\Binn\osql.exe

  3. OSQL.exe would query sql to verify the following but is not limited to

    1. SQL version

    2. Version of windows and Service pack level on which SQL is installed.

    3. membership of the "logged in" user.
  4. Query on the MS SQL installation directory to determine space requirements. If the drive has sufficient space then it would add the mount point to ...\Program Files\Microsoft SQL Server\MSSQL

After Verifying the system requirements to be sufficient for Remote components to run successfully it will start the process to create MDB.

  1. Run mdb setup command from E:\winsrvr.nt\mdb\mssql\setupmdb.bat
    ( media )

  2. Determine the DBMS type , DBMS instance, Set MDB name as MDB

  3. Set the source directory of MDB as E:\winsrvr.nt\mdb\mssql\setupmdb.bat and destination as %temp%\mdb . This is done as the files would be copied to %temp%\mdb

  4. The following files would be copied to %temp% directory from the media ( ..\winsrvr.nt\mdb\mssql ) in the order mentioned below:

    Create folder MDB and copy the contents as below:






    CumulativePatch < folder >

  5. Creates a 0 byte file called mdb_mssql.sql in %temp%\MDB .

    Reads data from %temp%\mdb\DDL\mdb_mssql.sql and writes to %temp%\MDB\mdb_mssql.sql

    Reads data from %temp%\mdb\mdb_mssql.sql and writes to ..\Mssql\data\mdb_log.LDF , mdb.mdf

  6. MDB is created in the above step after verifying the preexistence of MDB.

  7. Install cumulative patches on MDB by running %temp%\mdb\CumulativePatch\PatchMDB.bat

  8. Verifies the pre-existence of each patch and install andif not present else skips that MDB patch.
    The MDB patches are changes to the MDB schema.

  9. Creates a user ServiceDesk in database and Grants database roles to 'ServiceDesk'.


  10. Setting up MDB is complete , Servicedesk user in database is create and roles were added to Servicedesk to allow access to MDB.

  11. add_user.exe invoked from E:\winsrvr.nt\java\bin

  12. add_user.exe ServiceDesk <password> is executed to create a user called " ServiceDesk " in local machine.

Installation of remote components would not install any software on the database server nor make any registry changes apart from registry changes that are required to perform the above steps. For example creating a local user would change a few registry settings to create a shell, logon etc for that user.