Connecting to SA when already connected via Pulse?

[hutchingsp_]

I've just started experimenting with Pulse.

On our SA (7.2.x) we have a bunch of Terminal Services resources available via the main page.

If someone logs in via the SA directly and starts Pulse from the home screen they seem to still be able to access these resources.

If someone connects directly using Pulse and then attempts to connect to the SA so they can use the Terminal Services reources they're told they already have a session and it will be disconnected.

What's the best workaround here please?

[-red-_]

With the Pulse session already established, is the goal is to merely use the SA as a bookmarks page at that point? 

Aside from that, I would think there is no real value in going back to the SA bookmarks as they should be able to RDP via the established tunnel.

If you are really compelled to do this, you can increase the limit on the number of concurrent user sessions. I believe you have to do this at the ream as well as the sign-in policy level. Although I would still question the value of this approach..

[hutchingsp_]

---

@-red- wrote:

With the Pulse session already established, is the goal is to merely use the SA as a bookmarks page at that point? 

Aside from that, I would think there is no real value in going back to the SA bookmarks as they should be able to RDP via the established tunnel.

If you are really compelled to do this, you can increase the limit on the number of concurrent user sessions. I believe you have to do this at the ream as well as the sign-in policy level. Although I would still question the value of this approach..

Essentially yes.  The SA already has the resource published, bookmarked etc. so it's a nice "portal" to start things from.

I wanted to start rolling Pulse out to some people to test as it seems a much faster way of getting a VPN connection, but some of our major LOB apps run via Remote App from the SA portal - I'd like to avoid duplicating this list of bookmarks if possible.

[-red-_]

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.

[hutchingsp_]

---

@-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?

[-red-_]

---

@hutchingsp wrote:

---

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?

---

Any reason you dont have Pulse/NC set to autostart when the users log in?

[hutchingsp_]

Thinking about it, no, but having tried Pulse I rather like the ease of access you get with the icon always being in the system tray rather than fire up your browser, type an address/click a bookmark, watch the host checker, sign in etc.