Windows 10: Local app to VM running on local machine.

I have a laptop running an Allstarlink node in a Hyper-V virtual machine using Hyper-V's external switch. I would like to have a local laptop application, iaxRpt, connect to this VM and connect to the software running in it. i.e. Laptop running Hyper-V VM. VM running Allstarlink app. App on laptop outside of VM running iaxRpt connecting to Allstarlink in VM. This works as long as I am connecting from a 2nd Windows machine but not with both on the internal. Connecting from laptop Edge to Allstarlink in VM works fine. I can ping the VM ip address from anywhere.Allstarlink, iaxRpt are bo

:)

 

Converting Local Machine to use in VM ware

Hello Guys and Gals, I would would like to Convert my Local Machine to a use in VMware, ( I did a test run on a laptop of mine which was successful. )

I would like to do the same thing on my Local machine, i have VMware running on my local machine ( with several OS on it which are working fine )

I would like to add my local machine to the VM that is on my local machine, and use the newly Created Local VM in VMware,

could i use the newly created Local VM as a form of Backup ?

Could i use the newly created local VM as my main OS in VMware ?


Thanks in advance

 

Local vs Network user accounts

I just did a VM install, just to verify that I don't speak total crap.

Steps I took:

1. Installed Windows 10 Pro x64 Build 15063.0
2. Entered the License Key
3. Created a local account
4. Went to accounts and added my Microsoft account
5. Let Windows use this account for all apps
6. Checked status on Microsoft account web page.
7. Verified that the VM shows up there
8. deleted my VM locally
9. created a new VM installation without entering the License Key (on same VM but totally new Virtual disk)
10. re-did steps 3-7
11. verified that my VM is activated.

And indeed it is activated and I login to my VM using local account which is linked to my MS account.

Should I create a Video of this or do you trust my word on it? Or better yet test it yourself if you have a valid license key you can waste on a VM.

 

Local VM's no longer able to be RDP'ed

For over a year, without fail, I've had multiple locally hosted HyperV VM's that I have never had an issue connecting to using Remote Desktop. Now, it seems with Win10 21H2 update, I can no longer use Remote Desktop to connect to them and now have to use the crappy built in num-locks turning off "Connect" built into Hyper-V Manager.

I should mention that this is a work laptop that is connected to the company network via VPN software (this has never prevented local RDP connections before).

When I do use the built in "Connect" I am able to ping the host machine, I can browse files on the host machine, etc. I cannot from the host machine ping the VM, browse files, RDP into it, etc.

Has anyone had this issue? I've tried searching, but most anything I find is from 5-6 years ago (or older) and not relevant.

• I've done the Registry D-Word add.
  
• I've made and unmade changes to firewall to allow.
  
• I've made sure it's allowed via Firewall (firewall is turned off).
  
• Remote Desktop is allowed on the VM.
  
• I've added the VM's IP and host name to the host file.
  
• I've made sure NetBios is either on or set to default.
  

These are Win10 VM's on a Win10 Host.