gpupdate /force hangs - spent all day trying to work this out :-(

[TwistedHelixis]

Really odd issue in my hyper-v test environment.

 

Just restored our DC from backup into my test environment.

Installed a new Windows 10 pro VM

Joined the Windows 10 vm to the DC domain

Rebooted Windows VM, logged in to domain. The login seemed to take a bit longer then normal, but still only 1 minutes, so not crazy long.

Noticed the mapped drives had not mapped, so opened cmd and typed gpupdate /force, but it just hangs there until I power down the PC.

 

Next I deleted windows client VM, reinstalled, but still same issue.

 

Just to test things out, I installed a fresh new DC, added a few group policies, but get the exact same issue.

 

All above was setup using 'internal' hyper-v network.

I can ping the server from client

 

Whats going on???

 

EDIT - just went back to my original setup with the restored DC, now the client login is taking ages.

 

EDIT - Just made a few changes, including disabling IPv6 on client nic, and it just ran gpupdate /force. Ill need to do some more testing tomorrow and report back.

Edited October 24, 2022 by TwistedHelixis

[sluggster66]

Does dcdiag give you any info?

[sluggster66]

Also what nics on the test environment hardware? are the broadcom?

[kmount]

Just stepping back a moment.

 

The new DC you installed was this a completely new domain etc or joined to your restored server?

 

During the restore did you go through the authoritative restore in AD etc and check sysvol etc is shared out nicely?

[TwistedHelixis]

OK so its all working now and I would love to know what caused the issue, but I have no idea as I made so many changes to all systems including the host.

 

Also what nics on the test environment hardware? are the broadcom

Yes Broardcom

[sluggster66]

Might be worth checking the vmqs setting on the nic. This needs disabling