Configuring and troubleshooting AutoDiscover

Article:TECH108669  |  Created: 2003-01-06  |  Updated: 2008-01-05  |  Article URL
Article Type
Technical Solution


How to configure and troubleshoot AutoDiscover.


This article describes the basic configuration of the CCM AutoDiscover service.

Configuring AutoDiscover
The following sections contain information about the AutoDiscover configuration files and settings.

Configuration settings
See additional information in the ON Command CCM 5.1 Installation manual.

Configuration files

Deals with the basic configuration of the AutoDiscover Service. All parameters are set using the default values. Parameters can be changed by deleting the comments character '#' at the beginning of the corresponding line. It is strongly recommend to change the communication method to value 1 = Unicast and use only one server a time. Below is a list of the parameters and what the values mean.
  • debug
    0 = no error search protocol (default)
    1 = error search protocol is presented at the monitor
  • fixed - How should the computer ID of 8 characters be registered?
    0 = creates a random ID (default)
    1 = uses the first eight characters of the computer name
  • log - Activates the protocol level. The value (default) activates a minimal recording.
    1 = a sufficient recording level
    4 = the highest possible recording level
  • port - Assigning the port where AutoDiscover sends its Unicast or Multicast messages. By default port 3114 is being used.
  • timeout - Timeout value in seconds for communication with the CCM Server (default = 600)
  • unicast - Toggles the communication mode with the server
    0 = Multicast (default)
    1 = Unicast
  • check
    0 = Checks if the information in the Applications.cfg is correct (default)
    1 = Errors in the Applications.cfg are ignored.
  • password - Optional password used by AutoDiscover, when logging on the configuration server

Below is an example configuration of Ccmad.cfg:

This data file contains the configuration server, working with AutoDiscover. The recommended communication method is Unicast, and only one server entry. Multiple server entries are only used with multicasting. The specification of the CCM server entry is as follows:
    Server name = IP Address, CCMSiteAdministratorName, Password

For example:
    CCMServer =, siteadmin, adminpass

This data file contains a list of all used system software. The following packages must be listed here:
  • System software
  • RAM disk
  • Service pack
  • Desktop Agent

The file provides example templates which have to be adapted to your needs. Generally they are of the form:

    =packet ID
The current information for RAM disk and Desktop Agent packages is already entered at the install time of AutoDiscover. This configuration data file should be modified to integrate new AutoDiscover clients. Missing packages lead to a forced stopping of the AutoDiscover service when it tries to start. In this way, the administrator is notified of problem with the configuration. The starting routine verifies:
  • Whether at least one RAM disk is present in the Database
  • Whether at least one Desktop Agent is present in the Database
  • Whether at least one system software is present in the Database

The service is stopped if one of the above conditions is not fulfilled. To integrate a client successfully, all the dependencies of all the packages must be resolved.

This file is an extension of the Systems.cfg file. It is meant to recognize and create application entries at integration time. Unlike the Systems.cfg, this data file should not be modified when no applications are intended to be recognized. The format of an application entry is as follows:
    Acrobat Reader 5.0 (English) = aread01e.050

The application name before the equal sign must be formatted as listed and named in the Registry Uninstall string:


The second half, after the equal sign, refers to the CCM internal applications packet ID (as in the folder name of \ccm\config\sw). All the dependencies of all the packages should be respected (all the packets listed in the Dependency loop should be listed in Applications.cfg).

The DiscoverApps.dat file is directly dependent on the Applications.cfg file from the AutoDiscover service. This file is used for applications that have to be registered with a client and do not possess an entry in the Registry key:

These applications cannot be recognized by the AutoDiscover agent, but may be enforced if described in the DiscoverApps.dat file.

The following fact should be noted about the DiscoverApps.dat:
    • The DiscoverApps.dat does not replace the Applications.cfg.
    • All entries in this file must refer to an equivalent entry in the Applications.cfg.
    • Entries in this data file do not complement or add to Applications.cfg, but merely use the Applications.cfg file as a reference.
    • The applications are entered using the same name as already defined in the Applications.cfg, but without a package ID.
    • System software packages, Desktop Agents, or RAM Disks must not be entered into this file.

A new client is using WinZip and the User Profile Manager needs to be autointegrated with it. WinZip has an own entry in the Registry but the User Profile Manager does not.

ONWards is used to integrate the client in cooperative mode into CCM. Autodetection of applications is active. The Agent installs and scans the computer registry's uninstall section.The scan result is compared to the Applications.cfg, and all mapped applications are forwarded to the server for processing. The information in the Discoverapps.dat file is forcefully appended. In this case, Win Zip is recognized from the Uninstall section, mapped to the referenced package in the Applications.cfg file, and autointegrated. The UPM Application is read out of the Discoverapps.dat file as if it was written to the registry, mapped to the referenced package in the Applications.cfg, and autointegrated.

Error Analysis
On the Server
The console mode is used for troubleshooting AutoDiscover. Starting the console mode is done as follows:

To start console mode
  1. Click Start > Run.
  2. In the Run dialog box type:

  3. Browse to the \ccm\config\services\autodiscover directory.
  4. Type the following command at the command prompt:

    ccmad –s console –verbose

You can create a batch file to do this and run it as follows to generate a log:

    ccmadj.bat > auto.txt
All the entered applications and system software packets are listed as well as information about their availability in the auto.txt file.

On the Client
The AutoDiscover Agent log is meant for error analysis or recording part of the program flow.

Manual installation of the CCM AutoDiscover Service on the server

To install AutoDiscover
  1. Click Start > Run.
  2. In the Run dialog box type:

  3. Browse to the  \ccm\config\services\autodiscover folder.
  4. At the command line type:

    ccmad –s install
The \ccm\config\dbin\ccm.bat file must be modified to enable autostart of AutoDiscover with the other CCM related services.

To modify the ccm.bat file
  1. Open the Ccm.bat file in a text editor.
  2. Locate the entry similar to the following:

    set STARTINSTALLEDSERVICES=rm ad da po pa wi no pr
  3. Add the string 'au' for AutoDiscover so that it looks like:

    set STARTINSTALLEDSERVICES=rm ad da po pa wi no pr au
  4. Save your changes and close the file.

To uninstall AutoDiscover
  1. Click Start > Run.
  2. In the Run dialog box type:

  3. Browse to the  \ccm\config\services\autodiscover folder.
  4. At the command line type:

    ccmad -s remove

Legacy ID


Article URL

Terms of use for this information are found in Legal Notices