Previous Topic: Replace Policy Data

Next Topic: Troubleshooting Policy Data Transfer

XPSImport

The XPSImport tool supports the following tasks for migrating policy store data:

Note: XPSImport does not import keys into the key store. You must use smkeyimport for this purpose.

Syntax

The syntax for XPSImport is:

XPSImport input_file [-passphrase phrase] [-validate] [-fo] [-vT] [-vI] [-vW] [-vE] [-vF] [-e file_name] [-l log_path] [-?]

Parameters

input_file

Specifies the input XML file.

-passphrase phrase

(Optional) Specifies the passphrase required for decryption of sensitive data. The phrase must be the same as the phrase specified during export, or the decryption will fail.

-validate

(Optional) Validates the input XML file without updating the database.

-fo

Allows force overwrite of existing policy store date for a dump load.

-vT

(Optional) Sets verbosity level to TRACE.

-vI

(Optional) Sets verbosity level to INFO.

-vW

(Optional) Sets verbosity level to WARNING (default).

-vE

(Optional) Sets verbosity level to ERROR.

-vF

(Optional) Sets verbosity level to FATAL.

-l log_path

(Optional) Outputs a log file to the specified path.

-e file_name

(Optional) Specifies the file to which errors and exceptions are logged. If omitted, stderr is used.

-?

Displays command-line help.

Example

XPSImport PolicyData.xml -e C:\\tmp\\ExceptionLog.txt 

This example imports policy data objects as specified in the PolicyData.xml file. It is not immediately evident from the command line if the import is a dump load or a granular import. That information can however be retrieved by looking at the IsDumpExport attribute of <PolicyData> element in the input XML file. If this attribute is set to true, it indicates that the input XML file has to be used for dump load.