|
|
Configuration Overview
Exporter Pro was designed for easy and flexible configuration. There are two primary components to Exporter Pro's configuration:
Configuration File - The configuration file stores all of the settings that control exporting: For example, whether logging is enabled, what information is being exported (ie services, disk space, etc.), and the output files to export to. The configuration file uses the standard format for Windows initialization (.INI) files, and are recommended to have an .INI file extension. You may create as many configuration files as you require, each with its own set of exporting options and properties.
Object File - The object file contains a list of objects that will be exported. Each export configuration is associated with one object file. The information in an object file is stored in a tab-delimited format, and can be created and managed externally if desired. By default, object files have a .DAT file extension. See the File Formats topic for specific formatting information.
The other file components used by Exporter Pro are used to store specialized template information for registry, WMI, File/Directory, and Active Directory exporting. These files and their purposes are:
Registry Template (RegTemplates.CFG) - The registry template file contains a list of defined registry templates that can be selected for use in any export configuration.
Active Directory Query Templates (DirectoryQueries.CFG) - The Active Directory (AD) query file contains a list of defined AD queries that can be selected for use in any export configuration.
Active Directory Schema (DirectorySchema.CFG) - The AD schema file is used for constructing a list of common attributes for use in building AD queries.
WMI Query Templates (WmiQueries.CFG) - The WMI query file contains a list of defined WMI query templates that can be selected for use in any export configuration.
File and Directory Templates (FileTemplates.CFG) - The file and directory template file contains all of the defined templates for exporting file and directory information.
Creating a New Configuration
To create a new configuration, select Configuration->New... from the menu, or click the New Configuration toolbar button to display the Create New Configuration File dialog:
Configuration Name - Enter in a meaningful name for the configuration. This name will be displayed in Exporter Pro's main window title bar.
Configuration File Name - Enter in a name and optionally the directory path to the file that will be used to store the configuration settings. This file will be automatically created if it does not already exist.
Object File Name - Enter in a name and optionally the directory path to the file that will be used to store the list of objects which will be exported. This file will be automatically created if it does not already exist.
Click OK.
Note: If you are unsure of the names to
use for these options, enter the name of your company, for example,
'AMCORP'
Opening an Existing Configuration
To open an existing configuration, either select Configuration->Open... from the menu, or click the Open Configuration toolbar button. Prior configurations that have been opened are also available on the Recent File List on the Configuration menu.
Deleting an Existing Configuration
To delete an existing configuration, simply delete the associated .INI file. By default, these files can be found in the Export Pro installation directory.
Changing Configuration File Locations
To change the names or locations of the object file, or registry/Active Directory template files, select Configuration->Properties->File Locations...
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.
More information about this error may be available in the server error log.
Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.