Microsoft"We also use local network sharing and none of the PC's that updated to 24H2 can connect to the other network shares. Mapped drives fail to connect. Reverting to 23H2 resolves the problem. Is this related to this NAS SMB1 issue or unrelated?"
We are having pretty much the same issue as well. Connecting to our file shares gives us a credential error when the same process would give us no error on devices running builds prior to 24H2.
We are also unable to update Computer Management on the domain joined device when logged in as regular user, even when attempting to passthrough credentials with a domain admin account when prompted. We get the same credential errors as we do with the shares. Issue still occurs even when logged in as local or domain admin.
Our Autopilot also got new issues with provisioning a user account during the autopilot pilot sign-in, as it would time out with an error after about 90 minutes and not intiate Bitlocker when signing in with a new user account not having MFA already setup for the account.
The device would still join the domain and allow us to login to the desktop with our accounts, but I would then have to login with an existing user account that already had MFA setup, and then sign into the Company Portal with that account to finish the device Intune enrollment join and Bitlocker setup. Since most autopilots are for new user accounts not already having MFA setup, this is a rather annoying workaround for the time being.
Lastly, we are also unable to run gpupdate on the 24H2 devices, as that gives us an error as well stating a lack of network connectivity to the domain controller.
All devices are Autopilot Hybrid Domain Joined devices. When trying to then run a gpreport, we get an error that the user does not have RSoP data.
These are the current main issues we have discovered on devices that have been "upgraded" to 24H2. So far, it's been an aggravating mess.
