![]() ![]() One important aspect of non-persistent VDI that is based on a single image is servicing. ![]() In some cases, the user's profile is merged with the standard VM to provide the user their settings. Usually the users are provided network locations to store their data. Activity that occurs during startup and thereafter until the next reboot is redirected to a temporary location. When a non-persistent VDI VM is started, a copy of the base image is streamed to the VM. With image-based non-persistent VDI, the base image is read-only. When a non-persistent VDI implementation is based on a base or “gold” image, the optimizations are mostly performed in the base image, and then through local settings and local policies. In this circumstance, operating system and app servicing might operate normally, using traditional servicing software such as Windows Server Update Services or other management technologies. are redirected to the read/write virtual disk assigned to that VM. At the same time, a persistent virtual disk assigned to that VM, with any previous operating system changes merged through a complex process.Ĭhanges such as event log writes, log writes, etc. When the VM is started, a copy of the base image is read into the memory of the VM. A VM is created, and one or more virtual disks are created and assigned to this disk for persistent storage. In this type of implementation there is a base/gold image on one or more host servers. Image-based persistent virtual machine, with personal virtual disks. There might be a web portal the user logs into that automatically directs the user to their one or more assigned VDI VMs. The difference is how the user accesses this VM. Traditional virtual machine, where the VM has its own virtual disk file, starts up normally, saves changes from one session to the next, and is essentially just a normal VM. There are several different implementations of persistent VDI: Other software layers of the VDI solution provide the users easy and seamless access to their assigned VMs, often with a single sign-on solution. ![]() Persistent VDI is, at the basic level, a VM that saves operating system state in between restarts. An in-depth discussion regarding these technologies is outside the scope of this topic, which focuses on the Windows base image settings with reference to other factors in the environment such as host optimization. There are other types of VDI such as persistent and Remote Desktop Services (RDS). Start by installing default operating system on the base VM, and then optimize the base VM for VDI use by removing unneeded apps, installing Windows updates, installing other updates, deleting temporary files, applying settings, etc. A VM is an ideal place to build the image, because you can save the state, make checkpoints and backups can be made, and other useful tasks. The optimization settings would take place on a reference device. To the user this desktop is little different than other virtual or physical device, other than it is accessed over a network. The non-persistent type does not preserve changes to the VDI desktop operating system from one session to the next. There are variations of VDI implementations such as “persistent”, “non-persistent”, and “desktop session.” The persistent type preserves changes to the VDI desktop operating system from one session to the next. VDI environments usually use a base operating system image, which then becomes the basis for the desktops subsequently presented to the users for work. VDI optimization principlesĪ VDI environment presents a full desktop session, including applications, to a computer user over a network. A script that implements the optimizations discussed in this topic-as well as a GPO export file that you can import with LGPO.exe-is available at TheVDIGuys on GitHub.
0 Comments
Leave a Reply. |