The UDS Enterprise VDI connection broker allows access to any remote desktop service, such as virtual desktops or applications, from either a corporate network, also called LAN (Local Area Network), or Internet or WAN (Wide Area Network).
The following diagram illustrates how traffic works to access UDS Enterprise from LAN and the relationship between the different components of the virtual infrastructure:
It has not been a month since The Document Foundation launched LibreOffice 6.0 and it has already exceeded one million downloads. This milestone reflects the growing use of Free Software and Open Source, which is gaining acceptance against proprietary software.
Before making a VDI deployment it is advisable to invest some time in making a detailed design of each of the layers that make up the platform to ensure optimum functioning and maximize the performance of all the components.
In the following image you can see an example of a remote desktop services architecture with the UDS Enterprise connection broker:
In some circumstances, desktop virtualization deployments can be affected by issues such as service interruptions, poor performance or a bad user experience. To solve these incidents and prevent them from happening again, it is convenient to deepen and detect the origin of the problem.
In order to deploy a remote desktop services platform with UDS Enterprise some resources are needed. The components mentioned in this article are essential to successfully install and run the virtual desktops, virtual applications sessions… that we are going to deploy with the VDI connection broker UDS Enterprise.
