Forum Discussion

Abdessamad1's avatar
Abdessamad1
Icon for Cirrostratus rankCirrostratus
Dec 04, 2019

APM Dialup Windows Logon Integration v14

Hello,

 

We use the F5 Edge client to connect corporate laptop to VPN once the user is logged into his computer.

The client has been customized with the following settings:

  • Enable Always connected mode
  • Allow-Only-In-Enterprise-LAN
  • BIG-IP Edge Client
  • BIG-IP Edge Client COM API
  • Web Browser Add-ons for BIG-IP Edge Client
  • Endpoint Security
  • Component Installer Service
  • DNS Relay Proxy Service
  • Traffic Control Service
  • User Logon Credentials Access Service
  • Machine Certificate Checker Service
  • Inspector Service

 

User VPN is working correctly after Windows logon (auto-connect).

 

We want to make it possible to start the VPN before the Windows login using the Windows Logon Integration feature (as described in K07608215).

So we added the following to the package:

  • Dialup Entry/ Windows Logon Integration
  • Prompt Username and Password
  • Enforce Access Policy in Custom Dialer

And we assigned a name for the phonebook entry.

 

But for some reason, these settings are not working properly.

We don't see any attempt on the F5 APM side and no packet with a tcpdump.

And on the end user we get an error "Logging on to the network has failed. Contact your Administrator for assistance".

 

We're running software version 14.1.0.3.

 

Any idea if I missed something here? maybe a client side setting ?

 

Thanks.

  • no, we dropped this option for now and used a workaround.

    if you ever get this working, I'll be happy to hear about it.

     

    regards

  • The workaround was simply using a local user to login the first time without VPN being up.