![hp connection manager fatal error windows 7 hp connection manager fatal error windows 7](https://allitexpert.com/blog/wp-content/uploads/2020/05/imgpsh_fullsize_anim.jpg)
Once we were sure it was running well, we’d activate the license server and install the RDS CALS. Our plan was to set up the server for production use, test it for a few weeks, then deploy it and run it for a few more weeks. You can pick up 2003 or 2008 CALS for a good price, but not 2012 CALS. They’re never cheap for the current server O/S. In case you don’t know, Remote Desktop requires a client access license (CAL) for each user or device that will access the server. We also took the opportunity to upgrade to Server 2012. Now, our in-house 2003 Server was beginning to show it’s age, so we planned to upgrade the hardware to a newer 64-bit dual quad-core server with 32gb of RAM. They set up a dedicated server in-house and deploy thin clients or PC’s for their employees. Most of our larger customers also use Remote Desktop to run our software. We host these customers on a dedicated 2008 Server that they access via the internet, again via Remote Desktop. Customers can sign up and pay monthly to use the software. We also rent our point-of-sale system via Remote Desktop. It makes managing 50 users in a 3 story building easy. The thin clients are commodity items, if one fails it can be swapped out within minutes. All of our software is installed on one machine, the server. It’s a great solution as it centralizes the management of the IT infrastructure to one server. They have around 50 users who access it via thin clients, Windows 7, and Windows 8. Our sister company runs our point-of-sale system from a 2003 Server via Remote Desktop.
![hp connection manager fatal error windows 7 hp connection manager fatal error windows 7](https://cdn.diskinternals.com/media/en/products/partition-recovery/diskdrive_get_status.png)
At BBL Systems, we use Remote Desktop Services extensively.