Log In    |    Knowledge Base    |    4D Home
Tech Tip: Windows 2003 Server: How to see the 4D Server window via RDC
PRODUCT: 4D Server | VERSION: 2004.3 | PLATFORM: Win
Published On: February 17, 2006
Your current browser may not allow you to download the asset. We recommend Mozilla Firefox or Google Chrome.
Log In

If you have 4D Server installed as a service on a Windows 2003 Server machine it may be desirable to view the 4D Server window Remote Desktop Connection (RDC).

In order to see the 4D Server window via a Remote Desktop Connection (RDC) in Windows 2003 Server you must complete two basic steps:

1. Install 4D Server as a service and set the service to interact with the desktop.
2. Log into a Console session via RDC.

Step 1.

In order to properly configure the 4D Server service on the Windows 2003 Server machine follow these steps:

-Launch your database in 4D Server.
-Open the File menu and select "Register Current Database as Service".
-Quit 4D Server.
-Open the Services window (found under Administrative Tools).
-Right-click on the "4D Server - " service and select Properties.
-Select the "Log On" tab.
-Under "Log on as:" select "Local System account".
-Be sure the "Allow server to interact with desktop" checkbox is checked.
-Click the "OK" button to close the service Properties dialog.
-Start the service.

Step 2.

Since the "owner" of the 4D Server service will be the "SYSTEM" account, it is necessary to be logged into a Console session in Windows 2003 Server to be able to see the 4D Server Window. A Console Session means that your remote login is treated as if it were done at the physical machine. There are at least 2 ways to do this:

1. Create and edit an RDP connection file (edit with a text editor). Add this line to the file:

connect to console:i:1

2. Execute this command from the command line:

mstsc /console /v:servername

Where "servername" is the name of the server you are connecting to.

After completing these steps you should be able to see the 4D Server window (along with any other SYSTEM processes) via a RDC.

Here is a useful Microsoft article on this issue: