dylmurph
September 27, 2023, 2:12pm
1
Hi,
Currently trying to virtualise one of our physical server running Windows Server 2008 R2 using MVMC. Unfortunately, i’m being met with the below error. Does anyone know what could be causing this? Mentions an error with the Secure Support Channel.
Thanks,
Dylan
ca4e6609-d6d5-4107-b9b7-43fe8469946f-MVMC_Error.txt (20.5 KB)
3 Spice ups
Hello,
It seems like you’re encountering an issue with the Secure Support Channel while trying to virtualize a Windows Server 2008 R2 using Microsoft Virtual Machine Converter (MVMC). This error could be caused by various factors. Here are some steps you can take to troubleshoot the issue:
Check Network Connectivity :
Ensure that the physical server and the machine where MVMC is installed have proper network connectivity.
Confirm that there are no firewall rules blocking communication between the source and target machines.
Verify Credentials :
Make sure that you’re using valid and correct credentials with appropriate administrative privileges for both the source physical server and the target virtualization platform.
Time Synchronization :
Ensure that the system times on both the source and target machines are synchronized. Time discrepancies can sometimes cause authentication issues.
DNS Resolution :
Verify that DNS is working correctly on both the source and target systems. Ensure they can resolve each other’s hostnames.
Check for Duplicate Names or SIDs :
If you’ve already created a virtual machine with the same name on the target platform, it could cause conflicts. Try using a different name.
Reset Secure Channel :
On the source machine (Windows Server 2008 R2), you can try to reset the secure channel using the following command in an elevated command prompt:
netdom resetpwd /s:<target_dc> /ud:<domain\username> /pd:*
Replace <target_dc> with the name of a domain controller and <domain\username> with appropriate credentials.
Check for Trust Relationship Issues :
Verify that the source server has a valid trust relationship with the domain. If there are trust issues, it can cause problems during the conversion process.
Update Integration Services (if applicable) :
If you’re converting to a Hyper-V VM, make sure that Integration Services are up to date on the source server.
Check Event Logs :
Look in the event logs on both the source and target machines for any relevant error messages that might provide more information about the issue.
Consult MVMC Documentation and Forums :
Check the official Microsoft documentation for MVMC and browse forums or communities where others may have encountered similar issues.
If none of the above steps resolve the issue, it might be necessary to provide more specific information about the error message or consult with Microsoft support for further assistance.
Remember to always back up critical data before attempting any major system changes or virtualization processes.
Based on the provided log, it seems like you’re encountering an issue during the virtualization process using MVMC (Microsoft Virtual Machine Converter). The error message indicates a problem related to the secure channel support.
Here are a few things you can try to troubleshoot the issue:
Verify Administrative Privileges :
Make sure that the account you are using for the conversion process (elcometerad\DM.Admin) has administrative privileges on both the source machine (server22.elcometer.local) and the target Hyper-V host (hvunit12.elcometer.local).
Check RPC Connectivity :
The error message “The RPC server is unavailable” suggests an issue with RPC (Remote Procedure Call) communication between the source machine and the target Hyper-V host. Ensure that RPC is not blocked by any firewall or security software.
Verify Source and Target Machine Names :
Double-check that the machine names (server22.elcometer.local and hvunit12.elcometer.local) are correct and can be resolved in your network.
Verify DNS Configuration :
Ensure that DNS is properly configured on both the source machine and the Hyper-V host. The machines should be able to resolve each other’s names.
Check BITS Service :
BITS (Background Intelligent Transfer Service) is used for transferring files during the conversion process. Ensure that the BITS service is running on both the source and target machines.
Firewall and Security Software :
Make sure that there are no firewall rules or security software blocking the communication between the source machine and the Hyper-V host.
Review SSL Certificates :
Check if there are any issues with SSL certificates on the source machine or the Hyper-V host that might be causing secure channel errors.
Check Disk Space :
Ensure that there is enough free disk space on the target Hyper-V host to accommodate the virtualized machine.
Update MVMC :
Make sure you’re using the latest version of MVMC. If not, try updating to the latest version to see if the issue persists.
Log Analysis :
Analyze other logs and event viewer entries on both the source machine and Hyper-V host for any additional error information.
If none of these steps resolve the issue, it might be necessary to consult Microsoft support or community forums for more specific troubleshooting tailored to your environment. Remember to back up important data before attempting any major changes or conversions.
Hey,
Check the following thread.
You might need to install additional software to make MVMC work.
As another option, you can use StarWind V2V Converter, which can convert directly to a Hyper-V VM. Check for more info:
1 Spice up
dylmurph
September 28, 2023, 6:20am
4
Hi Max,
Unfortunately, I did try Starwind but we’re getting an access denied error.
Thanks,
Dylan
Hey,
Can you please share the details of the error you are getting?
In addition, you can always contact our support team on our support forum. Our engineers will gladly assist with the error your are facing.https://forums.starwindsoftware.com/
dylmurph
October 11, 2023, 7:16am
6
Hi Max,
Error below. I’ll also put this in the forum. The account mentioned is a domain admin.
Thanks,
Dylan
