Use Local Devices and Resources on Hyper-V Virtual Machine in Windows  

m534753 said:

I just wanted to create internal network so that the virtual image will be able to communicate the host system.

For an XP Hyper-V VM there are three things to know in order to use sharing. The first is that the XP VM can only use a 'Legacy Network Adapter'.

The second is that you need to create a an external switch for XP to use.

   Note

Since Windows 10 version 1709, Hyper-V now includes a default virtual switch named simply as Default. Creating your own external virtual switches is no longer required to get Internet connection to virtual machines.

However, to guarantee best networking capabilities between host machine and its virtual machines, it is recommended to create an external switch and use it instead. Using Default switch is totally OK if networking between host and Vm is not required.

Hyper-V virtualization - Setup and Use in Windows 10

The third is that any W10 machine you want to connect to from XP must have 'SMB 1.0/CIFS Server' enabled in Windows Features' because XP uses SMB1. If you just want to connect to an XP share from W10, then you only need 'SMB 1.0/CIFS Client' on the W10 machine.

Here's one I made earlier: Win 10 networking to an XP computer has changed - post #10

Hey,

Thanks for the information.
I want to ask if it is possible to automate this process through a ps1 script? Or this has to be done manually?
I'm able to enable enhanced session through ps1, but I'm not able to find anything that can help me automate the rest of the process (step 4-9).
Do you have any ideas?

Thanks!

Hello Shawn @Brink,

Your words:
Upon creating "If you don't see the VMConnect dialog and the virtual machine is currently running without enhanced session, then click/tap on View on the menu bar of the virtual machine, and click/tap on the unchecked Enhanced session to open the VMConnect dialog."

On the 'View' menu, in between ''Toolbar' and 'Zoom', the 'Enhanced session' is grayed out on . My Manjaro linux VM runs well, but without sound. When this VM was created, I did enable the Server setting "Enhanced Session Mode Policy", and in the User setting "Use enhanced session mode".

What could be the reason for the 'Enhanced session' being grayed out? I wanted the enhanced session as I thought it would enable the local sound and video card hardware on my Windows 10 sever to be used by my Manjaro VM.

Thank you Shawn. Thinking about it before seeing your response, I thought it might have been the inability to create a generation 2 VM. Upon creation, gen1 was my only choice. You've completely cleared up why 'Enhanced session' was grayed out.