TSplus Remote Access is a Windows-based remote desktop and application delivery platform designed to allow multiple users to remotely access centralized Windows desktops and business applications.

It can be useful for organizations that need employees, branch offices, accountants, consultants, remote workers, or customers to access applications installed on a central Windows system without installing and maintaining those applications independently on every endpoint.

Depending on the TSplus edition and configuration, users can access resources through:

• Full Windows Remote Desktop sessions
• Published Windows applications
• RemoteApp-style connections
• TSplus connection clients
• HTML5 Web Portal
• Standard web browsers
• PCs and laptops
• macOS devices
• Tablets and smartphones

This guide explains how to install, configure, secure, test, troubleshoot, and maintain a TSplus Remote Access deployment.

1. What Is TSplus Remote Access?

TSplus Remote Access provides centralized access to Windows applications and desktops.

Instead of installing an application independently on every user's computer, an administrator can install the application on a centralized Windows server and allow authorized users to access it remotely.

For example, an organization may have applications such as:

• TallyPrime
• Accounting software
• ERP software
• CRM applications
• Microsoft Office
• Database applications
• Legacy Windows applications
• Customized business software

installed on a central server.

Authorized users then remotely connect to the server and use those applications from their own devices.

The processing is primarily performed on the server, while the remote device displays the user interface and sends keyboard/mouse input.

2. Common TSplus Deployment Architecture

A typical deployment looks like this:

Remote User

↓ Internet

Firewall / Router

↓ HTTPS / configured remote-access path

TSplus Remote Access Server

↓

Published Applications / Windows Desktop

For larger organizations, the architecture can include:

Internet

↓

Gateway

↓

Multiple TSplus Application Servers

↓

Business Applications and Data

Enterprise deployments can additionally use server farms, gateways, load balancing, and failover depending on licensing and architecture.

3. TSplus Remote Access vs Standard Windows RDP

Standard Microsoft Remote Desktop provides remote access capabilities built into Windows.

TSplus adds an administration and application-delivery layer that can provide features such as:

• Application publishing
• Web Portal
• HTML5 remote access
• Client generation
• Centralized application assignment
• Remote printing
• Gateway functionality
• Farm management in applicable editions
• Additional security products and options

The exact features available depend on the TSplus edition and licensing.

4. Before Installing TSplus

Do not immediately install TSplus on a production server without preparation.

First verify:

Operating System

Confirm that your Windows version is supported by the TSplus release you plan to install.

This is particularly important after major Windows feature updates or Windows Server cumulative updates.

Administrator Access

Installation and major configuration changes require administrative privileges.

Windows Updates

Install appropriate security and stability updates before putting the server into production.

However, for critical production systems, updates should ideally be tested and deployed using a controlled maintenance procedure.

Server Backup

Take a complete backup before installation.

For virtual machines, consider taking an appropriate VM-level backup or snapshot according to your virtualization and backup policy.

Do not treat a snapshot as your only long-term backup.

Static Network Configuration

Production servers should normally have a predictable internal IP address.

Example:

192.168.1.10

A changing server IP can break firewall rules, NAT rules, DNS mappings, and remote connectivity.

Public Connectivity

If users will connect from outside the office, determine whether you will use:

• Public static IP
• DNS hostname
• Dynamic DNS
• VPN
• Gateway
• Reverse proxy
• HTTPS Web Portal

Avoid exposing unnecessary services directly to the public internet.

5. Hardware Planning

The correct hardware depends more on the applications and concurrent workload than TSplus itself.

Important resources include:

CPU

CPU requirements depend on:

• Number of concurrent users
• Application workload
• Reports being generated
• Browser usage
• Database operations
• Accounting/ERP calculations
• Antivirus activity

RAM

Memory usage increases with every active user session.

For example, each user may run:

• Chrome
• Excel
• Word
• PDF Reader
• Accounting application
• ERP
• WhatsApp Web
• Other business software

Therefore, calculate RAM based on real concurrent workload rather than simply the number of Windows user accounts.

Storage

For multi-user servers, SSD or NVMe storage is strongly recommended.

Storage latency can significantly affect:

• Login speed
• Application launch
• Profile loading
• Database operations
• Temporary files
• Browser cache
• Windows paging

Network

The server should ideally use stable wired networking.

Internet upload bandwidth at the server location is particularly important because screen updates and remote-session traffic must travel from the server to remote users.

6. Download TSplus Remote Access

Download TSplus only from its official source.

Avoid installers obtained from:

• Software download aggregators
• File-sharing websites
• Torrents
• Unknown mirrors
• Cracked software websites

Using modified remote-access software creates a serious security risk because the software operates at a highly privileged level.

7. Installing TSplus Remote Access

Log on to Windows using an administrator account.

Run the TSplus installer with administrative privileges.

Follow the installation wizard.

The installer may request:

• License acceptance
• Installation location
• Components
• Server configuration
• Restart

After installation, restart the server if requested.

For production servers, schedule installation during a maintenance window so active users are not interrupted.

8. Open TSplus AdminTool

TSplus administration is performed through its administrative interface, commonly referred to as AdminTool.

Use AdminTool to manage areas such as:

• Server configuration
• Web access
• Applications
• Users
• Sessions
• Security settings
• Licensing
• Client generation
• Printing
• Advanced settings

The available options can vary between TSplus releases and editions.

9. Activate the TSplus License

Open the licensing section of AdminTool.

Enter or activate the appropriate TSplus license according to your purchase or subscription.

After activation, confirm that the server reports the expected:

• Edition
• Licensed user capacity
• Update/support status
• Additional components

Do not wait until deployment day to verify licensing.

Test activation before giving the server to production users.

10. Create Windows User Accounts

Remote users require valid Windows accounts.

Accounts can generally be managed through Windows local-user administration or an Active Directory environment, depending on the deployment.

Each person should preferably have an individual account.

For example:

accounts01

accounts02

manager01

sales01

Avoid giving multiple employees the same username and password.

Individual accounts improve:

• Security
• Auditing
• Troubleshooting
• User-specific permissions
• Application assignment
• Accountability

11. Use Strong Passwords

Remote access accounts are attractive targets for password attacks.

Passwords should be:

• Long
• Unique
• Difficult to guess
• Different from usernames
• Not reused between employees

Avoid passwords such as:

123456

password

admin123

company123

user@123

Welcome123

A long passphrase combined with MFA/2FA is substantially safer than a short predictable password.

12. Avoid Routine Administrator Access

Ordinary users should not normally be members of the Windows Administrators group.

Apply the principle of least privilege.

Users should receive only the permissions necessary to perform their jobs.

Administrative accounts should be reserved for administrative work.

This reduces the impact of:

• Malware
• Ransomware
• Accidental deletion
• Unauthorized configuration changes
• Malicious scripts

13. Publishing Applications

One of the major advantages of TSplus is centralized application publishing.

Instead of presenting the complete Windows desktop, administrators can publish only selected applications.

Examples include:

• TallyPrime
• ERP
• CRM
• Microsoft Excel
• Accounting software
• Custom applications

Open the application-management area in AdminTool and add the required application.

Specify its executable path.

Example:

C:\Program Files\Application\Application.exe

Then assign the application to the appropriate users or groups.

14. Full Desktop vs Published Applications

There are two major approaches.

Full Desktop

Users receive a complete Windows desktop.

Suitable when users need access to many applications and Windows features.

Published Applications

Users see only authorized applications.

Suitable for:

• ERP users
• Accounting users
• Data-entry operators
• Branch offices
• External users

Published applications can reduce user confusion and limit unnecessary access to the server desktop.

15. HTML5 Web Portal

One of the useful TSplus capabilities is browser-based remote access.

With the HTML5 client, users can connect through a compatible browser without requiring a conventional RDP client on the endpoint.

A typical deployment may use an address such as:

https://remote.example.com

Users authenticate and then access the applications or desktops assigned to them.

Browser access is particularly useful for:

• Windows computers
• macOS
• Linux endpoints
• Tablets
• Smartphones
• BYOD environments

16. Configure DNS

For professional deployments, use a hostname rather than asking users to remember an IP address.

For example:

remote.company.com

Create the appropriate DNS record pointing to the public IP or gateway used by the deployment.

DNS-based access also makes certificate management easier.

17. Configure SSL/TLS

Production Web Portal deployments should use HTTPS.

Instead of:

http://remote.company.com

use:

https://remote.company.com

TSplus supports encrypted connections and certificate-based HTTPS configurations, including integration with Let's Encrypt in supported configurations.

Ensure that:

• The certificate matches the hostname
• The certificate is valid
• The certificate has not expired
• The certificate chain is trusted
• HTTPS is correctly configured

18. Force HTTPS

Where appropriate, configure the Web Portal to redirect HTTP requests to HTTPS.

This prevents users from accidentally using an unencrypted HTTP connection.

HTTPS should be considered a baseline requirement for internet-facing production deployments.

19. TLS Security

Modern deployments should use current TLS protocols.

Older protocols and weak cipher suites should be disabled where compatibility permits.

For internet-facing environments, administrators should periodically review TLS configuration as security recommendations evolve.

20. Firewall Configuration

Only ports that are genuinely required should be exposed.

The exact ports depend on your TSplus configuration.

Common examples can include:

Service	Typical Port
HTTP	TCP 80
HTTPS	TCP 443
Windows RDP	TCP/UDP 3389

Important: Do not assume that every TSplus installation must expose all these ports.

Port numbers can be changed, and some deployment architectures do not require direct public RDP access at all.

Verify the actual configuration in AdminTool and Windows Firewall before creating firewall or router rules.

21. Do Not Expose RDP Unless Required

A common security mistake is forwarding TCP 3389 directly from the internet to a Windows server.

For example:

Internet → TCP 3389 → Windows Server

This makes the RDP service continuously reachable by internet scanners and password-guessing systems.

Where possible, prefer a controlled architecture such as:

Internet → HTTPS → TSplus Web Portal/Gateway → Server

or an appropriately secured VPN/gateway architecture.

If public RDP access is unavoidable, implement strong additional controls.

22. Router Port Forwarding

If the TSplus server is behind a NAT router and internet users need direct inbound access, the router may require port forwarding.

Example concept:

Public HTTPS Port → Internal TSplus Server

Forward traffic only to the correct internal server.

Do not create broad DMZ exposure merely to make remote access work.

A DMZ-host rule that forwards virtually all unsolicited traffic to the server can unnecessarily expose other Windows services.

23. Windows Firewall

Windows Firewall should remain enabled.

Create only the required inbound rules.

Avoid disabling Windows Firewall as a troubleshooting shortcut.

If disabling the firewall makes TSplus work, that indicates the firewall rules need correction—not that the firewall should permanently remain disabled.

24. Enable Network Level Authentication

Where supported by your deployment, enable Network Level Authentication (NLA).

NLA requires authentication earlier in the connection process and helps reduce unnecessary exposure of a full remote desktop session to unauthenticated connections.

25. Two-Factor Authentication

For internet-facing remote access, password-only authentication should be avoided where practical.

Two-factor authentication adds another verification step in addition to the user's password.

This significantly reduces the risk associated with stolen or guessed credentials.

TSplus provides 2FA functionality as an available security option/add-on depending on licensing.

26. TSplus Advanced Security

Organizations requiring stronger protection can consider TSplus Advanced Security.

Depending on edition, available protections can include controls such as:

• Brute-force protection
• Geographic restrictions
• Firewall-related protection
• Working-hours restrictions
• Ransomware protection
• Permission management
• Access policies
• Trusted devices

The precise functionality depends on the Advanced Security edition and current TSplus licensing.

27. Brute-Force Protection

Internet-facing authentication systems are routinely scanned by automated bots.

Repeated login attempts may come from thousands of different IP addresses.

Implement protections that detect and block repeated failed authentication attempts.

Also review security logs regularly for abnormal login activity.

28. Geographic Restrictions

If users operate only from specific countries or regions, geographic restrictions may reduce the attack surface.

For example, if every employee operates from India, login attempts from unrelated countries may deserve additional scrutiny or blocking according to company policy.

However, consider legitimate travel, VPN services, cloud networks, and roaming employees before implementing strict geographical blocks.

29. Restrict Login Hours

Organizations with fixed operating hours can consider restricting remote access outside approved periods.

For example:

Monday–Saturday
08:00–21:00

This is not a replacement for MFA or proper security, but it can provide an additional layer of access control.

30. Remote Printing

TSplus provides remote-printing functionality including its Universal Printer feature.

Remote printing allows a user working inside the server session to send documents back toward their local device for printing.

Test printing carefully with:

• PDF documents
• Accounting reports
• Invoices
• Excel sheets
• Different paper sizes
• Multiple printers

Printer redirection is often one of the areas that requires testing before production rollout.

31. Test Internal Access First

Before testing from the internet, verify that TSplus works on the internal network.

This separates server configuration problems from router/firewall/internet problems.

Recommended sequence:

Test 1: Local server login

Test 2: LAN remote access

Test 3: HTML5/Web Portal on LAN

Test 4: External internet access

Test 5: External HTTPS certificate

Test 6: Published applications

Test 7: Printing

Test 8: Multiple simultaneous users

32. Testing from Outside the Office

Do not test public access only from another computer connected to the same LAN.

Use a genuinely external connection such as:

• Mobile hotspot
• Another broadband connection
• Remote office
• Mobile network

This confirms that NAT, public DNS, firewall rules, and certificates work from the internet.

33. Common TSplus Connection Problems

Problem: Cannot Connect from Internet

Check:

• Public IP
• DNS resolution
• Router NAT
• ISP restrictions
• Firewall
• TSplus services
• Correct hostname
• Correct ports

Problem: Works on LAN but Not Internet

This strongly suggests an issue with:

• NAT
• Port forwarding
• Public firewall
• ISP
• Public IP
• DNS

Problem: Web Portal Does Not Open

Check:

• TSplus web service
• HTTP/HTTPS configuration
• Windows Firewall
• Certificate
• DNS
• Port conflict

Problem: Login Works but Application Does Not Open

Check:

• Application executable path
• User permissions
• Application assignment
• NTFS permissions
• Application licensing
• Dependencies
• Profile permissions

Problem: One User Works but Another Does Not

Compare:

• Windows group membership
• TSplus application assignment
• Folder permissions
• Registry permissions
• User profile
• Local security rights

34. TSplus Server Is Slow

Do not immediately assume TSplus itself is causing the problem.

Check:

CPU

Use Task Manager or performance-monitoring tools to determine which processes consume CPU.

RAM

Check memory usage across all sessions.

Storage

Monitor disk latency and active time.

Applications

Some applications consume considerably more resources than others.

Browser Usage

Multiple users running Chrome or Edge with many tabs can consume substantial RAM.

Antivirus

Security scanning can increase CPU and disk activity.

Database

ERP and accounting software may depend heavily on database or storage performance.

35. Monitor Individual User Sessions

For multi-user environments, administrators should periodically check which users and applications are consuming resources.

Useful metrics include:

• CPU usage
• Memory usage
• Disk I/O
• Session duration
• Disconnected sessions
• Number of browser processes

A single user with a runaway process can affect every other user on the server.

36. Configure Session Timeouts

Disconnected sessions should not necessarily remain active indefinitely.

Configure suitable policies for:

• Idle sessions
• Disconnected sessions
• Maximum session duration
• Automatic logoff

This can free:

• RAM
• CPU
• Application licenses
• Database connections

Do not use aggressive timeout settings for users who run legitimate long-running processes.

37. Avoid Shared Accounts

Never create one account such as:

officeuser

and allow ten employees to share it.

Instead use:

user01

user02

user03

Individual identities improve:

• Security
• Logging
• Auditing
• Application assignment
• Troubleshooting

38. Back Up the Server

Remote-access servers often become business-critical systems.

Implement backups for:

• Business data
• Databases
• Application configuration
• User profiles where required
• Important server configuration

Use multiple backup layers where practical.

For critical business data, consider combining local/server backups with an independent offsite or cloud backup.

39. Protect Backups from Ransomware

A backup permanently writable from the production server can potentially be damaged by ransomware.

Consider:

• Offsite backups
• Immutable backups
• Versioned backups
• Separate credentials
• Restricted backup permissions
• Multiple retention points

Regularly test restoration.

A backup that has never been tested should not automatically be assumed recoverable.

40. Keep TSplus Updated

Remote-access software is security-sensitive.

Keep TSplus updated according to a controlled maintenance process.

Before updating a production server:

1. Verify release compatibility.
2. Review release notes.
3. Back up the server.
4. Record the existing configuration.
5. Schedule downtime if necessary.
6. Apply the update.
7. Restart if required.
8. Test user login.
9. Test published applications.
10. Test printing and external access.

Avoid blindly updating critical production servers during working hours.

41. Keep Windows Updated

TSplus depends on the underlying Windows environment.

Windows security updates remain important.

However, because remote desktop environments are business-critical, use an update policy that includes:

• Backup
• Maintenance windows
• Compatibility checking
• Post-update testing
• Rollback planning

42. Antivirus and Endpoint Security

The server should have appropriate endpoint protection.

Configure antivirus exclusions only when specifically required by trusted application vendors.

Never exclude entire drives merely to improve performance.

Broad exclusions can create major security gaps.

43. Event Logs

Windows Event Viewer can provide valuable information when troubleshooting:

• Authentication failures
• Application crashes
• Service failures
• Network problems
• Security events
• User profile errors

Check logs rather than repeatedly changing settings without identifying the underlying cause.

44. Production Security Checklist

Before putting a TSplus server on the internet, verify:

• Windows is supported and patched.
• TSplus is updated.
• Server has a static/predictable LAN address.
• DNS is correctly configured.
• HTTPS is enabled.
• Certificate is valid.
• HTTP redirects to HTTPS where appropriate.
• Only required firewall ports are open.
• Direct public RDP exposure is avoided where possible.
• Strong passwords are enforced.
• 2FA is enabled where available and appropriate.
• NLA is enabled where supported.
• Administrator access is restricted.
• Users have individual accounts.
• Application permissions follow least privilege.
• Brute-force protection is implemented.
• Backups are configured.
• Restore testing has been performed.
• Logs are monitored.
• Unused accounts are disabled.
• Disconnected sessions are managed.
• External access has been tested.

45. Recommended Secure Architecture

For a small organization:

Remote User

↓

HTTPS

↓

Firewall / Router

↓

TSplus Web Portal

↓

Published Application / Desktop

For larger environments:

Remote Users

↓

HTTPS

↓

Gateway / Security Layer

↓

TSplus Application Servers

↓

Business Applications / Data

The objective should be to expose the minimum number of services necessary.

46. When Is TSplus Useful?

TSplus can be particularly useful when organizations need centralized access to Windows applications without installing them on every remote endpoint.

Common scenarios include:

• Accounting offices
• Chartered Accountant firms
• Manufacturing businesses
• ERP deployments
• Tally environments
• Branch offices
• Work-from-home employees
• Remote data-entry teams
• Software vendors delivering Windows applications remotely
• Legacy Windows applications that need browser-based delivery

47. Advantages of TSplus Remote Access

Potential advantages include:

• Centralized application management
• Remote desktop access
• Application publishing
• Browser-based HTML5 access
• Remote printing
• Reduced endpoint application installation
• Centralized business data
• Access from multiple device types
• User/application assignment
• Security add-ons
• Scalable server/farm options in appropriate editions

48. Important Security Principle

Installing remote-access software changes the security profile of a Windows server.

The correct approach is not simply:

Install → Open Port → Give Password

A professional deployment should instead follow:

Plan → Install → Configure → Restrict → Encrypt → Authenticate → Protect → Monitor → Back Up → Test

Remote access should be treated as part of the organization's security infrastructure.

Frequently Asked Questions (FAQ)

1. What is TSplus Remote Access?

TSplus Remote Access is software for delivering Windows desktops and applications remotely to authorized users.

2. Can TSplus provide multiple-user remote access?

Yes. Concurrent-user capability depends on the TSplus license, Windows environment, server capacity, and configuration.

3. Can TSplus run on Windows Server?

Yes, supported Windows Server versions can be used, but administrators should always verify compatibility with the current TSplus release.

4. Can TSplus work with Windows 11?

Supported Windows desktop versions can be used depending on the current TSplus release and licensing. Verify compatibility before deployment.

5. Does TSplus support Windows Server 2025?

Current TSplus releases include Windows Server 2025 compatibility. Always verify the specific release before production deployment.

6. Can users access TSplus from a browser?

Yes. Editions supporting the Web Portal/HTML5 client allow users to access remote resources through compatible web browsers.

7. Does the client computer need TSplus installed?

Not necessarily. HTML5 browser access can eliminate the need for a conventional TSplus/RDP client on the endpoint.

8. Can I publish only TallyPrime instead of the complete desktop?

Yes. Applications can be published and assigned to selected users or groups.

9. Can I publish multiple applications?

Yes. Multiple applications can be published and assigned according to user requirements.

10. Does TSplus support Active Directory?

TSplus can operate in Windows environments using local or domain-based user accounts depending on deployment configuration.

11. Does TSplus support SSL?

Yes. Web-based remote access can be protected using SSL/TLS certificates.

12. Can Let's Encrypt be used?

TSplus supports integration with Let's Encrypt in supported configurations.

13. Should I use HTTP for remote access?

For production internet access, HTTPS should be used instead of unencrypted HTTP.

14. Which ports does TSplus use?

It depends on the selected access method and server configuration. HTTP commonly uses 80, HTTPS 443, and standard Windows RDP 3389, but administrators must verify the actual configuration rather than assuming fixed ports.

15. Does TSplus always use port 3380?

Do not assume that TSplus universally uses port 3380. Port configuration varies by version, architecture, and access method. Verify the current AdminTool configuration.

16. Should port 3389 be open to the internet?

Avoid direct public RDP exposure where possible. Prefer a properly secured Web Portal, gateway, VPN, or another controlled remote-access architecture.

17. Can TSplus work without a static public IP?

Yes, depending on the architecture. Dynamic DNS, VPN, or other solutions may be used, but a static public IP generally simplifies business deployments.

18. Can I use a domain name?

Yes. A hostname such as remote.company.com is recommended for professional deployments.

19. Does TSplus provide two-factor authentication?

TSplus offers 2FA functionality as an additional feature/product depending on licensing.

20. Is TSplus secure?

TSplus provides security capabilities, but overall security depends on the complete environment—including Windows security, passwords, MFA, firewall configuration, TLS, patching, account permissions, exposure, and monitoring.

21. Can I restrict users to only one application?

Yes. Application publishing and user assignment can be used to provide access only to required applications.

22. Can users print locally?

Yes. TSplus includes remote-printing options such as Universal Printer functionality.

23. Why does TSplus work inside the office but not from outside?

The most common causes are incorrect NAT/port forwarding, firewall rules, public IP configuration, ISP restrictions, or DNS configuration.

24. Why is TSplus slow?

Potential causes include insufficient CPU/RAM, slow disks, overloaded applications, excessive browser usage, database latency, antivirus activity, poor internet connectivity, or too many concurrent sessions.

25. Should every user be an administrator?

No. Users should normally operate with standard permissions and receive only the privileges required for their work.

26. Should users share the same Windows account?

No. Individual user accounts are strongly recommended.

27. Can TSplus replace Citrix?

TSplus can provide remote desktop and application-delivery functionality for many organizations, but whether it can replace Citrix depends on the organization's scale, architecture, security, application, integration, and management requirements.

28. Can TSplus replace Microsoft RDS?

TSplus can provide an alternative remote-access/application-delivery architecture for certain deployments. Licensing, technical requirements, application compatibility, and organizational policies should be evaluated before migration.

29. Should TSplus servers be backed up?

Yes. Both the server configuration and, more importantly, business applications and data should be protected by a proper backup strategy.

30. How often should TSplus be updated?

Updates should be reviewed regularly and installed according to your organization's security and maintenance policy after compatibility checking and backup.

Conclusion

TSplus Remote Access can provide a practical platform for centralized Windows desktop and application delivery, allowing users to work remotely through traditional remote desktop methods, published applications, or browser-based HTML5 access.

However, successful TSplus deployment involves much more than installing the software and opening a firewall port.

A reliable production environment requires careful attention to:

server sizing, user management, application publishing, network configuration, HTTPS/TLS, firewall rules, 2FA, least privilege, session management, monitoring, Windows security, updates, and backup.

For internet-facing deployments in particular, minimize publicly exposed services and avoid relying on passwords alone. Use HTTPS, strong authentication, restricted permissions, appropriate defensive controls, and regular monitoring.

A properly planned TSplus environment can provide secure and convenient remote access to centralized Windows applications while reducing the need to install and maintain business applications independently on every endpoint.

#Tags