APM - How to modify the interface name used for VPN-SSL on windows

Hi,

Last days I was dealing with the same issue. In our case, the German language caused the VPN name to be registered with unreadable characters in Windows registry, while the VPN name contained correctly the "ä" character.

The result was that when Edge Client made connection to the F5 it was looking for registry key with the name containing "ä" but no such key existed. So no proxy settings were applied and clients were not able to browse.

It took us a while to figure out that it is because of the VPN name.

I was about to apply the solution from AKHATIR, but rewriting it directly in filesystem would probably cause that the next time we upgrade the OS, this change disappears. Plus it affects all network access resources.

Then I found knowledge base article published just yesterday:

https://support.f5.com/csp/article/K95422068

Followed the instructions and added the variable assign item to APM policy - worked like a charm! :-)

So it's maybe a good idea also for you Nicolas to do this in APM policy - should save you pain after OS upgrade and it is definitely more transparent solution.