Previous Topic: XPSExportNext 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 [-pass <passphrase>] [-npass] [-validate] [-fo] [-vT] [-vI] [-vW] [-vE] [-vF] [-e file_name] [-l log_path] [-?]

Parameters

input_file

Specifies the input XML file.

-q

(Optional) Suppresses progress messages.

-m <number>[%]

(Optional) Indicates that progress messages are output after every <number> of objects.

If the optional percent sign ("%") is included, then <number> is a percentage of the total objects, not a number of objects.

Default: 10%.

-pass <passphrase>

(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.

-npass

(Optional) Specifies that no passphrase is to be used.

Important! Sensitive data is imported as clear text.

-validateOnly

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

-schemaFile

Specifies the schema file to validate the input file. If this option is not specified then input file will not be validated.

-fo

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

-?

Displays command-line help.

-nb

(Optional) Averts the beeps on error.

-vT

(Optional) Sets the verbosity level to TRACE.

-vI

(Optional) Sets the verbosity level to INFO.

-vW

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

-vE

(Optional) Sets the verbosity level to ERROR.

-vF

(Optional) Sets the verbosity level to FATAL.

-l log_file

(Optional) Outputs log to the specified file.

-e err_file

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

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.