Desktop virtualization has become an inevitable option for businesses to optimize resources, provide mobility solutions, and deliver a higher level of performance.
Virtual desktop infrastructure (VDI) is virtualization technology that hosts a desktop operating system on a centralized server in a data center. VDI is a variation on the client-server computing model, sometimes referred to as server-based computing.
Remote Desktop Services (RDS) is an umbrella term for features of Microsoft Windows Server that allow users to remotely access graphical desktops and Windows applications.
For desktop virtualization, companies can choose between VDI or RDS: either a virtual desktop infrastructure (VDI) or a remote desktop service (RDS).
While both these technologies have their own strengths and weaknesses, they each have a specific purpose, and businesses need to choose the right solution for their desktop virtualization requirements based on their present and future business needs.
Benefits of VDI:
Utilization of Same Image.
Management of a Single OS Can Reduce Costs.
Processing moves from individual workstations to a VDI server.
Troubleshooting Problems is Easier.
Data is More Secure.
Benefits of RDS:
Single point of maintenance.
Install once, use many.
Reduced licenses expense.
VDI is different from RDS in various ways:
In a RDS environment multiple users can access a single environment, which could be customized on a per user basis but resources are not dedicated to a particular user. Whereas, In a VDI environment each user either accesses their own centrally hosted physical PC or VM or they can access a shared VM.
Also, In a VDI environment physical CPU, Memory and Disk capacity can be allocated to particular user which stops one user’s actions affecting other users.
In Hyper-V virtualization, a guest virtual machine has something called “Integration Services.” By default, all of these services are pretty much enabled, including time synchronization. However, this can cause big issues if you have virtual Domain Controllers, and your physical host servers are not getting their time from a common, reliable source, such as an external NTP server like 0.us.pool.ntp.org, 1.nl.pool.ntp.org, etc.
In particular, if a virtual host is running a guest Domain Controller (DC), then the DC will be getting its time from the clock of the physical Hyper-V server at start-up.
Keep only one time authority
There should be only one time authority on the network, which in turn should be synchronized with a reliable NTP server. Hencem, we up our virtual Domain Controller (DC01) to sync with an outside NTP server, and then set other DC02 to refer to the primary DC only.
To see what our server (DC01/DC02) is using as it’s time authority use:
C:\>w32tm /query /source
Disable time synchronization for both Domain Controller VM’s