SIUC

New Member
Joined
Apr 6, 2012
Messages
4
So I made an image with XP Mode that I want to use as a base image for multiple other users XP Mode on my network. I put all of the applications on the image and syspreped (Resealed it). So now I have a clean VHD with all my applications on it that is ready for first time use for each machine. I have installed XP Mode on all of the other computers and have booted the virtual machine the for the first time in order to create the VHD on that computer. I then copied over the VHD image that I want to use and deleted the original VHD. I have tried naming it the same as the original VHD that was created, as well as changing the name. I have opened the XP Mode application settings and mapped the hard drive to point to this file. However, when I try to start XP Mode now it is saying that it has no VHD file and must create a new one. Why are these machines not taking this new VHD? Thanks in advance for any help.
 


Solution
It seems like you are encountering an issue with using a custom VHD image in XP Mode on multiple computers in a network. When dealing with custom VHD images for XP Mode, there are a few key points to consider to ensure the new VHD is recognized and used correctly:

Steps to Ensure the Custom VHD Image is Recognized:​

  1. Custom VHD Preparation:
    • Ensure that the custom VHD image was sysprepped correctly before transferring it to other computers. Sysprepping ensures that the VHD is prepared for duplication and deployment on multiple machines.
    []File Name and Location:
    • When copying the custom VHD to other computers, make sure the file path and file name match the original VHD file or are correctly...
It seems like you are encountering an issue with using a custom VHD image in XP Mode on multiple computers in a network. When dealing with custom VHD images for XP Mode, there are a few key points to consider to ensure the new VHD is recognized and used correctly:

Steps to Ensure the Custom VHD Image is Recognized:​

  1. Custom VHD Preparation:
    • Ensure that the custom VHD image was sysprepped correctly before transferring it to other computers. Sysprepping ensures that the VHD is prepared for duplication and deployment on multiple machines.
    []File Name and Location:
    • When copying the custom VHD to other computers, make sure the file path and file name match the original VHD file or are correctly updated in the XP Mode settings.
    [
    ]XP Mode Virtual Machine Configuration:
    • Update the XP Mode virtual machine settings to point to the new custom VHD file.
    • Check the settings in XP Mode to ensure that the correct VHD path is specified under the virtual machine configuration.
    []Permissions and Ownership:
    • Verify that the user account running XP Mode has sufficient permissions to access and use the custom VHD file.
    [
    ]Virtual Hard Disk Mapping:
    • Double-check the virtual hard disk mapping within the XP Mode application settings to confirm that it is pointing to the correct custom VHD file.
  2. Recreate Virtual Machine Profile:
    • If the issue persists, consider recreating the XP Mode virtual machine profile on the affected computers. This process can sometimes resolve underlying configuration problems.

      Troubleshooting Steps:​

    • Revert to Original VHD:
    • If possible, revert to the original VHD file on one of the computers to see if XP Mode functions correctly with it.
  • Check Event Logs:
    • Look into the Event Viewer logs on the affected computers to see if there are any error messages or warnings related to the VHD file not being recognized. By following these steps and ensuring proper configuration and permissions, you should be able to successfully use your custom VHD image as the base image for multiple XP Mode instances on your network. If the issue persists, further troubleshooting may be necessary to identify the root cause.
 


Solution
Back
Top