Purpose
This document outlines how to import and export LDMS Patch Content/Definitions. This can be useful to know when moving content between LDMS Cores.
Example:
- Export Custom Definitions on one Core, and import for use on a second Core.
- Import new Content from LDMS when testing for detection issues.
Export Content
- In the LDMS Core select Tools | Security and Compliance | Patch and Compliance
- In the Patch and Compliance window select the Content(s) to be exported
- Right click the Content(s) highlighted, and choose Export
- In the Select Export Filename window navigate to the directory you want to save the file to
- The Filename will automatically show the name of one of the selected Content items. You can change the name as needed. Keep the file extension as *.ldms.
- Choose Save
- The Export Status window will display the progress.
- When the Export Status window indicates Done, click Close.
The content is now available as a single *.ldms file that can be copied to other LDMS Cores and imported for use.
Note: If multiple Content items were exported together, they will all exist within a single *.ldms file.
Import Content
- In the LDMS Core select Tools | Security and Compliance | Patch and Compliance
- In the Patch and Compliance window right click the Scan folder and choose Import
Note: Content can be imported into any folder or group by right clicking, but must be set to 'Scan' to be included in a patch scan.
- In the Select File to Import window, set the filter to match your content file's extension.
- Next select the content file to be imported and click Open.
Note: Content Exported from an LDMS core will typically have the extension *.ldms. Content received while troubleshooting a content detection issue will typically have the extension *.xml.
- In the Import Options window select Update and click Import.
- When the Import Status window displays Done, click Close.
The imported content is now available for use within the LDMS Core.