Terminal Services
Microsoft Terminal Services is a multi session environment that provides remote computers access to Windows-based programs running on a server.
Disabling Administrative Functions
In prior releases, the ability to perform administrative functions was prohibited from the client. In Pervasive PSQL v11 SP3, Pervasive PSQL clients running within Terminal Services client sessions can perform Pervasive PSQL administrative functions by default. For example, a user with such a client can change configuration settings for Pervasive PSQL, create DSNs, and use the Monitor utility.
If you want to restrict this capability, intervention is necessary from a system administrator.
►
To disable remote administrative functions for Terminal Services clients
1
From PCC, open the properties for the MicroKernel Router under Local Client.
See To access configuration settings in PCC for a local client in Advanced Operations Guide.
2
On the Properties dialog, check Restrict Administrative Functions from a WTS Client.
3
Click OK, then exit PCC and start it again for the setting to take effect.
*Note: Pervasive PSQL Server engines are supported for use with Microsoft Terminal Server and Citrix XenApp running within an Active Directory environment.
Terminal Server as Network Server
You may use your terminal server as your main network server and database server. However, if you have high usage of the server as a file server as well as many terminal sessions running at the same time, you may find the performance less than satisfactory.
Another concern is having all of your mission critical services on the same machine. If it goes down, all of your services go down at once.
For these reasons, you may wish to consider distributing your mission critical services on two or more computers.
Workgroup Engine Running as a Service
You may configure your server to run the Workgroup engine as a service. This allows the engine to start automatically when the operating system starts. A user is not required to log in to start the engine. Refer to Running the Workgroup Engine as a Service.
*Caution: Running the engine as a service requires the Log On as Service privilege. If you select to run the engine as a service under a user account other than the default Local System account, you will need to modify the Log On Properties for the Service using the Windows Control Panel.