I'm trying to set up SVW for access to some services (and preventing screen capture as per an earlier post on the subject). Some of the servers are Windows Terminal Servers and these seem to work fine using a defined Terminal Services profile available to the role. Users can get to the terminal servers from inside the SVW, but not from the main desktop, and they can't copy data from the SVW sessions back into unsecured territory. So far so good.
Some of the servers are not accessible using Terminal Services, so I am trying to configure access to them either through Pulse or WSAM. First problem is that Pulse does not connect after signing in to SVW and I get a message that Pulse is not compatible with SVW (see attachment). Is this true - I am running 7.2R4 VTE in my test lab?
Next I tried configuring server access via WSAM instead of Pulse. This works fine from inside SVW, but it also works just as well from outside it. Is it possible to tie WSAM down so that only traffic from inside SVW is allowed? If so, how?
Any help gratefully received.
you can disable the option of switching back to the real desktop but WSAM is still active in the real desktop after existing SVW. Is there any option to log off the session after exiting the SVW?
yes, that is correct: SVW is not supported with Pulse.
From the Pulse admin guide:
On endpoints that connect to Junos Pulse Secure Access Service, if Junos Pulse is running on the Windows main desktop, you cannot launch Pulse within Secure Virtual Workspace (SVW). SVW is not supported with Pulse.
For WSAM, no, it is not possible to prevent the real desktop from connecting to resources over the WSAM "tunnel;" however, you can prevent users from switching back to the real desktop while the SVW session is open.