HP Insight Control - Manual (Page 158)

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 Insight Control server migration
Installation Folder\log\AgentLogs\hp\log\source IP\
folder.
To resolve this issue, 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 occured 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 occured. In addition, the Insight Control
server migration Installation Folder\log\AgentLogs\hp\log\source
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
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 1
(SP1) or 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.
To perform a V2P or P2P migration, the source server must have both of the following installed:
•
Windows Server 2003 SP1 or Windows Server 2003 SP2
•
Microsoft Storport Storage Driver from KB article 932755
After downloading and installing Windows Server 2003 SP1 or Windows Server 2003 SP2 and the Microsoft
Storport Storage Driver from Knowledge Base (KB) 932755 article, perform the V2P or P2P migration.
A PSP installation after an X2P migration of Windows 2000 Server to a server with the Emulex
LPe1105-HP 4Gb FC HBA might cause a blue screen on the destination server
A SAN migration of Windows 2000 Server or Advanced Server (with SP4) to a destination server with the
Emulex LPe1105-HP 4Gb FC HBA might cause a blue screen on the destination server. This can happen if
you select automatic installation of PSP during step 6 of the Migration Wizard or if you manually installed
PSP without immediately installing the latest Emulex boot from SAN HBA driver for Windows 2000 Server.
To resolve this issue:
158 Troubleshooting