This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.
BMC Client Management
BMC Client Management 9.1, 9.0, 10.0, 11.5, 11.1, 11.0, 10.1, 12.X All
- What can I do to help improve the performance of Client Management?
- The Client Management application can be SQL intensive. Therefore, it is very important to make sure that the database server is not overburdened.
- The Client Management master server can perform many small file disk reads and writes provided the physical hard drive is on a fast RPM drive. In addition, a balanced SAN can help performance.
- If the Client Management server and its database are installed on the same machine, a multi-core CPU will help with parallel processing.
- Ideally a physical database server should be used instead of a virtual machine. There are no specific issues related to a virtual machine environment, however with a virtual environment a drop in performance will be noticed compared to an actual server. This is because with virtual machines, the processor, drives, memory, bus speed, and other components are being shared, and cannot be dedicated to one specific virtual session.
Because the Client Management agent performs a large number of small file reads and writes, real-time file scans performed by security software (for example, anti-virus, anti-malware, or anti-spyware software) can cause performance to be slowed while these file scans are taking place, particularly on relay servers or the master server. Adding an exclusion to the security software's real time scanning engine is often helpful in improving the performance of the Client Management agent. Please note that the exclusions described below should be entered only for the real time scanning component; these locations should still be scanned on a schedule (preferably during times when few users are active).
Real time scan exclusion suggestions:
- The Client Management agent directory - Excluding the entire directory where the Client Management agent is installed (typically \Program Files\BMC Software\Client Management\Client\ or \Program Files\BMC Software\Client Management\Master\) is typically easiest, and as the files distributed to clients (such as software packages, or patch updates) would be scanned by the scheduled AV scanner on the master server, and are checksummed the security risk is minimal. Specifically, the scheduled scans on the master would detect any potential threats when the package is published to the master, and the checksum ensures that a threat can't be inserted after this publication of the package/patch.
- Exclusions by sub-directory under agent folder - In cases where excluding the entire agent directory is not possible, excluding the directories which contain the most frequently accessed files. Excluding the directories listed below should provide most of the performance improvements which would be seen when excluding the entire agent directory.
- \data\Vision64Database\filestorefiles\ (only applicable to master server)
- \data\Vision64Database\index\ (only applicable to master server)
- \data\Vision64Database\patches\ (only applicable to master server)
- \data\Vision64Database\packages\ (only applicable to master server)
- \log\AssetDiscovery\ (only applicable to Asset Discovery scanners)
- \data\OSDeployment\ (only applicable to OS Deployment managers)1
- c:\pxetftp\ (only applicable to OS Deployment managers)
- Exclusions by file type - In environments where adding an exclusion by directory is not possible, excluding the following file types from real time scanning would improve performance when compared to the same environment with no exclusions, however, as the Client Management agent regularly handles files which do not have an extension (for example, files sent by an agent containing inventory data), these would still be scanned with the extension-based exclusion.
- *.sqlite and *.sqlite3 files
- *.xml files
- *.ini files
- *.chl files
- *.wim files(only applicable to OS Deployment managers)
There are several steps that can be taken to try and improve performance. However, before beginning please ensure that you have a working backup of the database.
- Create a Backup:
Before backing up the Client Management database, if possible have everyone close out of any Client Management consoles. In addition, stop the Client Management Agent service on the master. (this is not required in most cases)
NOTE: If you do not have SQL Management Studio and their query tools, download SQL Server Management Studio Express. The installation will provide these tools and will allow you to manage any SQL Server 2005 or 2008 or 2012 database. If you download this, follow the backup steps under the "Client Management running against SQL Server 2005" section below.
- Client Management running against SQL Server 2005/2008/2012:
- Open SQL Server Management Studio on the existing Client Management SQL 2005 database server.
- Login as SA or an SA equivalent account.
- Expand the Databases folder.
- Right-click the database that you would like to backup and select Tasks -> Back Up.
- If a file path already appears in the "Destination" window at the bottom, take note of the path and name of the backup file that will be created and skip down to step i.
If a file path does not exist in the window, click the Add button and continue with the steps below.
- Click the ellipse button to the right of the "File name" field.
- In the "File name" field at the bottom of the "Locate Database Files" window, enter the desired backup file name. This will be the name of the backup file once the backup is complete. Take note of the path where the backup file will be created.
- Click Ok Locate Database Files window and then click Ok to close the "Select Backup Destination" window.
- Click Ok to begin the backup.
- Click Ok once the backup is completed successfully.
Rebuild the database indexes:
NOTE: It is recommended that this procedure be run at a slower time of the day, or even after hours since the re-building of the indexes could take several minutes to complete.
- Download the attached file DM_Maintenance_SQL.zip that can be used to re-build the indexes of all Client Management tables.
- Extract the file in the zip to the Client Management SQL server.
- Run SQL Server Query Analyzer (SQL 2000) or SQL Management Studio (SQL 2005/2008/2012).
NOTE: If you do not have SQL Server Enterprise Manager or SQL SQL Management Studio and their query tools, download Microsoft SQL Server Management Studio Express for 32-bit or 64-bit systems. The installation will provide these tools and will allow you to manage any SQL Server 2005 or 2008/2012 database.
- Login as an SA equivalent account and open a new query window.
- Copy the SQL script from the file that was extracted earlier into the new query window.
- Make sure the correct Client Management database is selected at the top, and then press F5 or click the "Execute" button in SQL 2005/2008/2012 at the top to execute the script.
- Once the script completes, which could take several minutes, close the query tool.
Backup the SQL Transaction log and Shrink the File:
SQL Server 2005 and 2008:
- On the SQL Server, or a machine that has the database administration tools installed, start SQL Server Management Studio.
- Connect to the Client Management database server and login with an SA equivalent account.
- Right-click the database and select Tasks -> Back Up.
- Take note of the recovery model of the database. If it is set to FULL or Bulk-Logged, select "Transaction Log" for the Backup Type. If the recovery model of the database is set to SIMPLE, this will not be available.
- Click Ok to begin the transaction log backup.
NOTE: A full backup must have been done prior to backing up the transaction log, or the backup will fail.
- Once the backup is complete, click Ok.
- Next, right-click the database and select Tasks -> Shrink -> Files.
- Select "Log" from the File Type drop down list, and then click Ok.
Database Maintenance Plans
To help keep your database optimized as much as possible, a Maintenance Plan can be setup in SQL Server Management Studio and Enterprise Manager. Although database maintenance is really a database administration function that should be handled by an experienced database administrator, the following information should help to get you started. For further help with database maintenance tasks, please refer to the SQL Server documentation:
- SQL 2005/2008/2012
- On the database server, open SQL Server Management Studio.
- Login to the database server with an SA equivalent account.
- Under the database server name, expand the Management folder.
- Right-click Maintenance Plans and then select Maintenance Plan Wizard.
NOTE: If you receive an error in regards to "Agent XPs", please run the following SQL command in a new query window to enable Agent XPs:
sp_configure 'show advanced options', 1;
sp_configure 'Agent XPs', 1;
- On the first screen, click Next.
- Enter a name for the plan and description if desired.
- If you are logged in as a user that has database administration rights, you may leave the Use Windows Authentication option enabled. Otherwise, change to Use SQL Server Authentication and enter the SA user's credentials.
- Click Next and then enable the following maintenance tasks (make sure they are configured in this order):
- Once they are set, along with any others that you would like to enable, click Next.
- On the next screen, you may change the order in which these tasks execute. Once finished, clickNext.
- The next few screens will allow you to choose the current Client Management database for each database maintenance task. Select the current database and then click Next for each screen.
- When the schedule screen appears, click the Change button to define the schedule for the maintenance plan.
- On the last two screens, click Next and then Finish.