How to configure 0 clients on a server

If you want to reduce the time available for desktop support and configuration for your users, you cannot use the local operating system. 0 clients emerged. Virtual Desktop Infrastructure (VDI) can deliver the operating system to end users in a better way, but it still needs to use terminal equipment. In this case, I usually choose thin clients, but they also need to use their own operating system. A series of local configurations are also required. If you can avoid using the operating system, you can reduce potential factors that can cause problems. VDI provides the operating system to the user, but the 0 client cancels the operating system on the terminal. And the end result is that we don't have to do the wrong line for the terminal. Configuring 0 Client 0 Clients on a server is a very simplified device. They are stateless devices with no fans, hard drives, operating systems, and local configuration. In fact, unlike traditional multitasking processors, they typically contain a specific set of chipsets. For example, Wyse P25. Its "processor" is a Teradici TERA2321 PCoIP chip. In other words, P25 is a quiet, low-power (less than 8 watts) device without a brain until it is plugged in and receives instructions. You may want to ask 0 whether the client really does not need any configuration. The answer is yes and no. You need to configure the system, but not on the terminal, and only a few parts need to be configured. What you need to configure first, you should know that when 0 clients start, it's like a newborn baby bird. The birds have no ability to find food on their own. They can't see, they can't hear anything, they don't have the strength to stand up. The only thing they know is to send out signals (Jabber calls) to attract other birds, feed them, and teach them how to prey. The same is true for 0 clients. The DHCP broadcast is sent after it is started because it needs to connect to the agent to get the desktop. But now it doesn't know what time zone it's in (not to mention the time), where the agent is, which resolution to use, and where to send its redirected media stream and USB data. Therefore, the DHCP server needs to contain all this information. These are usually textual information, not a record of a or other pointers. Once this information is obtained, the specific chip in the 0 client can communicate with the agent, and the instructions can be obtained from the management application. These three things teach it how the desktop should work. "After you configure the DHCP server, you need to start 0 client management applications." Each manufacturer has a similar product. It can scan the network for 0 clients that are not connected. Once they are found, you will be given the configuration you defined previously, such as display resolution, connection server information (some models get information from here, not a DHCP server), and restrict the use of sound and USB according to compliance requirements. Each manufacturer's product is different. Some models do not need to configure services at all-but all configurations are implemented through both the DHCP server and the connection server--but some models need to use a configuration server every time the device is started. The other 0 clients may just have to do a search for the configuration server and then store the data in flash memory. In a few cases, the 0 clients introduced by some small manufacturers will first proactively look for configuration servers. Finally, no configuration is required for the actual terminal equipment. The configuration you have previously done will be a reference configuration for the terminal equipment and will only need to be done once. Once you have deployed 0 client systems, you can use any kind of device, regardless of whether they are exchanged or updated, and will get the same performance as the original device. The best reason to use 0 clients is because it is stateless and there is no active component, the only thing that can cause it to fail is because the user has spilled cola on the machine or the machine is physically damaged. The worst news is that we don't have to go to the user's seat to solve the problem, maybe one day we will lose our present job opportunities.