This is the built-in help made by Microsoft for the command 'Import-IscsiTargetServerConfiguration', in PowerShell version 5 - as retrieved from
Windows version 'Microsoft Windows Server 2012 R2 Standard' PowerShell help files on 2016-06-23.
For PowerShell version 3 and up, where you have Update-Help, this command was run just before creating the web pages from the help files.
Imports an iSCSI Target Server configuration.
Import-IscsiTargetServerConfiguration [-Filename] <String> [[-ComputerName] <String>] [[-Credential] <String>] [-Force] [<CommonParameters>]
The Import-IscsiTargetServerConfiguration cmdlet imports a Microsoft iSCSI Target Server configuration.
The configuration information includes the following:
-- If you exported the configuration from a clustered iSCSI Target Server instance, the resource group name.
-- If the cmdlet imports the configuration into an iSCSI Target Server clustered instance, the name of the resource group into which to import the configuration. This
resource group name is the same as the iSCSI virtual disk attribute named MigrationResourceGroup.
-- The following attributes for each iSCSI target that iSCSI Target Server hosts: Enabled (target state), HostName, TargetIQN, Description, ResourceGroup,
MigrationResourceGroup, EnforceIdleTimeoutDetection, FirstBurstLength, MaxBurstLength, MaxRecvDataSegmentLength, NumRecvBuffers, EnableCHAP, CHAPUserName, EnableReverseCHAP,
ReverseCHAPUserName, InitiatorIDs, and LunMappings.
-- The following attributes for each iSCSI virtual disk that iSCSI Target Server recognizes: DiskId, Type, Enabled, DevicePath, ParentPath, Description, SnapshotStorageSize,
MigrationDevicePath, MigrationParentPath, and MigrationResourceGroup.
MigrationParentPath and ParentPath always have a value of null.
Before you import a configuration, perform the following tasks:
-- Move the files for all the virtual disks that are eligible for migration from the source server to the destination server. If there are any file path changes, note the
source to destination changes.
-- In a cluster configuration, ensure that the destination path of the file copy is on a cluster disk and that the cluster disk has been assigned to the desired iSCSI Target
Server resource group, which you created on the destination cluster. Note the resource group that owns the path.
-- If the file paths have changed between the source and the destination servers, open the exported configuration .xml file in a text editor, and identify the
MigrationDevicePath tags to change to reflect the changes.
-- In a cluster configuration, if the file path or the resource group name have changed between the source server and the destination server, open the exported configuration
xml file in a text editor, and identify the MigrationResourceGroup tags to change to reflect the new resource group.
After you import a configuration, perform the following tasks:
-- You must manually reconfigure the forward and reverse Challenge Handshake Authentication Protocol (CHAP) secret keys.
-- Because importing does not include logical unit (LU) snapshot information, you must take necessary snapshots.
-- Manually apply any iSNS settings that are relevant to the new configuration.
-- Manually apply any iSCSI target portal settings that are relevant to the new configuration.
Online Version: http://go.microsoft.com/fwlink/?LinkID=294066
Example 1: Import configuration into the current computer or cluster
PS C:\>Import-IscsiTargetServerConfiguration -Filename "D:\ServerConfig78.xml"
This command imports the iSCSI Target Server configuration of a standalone iSCSI Target Server or clustered iSCSI Target Servers from a specified file. The cmdlet imports
into the current standalone computer or the current clustered node.
Example 2: Import configuration into a specified computer or cluster
PS C:\>Import-IscsiTargetServerConfiguration -Filename "D:\ServerConfig78.xml" –ComputerName "TargetServer09.Contoso.com"
This command imports the iSCSI Target Server configuration of a standalone iSCSI Target Server or clustered iSCSI Target Servers from a specified file. The command imports
the servers into the specified remote standalone computer or remote clustered node.