Remote Desktop Application

[StevenMcLean]

Re: Remote Desktop Application

If you are using dbf's, then all the processing is done on the run time machines. The server i just a central repository for the data.

If you are using a SQL back end, some of that processing can be moved to the server.

As for the slowdown, the network traffic is the concern not the server slowing down.

[Chuck Bytes]

Re: Remote Desktop Application

With the little knowledge I have of networks, I built my application to run from a central shared machine. I got everyone to map their S drive to the shared folder that contains the application.

When multiple people save or access data, they all share and save to the same location.

In some ways that was bad planning on my part because I never thought I�d be going public with this application.

My quandary lies around the fact that I now want to package and publish this application for distribution so that it will be able to run on anyone�s machine. However, some function buttons I have restricts any new users to create a mapped �S� drive pointing to specific folders. What if there is no network, what if the user wants to just run the app on their own �C� or �D� drive. I guess I�d have to rewrite all the buttons that point to S.

My question is basically two parts. I'm trying to understand how Alpha interacts with my application over a shared computer vs. local computer.

1. Does the machine operating the runtime version do the processing or does the machine (server) containing the developed version do the processing of the application. Which machine does the work of repainting the screens and changing the data in the fields.

2. As more users log into a server containing the application, does this slow down the server.

[jkletrovets]

Re: Remote Desktop Application

I can access my USB items pluged into my computer to get information into the TS session. I have not tried a scanner yet but I have used local printer, USB drives, cameras, & other items like that. We are using Terminal services with a Dell server, Windows 2003 64x server OS, 4g ram, 4 core processor. I check time to time and I have not seen a reason to add more ram. We have had 10 users with no problem at all. Maybe after that it takes a hit but we have not seen any problems. We have set up A5 where it will use a different processors for the different users since by default it will only use one. We also have Quickbooks on this server with no problems. Quickbooks uses the processor with the least demand when accessing the program.

Yeah....ya know....I typed without thinking on this one...I am not real sure of the exact limitations of Microsoft Terminal Server......I forgot the box the network people setup at my client was using Vmware to run 2 virtual servers running Miscrosoft Terminal Server. Now that I think of it...I think it was the Vmware that was causing the problem in this particular instance. In this case it was a nightmare with the config I just mentioned.


I love logmein for support and remote access. I couldn't get along without it. But, I could never see setting up an app for contant day to day access by normal users using it. There is always that slight internet lag.

Regards,

Jeff

[David Boomer]

Re: Remote Desktop Application

I used uSoft Remote Desktop for a while but it was unreliable and different service providers made my life miserable by doing things like blocking port 80 etc...

So... i have used logmein for about a year now... works PERFECTLY!!!


take a look at www.logmein.com

D

[martinwcole]

Re: Remote Desktop Application

if they set up 2003 and T/S, they could have switched to Citrix, which has greater support for local devices.

I understand 2008 will offer support for a much wider range of devices, as well as a new universal printer, instead of a separate driver for every user.

I have heard that after 13 users of the same program, it is best to set op additional servers for T/S for every 13 users - I know of one app that uses about 175 concurrent users of the same program.

[turbojack]

Re: Remote Desktop Application

Just my 2 cents.....

While the theory of running something like Microsoft Terminal Server seems great...and I can see how it might be in the right situation...beware that if you have any peripherals that work with your program you will be out of luck using it. By that I mean, scanners, local printers, Dymo label printers, etc. That'll put a big screeching halt to your app in the TS world. I should mention you can set up printers to work...but it is not as easy as you might expect. But, other USB peripherals are a show stopper.

I have a client who was sold a new TS network in advance of an app I wrote....seemed like a good idea. It has now been completely removed because of the peripheral issue. Lots-O-Money wasted....vendor of the network forgot to mention the whole USB limitation.

Ton - btw from my research you get limited at about 10-12 users per MS Terminal Server...after that performance takes a big hit from what I have read.

Regards,

Jeff

I can access my USB items pluged into my computer to get information into the TS session. I have not tried a scanner yet but I have used local printer, USB drives, cameras, & other items like that. We are using Terminal services with a Dell server, Windows 2003 64x server OS, 4g ram, 4 core processor. I check time to time and I have not seen a reason to add more ram. We have had 10 users with no problem at all. Maybe after that it takes a hit but we have not seen any problems. We have set up A5 where it will use a different processors for the different users since by default it will only use one. We also have Quickbooks on this server with no problems. Quickbooks uses the processor with the least demand when accessing the program.

[StevenMcLean]

Re: Remote Desktop Application

Jeff, we do not use a "Terminal Server" We use Terminal Services and TS Gateway to access physical desktops. This eliminates Terminal Server restrictions and is limited by bandwidth only.

[jkletrovets]

Re: Remote Desktop Application

Just my 2 cents.....

While the theory of running something like Microsoft Terminal Server seems great...and I can see how it might be in the right situation...beware that if you have any peripherals that work with your program you will be out of luck using it. By that I mean, scanners, local printers, Dymo label printers, etc. That'll put a big screeching halt to your app in the TS world. I should mention you can set up printers to work...but it is not as easy as you might expect. But, other USB peripherals are a show stopper.

I have a client who was sold a new TS network in advance of an app I wrote....seemed like a good idea. It has now been completely removed because of the peripheral issue. Lots-O-Money wasted....vendor of the network forgot to mention the whole USB limitation.

Ton - btw from my research you get limited at about 10-12 users per MS Terminal Server...after that performance takes a big hit from what I have read.

Regards,

Jeff

[StevenMcLean]

Re: Remote Desktop Application

http://support.microsoft.com/kb/925876

It is simple to configure, and is very flexible.

[mazatec]

Re: Remote Desktop Application

You can try XPUNLIMITED. Turns Windows XP workstation into a terminal server, can also be used on a server. I have it working at a customers site on SBS2008 and haven't had any problems.

Beau

[Ton Spies]

Re: Remote Desktop Application

For experienced users.

Is there information about TS for beginners?

with the advantages and the disadvantages
about what does it take to buy
number of optimal users

Information with warnings and recommendations (or links to it) are very welcome.

Ton

[StevenMcLean]

Re: Remote Desktop Application

Most of our users work remotely as well as at the office. We are using SBS2008 and they connect to their desktops through either RWW or RDP over TS Gateway. Provided you have good bandwidth Up and Down works like a charm. We have very few issues. About 30% of work is remotely.

[Chuck Bytes]

Re: Remote Desktop Application

I am using V8 & it works. I have not tried with V9 I use Novell Groupwise for email. That may make the difference.

Good to know, but my users won't be apply those functions remotely. What about printing reports from a remote location, will they print at the local computer printer (hard copy and preview)

[turbojack]

Re: Remote Desktop Application

One caution: The one thing I found that did not work when using TS is Letter.Send() or Report.Send() when using the Windows default email client (e.g., Outlook, Thunderbird, etc.). Using the A5 email client does work with those functions, but many users do not like using anything other than what they are used to.

Yes, there may be alternatives to Report.Send() for emailing a report using a default email client under TS. But I for one am sick of having to spend time searching for work arounds for things that should just work as specified.

Raymond Lyons

I am using V8 & it works. I have not tried with V9 I use Novell Groupwise for email. That may make the difference.

[Raymond Lyons]

Re: Remote Desktop Application

One caution: The one thing I found that did not work when using TS is Letter.Send() or Report.Send() when using the Windows default email client (e.g., Outlook, Thunderbird, etc.). Using the A5 email client does work with those functions, but many users do not like using anything other than what they are used to.

The above was true with V9. Probably also true for V10--I do not know. All I know is I could never get any progress on this issue, probably because it is a desktop issue and in case you haven't noticed, Alpha isn't exactly paying rapt attention to there desktop product.

Yes, there may be alternatives to Report.Send() for emailing a report using a default email client under TS. But I for one am sick of having to spend time searching for work arounds for things that should just work as specified.

Raymond Lyons