Terminal Server

[William Jaurbe]

I am running Win 2000 with Terminal Server services using Thin Client (NCD). I installed and I have the following message when I try to open two sessions “currently, another user has Peachtree Accounting open on this computer. Before you or any other Windows user can star Peachtree Accounting, the other user must exit Peachtree Accounting”

Did anyone know how to fix this?

William Juarbe

[Unregistered]

I doubt you will get that to run, unless it is a multi user license.



You did not say which version, but highly graphical interfaces like the latest versions are typically NOT good performers on Terminal Server clients. Especially, if you have clients working over slow links, VPN, dialup etc.


In addition get rid of all the eye candy, Active desktop, window animation, screen savers, fancy icons and cursors. It takes alot of bandwidth to push all those pixels around.


You would be better off doing local installs and a more convetional network setups. The other alternative is Citrix, not cheap, but better performance.

[Unregistered]

I am using version 9.0 and I have a Multi User Version on a Win 2000 Terminal Server using Thin Clients (Workstation without no Disc and no Hard Drives) on regular LAN Cat 5. Any suggestion?



Originally posted by Unregistered
I doubt you will get that to run, unless it is a multi user license.



You did not say which version, but highly graphical interfaces like the latest versions are typically NOT good performers on Terminal Server clients. Especially, if you have clients working over slow links, VPN, dialup etc.


In addition get rid of all the eye candy, Active desktop, window animation, screen savers, fancy icons and cursors. It takes alot of bandwidth to push all those pixels around.


You would be better off doing local installs and a more convetional network setups. The other alternative is Citrix, not cheap, but better performance.

[PPIE]

I am having the same problem you are having. I use Terminal Server in combination with Citrix to provide remote offices/users access.

I had the problem worked out until I was mandated to upgrade to 2002. If you are still using Peachtree 2000 the workaround is..

Copy and paste bti.ini & pcw80.ini in every users profile..
c:\wtsrv\profiles\YOURUSERS\windows

Then edit the line in the bti.ini file to read...
trnfile=c:\wtsrv\profiles\YOURUSER\windows

That will do it, but don't let them upgrade you to 2002 until the fix for that is found. Hope this helps...

PPIE

[Tara]

I called peachtree support and they told me that they don't support terminal server at this time, but they faxed me a setup help and it worked. This is what they sent me:

"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 alink 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. Version 9 will use the PCW90.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. Ecpand 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."

This is what they sent me and the person putting in the server used this and it worked.

[thebarnesgroup]

Hi,

To both NT 4.0 Terminal Server and Windows 2000 Terminal Services installers. The solution posted by Tara, to get ver 9 to run, and listed in various threads in this forum is a good solution. I banged my head against the wall for almost a week trying to fix the problem. I even tried the Pervasive Technologies folks who through up their hands, because they no longer support the Btrieve components shipped with the Peachtree product line. They also could not propose a replacement because Peachtree requires version 6.15.x of Betrieve.

Once I saw that a registry change is needed the gong went off. There is one small caveat. If you are not familiar with the Home directory structure of your network, please sit down with your administrator and get a clear picture. The reason for this is that the registry change is a one time change that will affect your Terminal Server users globally.

Tara showed two examples:

"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."

The first example is preferrable, make sure you substitue the correct path for the fragement "C:\USERS". The item "%user% is a environment variable which will be resolved at runtime with the correct user name.

The second example can cause you the same probllem as you are experincing if you have all of your users going to the same subdirectoy. Make sure you substitute the same variable: "%user% for username.

Good Luck,


__________________
Marvin Barnes
thebarnesgroup@ameritech.net
Troy Michigan