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.
The syntax for XPSImport is:
XPSImport input_file [-passphrase phrase] [-validate] [-fo] [-vT] [-vI] [-vW] [-vE] [-vF] [-e file_name] [-l log_path] [-?]
Specifies the input XML file.
(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.
(Optional) Validates the input XML file without updating the database.
Allows force overwrite of existing policy store date for a dump load.
(Optional) Sets verbosity level to TRACE.
(Optional) Sets verbosity level to INFO.
(Optional) Sets verbosity level to WARNING (default).
(Optional) Sets verbosity level to ERROR.
(Optional) Sets verbosity level to FATAL.
(Optional) Outputs a log file to the specified path.
(Optional) Specifies the file to which errors and exceptions are logged. If omitted, stderr is used.
Displays command-line help.
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.
Copyright © 2010 CA. All rights reserved. | Email CA about this topic |