DS Performance Related Settings

book

Article ID: 181638

calendar_today

Updated On:

Products

Deployment Solution

Issue/Introduction

 

Resolution

Question
Where are the performance related settings for DS located and what do they represent?

Answer

In the Deployment Server Configuration control panel applet.

To open the configuration applet, navigate to Start > All Programs > Altiris > Deployment Solution > Configuration

For Server 2012, it would be under All Apps > Altiris > Deployment Solution > Configuration

 

 

Options

 

 

Update Inventory on active computers:  This setting dictates how often the AClient will send inventory to the DS.  Typically, the setting can be relaxed to 24 hours to free up processing cycles on the DS.  Any time an agent restarts, it will send the inventory.

 

Update active client connections:  This setting dictates how frequently agents update their status to the DS when not executing jobs.  In large environments this setting can be relaxed to approximately 8 hours.

 

Reset inactive connections:  This setting causes agents to break down the TCP session with the DS and re-establish a new session.  When this occurs, inventory will be resent.

 

Encrypt communication between IIS and data manager:  Enables secure connection between the DS engine and IIS for the DS Web console.  This setting does increase overhead on the engine and should only be used when absolutely necessary.

 

 

Engine debug logging:  Increases engine overhead due to cycles being spent on logging activities.  This setting should be disabled unless support is requesting logs.

 

 

Allow encrypted sessions:  Allows agents configured to encrypt communications with the DS to securely communicate with the DS.  This setting increases overhead on the DS Engine and should only be used when absolutely necessary.

 

 

SQL Server

 

A common issue found when troubleshooting DS performance related issues is that the SQL instance is set to dynamically allocate memory.  Dynamically allocating memory to SQL puts the engine in contention with the database for memory resources and most often has an adverse affect on performance.  It is recommended that SQL be statically allocated approximately 60% of the available memory on the server.  The example below is for a server with 2GB of RAM.  1200MB represents 60% of the installed RAM for the server.

 

 

Attachments