[2004, 20h2] direct access stops working after clients upgrade to 20h2

[chazzy2501]

I'm aware that DA is EOL but I didn't see any news on 20H2 breaking it or disabling it. My users are now getting prompted to update to 20H2 from 1909 and the 3 that have all got orphaned. No errors it just doesn't work.

 

I've re-applied the policy but it still fails.

 

Always on VPN has some technical hurdles and quite the infrastructure upgrade.

[RobFuller]

After upgrading to 20H2 I have also lost DA.. Was confused so ended up using an alternative vpn but would be interested in hearing if it's being disable.

I've started the work on setting up AoVPN mainly in the hope of overcoming home internet connection issues for some of our users but looks like it's still a thing with AoVPN.

[free780]

The main thing with AOVPN is that wired connections are beter than wireless at home.

ISP DNS can also get in the way.

[Jcx500]

I haven’t used Direct Access , but we are using a rras vpn on a windows server box running over L2TP/ipsec, we had to make some changes on our staff laptops via a registry.

[RobD]

I lost all my machine certs after an upgrade. Had to pull them down again.

 

No errors on the server or the client?? Can you ping the server from outside the domain?

 

https://directaccess.richardhicks.com/2018/03/15/directaccess-troubleshooting-windows-10-network-connectivity-assistant/

[chazzy2501]

@RobD when I say no errors I mean it just says connecting indefinitely. Nothing on the DA dashboard for the client. These are remote users so I haven't a failing machine in front of me. The other staff (30+) are still working. They all should be 1909 unless they've done the upgrade.

 

The DA troubleshooter isn't for Windows 10 and it has a lot of windows 7 quirks in it.

 

The DA server is 2012 (not R2) but it up to date on security patches.

[Squelch]

I lost all my machine certs after an upgrade.

 

Same for me, as it happens I was almost finished moving my remote users from DA over to a new VPN.

[computer_expert]

Same for me, as it happens I was almost finished moving my remote users from DA over to a new VPN.

 

It's a bug with the 20H2 install media you used. If you install the latest patches on an older build (e.g. 1909), then upgrade using unpatched 20H2 media, all your certs go missing. The fix is to use the latest 20H2 ISO on VLSC or patch your exising 20H2 media with the latest updates.

[chazzy2501]

It's a bug with the 20H2 install media you used. If you install the latest patches on an older build (e.g. 1909), then upgrade using unpatched 20H2 media, all your certs go missing. The fix is to use the latest 20H2 ISO on VLSC or patch your exising 20H2 media with the latest updates.

 

These are not clean installs, these are laptops doing a windows update from 1909 to 20h2. (I'm not even using WSUS) As per teacher request I've allowed staff to choose how and when the laptops update.

[computer_expert]

These are not clean installs, these are laptops doing a windows update from 1909 to 20h2. (I'm not even using WSUS) As per teacher request I've allowed staff to choose how and when the laptops update.

 

I believe it affected windows update too at one point as microsoft lifed the upgrade block at some point in December.