I'm sure I'm not the only person to run into this, so here is some very helpful info.
We setup PT2004 on a Windows Terminal Server 2003. I found some articles on how to get it working.
Basically I just followed that article, but I modified the registry for The "HKLM\SOFTWARE\Btrieve Technologies\Microkernel Workstation Engine\Settings\Home Directory" setting. I pointed that to %userprofile%\Windows. Props to Matt! We didn't use the W: drive.
Getting Peachtree working on a terminal server is nothing new, and I don't claim that I've come up with anything special. Here's the interesting part....
2003 SBS Server Called SERVER-DATA has the PT data on it.
\\SERVER-DATA\PEACHTREE\ mapped as P:. This doesn't have the PT program installed. Just the company file.
2003 Server called SERVER-TERM. This is the server that has PT installed on it. It opens PT from C:\Program Files\"Typical Peachtree Folder". It opens the data from P:\.
Scenario 1: No other users are in PT (LAN or TS). I go in via a TS session, open PT and open the company files. It opens fine. It closes just fine.
Scenario 2: 1 XP Pro User in PT. The PT app is installed on the XP Pro machine, and the company is accessed by the P: drive. I go in via a TS session, open PT and open the company files. It opens fine. It closes slowly. The child window, what appears to be the actual company closes in two or three seconds. The main PT window takes
another 10-15 seconds to close. If the XP Pro users closes out before the TS session does there isn't any lag. This scenario applies to two TS sessions accessing the company data as well.
Scenario 3: I go in via a TS session as administrator, open PT and open the company files. It opens fine. I go in via a second TS session as myself and open a sample company located on P:. Guess what? Either session will close out PT w/o any lag.
We worked on various options. Tried SMB redirector mods with no real effect. Eventually we found this article:
Its a patch, just call Microsoft, download, and enjoy!
Thanks to Matt and all your help!
We setup PT2004 on a Windows Terminal Server 2003. I found some articles on how to get it working.
Basically I just followed that article, but I modified the registry for The "HKLM\SOFTWARE\Btrieve Technologies\Microkernel Workstation Engine\Settings\Home Directory" setting. I pointed that to %userprofile%\Windows. Props to Matt! We didn't use the W: drive.
Getting Peachtree working on a terminal server is nothing new, and I don't claim that I've come up with anything special. Here's the interesting part....
2003 SBS Server Called SERVER-DATA has the PT data on it.
\\SERVER-DATA\PEACHTREE\ mapped as P:. This doesn't have the PT program installed. Just the company file.
2003 Server called SERVER-TERM. This is the server that has PT installed on it. It opens PT from C:\Program Files\"Typical Peachtree Folder". It opens the data from P:\.
Scenario 1: No other users are in PT (LAN or TS). I go in via a TS session, open PT and open the company files. It opens fine. It closes just fine.
Scenario 2: 1 XP Pro User in PT. The PT app is installed on the XP Pro machine, and the company is accessed by the P: drive. I go in via a TS session, open PT and open the company files. It opens fine. It closes slowly. The child window, what appears to be the actual company closes in two or three seconds. The main PT window takes
another 10-15 seconds to close. If the XP Pro users closes out before the TS session does there isn't any lag. This scenario applies to two TS sessions accessing the company data as well.
Scenario 3: I go in via a TS session as administrator, open PT and open the company files. It opens fine. I go in via a second TS session as myself and open a sample company located on P:. Guess what? Either session will close out PT w/o any lag.
We worked on various options. Tried SMB redirector mods with no real effect. Eventually we found this article:
Its a patch, just call Microsoft, download, and enjoy!
Thanks to Matt and all your help!