Remote desktop vs. browser based web apps. (1 Viewer)

[BlueSpruce]

If the users have a pro version of windows installed on their pc, then the RDP license is included.

Those are only the RDP clients. We're going to be using Terminal Server RemoteApps on Thin Client workstations, which require CAL'$.

 

[CompSMART]

RDP is basically streaming video P2P accross the web with a refresh rate of 30 frames per second. Each viewer's workstation has an RDP client installed which communicates with the RDP server on the host. Since my propsect wants to start out with 15 seats, I did the math on the TS CAL's and it's within the prospect's budget. We also put together a server config for under $5K that can scale up if needed. Windows Server 2022 and SQL Server 2022 Standard editions are also within budget. I'm even looking at Wyse 3040 Thin Clients for the workstations, which I can get for ~ $75/ea.

$5K for a terminal server sounds like a good deal and far less than I would have guessed. I dabbled with thin clients but always found them too limiting for end-users. I work daily using RDP I place a lot of value in being able to do some things locally as a matter of both performance, conserving bandwidth and reducing load on my host.

It sounds to me like you have a good plan and are leading your customer in the right direction - I wish you a successful implementation!

 

[BlueSpruce]

Take a look at WinBoat. MS Access on Linux - in Beta but currently works

I reviwed the README in Winboat's git and it's a VM that runs in a docker container. I've been running Win10/Access in a Linux KVM since 2015. Someone show me Office running natively, not emulated, on Linux, there's no such animal, and probably never will because MS is not going to port it to Linux. It's too bad MS deprecated Xenix back in the 1980's. They could've owned the entire eco system.

 

[Albert D. Kallal]

If no internet browsers or desktop Outlook used! They are resource eaters.

Agree. but then again, my Access applicaitons when run from RDP launch the local copy of outlook (and with attached PDF's etc.).
And we do the same for hyperlinks in Access - we launch + use the local copy of web browser. So, only software we install on the RDP is the free Access runtime. .Full office, Excel, word, and outlook? They remain on the client side, and we thus don't require extra license(s) of office to be installed server side.
And of course with large PST outlook files, it's always a pain point to have multiple installs of outlook based on the same user....

So, if you one of many local users, on company LAN, then clicking on a email button inside of Access? Then local outlook is used + launched.

However, if you running the access app via remote (RDP). Then clicking on that same email button in Access will launch + use the local copy of outlook - not the one on the RDP server (which as noted, we don't have nor install server side).


R
Albert