But some action is needed on your part before December 1st, 2023!
With the traditional SAP Business One Client that many of you are familiar with, deployment via the Cloud is dependent on Microsoft Remote Desktop Services.
To build a fault-tolerant and scalable Remote Desktop Services (RDS) deployment, additional servers are required that perform different functions in the RDS landscape. The gateway handles the initial connection and encrypts the data, and the connection broker makes sure that your session (if disconnected) gets reconnected to the right RDS server. In front of both of these, the RDS Web Server handles the publishing of the sessions for the RDP Client and the HTML5 RDS Web Client.
For this reason, it’s important to make sure that these services are always available. To that end, we have recently deployed additional gateway, connection broker and RDS Web Servers, all of which sit behind a load balancer, which ensures that sessions are sent to the most available servers. By most available, we mean that the load balancer looks at how many sessions are on each server and what available resources are there and will send your inbound connection to the best one.
For many of you, this will be transparent as you are using the Windows Control Panel RDS Feed. But for others, to take advantage of this additional investment we have made to boost performance resilience and redundancy, you may have to make a couple of changes.
Analytics Cookies (Google Analytics)
These allow us to measure and improve performance, understand how visitors interact with our site, and ensure we're meeting your needs.
Third-Party Cookies (YouTube Embeds)