- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
| Change | Justification | Problem | Implementation |
|---|---|---|---|
| Lower PSM Quality | From version 9.8, the param "FramesPerSecond" in PVWA became obsolete, and PSM always recorded sessions at 10 FPS unless there is a load on the machine, where depending on CPU threshold the quality would be lowered up to 2 FPS. | The first few sessions would always be recorded at the max quality (10 fps), thus taking more CPU % until a certain point where quality would be reduced, so the customer had no way of knowing how to gauge the performance because it wasn't linear. By reverting this change manually, we were able to get consistent sessions and approach scaling better during early deployments, the quality at 2-3 FPS is still really good for just desktop recording |
|
|
Slow RDP Connection from PSM Server to Targets when missing certificates | Most customers don't use RDS certificates, which means when PSM tries to RDP it waits the internal timeout time before giving up and connecting through (roughly 15 secs+, the problem is better explained here). |
This can have a bad effect on POC presentations, training courses, and PROD deployments -> End user's complaints. What we've always done in the past is completely disable the certificate check, but recently I stumbled on a case where if PSM is in Azure, it needs to have a certificate check otherwise connection doesn't work. The solution was to just lower the timeout to 3 secs instead of completely disabling it. So I think it's a good enough middle ground where we both lower it and not completely disable it (from an official standpoint). |
|
| Slow non-RDP connection component startup |
RDS Has a built-in session manager that defines how to distribute CPU/DISK resources per each connection, depending on the connection type (RDP, IE, SQL, MMC).
|
It uses a flag called TS Fair Share, which prioritizes different sessions and allocates resources dynamically. Meaning, that some sessions will run fast (Like native RDP and IE) because they will get prioritized and some not (Like TOAD, PLSQL, Checkpoint, or Any local customer app), this breaks our PSM behavior as our sessions are predetermined and shouldn't be treated as adaptive programs. |
|
| Slow connection from PSM to target servers requiring NLA | PSMs are generally installed on a server that will not have access to the internet. As a result, they cannot perform automatic root certificate updates regularly. If they cannot update root certs, they will continue to attempt to do this update on each RDP connection - causing a 15-30 second timeout on each connection attempt. |
The PSM will go to the internet to automatically update root certificates using the Windows Update website when connecting to NLA-enabled Windows servers. When there is no internet connection from the PSM server (especially first installed), you may experience extremely slow RDP from PSM to NLA-enabled Windows Servers. Direct RDP client to these servers takes 2 seconds to establish, through PSM it runs into 20+ seconds or even more. |
On the PSM server, use GPEDIT.msc to change "Turn off Automatic Root Certificates Update" to "Enabled" and then reboot PSM. Location: Computer Configuration | Administrative Templates | System | Internet Communication Management | Internet Communication settings |