Installing Peachtree 2002 on NT4.0 Terminal Server

[jyingling]

We tried to install Peachtree 2002 onto a NT4.0 Terminal server machine, so users in other states can access and run Peachtree on the server here rather than on their local machines. This is because we want to enter some info here, but let the other user enter some info too. Anyways, when installing, everything seems to go ok, except the install is considerably slower than on other work stations. When trying to run Peachtree for the first time, we get an error message saying that we are running Windows 2000, and don't have rights that these files or applications. We are not ever running that OS. Any ideas????

[Cavarly]

I am in precisely the same boat. I made the changes suggested with the BTI and PCW90 files copied, and made the Regedit change, and now I get the message that it is logged into a 2000 server with restricted rights. I am logged in as an Administrator so I cannot understand that message. I am on a MTS4.0 with Citrix 1.8.

[Dmnkly]

Same here... I'm trying to get Peachtree 2002 to work on a Windows 2000 server under terminal server mode, and when I log in remotely I get the notice that I'm logged on with restricted rights, and need to be granted administrator or power user status to run the application... odd, since I'm logged in as the administrator. I have noticed, however, that if I switch to install mode ("change user /install" from the command prompt), 2002 seems to run just fine. The problem, obviously, is that means only administrators can run it, and also not being familiar with installation mode, I'm quite reluctant to use it for anything other than installations.

Does this little tidbit help anybody?

[TheWolf]

A few months ago I got this back from Peachtree which I forwarded to one of my clients. Don't know how to do it myself but here is the info:

Peachtree does not officially support NT Terminal Server at this time. This is simply a guide as to how many of our NT Terminal Server customers have set up their network to run Peachtree.

NT Terminal Server is similar to a diskless workstation. It can also be a link to Unix via Citrix (Citrix Systems, Inc.).

Usually the workstations do not have local hard or floppy drives. They boot off of the Server. Each user has a directory that not only has the normal user information, but the Windows information as well - such as SYSTEM.INI, WIN.INI, etc.

For example, the users directory path could be C:\WINNT\PROFILES\USERS|username\WINDOWS or C:\USERS\%user%, depending on what is set up for each user and where the user home directories are. Directory paths might be slightly different in your environment.

Release 7 and above:
For Peachtree to run in the NT Terminal Server environment, copy the BTI.INI (Fixed Assets still requires the BTI.INI file) and the PAW70.ini file into the users home directory. Version 8 will use the PCW80.ini file. A registry change must be made to change the Home Directory registry entry to be each users home directory.

To make the registry change, click on Start, then Run. Type Regedit in the Run box. In Regedit, expand the HKEY_LOCAL_MACHINE entry by clicking on the plus sign. Expand the SOFTWARE entry. Expand the Btrieve Technologies entry. Expand the Microkernel Workstation engine entry. Expand the Version 6.15 entry. Select Settings (do not expand Microkernel Interface). Double click the Home Directory entry. Enter the users home directory,

for example, enter be C:\USERS\%user% or C:\WINNT\PROFILES\USERS|username\WINDOWS.
Not doing the above registry change will result in an error 20.

Release 3.5 through release 6:

For each user The BTI.INI and the PAWxx.INI file MUST be copied to the C:\WINNT\PROFILES\username\WINDOWS directory. Also, the bti.ini trnfile= needs to be C:\WINNT\PROFILES\username\WINDOWS.

[Cavarly]

It seems the combination of Wolf's solution and Dmnkly works. you have to use the Changeuser command each time you log on, but it works for that session. The user has to have administrative privileges also.

This should not be done if you have a problem with the peachtree user having full access to the system in addition to Peachtree.

Perhaps Peachtree will eventually support it properly and this workaround will no longer be necessary.

[TheWolf]

Glad I could help. From what I have heard, Peachtree will never make it easy to do remote access or so that one installation can be used by multiple users.