Virtual desktop infrastructure (VDI) is the practice of hosting a desktop operating system within a virtual machine (VM) running on a hosted, centralized or remote server. The term was coined by VMware Inc.
VMware describes Virtual Desktop Infrastructure (VDI) as “delivering desktops from the data center”. In other words, VDI is where enterprise desktop computers are virtualized, moved to the data center, then presented over the LAN or WAN to the end users.
XenApp 5.0 for Windows Server 2003 supports both 32-bit and 64-bit editions of the Windows server in the same farm.
XenApp 5.0 for Windows Server 2003, 32-bit Edition XenApp 5.0 for Windows Server 2003 is supported on the following operating systems:
Windows Server 2003 (Standard, Enterprise, and Datacenter editions) with Service Pack 1 or 2 Windows Server 2003 R2 Requirements:
Disk space: 400MB for XenApp 5.0 for Windows Server 2003, Enterprise Edition 50MB for the Presentation Server Console 25MB for the Access Management Console Terminal Services, running in application mode Autorun installs the following software, if it is not already installed (you can also install it manually from the Support folder on the installation media):
Desktop virtualization(sometimes called client virtualization), as a concept, separates a personal computer desktop environment from a physical machine using the client–server model of computing. To check about what is VDI, Click Here
Client Hypervisor: A client hypervisor is a hypervisor that resides on a laptop, PC or other client device. A hypervisor is a program that allows multiple operating systems to share a single hardware host.
XenDesktop Terminology and Definitions: Farms are now called Sites (Servers that point to same database are grouped together called sites).
Hubs, switches, routers, and access points are all used to connect computers together on a network, but each of them has different capabilities.
Hubs Hubs enable computers on a network to communicate. Each computer plugs into the hub with an Ethernet cable, and information sent from one computer to another passes through the hub. A hub can’t identify the source or intended destination of the information it receives, so it sends the information to all of the computers connected to it, including the one that sent it.
XenServer DMC (sometimes known as “dynamic memory optimization”, “memory overcommit” or “memory ballooning”) works by automatically adjusting the memory of running VMs, keeping the amount of memory allocated to each VM between specified minimum and maximum memory values, guaranteeing performance and permitting greater density of VMs per server.
Without DMC, when a server is full, starting further VMs will fail with “out of memory” errors. To reduce the existing VM memory allocation and make room for more VMs you must edit each VM’s memory allocation and then reboot the VM.
The OSI, or Open System Interconnection, model defines a networking framework for implementing protocols in seven layers. Control is passed from one layer to the next, starting at the application layer in one station, proceeding to the bottom layer, over the channel to the next station and back up the hierarchy.
Easy Way to Remember the OSI 7 Layer Model
All People Seem to Need Data Processing or Please Do Not Throw Sausage Pizza Away
A virtual machine (VM) is a software container (sometimes called a “guest”) that runs on a host physical computer and that behaves as if it were a physical computer itself. VMs consist of an operating system plus CPU, memory (RAM) and networking resources, and software applications.
A template is a virtual machine encapsulated into a file, making it possible to rapidly deploy new VMs. Each template contains installation metadata—the setup information needed to create a new VM with a specific guest operating system, and with the optimum storage, CPU, memory and virtual network configuration.
You can create new VMs and templates by copying (cloning) an existing VM or template. XenServer has two mechanisms for copying VMs and templates, full copy or fast clone:
Full copy makes a complete copy of the VM’s disks. Fast clone (Copy-on-Write) writes only modified blocks to disk, using hardware-level cloning features for copying the disks from the existing VM to the new VM. This mode is only supported for file-backed VMs.
Using xencenter, we can create our own custom templates like create a vm based on existing templates, install OS, run sysprep and shutdown, then convert to template. Using this custom template we can deploy as many vms as we need and it has some OS in it. But if we want to create an empty template(skeleton template) without any OS, we can do it by this process:
create a vm using “Other install media” template in xencenter.
To create a new storage repository, you use the New Storage Repository wizard: to open the wizard, click New Storage on the Toolbar.
Alternatively, do one of the following:
On the Storage tab for the selected pool or server, click New SR. On the Storage menu, click New SR. You select the physical storage type on the first page of the New Storage Repository wizard and then follow the steps in the wizard as it takes you through the configuration process for that storage type.
