Last edited by Cliff S; 27 Nov 2015 at 18:28.
Hi there, Kari!
Thanks for your tutorial, it was very informative and easy to follow.
Perhaps you could help me with advice - I have a Windows 10 PC on which I've created virtual PC with Windows XP (following your guide). The problem is that the virtual pc does not have sound. I've checked the Integration Services - they are all checked.Attachment 50729
This quote from another thread:
Remote Desktop Connection to connect to your Windows XP guest to get audio.
Only it seems I'm missing something here - I can't connect to my virtual pc, I keep getting error message that "Remote Desktop can't find the computer "XPSP3". This mean that "XPSP3" does not belong to the specified network. Verify the computer name and domain that you are trying to connect to.
First, is the Windows XP guest a Pro edition? You cannot remote desktop to Home edition, for that you need a third party solution, TeamViewer or similar.
Second, are incoming remote connections allowed in XP guest?
If connections are allowed, you can now connect to the XP guest with Remote Desktop Connection using either the PC name or IP address. Screenshot from just now, I have connected to my XP vm using Remote Desktop Connection:
In addition to my previous post, here's a practical tip:
Once again, thanks for being so helpful. Yes, selecting that tick box (allow users to connect remotely to this computer) solved it and now I can connect to vm and it has audio! Great!
But there's one more problem - the video is not great at all so in the vm settings I added that RemoteFX 3D Video Adapter which should solve the problem but it is not installing. If I connect through RDC, nothing ever happens with video - it continues to use basic crappy video adapter. If I connect through Hyper-V it runs "Found New Hardware" Wizard and - oops, it can't install the hardware because it can't find the necessary software. Somehow I didn't find any solution to this using Google so once again - can you please help me solve this?
Ok I turned RAPID mode off(in Samsung Magician), that wasn't the problem....
I look into it more when I wake up
Remove (delete) the vm in question, also delete its virtual hard disk file in the default VHD location. When done, change the default storage location of both the vm configuration files and virtual hard disks as told in Part Two Step 2.5 in this tutorial. The default locations are:
- Config files: C:\ProgramData\Microsoft\Windows\Hyper-V\Virtual Machines
- Virtual Hard Disks: C:\Users\Public\Documents\Hyper-V\Virtual hard disks
To change the locations, create a folder on root of any drive except C:, name it as you wish. I always use the D: drive for my virtual machines and create a folder D:\Hyper-V. Create a subfolder in the Hyper-V folder for virtual hard disks (D:\Hyper-V\Virtual Hard Disks). Now open Hyper-V settings and select D:\Hyper-V\Virtual Hard Disks as location for the virtual hard disks, and D:\Hyper-V as location for virtual machines (config files):
Now start from scratch, creating the Ubuntu vm. Come back to tell what happened.