NetConfig XML Format

The following is an example NetConfig.xml file:

NetConfig.xml is an XML file and must adhere to the XML constructs.

• The first line is the XML processing instruction and must be present for the XML parser (msxml3.dll) to recognize the file contents

• The <resources> tag envelopes the entire contents and is considered the top-level tag. It serves no purpose other than ‘containing’ all the file contents. XML requires a top-level tag

• The <group> tag specifies the group to which the computer is assigned. The <group> tag must be present, but it may have the same ‘name’ attribute as the <domain> tag

• The <domain> tag specifies the domains and the <computer> tag specifies the computers within that domain.

• If the <domain> tag is empty (does not contain any <computer> tags), then all computers within that domain will be discovered and tracked

• If a <computer> tag exists, it must reside within a <domain> tag

• If a <computer> tag exists within a specified domain, then all computers NOT specified under that <domain> tag would NOT be discovered and tracked

• The ‘name’ attribute must be specified for each tag (<group>, <domain>, and <computer>), otherwise that tag will be ignored

• The <domain> ‘name’ attribute must be an exact match, but the comparison is case-insensitive

• The <computer> ‘name’ attribute can be an exact match (also case-insensitive comparison), but it can also include a wild card * prefix or suffix (see above example). This is a wild card to help reduce the number of computer entries in the file. In the above example, the “name=JOHN*” attribute signifies that all computers that start with JOHN in the YOURDOMAIN domain will be discovered and tracked

• A <computer> tag cannot contain a prefix and a suffix in the same ’name’ attribute. If both are used in the same ‘name’ attribute, that <computer> tag entry will be ignored. Also, in the above example, the “name=PETE” attribute does not have a wildcard character, therefore, there must be a computer named PETE (case insensitive) in the YOURDOMAIN domain on the network for it to be discovered and tracked

• Finally, in the above example, a <domain> tag exists that does NOT contain any <computer> tags.  In this case, all workstations in the MYDOMAIN domain will be discovered and tracked

The Control Center also uses the NetConfig.xml file to ‘store’ additional data associated with each computer when exiting the console. This data is read back in upon the next invocation of the console. The data is stored under each <computer> tag with a <data> tag. The <data> does not need to be present, but it will automatically be generated and maintained by the Control Center.

The DelayedSettings.xml file also utilizes the same format. This file utilizes a second tag <setting> under the <computer> tag. This tag is used to store specific setting information for the computer. Currently, the attribute ‘file’ within the <setting> tag is used to determine what Client configuration settings file to copy to the computer.  

Note: the DelayedSettings.xml file is administered by the Control Center and does not need to be edited manually. This discussion is provided for informational purposes only.

Related Topics:

Knowledge Base

Technical Support