@-red- wrote: I am still having a hard time thinking through this :) I assume your RDP bookmarks are configured to use the IVE as a broker, so even with the Pulse session established, RDP traffic takes a different path. I wonder if there are performance implications here. Just thinking through the path in this scenario. User established VPN session via Pulse terminated at the IVE Using an established Pulse session, user opens a new session to the IVE, presumably via internal interface? User clicks the RDP bookmark and uses the IVE broker functionality on the IVE to connect to the resource. If I am not mistaken, (and I would encourage one of the Juniper guys to speak to this) enabling multiple user sessions would also consume additional user licenses. It may be a whorthwhile effort to figure out which of the RDP users actually need the full Pulse client, and who would be content just using the RDP bookmarks. Let them have a choice in how they establish a session. Allow your RDP users, and users to continue logging in via a browser, and encourage those who dont to use Pulse. Ahh sorry perhaps I wasn't clear about this part. Right now users sign into the IVE and launch NC from the portal. They can still launch TS apps from the IVE portal with network connect running. Pulse seems to be where Juniper is headed and it looks like a quicker way to establish a TCP/IP level connection to the LAN to get to mapped drives etc. but it seems if you initiate the connection from Pulse, rather than starting Pulse from the IVE portal, you have the issue I described. The way it works now it's a two-step process to start NC, but I only have to update one set of TS bookmarks in one location and everyone is good to go. Hopefully that's a little clearer?
... View more