Windows 10: A windows 10 domain joined on Hyper-v is loosing network frequently

Hello guys..


I have a windows 10 VM that looses internet connection frequently


Environment :

• I'm in the middle of deploying an RDS farm lab on HYPER-V a very small one..I started with 2 machines. A windows server machine 2016 with remote desktop services and ADDS roles and a windows 10 joined to this domain.
• I went with the default switch on hyper-v ..didn't change anything
• To join my W10 machine. I just put W2016 IPV4 in the preferred DNS server of the client All are private IPs

Issue :

• I was working on my LAB .. didn't change any thing related to network and suddenly I find no internet on W10 machine

Research :

• IP of DC still added as preferred DNS server in Win10 config
• Machine still joined
• Can only ping DC not any external site

:)

 

Windows 10 Enterprise - PCs unable to join the domain using Task Sequence (Potential issue is Hyper-V?)

Hi All,

Reaching out for assistance on an issue that has been ongoing for the past 4 months.

Infrastructure:

Windows 10 Enterprise 1607 CBB

Config Manager 1602

OSD using MDT latest version

Issue: Windows 10 Image Task Sequence will work on any new PCs or existing PCs that had previous Windows 7 image loaded. On PCs that we have already imaged with the Windows 10 Image Task sequence, and we are re-imaging again, the PC fails to join the domain.
We are using an answer file to join the domain.

Earlier Troubleshooting:

The logs for the failed domain join systems all say the same thing...relating to time Sync, but this is not the issue. The image in all the other scenarios work just fine, it's only re-images on the WIn10 Task Sequence that does not work.

We are now looking into Hyper-V potentially causing the issue. We have BIOS settings to enable Virtualization and also enable in the WIM the Hyper V settings in the 1607 image. However we created the WIM using a VM, and the Hyper-V Hypervisor does not get
enabled if the WIM is created using a VM. We also tested creating the WIM with a Physical PC and confirmed that both Hyper-V Hypervisor and Hyper V services are enabled, however this still did not fix the issue.

Is anyone experiencing issues like this regarding PCs joining the domain for Windows 10 1607 build in the enterprise using OSD?

Thanks

 

Hyper-V networking

Windows 10 Pro, Build 10586.71. Hyper-V installed. All was working well, and then I got a chipset update from Dell. Installed the update and rebooted computer. After that networking was not working correctly, windows showed limited connectivity. I looked
a little to roll back the driver update, but Windows did not show a new Nic card driver and the chipsets I looked at also did not show a current date. The Dell Command update program does not provide a way to uninstall updates.

I tried to access hyper-v switch manager but it returns an error that "an error occurred while trying to retrieve a list of virtual switches". Also tried using the powershell cmdlet but got a general error.

I accessed the networking center and deleted the Hyper V adapter, then edited my LAN card's config disabling the two Hyper V protocols and enabling the rest. This let me get back on-line with my computer. I have tried uninstalling the Hyper V feature,
reboot, reinstall - but I am still unable to access the switch manager. I then removed the feature again, re-named the C:\ProgramData\Microsoft\Windows\Hyper-V directory, rebooted, added the feature again. This time (obviously) none of my VM's show up but
I'm still unable to access the switch manager.

There is no critical data in my Hyper V, I use it for testing, re-creating issues, learning, etc. Is there a way for Windows 10 (or something designed for server 2012 that will apply) that I can use to fully reset the Hyper v networking, or fully rest all
of hyper v so I can get it working again? I do use the workstation heavily, it's my work computer so it would be very difficult to impossible to reinstall the OS.

Thoughts and suggestions appreciated.

 

Re-join the domain after upgrade

There is no need to leave the domain, you can perform the upgrade (with Admin privileges).

You can also leave the domain, upgrade with a local account, then join the domain again.

Resources:

• Quick
  Tip: Join a Windows 10 PC to a Domain