Since W10 2002, connected Standby cannot be disabled anymore Due to this feature , Wi-Fi adapter enters in DRIPS mode if not used by other ressources (even with laptop on AC adapter), & tunnel is lost . Client re-connect as soon keyboard/mouse entry or other ressource needs (Connected stand-by is not Sleep or Hibernate, apps still working). But while all mappings are gone f.e. , user need to re-enter credentials for some apps, etc ... and reconnection can take a minute (check compliance) . Did someone have already found best practices or any recommandations about Pulse Secure Client & Connected Standby (aka Modern standby) Thx  ... View more

Since Windows 10 ver.2004 , we cannot disable Modern/Connected Standby anymore. A lot of settings are moved from old control panel power settings (through powersheme customisation f.e.) to the modern one. All is working fine for physical NICs , power related settings are fully customisable as desired... Except for Pulse Secure Virtual adapter : it's the only adapter that keep is "Power Management" tab into NIC hardware properties. and of course, "Allow the computer to turn off this device to save power" tick box is checked by default . It seems (it's only a guess) that driver is too old to be Modern standby aware. We don't want to tweak this tick-box through custom reg key forced by GPO : Class Adapter rank position change from one laptop hardware model to another. Now the issue is that sometimes, when screen locks after inactivity time-out, (NOT sleep, NOT hibernate, just the black screen power save feature)  VPN goes down until user is back behind his laptop, then VPN reconnect . Did someone already fins a way to avoid this ? Thx a lot  ... View more