You can also run the “RDPlus System Audit” in the License tab of the Admin Tool, this can sometimes help find where the issue lies if Anti-virus is not the culprit.
C:\Program Files (x86)\RDPLUS or C:\Program Files\RDPLUS for 32bit systems
(Assuming you installed RDPlus on C: drive)
1. Disable all automatic updates, Windows and other
As a general rule it is not advised to install anything on a production system without good reason, you should always know the content of what you are installing and the potential impact it could have on the application stack installed on the system. These days software vendors are pushing tens of MB of software (bugs included) into live systems all over the world, usually in the background without any notice to the system admins or end users.
If you want to keep your software up to date perform all updates manually outside of production hours and preferably post-backup of your system. We have seen countless cases where businesses show up to work on Monday to a broken system due to automated updates over the weekend.
2. Perform reboots on a regular basis
This will reset the system memory and clear out any unnecessary processes that could be eating up your resources.
3. Avoid web browsing within remote sessions
This will prevent users from downloading and installing incompatible or malicious software on the system.
Additionally, web browsing can be highly resource intensive when users have multiple tabs of complex graphical web pages open, if your server is not spec’d to handle this, RAM and CPU usage can easily spiral out of control.
RDPlus enables you to set the server to forward the opening of web links to the user PC, this can be a smart way to handle this rule.
4. Setup appropriate Anti-virus exclusions
A false detection of RDPlus components can break RDPlus and result in unnecessary downtime. Make sure to exclude native RDPlus files from Anti-virus monitoring to avoid this.
More so, some Anti-virus software will launch a separate instance for each user session, this can heavily affect the performance of your system, when you have 10 separate instances of the exact same software monitoring the exact same system.
To do so all you need is the local IP address of the RDPlus server or the PC name.
You can generate your own specially configured remote link within the RDPlus admin tool or you can use your favourite RDP connection client.
All Windows PC’s come default with Windows default client “Remote Desktop Connection” you can find this by searching for “Remote Desktop” within your Start search function, or run “mstsc.exe”.
External port: Port used for external connection (This can be any port you pick or default 3389)
Internal port: Port used by RDPlus internally, 3389 by default. (Can check or change this port within admin tool Server Change RDP Port)
Internal IP: Internal/Local IP address of your RDPlus server
Protocol: TCP or TCP/UDP
You should now be able to initiate a remote connection using the externally IP address of your server (e.g 100.100.100.99) and the external port you have just forwarded (e.g 55501).
If using the Windows RDP client, you will need to insert a colon after the IP address and enter the external port.
Please note: If you do not hold an active RDPlus Support and Updates subscription you are not entitled to install these updates and could face downtime in a live environment.