How to change the Client Management database password

Version 10
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    BMC Client Management


    COMPONENT:

    Client Management


    APPLIES TO:

    BMC Client Management All Versions



    PROBLEM:

    How do I change the database password used by the Client Management master server?


    CAUSE:

    Product does not include a utility for changing the DB Password due to the number of unique DB Server types and connection methods.


    SOLUTION:

     

       
      
      This article details the method to alter the DB login password for Microsoft SQL when using a direct connection.  Connections to alternate database platforms (Oracle or PostgreSQL) are similar however require different methods for setting the password on the Database Server, contact your DBA for assistance).

    Instructions:
     
      
      
      1) Stop the Client Management Master Server service

    2) Update the SQL login used by Client Management:
      
       
    •     
          Login to Microsoft SQL Management Studio   
    •  
    •     
          Expand the Client Management database tables dialog to view the table names  
    •  
    •     
          Note the schema name that prefixes each Client Management Table  
    •  
    •     
          If the table names do not start with bcmdbuser. we must change line 3 in the query below to match the DB Schema before executing the query!   
    •  
    •     
          Right click on the Client Management database DB name and select "New Query"  
    •  
    •     
          Past the following query, alter line 3 (if needed), alter line 5 to the desired password, then execute the query:  
      
      exec sp_change_users_login
      
              @Action = 'Auto_Fix', 
              @UserNamePattern = 'bcmdbuser', 
              @LoginName = null, 
              @Password ='Bcmuser@06' 
      
       
      
      UserName and Schema Example
      
      3) Update the Client Management Configuration file to use the new password
      
       
    •     
          On the Master Server open the following file for edit:  
    •  
    •     
          C:\Program Files\BMC Software\Client Management\Master\config\Vision64Database.ini  
    •  
    •     
          Update this file to use New password by removing the previously encrypted password from the PasswordENC= entry  
    •  
    •     
          Populate the Password= value with the clear text password defined in Step 2  
    •  
    •     
          Example Vision64Database.ini:  (Highlighted values indicate the changes required)  
      
      [Database]
    ; Section for database settings.
    ; The database connection type. This can be Postgres, ODBC,
    ; ODBCDirect, ORACLE or DB2. The value is not case-sensitive.
     
    DatabaseType=odbcdirect
     
    ; The database name. The value is interpreted based on the type:
    ;
    ; Postgres: The name of the database.
    ; ODBC: The name of the DSN which should be correctly configured already.
    ; ODBCDirect: The ODBC driver connection string which is DBMS dependent ; and something like the following:
    ;
    ; Driver={SQL Server};Server=MyServerName;Database=myDatabaseName;Uid=myUsername;Pwd=myPassword
    ; Driver={Oracle ODBC Driver};Dbq=myDBName;Uid=myUsername;Pwd=myPassword
    ;
    ; If the Uid and Pwd are not specified they are taken from the User and
    ; Password settings in this file.
    ; ORACLE: DatabaseName is the service name specified in tnsnames.ora
    ; Login and password used are in User and password field.
    ; DB2: DatabaseName is the name of the database, user the system login.
    DatabaseName=Driver={SQL Server};Server=MySQLServerl\MyInstance;Database=bcmdb
     
    ; The host name where the DBMS is running. Ignored for ODBCDirect, Oracle and DB2.
    Host=
     
    ; The connection port. Only avalaible for postgres database.
    Port=
     
    ; The user id to use for loggin on to the DBMS.
    User=bcmdbuser
     
    ; The clear text password to use with the user login. If supplied, this
    ; gets encrypted and stored as PasswordEnc. The Password field is then
    ; deleted.
    Password=Bmcuser@06
     
    ; If true, we drop our current connection if there's an SQL error on
    ; it. If false, we handle the error by printing the status but then keep the
    ; connection.
    DropConnectionOnError=true
     
    ; Comma-separated list of prioritary operations to perform.
    ; Possible values can include: SoftwareInventory, HardwareInventory, CustomInventory
    ; or EventManagerEvent
    FileTypePriority=EventManagerEvent,PatchInventory2,PatchUpload,PackagerZipPackage
     
    ; If true, assignment are sent in a pre-5.2 compatible way
     LegacyAssignments=false
     
    ; Used to define the maximum number of Retry and the gap between each of them,
    ; should the connection to the database be unavailable
    RetryMax=5
    RetryGap=10
    PasswordEnc=
      
        
      
       
    •     
          Start the Master Server Service  
    •  
    •     
          Monitor the mtxagent.log file to verify the database connection is working properly.  
      
      **Note: On Service Startup if the Password= value is populated with the clear text password, the following events will occur automatically:
      
       
    •     
          The clear text password value will be read  
    •  
    •     
          The password will be encrypted by the application  
    •  
    •     
          The configuration file is updated to remove clear text password value for Password=  
    •  
    •     
          The new Encrypted Password is written to the PasswordENC= entry   
      
        

     


    Article Number:

    000346028


    Article Type:

    Solutions to a Product Problem



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles