RDC - Connect Remotely to your Windows 10 PC  

Almeister9 said:

It seems to me that the destination's connection speed has the most effect on the experience.

Yes. Especially the upload capacity of the remote host.

Hi Hibs, welcome to the Ten Forums.

hibs said:

If I read it correctly after a few times, the Host is the one that is being connected to by another computer. And the Client is the one trying to send out the internet-computer connection using RDC?

In Remote Desktop Connection, the Remote Host is the computer or virtual machine you connect to, and the Remote Client is the computer or virtual machine you use to connect to that Remote Host.

hibs said:

Here is my situation: I have a Windows 10 on my computer, and through Hyper-V I've created a Windows XP Virtual Machine inside the Windows 10 computer. But I'm not getting sound or connecting to USB ports from Win XP Home Edition. So do I from the Win XP (the client) connect RDC to my Win 10 (host) to get my sound and connections?
I've tried opening RDC or connecting to Win XP from Win 10 Pro home computer but it does not allow me. Is that because Win XP is not a Professional version? And because I'm doing things backwords order?
I need to work mostly from the Win XP computer with my music programs, so do I need to connect to Win 10 through RDC from XP? And the XP would be the Remote Client? I need to understand the proper order for me to set up first the Remote Host as described, then connect to the Remote Client. Please clarify for me.
Hibs

This is where the terms used get really complicated:
Your Windows 10 computer is when speaking about virtualization the virtualization host. The Windows XP Hyper-V virtual machine on your Windows 10 host is the virtualization guest. In other words, you are running a Windows XP guest on your Windows 10 host.

That's the virtualization, virtual host and guest. The Remote Desktop steps in and totally confuses you now with new terms: For Remote Desktop, when trying to connect from your Windows 10 virtual host to your virtual Windows XP guest, the terms are totally different. Now your virtual host Windows 10 is called a client, and your virtual guest Windows XP is called a host.

Let's try to clarify this:

• In virtual computing:
  
  • HOST = The main computer running a virtualization program or hypervisor, for instance Hyper-V
  • GUEST = the virtual machine on the above mentioned Host
  
  
• In Remote Desktop:
  
  • HOST = The computer or virtual machine you will connect to using a Remote Desktop Connection
  • CLIENT = The computer you use to connect to another computer or virtual machine

In your case now you cannot do what you want to. Your virtual Guest Windows XP is a Home edition which cannot be used as a Remote Host. A Remote Host must be Windows XP Pro, Windows Vista Business, Ultimate or Enterprise, Windows 7 Professional, Ultimate or Enterprise, Windows 8 / 8.1 Pro or Enterprise, or Windows 10 Pro, Education or Enterprise Edition.

You cannot connect to (read = these editions cannot be remote hosts) Windows XP Home, Windows Vista Home Starter, Basic & Premium, Windows 7 Starter, Hoime Basic / Premium, Windows 8 & 8.1, or Windows 10 with Remote Desktop Connection.

In your case the only two alternatives are:

1. Get a Windows XP Professional license
2. USe a third party remote desktop application to connect to Windows XP Home. TeamViewer is my recommendation (using a third party remote app, the audio will never be enough for you to work with audio files but you can of course try)

Kari

hibs said:

Thank you Kari for explaining those terms both for virtualization Host and the Remote Host. There is definitely at difference. Now I am glad to understand those differences.
I will either try to get XP Pro license. If I did, would it be best to try to connect XP Pro (Remote Host) from Win 10 (Remote Client) to work with XP software? Or vise-versa?

To work with software installed in Windows XP, you of course have to use that machine. In you case you connect to it from your Windows 10 virtual host and use then XP remotely.

hibs said:

Or possibly I could try the suggestion you gave me a few days ago, and that is to create a new Win7 Pro virtual machine with Win XP Home inside of it > like a third generation virtualization. I did have Win 7 Pro working perfectly with my XP Home, but after I installed Win 10, I didn't check on the fact that there was a 30-day grace period to restore back to previous system, and my "back up" file was removed by Windows. Now it is almost 90 days after.

I was not talking about using XP Home vm in Windows 7, I was talking about using XP Pro which can be downloaded and installed for free in Windows 7 Professional, Ultimate and Enterprise editions. Let's read that reply of mine you referred to once again (quote from your thread):

Kari said:

You simply cannot use Windows XP Home as remote host, meaning you cannot connect to it using the Remote Desktop Connection. There are some hacks around the Internet but I very strongly advice against them.

A workaround, in case you have or can find a valid Windows 7 Professional or Ultimate license is to install Windows 7 on a Hyper-V virtual machine, then install Windows Virtual PC and Windows XP Mode on that virtual machine. Works perfectly giving you Windows XP Pro SP3.

Read more about XP Mode and installing it in Windows 7 on our sister site the Seven Forums: Windows XP Mode - Install and Setup - Windows 7 Help Forums.

XP Mode can easily be installed also in virtual Seven running on a Windows 10 Hyper-V virtual machine, so called nested virtualization: Windows XP Pro virtual machine running on a Windows 7 virtual machine running on a Windows 10 host.

Kari

hibs said:

Thank you again for that valuable information. That explains why I was able to use XP Home when I used Windows 7 Pro, which I have a licensed copy here. So that may work.
Thanks for the excellent information you supply, Kari.
Hibs

I'm afraid you are still misunderstanding this. You can never in any circumstances use Windows XP Home over Remote Desktop Connection (without non-supported hacks, that is). Not from Windows 10, not from Windows 7.

My workaround was and is to install Windows 7 Professional or Ultimate on a Windows 10 Hyper-V virtual machine, then install Windows Virtual PC and Windows XP Mode to that virtual machine. Windows XP Mode gives you a Windows XP Pro.

In this scenario you would then have a Windows XP Pro virtual machine running on a Windows 7 virtual machine running on Windows 10 host, and you could use Remote Desktop Connection to connect tro both Windows 7 vm and Windows XP Mode vm to get the remote audio from the XP, as this was your original issue: no audio in Windows XP Home vm.

Cliff said:

Kari , Thank you for all you do. Please allow me to point out a typo in the tips section toward the end of Part 3, where you explain using a command prompt to do a shutdown or restart of the host machine. The switch for restart should be -R.

Yes, of course. Seems that when I have written this tutorial I have simply copy & pasted the previous line and forgot to edit it, forgot to replace the -s with -r.

Thanks to you the typo is now fixed :)