Terminal Service does not work for Home Office

[freed96]

lolies. If they aren't connected to vpn how does PDQ reach them.

[freed96]

Pulse just update the ETA to "4/12 midnight PST"

Does that mean it was fixed last night?

[tnguyendoit]

This part isn't clear to me.

I have a bunch of users who connect over the web, authenticate via SAML then LDAPS, then use Pulse Terminal Services Client to RDP.

Let's say when my existing appliances running PCS 9.1R8.2 / PCS 9.1R10 are upgraded to the 9.1R11.x FIXED RELEASE (assuming it's released tonight),

when a user (who's already had the older PSAL / Pulse Setup Client / Pulse Terminal Services Client installed in their Windows profile "\AppData\Roaming\Pulse Secure" previously fetched from PCS 9.1R8.2 / PCS 9.1R10) connects to the newly upgraded appliance which will be running the 9.1R11.x FIXED RELEASE:

---> will those existing Pulse components in the user's profile be automatically updated to a newer version of PSAL / Pulse Setup Client / Pulse Terminal Services which addressed this issue?

From what I see, Pulse Setup Client might be the component with the bad implementation which checked for code-signing cert expiration instead of checking whether the code signing time falls into the period for which the code-signing cert was valid.

[jordanl17]

I've contemplated giving the local user full rights over the Pulse Secure install folder.  has anyone tried this?   I've only got about 40 users and even for me it can be a pain to roll these out.  

[Norsen]

Hey tnguyendoit,

for my point of view, the update from PCS 9.1R9 or R10 to PCS9.1R11.1 would be a "normal" update.

The installerfiles at the PCS would be exchanged to the new version.

As soon a client connects to the PCS he will get the new installer files (via Client or via Webbrowser).

Normaly for RDP-Components or upgrading an existing PulseClient the User doesn´t need any adminrights.

One thing what could be a problem (It´s not mentioned in the KB as broken!):
For the user that haven´t installed the PulseClient yet and don´t have adminrights, there is a small "Installer Service".

If this Installer Service is also broken maybe the user won´t be able to install Pulse Client without adminrights.
=> but this should be only a small group of clients, which are staged right now, the Clientmanagement should exchange the "Installer Service" to the new version

Ressources:
Guide for "Upgrading Pulse Secure Client":
https://docs.pulsesecure.net/WebHelp/PDC/9.0R1/Content/PDC_AdminGuide_9.0R1/Upgrading_Pulse_Secure_C...

InstallerService FAQ:
https://kb.pulsesecure.net/articles/Pulse_Secure_Article/KB23315

[Norsen]

Edit: deleted - wrong info

[crazynick9600]

Don't believe that's the update file. That one was released March 30th and likely still has the issue.

---

@Norsen wrote:

Updatefile is avaiable:
PS PCA SA 9.1R11.1 - build 11915

Who wants to try first 

---

[crazynick9600]

---

@Norsen wrote:

Updatefile is avaiable:
PS PCA SA 9.1R11.1 - build 11915

Who wants to try first 

---

Don't think thats the update. That version was released March 30th so it likely still has the same issue.

[jdkeyworth]

The latest info says:

"Upgrading to the PCS/PPS fix release is not dependent on clients upgrading."

[jdkeyworth]

Latest info says:

"Upgrading to the PCS/PPS fix release is not dependent on clients upgrading."

:-)