How to Administrate Pervasive PSQL Through
Terminal Services

The security and communication layer used by the Pervasive database relies on your local credentials to validate authentication and administrative rights. The model for administrative functions in Pervasive
has been:

1)To require a login if the request is from a client to a server or
2) To allow any valid user who is logged into a local machine full administrative rights to their local Pervasive configuration.

However, a user who is logged into the system via a Terminal Services or Remote Session appears as a local user to Pervasive and has privileges that are assumed to be at the server level. To ensure a higher level of security, we have chosen to disallow administration-level control when running from a remote Terminal Services client.

You may ask, "What if I can’t connect through a standard
remote connection?"

In order to perform database administration using PCC or other utilities, you need to modify the following registry key on the Server where the Pervasive Database engine is installed:

HKEY_LOCAL_MACHINE 
	SOFTWARE 
		Pervasive Software 
			Utilities Interface 
				Settings 
Restricted Access On WTS client REG_DWORD 0x00000001 (1)

Default value (1=True) enforced access restriction. When changed to 0 you will be able to administer your Pervasive database from the Terminal Services client.

IMPORTANT: It should be noted that changing this value gives users full control of the Pervasive PSQL server; we would recommend using that solution on a temporary basis as needed. The administrator could narrow the security threat by changing the value to 0 only when doing required administrative tasks. Pervasive recommends that the setting only be modified using "regedt32" and restrict most users from changing this value. Remember to only change this setting as needed for required administrative access to Pervasive.