Registry location of AutoTriggerDisabledProfileList In any case – what happens is, that this lands the VPN connection on a list in the registry called AutoTriggerDisabledProfileList which is a REG_MULTI_SZ property type that you might be interested in clearing out the Always On VPN connection name from. This might have happened because the user manually disconnected the user tunnel at some point in time, or because of something that is yet to be explained. Some hacks to fix this, include scheduling the “rasdial ” command to re-establish the connection, but wouldn’t you rather know why it has stopped auto-connecting? Why is it not auto connecting then? Which just scratches the surface of some of the woes you will have with this technology…īut setting all the configuration issues aside for a moment… I think that anyone working with Microsoft Always On VPN infrastructure and client configuration has run into an issue where user tunnel connections don’t always auto-connect – despite having configured “AlwaysOn” in the ProfileXML or Intune configuration policy. The Microsoft Always On VPN Solution that is pushed by Microsoft as the successor to DirectAccess, is a great tool for remote workers and admins alike because it’s always on – or is it?ĭespite the high level of skills required to implement this technology, many try out their luck with the official documentation from Microsoft, only to end up at the troubleshooting section at.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |