APM "drive mappings"

Hi, it works for me. I just added /persistent:no to disconnect the shared drive after reboot

I forgot to mention to use "net use" command, see: http://technet.microsoft.com/en-us/library/gg651155.aspx for syntax, for example: net use v: \\10.10.4.77\share /user:%{session.logon.last.domain}\%{session.logon.last.username} %{session.sso.token.last.password} Note: everything after "net" command is parameter and has to be specified in the parameters box, otherwise Windows will not launch it :) Also if the environment variables are not set for windows\system32 for some reason the path needs to be specified. There is one caveat, the share will stay mapped after VPN is disconnected, so like mentioned by Yann you should add /persistent:no as well. Also its worth noting that when using Edge client, the normal drive mapping works with SSO, as with Edge we would send the APM user credentials. In contrast, web browser will send the Windows client credentials and not APM user logon credentials, hence the SSO will not work.

Once connected, the user is prompted to allow the command to run for each mapped drive, at which point a command window pops up until that mapping is complete. This is rather painful for the users when you have four to five drive mappings like we do. The other issue is that the drives persist even after Network Access has disconnected. The /persistent:no option only applies when the system is rebooted. We still have thousands of users on Firepass where drive mappings and disconnections happen transparently to the user. It will be difficult to migrate them from Firepass to APM with this kind of APM experience. At the same time, F5 is not supporting Windows 8.1 with Firepass so they've kind of pushed us into a corner. I hope they fix this. I also made a request through our sales team.

good luck with that. im putting this in my list with firepass vs apm differences. f5 should have migrated functionality better then they have done.