Object Manager - External Object Lists

 

External Object File Support

 

Note: For General information about Hyena's Object Manager, click here.

 

Managing a large collection of objects (hundreds or thousands of entries) in Object Manager can be a bit cumbersome.  Object Manager supports "external" object lists that can be used to break the Object Manager listing into a more manageable size.  External object lists can be stored anywhere, including a network location.

 

Creating an External Object List Reference in Object Manager

 

To create a link to an external object list:

External Object List File Format

 

The format for external object lists follows the same format as the main Object Manager file, which is always named ad_objects.dat.  Hyena stores and maintains this file either in the designated storage location as specified under Tools->Settings->General, or by default, in the active user's profile directory.  Please note that the ad_objects.dat file stored in the Hyena installation directory is NOT generally used after installation. 

 

If a large set of objects are already stored in the main ad_objects.dat file, and it is desired to move these objects into a separate external object file, follow these steps:

 

IMPORTANT: First, create a backup of the existing ad_objects.dat file.

NOTE: The individual items in the file are separated by the TAB character.

 

To create an external object file manually, or by an external program, use this guide for the individual fields.  Again, the fields must all be TAB delimited.  The field order for both the main Object Manager file and External Object Listings is shown below.  Note that all fields must be present in the file, unless noted otherwise below.

 

1. Object ID - This field is not currently used for External Object lists.  Nesting of objects is not currently supported.  This field should be set to a '0'.

 

2. Object Parent ID - This field is not currently used for External Object lists.  Nesting of objects is not currently supported.  This field should be set to a '0'.

 

3. Object Type - The object type is used to indicate the type of object, for example a workstation or printer.  Use the following table as a guide when setting this value.  This value must be one of the following numeric codes:

 

99 - Windows (NT) Domain

101 - Windows 2000 Domain

113 - Windows 2000 Domain Controller
114 - Active Directory Organizational Unit

33 - Server (any operating system version)

24 - Workstation (any operating system version)

9 - Printer

52 - External Object List

86 - Directory Path
37 - Registry Key

23 - Local Workstation

89 - URL

46 - Enterprise Networking
61 - Switch

62 - Host

 

4. Reserved - Set this value to '1'

 

5. Object Name - Used for the display name in Hyena's GUI for the object.

 

6. Object Comment - Optional, used for the comment

 

7. Object Path - Used to specify the path to the object.  See the Object Manager documentation on how to format the path depending upon the Object Type.

 

8. Object 'Server' (optional) - The server field is used only for domain objects as a mechanism to reference a specific server.  See the Object Manager documentation on when and how to use this field.  Since this is the last field in the file, it can be left blank.

 

Note: Additional External Object Lists can be referenced within an External Object List (IE you can nest External Object Lists inside one another).

 

 

 

Hyena opens and reads the contents of external object files as needed.  Therefore, the file can be modified while Hyena is opened.  To refresh any objects from an external object list, simply collapse and expand the list.  Microsoft Excel can be used to directly read and write to the external object file as long as the file is saved as a TAB delimited text file.