PlateSpin Protect 10.x , 11.x
PlateSpin Forge 3.x, 4.x , 11.x
This article outlines information regarding jobs that have failed at the "Configuring Operating System" stage and the following error message may appear. The information below also is applicable to the "Configure Target Machine" or "Configure Virtual Machine" conversions steps.
NOTE: If you encounter this problem during a Disaster Recovery Restore job, please see TID 7920810
When a conversion fails at this step, you will need to check the following:
- For conversions to virtual machines, connect to the target VM Console using VMware VIC ( VMware Infrastructure Client ) or through the Microsoft Virtual Server Administration page and check the state of the target VM. In most cases, the overall migration is successful and it may still possible to continue with the configuration manually. For example, the job may have just failed/timed out due to an unexpected hardware installation prompt.
NOTE: It is normal for the target VM to perform several reboots during this step in order to complete the configuration process.
- For conversions to target physical machines, check the state of the target physical machine. In most cases, the overall migration is still successful and the job may have failed/timed out due to hardware installation prompts.
NOTE: It is normal for the target physical machine to perform several reboots during this step in order to complete the configuration process.
- The %WINDIR%\PlateSpin\Configuration\Data\log.txt file. Check the last few lines of the log file for any entry stating that the configuration service has completed. If you see this entry then the overall migration was successful. Please see TID 7920902 for additional details on how to clean up the target machine.
- Document any error messages (i.e. Blue screen errors) or warnings ( Screenshots ). Check the Windows Event logs to see if there is any additional information regarding these errors.
- If an error regarding the hal.dll is displayed upon bootup, please see TID 7920326
- If you are able to login to the VM, allow the PlateSpin Configuration service to run for approximately which might take half an hour to an hour. If you are unable to login with a domain account, attempt to log in with a local system account instead.
- For conversions to a virtual machine, ensure that the Virtual Floppy drive and CD Rom drive are set to be connected on power on. PlateSpin requires that a virtual floppy drive and CD Rom drive (for the VMware Tools install) are available in order to complete the configuration step. If the floppy and CD Rom are disabled, re-configure the VM so that they are connected on power on and then reboot the VM. Allow the PlateSpin Configuration service to run and check the log.txt mentioned in point 1 before using the migrated VM.
- Install VMware Tools or Microsoft VM Additions manually once you have had a chance to allow the PlateSpin configuration service to run.
- If the target VM or target physical machine is supposed to be part of a domain and receives errors regarding netlogon (or other similar network errors), try dis-joining and rejoining the domain manually once you are able to login successfully.
- Verify that all data and applications have been properly migrated
- Verify that the target VM/target physical machine has network connectivity and that the network configuration corresponds with what was specified in the Platespin Job Configuration
- For V2V migrations from MS Hyper-V to ESX or vice versa, please ensure that you will remove the Microsoft Virtual Machine Additions (if it is on MSHyper-V) or the VMware Tools (if it is on ESXi/GSX servers) from the source before the conversions. This scenario will cause issues when the Platespin configuration service will try to remove the tools from one vendor while the VM is on an VM platform from a different vendor. This will cause a failure at where the machine is not usable or loads with Microsoft Blue Screen of Death - please see TID 7920178