Share via

Metabase Import/Export Behavior

  • Article

Applies To: Windows Server 2003, Windows Server 2003 with SP1

When using the metabase import/export feature, you need to be aware of the following behaviors with which the feature operates:

  • If you attempt to import a property to a computer whose metabase schema file does not include the property, the import process continues, but errors are logged in Event Viewer. If you are using a script or application to perform the import, the script or application issues a warning.

  • If the key type of any imported metabase element does not match the destination element, an error occurs.

  • If you use a script or application that uses the inherited option, inherited settings are imported and applied to the top element. If you do not use the inherited option, only the elements that are explicitly set are imported.

  • If you import configuration data by using a script or application and you use the merge flag, existing elements are not overwritten, and new ones are added. If you do not use the merge flag, existing elements are deleted or overwritten.