HP Insight Control - Manual (Page 71)

Windows server migration Source Agent or PINT remote deployment fails with Agent
is already deployed or not required error
When you remotely deploy the Windows server migration Source Agent or PINT from the Insight
Control server migration application station or from Systems Insight Manager, the server migration
Source Agent deployment fails with the error Agent is already deployed or not
required
. In addition, no logs are generated for the agent deployment under the
migration installation folder>\log\AgentLogs\hp\log\source IP\ folder.
Suggested action
Perform one of the following:
• Remove the System_drive\WINDOWS\Temp\hp_sum\RepositoryManager directory on
the Insight Control server migration application station and retry the deployment.
• Manually install the server migration Source Agent or PINT on the source server.
Windows server migration Source Agent or PINT remote deployment is intermittent
and deployment fails with General failure occurred error
When you remotely deploy the Windows server migration Source Agent or PINT from the Insight
Control server migration application station or from Systems Insight Manager, server migration
Source Agent deployment fails with the error General failure occurred. In addition, the
\log\AgentLogs\hp\log\
IP>\timestamp_smp_log.txt file displays the following exception:
Received Target Exception: UnknownException : SoapSession::SoapSession : unknown exception!
No install was run, due to connection error
Suggested action
To resolve this issue, manually install the server migration Source Agent or PINT on the source
server.
Post-migration
Destination server connected to SAN displays a blue screen after boot
When performing a V2P or P2P migration, a destination server connected to the Storage Area
Network (SAN) may display a blue screen after booting the server. This occurs when performing
a migration under all of the following conditions:
• The source server is running Windows Server 2003 without Windows Server 2003 Service
Pack 2 (SP2) installed.
• The source server does not have the Microsoft Storport Storage Driver from Knowledge
Base (KB) article 932755 installed.
• The migration is performed to a destination server connected to a SAN Logical Unit Number
(LUN).
• The SAN fabric zone has multiple paths between the destination server and the SAN storage.
Suggested action
To perform a V2P or P2P migration, the source server must have both of the following installed:
• Windows Server 2003 SP2
• Microsoft Storport Storage Driver from KB article 932755
After downloading and installing Windows Server 2003 SP2 and the Microsoft Storport Storage
Driver from Knowledge Base (KB) 932755 article, perform the V2P or P2P migration.
Post-migration 71