Installing Realtime on a Server platform MS 2003 or 2008
First we must state that Realtime Advanced is a desktop product and server installation is not a supported install. With that said we do have clients who have installed RTA on MS Server 2003 and MS Server 2008.
The reason most clients will install on the server is to take advantage of Remote Desk Top for an inexpensive Terminal Server. The steps given here are ones we have found most effective when setting up the install but each IT department will have to realize that some of the steps may require a look at how tight the security is on the server in order for the installation to go smooth. Security settings are different from client to client so we rely on the local IT who manages the server to be able to handle these settings.
The first step will be to insure you have logged into the server as an Admin.
We then need to go to the Run box and change to "Install Mode" (yes this is done only on Terminal Servers or if you are RDP into the server but we have found that it helps greatly with all MS Server 2008 installs even if you are at the system keyboard), to do this the command is:
1. Click Start, and then click Run.
2. In the Open box, type Cmd, and then click OK.
3. At the command prompt, type
change user /install
and then press ENTER.
The following message appears:
User session is ready to install applications.
4. Type exit, and then press ENTER or close the Command Prompt window.
Now you are ready to install the application.
If you are installing from the CD then drill down to the SETUP file. The path on the CD is:
Drive letter:\RealTime\setup.3.5.exe
When we have the Setup file located or perhaps you copied to the server we want to Right Click the icon and run as Admin again. This helps with the registry security settings. Our installer will want to install on the root of C but by using the custom install option you can direct the install to a different partition. If we do this we will need to edit the config file, more on that later.
Once this is done you will need to add our MS Access 97 Run time to the DEP exceptions list.
Now to edit the config file for location find the RealTime.cfg file in the RT3 folder. Open it in Notepad or another text editor and edit the location of the executable, if we needed to change the location of our MSAccess 97 Runtime we will edit that here as well as if we needed to rename our MSaccess.exe.
User session is ready to install applications.
Here is the unedited Config File:
RuntimePath = C:\Program Files\Access 97 Runtime edit this line for location of runtime.
ExeName = MSAccess.exe edit this line if we renamed this executable
SendLoginName = True
SendWindowsUserName = False
LoginName = EndUser
SendPassword = False
Password =
UsePrivateApp = False
AutoCreatePrivateApp = False
Close and save the file. Now drag the config file and drop it on the RealTime.exe icon
This will bring up the user config file GUI:
The Data Root and RealTime Folder will be already populated with the paths chosen during installation and the Access Runtime Folder will reflect the text editing done in the previous step.
Check the options
"Use Private App"
and
"AutoCreate Private Application DB"
to insure that the Remote Desktop sessions will have separate Application Workspace.
At this time we need to put the Server back into execute mode:
1. Click Start, and then click Run.
2. In the Open box, type cmd, and then click OK.
At the command prompt, type
change user /execute
and then press ENTER.
The following message appears:
user session is ready to execute applications
3. Type exit and then press ENTER or simply close the command prompt window
Now we need to ensure that anyone who will be using the RealTime Adminstration software has Full Control permissions on the Sundial Time Systems Registry Key - Please see the KnowledgeBase article for information on setting the permissions
http://www.sundialtime.com/kbfaq/questions/44/Resolving+DSF+Registry+errors
When we run the application for the first time, Right click the short cut or exe file and choose Run as Administrator in order to insure that the Microsoft Access can finalize the Registry settings.
You are now installed on the Server.
Information for Install Mode and Execute Mode were found here in this MS KB entry: http://support.microsoft.com/kb/320185
Search the Knowledgebase
Browse by Category
Print this page
Email this page
Post a comment
Subscribe me
Add to favorites
Remove Highlighting
Edit this Article
