![]() Unfortunately, it was only possible to publish modern apps with this solution and not classical ones like Internet Explorer. My first idea was to use the Windows 10 function Assigned Access. Yes, these software solutions have their advantages – but the idea was to just use the available tools! ![]() The other solutions on the other side meant it would be necessary to implement / maintain / configure another software. He can’t choose which Desktop is started when he has assigned multiple Desktops. Desktop Lock always starts the first available Desktop for the user. Some of you might now think: There are solutions on the market available that solve these issues like:īut these solutions have some points we didn’t like in our Scenario: They are either quite limited – e.g. Automatic start of Desktop when only one Desktop is assigned.Installation must be possible with current Software Deployment Tool.Peripheral devices can automatically be redirected to the Citrix Session (e.g.Browser with StoreFront Website is automatically started.User has no access to the local system itself (e.g.The requirements to full fill had been assessable: In some remoting scenarios this is important for a smooth user experience. Furthermore, these devices are often quite powerful that they can easily handle H.264 decoding and even H.265. This means that you sometimes need less / cheaper licenses from Microsoft for connecting to your VDI / SBC environment – I can’t tell you details about this as I am no licensing expert (and honestly, I don’t try to get one). These devices often already have a Windows license included. As we also didn’t like the limitations of the Windows Thin Clients we thought: Why aren’t we creating our own Windows based Thin Client – based on a small form factor device. Beside that it would mean to implement another device type in your environment (which of course require a separate configuration).ĭuring my previous job we had some issues with Linux based Thin Clients that could not be fixed. But they are often limited in performance and manageability. On the other hand, the Thin Client vendors also often offer a Windows based version of their devices. Thus, you must install a native Linux on a hardware an reproduce the issue on this device with the official client software. The vendor of the actual VDI / SBC Client software does not support the (custom) implementation of the Thin Client vendor.Linux Clients have often less features compared to the windows version.the Citrix Workspace App (formerly Receiver). Most companies see them as a Hardware and Software delivery – although some of them now position as a software solution.īeside that most of them rely on a customized Linux system where they integrate the Client Version from the VDI / SBC vendors – e.g. There are several Thin Client vendors around. If you have a look at the Endpoint used in VDI / SBC environments, you often see Thin Clients.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |