Hello,
We are experimenting with jettisoning our terminal servers for high bandwidth sites and going to a local install. Our initial tests of 10 PC’s out of 200 in our main site have been very promising. We are seeing less frustrated users, fewer calls to the helpdesk and the application is opening charts about 3 times faster. We’ve also spoken with some very large customers (500+ desktops) that have gone all local installs with great success.
Our two worries are…
1. Deploying upgrades. I think we have that one figured out as we will be using a Manage Engine Desktop Central desktop management software tool to push software.
2. Bandwidth.
I’m wondering if anyone knows what the bandwidth requirements are for an average session of Centricty? I know on the NextGen EMR they require 50kbps for every terminal server session and 150kbps for every fat client, but haven’t found the requirements in the CPS documentation. The other tack we could take is loading up network tracer on some workstations and monitoring sql and html traffic to the CPS servers.
Thoughts?
Thanks,
Jeremy
Jeremy, I noticed that the most recent calculating_hardware_requirements_CPS122_2.19.16 document has a network bitrate calculation page that may help you figure this out.
I usually calculate it at 115kbps for a fat client install. Currently have around 150 fat clients in my environment with a total of about 400 total client installs.
I'd be curious how your Manage Engine software push works for you, especially if you have users using VAR-created addons.
Centricty has proven horrendous as far as "upgradability". In my experience, the silent installation capabilities of the EXE is terrible. Needless to say, I've never had any luck automating fat client upgrades, which is why we're exploring a RemoteApp environment. , Though, I heard they'll be supplying an MSI installer with the latest CPS 12 SP, so we'll see how that goes.
Thanks for everyone's help. Between the 115kbps quote and the hardware requirements document I think we're in good shape. I'll report back if we have any luck packaging an installation file.