PCNetSoftware - Own VPC Server
Software for remote access, remote desktop, remote administration and administration - Remote Administrator Control
Page Content
Own VPC Server
Help | Own VPC Server
- The own VPC server is part of the RAC Server, it is a basic variant,
which is sufficient for operating 10 thousand connected computers.
There is a special version, but it is not yet released for commercial purposes.
- Requirements for operating a VPC server:
- server system on the Windows platform, but not a condition
- minimum 512 MB RAM and enabled virtual memory.
One connection to a VPC will use about 30 MB of memory.
- For less memory usage when more than 1000 computer connections,
you can enable the dispatcher system in racs.ini in the section: VPS Server
[VPSServer]
bThreadDispatcher = 1
maxThreadOnDispatcher = 1000
waitServerThreadOnDispatcher = 10
- On the computer where the VPC server will be operated:
- install the latest version of RAC Server
- in the Settings menu, click on VPC Server Settings
- in the settings, check "Use VPC Server"
- set the ports that then need to be allowed in security programs (firewall, antivirus)
- confirm with the OK button
- assign a DNS address to the computer's IP address (recommended),
in case of IP address change
- This makes the VPC server active.
The next step is to test it by connecting one computer.
The settings for the computer that will be connected to the VPC server are
described on the page
VPC
, you only need to change the VPC server's communication address and possibly TCP ports.
- Finally, you need to try controlling the connected computer from the RAC Client.
The settings are described on the page
VPC
you only need to change the VPC server's communication address and possibly TCP ports.
- Recommendation:
- if the VPC server will be accessible from the public internet,
do not allow the creation of another VPC account
and create new accounts in "VPC Account Management" (Settings menu)
- for self-administration, also connect the VPC server,
to the VPC or enable remote control of the VPC server
- schedule a restart of the computer running the VPC server at least once or twice a week