Windows 11 connecting to Active Directory via Cisco AnyConnect

DaChiTriGuy 5

I'm going to start with the question here and if I need to move this elsewhere, I can.

We have just started deploying Windows 11. We have a couple of users that it is working well for, however, just this week two new computers were unable to access their homeshare via our login script. When I run the set command, the logonserver variable is populated but homedrive and homeshare is not. Everything works fine in Windows 10 and Windows 7. The network environment (AD) has not changed, AnyConnect has not changed, just the introduction of Windows 11 (hence the reason I started this discussion in this group). Has anyone run into anything like this recently?

Thanks

ajay 0 Reputation points

2024-04-16T20:13:36.7033333+00:00

We are seeing the same issue with a couple different VPNs. Connected on prem everything looks good. What I've found so far is that older versions of Windows hold onto the HOMEDRIVE, HOPEPATH, and HOMESHARE volatile environment variables when logging in with cached credentials. However, Windows 11 resets those. I'm still researching to see if there is a way to prevent these from getting wiped out when logging in with cached credentials.
ajay 0 Reputation points

2024-05-28T15:10:48.99+00:00

I used this as an opportunity to move from mapping drives using login scripts to mapping with Group Policy. For the home share I'm mapping it as an Update action, Location of %HOMESHARE%, and Reconnect enabled.

This has allowed the drive to be mapped manually, and then updated by GPO later when physically on the domain.

Share via

Windows 11 connecting to Active Directory via Cisco AnyConnect

Your answer