The important thing to note is that not all thin clients are created in the same way. You need to make sure that to use any item, you need to measure the needs of Thin Clients and select the right thin ones. How to manage Thin Clients is one of the key issues.
Designed to design desktops that are grouped into a pool based on similarities. To do this, you should use the information collected in the previous steps. This process is obtained by evaluating the desktops and other sources that you use when you start the design, and determine which desktop polls should be created. When the data is analyzed, you will notice the similarities between the programs you are using and decide how to draw pools based on the information. Your priority is to keep as small as possible the pools and not to be larger so big as the pools make it harder to recompose them and will negatively affect the performance. As you can see, balancing pools are one of the key issues in the implementation phase. We will talk about that in the next few articles.
Estimate (size) desktops
The following list contains some of the basics for estimating desktops. This information is gathered from the published VMware dossier and is based entirely on user experiences. For desktops that are built around programs, the solution is vital and vital. As:
Estimates of Servers to Host Desktops:
One of the most frequently asked questions in all projects is the number of virtual desktops that can be created on a host and serve the user. Or, for example, for each virtual desktop, how many Core CPUs should be considered, as in the previous routine, our only answer is: it depends !!!
- First, the CPU usage depends on how much your desktop needs. This is also directly related to the multiplicity of programs, so the answer to this question is only possible from the assessment of the data.
- Second, obviously, the number of desktops we can put on a server is directly related to their repositories. For example, we consider the RAM and CPU for hosts. It’s usually hard to choose between price / performance for an employer! Because these two elements have an inverse relationship.
For this part, we can not provide a precise evaluation that can be cited as solid and acceptable, but we use some assumptions and provide CPU-specific requirements for all types of applications. Users who are grouped into light consumer groups, consumer consumers, and heavy consumers. The basis of our computing is on a standard status, a rack-mount server number that is configured with two Intel Xeon E5-2660 CPUs that have 2.6 GHz and 10 cores per CPU, which is a total of 20 cores per host. To give
In the computational example below, keep in mind that there are fewer than two core hosts, since the Hyperspoker layer (ESXi) itself also needs a CPU repository to execute the executables.
The CPU utilization rate is around 300MHz. At peak time, adding some solutions is an added benefit for you. For this example, we add 10% to 300 MHz. A profile of this type of user can be a person who works in the call center, or is an admin or user that the web collects. These desktops can be unused and consumed at a low rate, and only one or more programs run on them. CPU work requirements are achieved with the following quick calculations:
In this scenario, the user uses the standard server described in the previous sections, and it’s about 17 users per Core.
Usual use of about 500 MHZ of CPU solutions, plus 10%. This kind of user can have data entry, doctors, students, users of Microsoft programs or a helpdesk in this grouping. These desktops are used extensively in business offices and do not consume much. We use the following method to calculate the amount of CPU consumed:
In the scenario, the user defined by the server uses the standard previously described, and you can have around 85 virtual desktops, which give 4 users per Core.
Usual use is about 750MHZ of CPU resolution. Plus 10 percent. This user model can be things like system development, administrator, IT employee, database administrator, or engineering unit. There are plenty of times on the desktop and usually these desktops are used throughout office hours. The CPU usage rate is estimated by the following formula:
In the scenario, a user defined by the standard servers used in the above describes, you can have around 65 virtual desktops giving you 3 users per Core.
Notable Points in RAM Estimates
Estimating the amount of RAM used by desktops is much easier than the CPU, although the balance between servers must be respected. If you have a virtual desktop that needs 2 GB of memory and look at it with the light user, you can create 141 virtual desktops based on previous examples. This means that the server has a storage capacity of 282 GB for hosting a virtual desktop, as well as the necessary memory for running a hyperlink.
Due to the choice of server hardware, it may not be possible to add this amount of memory to the server, or it is always with you to worry about problems with the development of desktops and the lack of hardware support on the server. Do not forget to never over-commit when sizeing and configuring the memory for a virtual machine. This will cause the swap file to be stopped and has no good consequences, such as a dramatic downgrade.
Compare Linked Clone and Full Clone :
There are two types of desktop images to use. Linked clone or full clone. In short, linked clones are made by replicating a golden image inside a thin provisioned replica. This VM has a size similar to that used inside the Golden Image. All the reads are from this VM, and the number of desktops inside the pools does not matter at all. Each desktop has a delta disk to write data on it that continues to grow until it is recomposed, refresh, or deleted on the linked clone. A full clone is exactly what is present and displayed, a copy of its own golden image and occupies space as much as its capacity.
If storage space is important to us, we should use linked cloned. There are important points in using Linked Clones, and with this feature, you lose some potential features, such as:
- VMware Mirage integration
When the linked clone mode is awesome from the outside and gives you the ability to be extensible, you’re certainly tempted to use it, but it’s not always a great strategy. When using the Full Clone design, you should carefully consider the design of the Storage. There are a lot of storage makers offering re-duplication, compression, etc., but the choice should be to increase performance and performance.
Persistent versus non-persistent
When deciding whether to use linked clones or full clones, you need to specify whether you want to use a persistent or non-persistent disk for desktops. With persistence desktops, the user has a dedicated desktop, whether manually or automatically. And when it’s connected to the desktop pool, it’s redirected to its desktop. With non-persistent desktops, users navigate to the pool desktop. In many designs, there are non-persistent linked clone desktops configured and full desktop clones are persistent Are set. But this is not always the case and it is different from your design.
It is recommended to use non-persistent desktops that are built upon request for use of linked clones or instant clones, whenever possible.
User profiles can be presented with View Persona Management and UEM. Group Policy is provided for configuring desktops and app volumes. If the design is appropriate, you can create the easiest way to refresh your desktops with minimal impact on users. If your design is such that it’s not possible, try revising it because it’s very functional and important. If you have implemented the Desktop Persistence mode, use the Horizon Mirage solution to protect and maintain the features listed in the Full Clone Persistence Desktop, depending on the data values or settings you have set.
Desktops that work when there is no connection to servers (whether they are connected via LAN or WAN).In the previous version, this feature was used. That way the server will move a copy of the user’s desktop so that users can use the system offline. When the connection is made, you can sync the desktop changes in the virtual environment. The process of doing this is not very complicated. But downloading and uploading files is very time consuming for users. You should also note that offline mode is often used during POC implementation. It’s rarely seen that this functionality is operational in the operating environment.
Build a hybrid desktop
Designing a flexible desktop is the ability to build and personalize different layers of the desktop. Layers in this area are provided as part of the desktop such as OS, Persona plus apps.
These desktops only have more flexibility to allow a base image to be used. The diagram below depicts a user’s desktop and all key elements that are controlled and managed.