After Windows 11 24H2 Update Client PCs Show Offline in Server 2016 Essentials Dashboard

Question

Server 2016 Essentials and 2016 Standard.  Both have Essentials Dashboard.

Windows 11 clients updated automatically to 24H2.  Once done all showed Offline under Devices.  Checked the clients and they all showed they had connection to server, but Network no longer showed any of the other PCs on the Network.  Network files were still available from each client.

Searched for a solution and found a number of users having similar issues with Network connection.  Only solution was to Roll Back each client to 23H2 and set Group Policy to only allow updates to 23H2.  This worked but Devices now show Updates needed for each.  When run Updates manually on Clients no updates found.

Not a long-term solution as should be able to update to 24H2 as any new clients will have that version.  

***Move from Windows / Windows 11 / Windows update***

Answer 1

I had tried all these suggestion except Network reset. Did find a solution from another source:

Did the following on each Win 11 PC.  After making the changes uninstalled the connector, left the domain back to Workgroup.  Updated to Win 11 24H2.  Once updated reran the Connector and rejoined the Domain.  Before doing this, I did setup a Test client with Policy fix in place.  It connected without an issue.

From another source:

 "What we found was an Encryption policy during GPO assignment was not deploying to devices.

The policy in question is located under the following location:

Local Computer Policy - Computer Configuration - Windows Settings - Security Settings - Local Policies - Security Options.

Policy is called Network Security: Configure Encryption types allowed for Kerberos. And we then enabled the following options to be applied from GPO:

RC4_HMAC_MD5

AES128_HMAC_SHA1

AES256_HMAC_SHA1

Future encryption types

Also, a good idea to check the following on the client side that is not joining and updating the reg key provided for it to receive the policy.

Also, a good idea to test this policy first before deploying to all devices.

On the client side

1. If a policy is specifying a kerberos encryption key, then you will need to change the following in the registry
2. The key will not be present if a policy is not applied
3. Faulty entry in registry

Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: \Sofware\Microsoft\Windows\CurrentVersion\Policies\System\Kerberos\Parameters\

Value Name: SupportedEncryptionTypes

Type: REG_DWORD
Value: 1, 2, or 3 are a finding.

1. Registry Hive: HKEY_LOCAL_MACHINE
   Registry Path: \Sofware\Microsoft\Windows\CurrentVersion\Policies\System\Kerberos\Parameters\

change to Value Name: SupportedEncryptionTypes       7ffffffc 2. Pc will need to restarted. 3. Run a gpupdate /force to enforce the new policies"

Our functional Domain Level is Server 2016 Only one PC did not have the correct Registry Value.

Answer 2

Hello

Thank you for posting in Microsoft Community forum.

The Windows 11 24H2 update has indeed caused network connectivity problems for many users. Here are a few potential solutions you can try:

Set Static IP Addresses: Some users have found that setting static IP addresses on their clients can resolve connectivity issues.

Problem in network Windows 11 24h2 - Microsoft Community

Update Network Drivers: Ensure that all network drivers are up to date. You can do this through the Device Manager by right-clicking on your network adapter and selecting "Update driver".

Windows 11 24H2 Update: Connectivity Issues and Solutions | Windows Forum

Allow Insecure Guest Logons: If your network relies on guest logons, you might need to enable insecure guest logons via Group Policy. Navigate to Computer Configuration > Administrative Templates > Network > Lanman Workstation and enable the "Enable insecure guest logons" policy.

FIX: Windows 11 24H2 Cannot Access Network Shares (0x80070035). - WinTips.org

Check DHCP Settings: There might be issues with DHCP. Some users have resolved their problems by adjusting DHCP settings or disabling certain DHCP options.

Network Reset: Performing a network reset can sometimes resolve these issues. Go to Settings > Network & internet > Advanced network settings > Network reset and click "Reset now".

Manual Network Path Access: Try accessing shared folders directly by typing the network path (e.g., \PCName or \192.168.1.25) in File Explorer's address bar. This can sometimes bypass the issue.

If these steps don't resolve the issue, you may need to wait for a patch from Microsoft for more targeted help.

Best Regards,

Wesley Li