1. Microsoft® Virtualization Solutions
Nicola Ferrini
Level Advanced

2. Who Am I ? Trainer Technical Writer Systems Engineer
Server & Application Virtualization Technology Specialist
Technet Speaker
Microsoft System Center Influencer
More on:

3. Agenda Evaluating and Planning for Virtualization
Server Virtualization using Hyper-V
Managing Virtual Machines using Virtual Machine Manager 2008 R2
Desktop Virtualization using Remote Desktop Services
Application Virtualization using APP-V
Desktop Virtualization using MED-V

4. Virtualization Modes Profile Virtualization
Document redirection
Offline files
Management
Presentation Virtualization
Application Virtualization
Desktop Virtualization

5. What Is Server Virtualization?
Server virtualization enables multiple virtual machines to run on one physical host
Benefits:
Server consolidation
Service or application isolation
Simplified server deployment and management
Increased service and application availability
Multiple operating systems can run on one consistent platform

6. What Is Hyper-V? Provided by OS ISV/IHV/OEM Microsoft Hyper-V
Microsoft / Citrix
Parent Partition
Child Partitions VM
Worker Processes
Applications
Applications
Applications
Applications
User
Mode
WMI Provider
VM Services
Windows Server 2008
Windows Server 2003, 2008
Non-Hypervisor Aware OS
Supported Linux Distributions
Windows Kernel
VSP
Kernel
Mode
Windows Kernel
VSC
IHV Drivers
Linux VSC
Emulation
VMBus
VMBus
VMBus
Windows hypervisor
Ring -1
“Designed for Windows” Server Hardware

7. Features of Hyper-V in Windows Server 2008 R2
Improved VHD performance
Live Migration
Dynamic virtual machine storage
Enhanced networking support
Enhanced processor support
Enhanced processor support
Hyper-V in
Windows Server 2008 R2
Cluster shared volumes

8. Requirements and Limits for Virtual Machines and Hyper-V
Host computer components
Virtual machine components
Component
Description
Logical processors 64
Virtual processors per logical processor 8
Virtual machines per server
384 running virtual machines
Memory
1 TB
Storage
No limits imposed by Hyper-V
Physical network adapters
Component
Description
Virtual processors 4
Memory
64 GB
Virtual IDE disks
Virtual SCSI disks
256
Virtual hard disk capacity
2040 GB
Snapshots 50
Virtual network adapters 12

9. LAB

10. Demonstration: How to manage Hyper-V
In this demonstration, you will see how to manage and configure Hyper-V using Hyper-V Manager

11. Using and Configuring iSCSI Storage
iSCSI Initiator
iSCSI storage:
Uses the existing IP network
Is configured using the iSCSI initiator
Should use a dedicated NIC
Required for virtual machine failover clustering

12. Settings for Virtual Machines
Virtual Machine Settings

13. Exporting and Importing Virtual Machines in Hyper-V
Originating Computer
Exported Virtual Machine
Destination Computer
Imported Virtual Machine

14. What Are Hyper-V Virtual Machine Snapshots?
Snapshot files:
Virtual machine configuration .XML file
Are a point-in-time copy of a virtual machine
Do not affect the running state of a virtual machine
Save state files
Differencing disk (.AVHD)

15. Demonstration: Using Snapshots in Hyper-V R2
In this demonstration, you will learn how to:
Take and manage a virtual machine snapshot
Create a snapshot
Revert to a previous snapshot
Merge snapshots

16. Planning Hyper-V Hosts
When planning Hyper-V hosts:
Simplify and standardize the host platform
Consider using the Server Core installation option
Automate and standardize administration of the virtual server environment by:
Standardizing the host and virtual server configuration
Implementing remote management solutions at the host server level
Implementing VMM

17. Guidelines for Designing Virtual Machines
Simplify and standardize the host platform
Plan virtual machines for specific server roles by:
Monitoring the servers before virtualization
Configuring each virtual machine with a hardware configuration that is similar to the hardware required on a physical server
Deploy Windows Server 2008 or Windows Server 2008 R2–based virtual machines whenever possible
Consider other options for ensuring physical server utilization

18. Designing Virtual Machines for SQL Server
Guidelines:
Ensure that the Hyper-V integration components are installed
Plan virtual machine hardware settings to match physical server hardware
Use fixed-size disks and SCSI controllers for database and log file drives
To ensure adequate CPU capacity:
Remember virtual machines are limited to four processors
Do not over-commit CPU resources
Remember networking-intensive workloads require more CPU capacity

19. Designing Virtual Machines for Exchange Server
When designing virtual machines for Exchange Server:
Use standard server sizing rules
Configure appropriate storage
Do not use virtual machine snapshots
Configure adequate CPU resources
Consider how to use Hyper-V and native Exchange Server high availability
Consider I/O requirements

20. Designing Virtual Machines for SharePoint
When designing virtual machines for SharePoint:
Configure virtual machine hardware like physical server hardware
Do not take snapshots of virtual servers
Avoid over-committing the virtual CPUs
Consider deploying all of the servers in a server farm on a single physical server
Assign adequate memory
Use only Internet Protocol Version 4 (IPv4)
Choose the right storage implementation for the SharePoint server role

21. What Is a Failover Cluster?

22. Failover Cluster Functionality in Windows Server 2008 R2
Clustered Shared Volumes
Live migration
Processor compatibility mode
Windows PowerShell cmdlets for failover clusters
Additional tests in cluster validation

23. How Does a Failover Cluster Work with Hyper-V Nodes?
Shared Bus or iSCSI Connection
A dedicated network connects the failover cluster nodes

24. Implementing Hyper-V and Failover Clustering
Install and configure Windows Server 2008 or Windows Server 2008 R2 1 2
Configure shared storage 3
Install the Hyper-V and Failover Clustering features 4
Validate the cluster configuration 5
Create the cluster 6
Create a virtual machine on one of the cluster nodes 7
Make the virtual machine highly available

25. Configuring Clustered Shared Volumes
CSV benefits:
Fewer LUNs required
Better use of disk space
Virtual machine files are in a single logical location
No special hardware required
Increased resiliency
To implement CSV: 1
Create and format volumes on shared storage 2
Add the disks to failover cluster storage 3
Add the storage to the CSV

26. What Is Live Migration?

27. Considerations for Implementing Live Migration
Verify basic requirements
Configure a dedicated network adapter for the private virtual network
Use similar host hardware
Verify network configuration
Manage Live Migrations

28. What Is VMM 2008 R2?
VMM 2008 R2 provides centralized administration and management of your virtual environment
VMM is used to:
Manage Hyper-V hosts
Manage virtual server hosts
Manage VMware hosts
Manage and deploy virtual machines
Perform physical-to-virtual (P2V) and virtual-to-virtual (V2V) conversions

29. Infrastructure Components of VMM 2008 R2
VMM Administrator Console
VMM Server
VMM Database
VMM Library
Hosts
Host groups
VMM Self-Service Portal

30. What’s New in VMM 2008 R2? What’s new:
Windows Server 2008 R2 Hyper-V Host Management
Enhanced Support for SAN Transfers
Enhanced Support for Shared Storage
Quick Storage Migration
Maintenance Mode for Hosts
Support for VMware Port Groups for Virtual Switches
Support for Virtual Machine Permissions Assigned in Hyper-V

31. Demonstration: Managing SCVMM 2008 R2
In this demonstration, you will learn how to manage SCVMM 2008 R2

32. What Is Windows PowerShell?
Windows PowerShell is:
A scripting and command-line technology
Directly accessible through a command shell, msh.exe
Used by GUI tools
Windows PowerShell features include:
Cmdlets
Aliases
Variables
Pipelining
Scripting support
Access to cmd.exe commands
Signed scripts

33. Using Windows PowerShell to Manage VMM
The VMM command shell includes the standard PowerShell cmdlets, as well as a set of cmdlets specifically for VMM, such as:
Get-VMCheckPoint
Get-VMCheckpoint -MostRecent –vm "VM01" | Restore-VMCheckpoint
Get-Help Get-VMMServer

34. Types of Hosts That VMM 2008 R2 Supports
Windows Server based host in trusted domain
Windows Server based host in non-trusted domain
Windows Server based host in perimeter
ESX based host
Supported Virtualization platforms:
Virtual Server 2005 R2
Hyper-V
VMware ESX Server 3.0 or above
VMware ESX Server 3.5i
VMware VirtualCenter (VC) 2.5 (VMware Infrastructure 3 [VI3])
VMware vSphere 4 (VI3 features only)

35. Demonstration: Adding Hosts to SCVMM
In this demonstration, you will learn how to add hosts to SCVMM 2008 R2

36. Supported Guest Operating System Platforms for Virtual Machines
Server operating systems that the child partition supports:
Windows 2000 Server SP4
Windows Server 2003 SP2 (x86 Edition or x64 Edition)
Windows Server 2003 R2 SP2 (x86 Edition or x64 Edition)
Windows Server 2008 (x86 Edition or x64 Edition)
Windows Server 2008 R2
SUSE Linux Enterprise Server 10 with SP2 (x86 Edition or x64 Edition)
SUSE Linux Enterprise Server 10 with SP1 (x86 Edition or x64 Edition)
SUSE Linux Enterprise Server 11 (x86 Edition or x64 Edition)
Red Hat Enterprise Linux (RHEL) 5.2 and 5.3 (x86 Edition or x64 Edition) (Emulated devices only)
Client operating systems supported in child partition:
Windows XP SP3 (x86 Edition or x64 Edition)
Windows Vista SP1 (x86 Edition or x64 Edition)
Windows 7 (x86 Edition or x64 Edition)
Integration Services improves integration between the physical computer and the virtual machine

37. Sources for Deploying New Virtual Machines

38. What Is Host Rating?
Represents suitability of the physical machine to the host virtual machine
Host rating:
Depends on:
CPU usage
Memory usage
Disk I/O
Network usage
Is a recommendation, not a mandatory condition
Calculation metric can be changed

39. What Is Virtual Machine Placement?
Evaluation and selection of the most suitable host for the virtual machine
Types:
Automatic placement
Intelligent placement
Considerations:
Default path must be configured
Host compatibility must be checked

40. Demonstration: Creating and Placing a New Virtual Machine Using VMM 2008 R2
In this demonstration, you will learn how to use VMM to create a new virtual machine, place it on the host, and store it in a library

41. What Is P2V Conversion?
Converts an operating system that is running on physical hardware to an operating system running inside a virtual machine
Considerations:
VHDs are made from disk images from source computer
New virtual machine has the same computer identity as the physical computer

42. Requirements for the Source and Destination Computers in the P2V Process
Requirements for the source computer:
Requirements for the destination computer:
RAM size
Volume size
ACPI BIOS
Cannot be in perimeter
Virtualization platform
RAM size
Cannot be in perimeter
Considerations for the operating system:
NT 4.0 is not supported
Itanium versions are not supported
Windows Server 2003 Sp1 is not supported

43. Online and Offline P2V Conversions
Online conversion uses VSS to convert the physical server to a virtual machine while the operating system and applications are running on the physical server
Offline conversion uses Windows PE to convert the physical server to a virtual machine while the operating system and applications are not running on the source server

44. Usage Scenarios for P2V Conversion
Consolidating servers
Decommissioning of old hardware
Simplifying support for old operating systems
Prioritizing Virtualization Candidates:
Underutilized computers that are not business critical
Computers with low utilization
Computers with higher utilization
The remaining underutilized computers

45. What Is V2V conversion?
Converts existing VMware virtual machines to virtual machines running on Hyper-V
Converting VMware-based virtual machines:
From ESX host, Library or File Share
Original VM is unaffected
.vmdk files are used as source to build .vhd

46. V2V Conversion Requirements
Operating system in virtual machine
Virtual machine files
.vmx
.vmdk
Requirements for the destination host server:
Windows Server bit with Hyper-V
Cannot be in perimeter network
At least 256MB RAM and memory for virtual machine

47. Methods and Considerations for the V2V process
Conversion directly from an ESX Server host
Conversion from the VMM library
Conversion from a Windows or NFS share

48. Demonstration: Performing a V2V Conversion
In this demonstration, you will learn how to convert a VMware virtual machine, from the VMM library, by using a V2V conversion

49. Migrating Virtual Machines Between Hosts
When migrating, be aware that:
Migration is supported only between compatible platforms
During migration, virtual machine files are moved to the new host
The virtual machine remains online during migration
You can move virtual machines by LAN or SAN transfer only
You can use Quick Storage Migration to move the virtual machine storage between storage systems while the virtual machine is running

50. Methods for Performing Virtual Machine Migration Between Hosts
Use the Migrate action
Use the Migrate Storage action
Drag and drop the virtual machine onto a host
Drag and drop the virtual machine onto a host group

51. Actions for Operating and Managing Virtual Machines
Description
Start
Starts a virtual machine that is stopped, paused, or in a saved state
Stop
Stops a virtual machine, and does not save any state information
Pause
Suspends execution of a virtual machine, and keeps all virtual machine state in memory
Save state
Suspends execution of a virtual machine, and saves the current virtual machine state to disk to release memory and CPU resources for other virtual machines
Discard Saved state
Discards the state that was saved for a virtual machine that is in a saved state, and turns off the virtual machine
Shut down
Shuts down the guest operating system on the virtual machine
Connect to virtual machine
Connects to a virtual machine by using Remote Desktop Protocol (RDP)

52. Deploying, Migrating, and Storing Virtual Machines
Action
Description
New virtual machine
Starts a wizard for creating new virtual machine
Clone
Clone existing virtual machine
Deploy
Removes virtual machine from VMM Library and place it on a host
Migrate
Migrate virtual machine between hosts
Migrate Storage
Migrate storage location of virtual machine
Store in Library
Stores virtual machine in VMM Library for later deployment
Delete
Delete virtual machine from VMM Admin Console and delete all virtual machine files

53. Managing Virtual Machine Configurations and Disks
Management options:
Convert to fixed type of virtual hard disk
Compact virtual hard disk
Expand virtual hard disk
Use and existing virtual hard disk
Create a new virtual hard disk
Pass-through to physical drive on host
Repair
Disable undo disks
Install virtual guest services
View networking
Disable
Virtual Hard Disk Configuration

54. What Is Virtual Machine Checkpoint?
By creating checkpoints for a virtual machine, you can restore the virtual machine to a previous state
Checkpoints:
Are created in the VMM Administration Console
Can be created while the virtual machine is running
Are portable
Are the same as Hyper-V snapshots
Virtual Machine Management

55. Considerations for Using VMM Checkpoints
Before restoring to a checkpoint state, you should perform a backup
Checkpoints:
Affect virtual machine performance
Are not a replacement for backup
Are stored with the virtual machine on a host

56. What Is the VMM Library? VMM Library is:
A catalog of resources that you can use to create and configure virtual machines in VMM
VMM Library:
Is hosted on a VMM Library Server
Can have one or more library shares
Content in a library share can be organized by creating subfolders
Content is refreshed (indexed) once per hour by default

57. VMM Library Resources File-based resources: Virtual hard disks
Virtual floppy disks
ISO files
Windows PowerShell (ps1) scripts
Answer files (inf, xml)
Virtual machine templates
Hardware profiles
Guest operating system profiles
Virtual machines that are not in use
VMware virtual machines

58. What Is a Hardware Profile?
A hardware profile is:
A library resource containing hardware specifications that can be applied to a new virtual machine or a virtual machine template
Hardware profiles:
Ensure consistent hardware configurations
Can manage hardware profiles are managed in library view
Can create a profile from scratch, from a template, or a hardware configuration of a virtual machine

59. Hardware Profiles Settings
BIOS Startup order:
Processor
Memory
Floppy drive
COM1 and COM2
IDE devices
Network adapter
Priority
Availability

60. What Is the Guest Operating System Profile?
A guest operating system profile is:
A collection of operating system settings that can be imported into a virtual machine template
Guest operating system profiles:
Are database objects
Are used in process of creation of new virtual machine
Can be changed later
Are not associated to virtual machines created based on it

61. Guest Operating System Profile Settings
Identity information - Computer name
Admin Password
Product Key
Time zone
Operating system
Domain/Workgroup
Answer file
[GUIRunOnce] Commands

62. What Is the Virtual Machine Template?
Virtual machine templates are:
A standardized group of hardware and software settings that you can use for new virtual machines
Two types of virtual machine templates:
Customized templates
Non-customized templates
Virtual machine template components:
Hardware profile
Virtual hard disk
Guest operating system profile (optional)

63. Virtual Machine Template Settings
General settings
Hardware Configuration
Operating system Configuration
Custom Properties
Quota Points

64. Demonstration: Creating and Modifying the Virtual Machine Template
In this demonstration, your instructor will show you how to create and modify the virtual machine template

65. Role Types Administrators: Delegated Administrators:
Full access to all actions
Full access to all objects
Can use the Admin console or PowerShell interface
Delegated Administrators:
Full access to most actions
Scope can be limited by host groups and Library servers
Can use the Admin console or PowerShell interface
Self-Service users
Limited access to a subset of actions
Scope can be limited by host groups and Library share
Can use the Self-Service Portal or PowerShell interface

66. Creating a User Role in VMM 2008 R2
Select the user role profile
Wizard configuration options

67. Demonstration: Creating A User Role
In this demonstration, you will see how to:
Add new members to the administrator profile
Create a delegated administrator profile, and delegate specific host groups and libraries to that profile

68. Implementing VMM Self-Service Portal
To implement the VMM Self-Service Portal:
Install the VMM Self-Service Portal
Create or configure host groups
Add default virtual machine paths
Create a self-service user role
Assign self-service user accounts or groups as virtual machine owners
Create virtual machine templates (optional)

69. Requirements for the VMM Self-Service Portal
Hardware requirements
Recommendations
Up to 10 concurrent connections
Enables monitoring and managing the hardware and software in a distributed environment
More than 10 concurrent connections
Enables automated installation and configuration of software and operating system updates
Operating system
Requirements
Windows Server 2003 and Windows Server 2003 R2
Web Server
Windows Powershell
.NET Framework 2.0
Windows Server 2008 and Windows Server 2008 R2
Web Server server role with selected role services

70. Demonstration: Configuring User Access to the Self-Service Portal
In this demonstration, you will see how to use the VMM Self-Service Portal

71. What Are Remote Desktop Services?
The Remote Desktop Services provides access from anywhere to session-based desktops, virtual machine–based desktops, and applications
RDS provides the following benefits:
Run an application or an entire desktop from a central location
Manage session-based desktops, applications, or virtual machine–based desktops on centralized servers in the data center
Provide users with an entire desktop environment, or with their individual applications and data
Provide integration of local applications and RemoteApp applications that run on RDS hosts
Enable secure remote access to an entire desktop, remote application, or virtual machine without users having to establish a VPN connection
Centrally control which RD Session hosts can be accessed, who can access them, and device redirection

72. What Are the RDS Role Services?
Previous Name
Name in Windows Server 2008 R2
Terminal Services
Remote Desktop Services (RDS)
Terminal Server
Remote Desktop Session Host (RD Session Host)
Terminal Services Licensing (TS Licensing)
Remote Desktop Licensing (RD Licensing)
Terminal Services Gateway (TS Gateway)
Remote Desktop Gateway (RD Gateway)
Terminal Services Session Broker (TS Session Broker)
Remote Desktop Connection Broker (RD Connection Broker)
Terminal Services Web Access (TS Web Access)
Remote Desktop Web Access (RD Web Access)

73. Client Experience with RDS
The following enhancements are available to Remote Desktop users in Windows Server 2008 R2:
Windows media redirection
True multiple-monitor support
Audio input and recording
Aero Glass support
Enhanced bitmap redirection
Improved audio and video synchronization
Language bar redirection
Task scheduler

74. RemoteApp and Desktop Connection
The RemoteApp and Desktop Connection feature provides a personalized view for users of RemoteApp programs, session-based desktops, and virtual desktops
The benefits of RemoteApp and Desktop Connection are:
Published Remote Desktop connections are included with RemoteApp programs
Changes to the published connection are automatically reflected on the user’s Start menu
RemoteApp programs can be easily accessed through Windows search
RemoteApp and Desktop Connection does not require domain membership for client computers
You can create and distribute client configuration files for users

75. Planning the RD Session Host Server Implementation
When planning the RD Session Host configuration:
Consider the basic hardware, software, and other requirements
Identify the applications that will be deployed on the server
Identify the number of concurrent client connections
Plan the server hardware configuration based on the application and client expectations
Perform server capacity testing

76. Using RemoteApp to Deploy Programs
RD Remote Apps provide access to individual applications running on RD Session Host computers
The benefits of RemoteApp are:
Enables user access to only applications and not the RD Session Host desktop
Applications run in individual windows on user desktops
Multiple RemoteApps share in single connection
You can configure per-user access to RemoteApps
You can enable access to RemoteApps by:
Creating and distributing .rdp files
Creating and distributing Windows Installer Package (.msi) files
Publishing the RemoteApp to an RD Web Access server

77. Demonstration: Deploying a RemoteApp
In this demonstration, I will show you how to:
Configure a RemoteApp
Create an .msi file to deploy the RemoteApp.
Distribute and install the RemoteApp
Test RemoteApp access

78. What Is the Connection Broker Role in RDS?
The RD Connection Broker role service:
Allows users to reconnect to their existing sessions in a RD Session Host server farm
Evenly distributes the session load among RD Session Host servers in a load-balanced RD Session Host server farm
Provides users with access to virtual desktops on RD Virtualization Host servers, and to RemoteApp programs hosted on RD Session Host servers through RemoteApp and Desktop Connection

79. What Is the Virtual Desktop Infrastructure?
VDI is a centralized desktop delivery architecture, which allows you to centralize the storage, execution, and management of Windows desktops
Benefits of VDI:
Provides access to data and applications from any device
Improves data security and compliance
Simplifies management and deployment of applications
Improves business continuity
Integrates management of physical, virtual, and session-based desktops
Centralizes data storage and backup
Key deployment scenarios of VDI are persistent virtual machines and pooled virtual machines

80. Personal virtual desktops Pooled virtual desktops
How Virtual Desktop Infrastructure Works
A user can connect to a virtual machined based on the VDI configured for:
A user can connect to a virtual machined based on the VDI configured for:
Personal virtual desktops
Pooled virtual desktops
A user initiates the connection to the personal virtual desktop
The user sends the request to the RD Session Host server running in redirection mode
The RD Session Host server forwards the request to the RD Connection Broker server
The RD Connection Broker server queries AD DS and retrieves the name of the virtual machine that is assigned to the requesting user account
The RD Connection Broker server sends a request to the RD Virtualization Host server to start the virtual machine
The RD Virtualization Host server returns the IP address of the FQDN to the RD Connection Broker server
The RD Session Host server redirects the request to the client computer that initiated the connection
The client computer connects to the personal virtual desktop
A user initiates the connection to the virtual desktop pool
The user sends the request to the RD Session Host server running in redirection mode
The RD Session Host server redirects the request to the RD Connection Broker server
The RD Connection Broker server verifies whether any existing session exists for the requesting user account
The RD Session Host server redirects the request to the client computer that initiated the connection
The client computer connects to the virtual desktop pool
Personal virtual desktops
Pooled virtual desktops

81. Virtual Machines for Virtual Desktop
RD Virtualization Host can assign each user a unique virtual machine, a personal virtual desktop, or can redirect users to a shared virtual machine pool, where a virtual machine is dynamically assigned
After installing a virtual machine, you must configure the following to work with RDS:
Join the virtual machine to a domain
Enable Remote Desktop
Add user accounts to the local Remote Desktop Users security group
Allow RPC
Create a firewall exception to allow Remote Services Management
Add permissions to RDP

82. What Is RD Web Access? RD Web Access enables:
Populating the list of available RemoteApps or virtual desktops in the RemoteApp and Desktop Connection application
Launching RemoteApps or virtual desktops from the RD Web Access Web site
Launching the Remote Desktop Web Connection which provide Remote Desktop connections to servers or client computers
RD Web Access only enables users to launch applications or Remote Desktop sessions, it does not proxy RDP sessions

83. Configuring RD Web Access

84. Configuring User Access to RD Web Access
To enable user access to RD Web Access:
Provide users with the URL for the RD Web Access server
Configure RemoteApp and Desktop Connections to subscribe to a feed from the RD Web Access server
To configure RemoteApp and Desktop Connections:
Configure the URL for the RD Web Access server
Create a client configuration file in RD Connection Manager and distribute the file to clients

85. Demonstration: Configuring RD Web Access
In this demonstration, you will learn how to configure Remote Desktop Web Access

86. Microsoft Desktop Optimization Pack
What the Desktop Optimization Pack provides
MDOP is comprised of software from Microsoft’s purchases of Softricity, Kidaro, AssetMetrix, Winternals Software and DesktopStandard.

87. Microsoft Desktop Optimization Pack
Feature
Description
Microsoft Application Virtualization
Dynamically streaming software as a centrally managed service
Microsoft Asset Inventory Service
Translating software inventory into business intelligence
Microsoft Diagnostics and Recovery Toolset
Powerful tools to accelerate desktop repair
Microsoft Advanced Group Policy Management
Enhancing group policy through change management
System Center Desktop Error Monitoring
Proactively manage application and operating system failures
Microsoft Enterprise Desktop Virtualization
Simplifying deployment and management of Virtual PCs

88. Microsoft Application Virtualization
Dynamically delivering the virtual application solution
Applications to users at log on
Centralized permissions
Sandboxed applications
Accelerates desktop deployment
Minimizes application coexistence testing
Runs real-time usage reports
Enables device roaming
Server components require Windows Server 2003 or
later
Requires SQL Server 2000 or later
Client requires Windows XP or later
Certain components require .Net Framework 2.0
Requirements:

89. Microsoft Asset Inventory Service
Translating software inventory into business intelligence
Scans desktops
Checks central host against extensive database
Assigns intelligent naming to software
Simplifies compliance and disaster recovery
Windows XP or later
Requirements:

90. Microsoft Diagnostics and Recovery Toolset (DaRT)
DaRT provides powerful tools to accelerate desktop repair
Recover deleted files, manipulate services, devices, passwords, and more
Recover instead of reloading Windows
Make computers safe to use
Accelerate desktop management and responsiveness
Windows Vista (32 and 64-bit), and Windows Server 2008 (32 and 64 bit)
Some features support Windows XP
Requirements for DaRT 6.0:
Windows 2000, XP, and Windows Server 2003
Requirements for DaRT 5.0:

91. Microsoft Advanced Group Policy Management
Enhancing Group Policy through change management
Role-based administration and templates
Flexible delegation model
Versioning, history, and rollback
Accelerate management with granular administrative control
Reduce risk of widespread failure
Group Policy Management Console (GPMC)
Windows Vista
Windows Server 2003 or later
Requirements:

92. Microsoft Desktop Error Monitoring
Proactively manage application and operating system failures
Agentless crash monitoring
Crash/hang data captured and stored in central server
Rich SQL database for data analysis
Direct access to troubleshooting and resolution knowledge base
Accelerate desktop management and IT responsiveness
Improve desktop stability and end-user productivity
Supports:
Windows 2000
Windows XP
Windows Vista
Windows 7

93. What Is Application Virtualization?
Operating System
Read Only
System Files
(Registry, .ini,
DLL, etc.)
Read & Write
System Services
(cut and
paste, OLE,
printers, etc.)
Read & Write
Virtual Environment
(Registry, .ini, DLL,
Group Policy, etc.)
Application
Profile Data
Read & Write

94. Application Management Lifecycle
Packaging
Monitoring/
Asset
Management
Management
Business
Continuity
Deployment
Testing will effect multiple stages in the lifecycle
Termination
Updates
Support

95. Application Deployment
Deploying
No client installs
No client footprint
No wasting resources
Pre-configuration of applications
Deploy

96. Application Packaging
.osd and .ico
Each published application contains:
.osd file – Open Software Description "link" files
.ico file – Icon file
.osd and .ico
.osd and .ico
Each package contains:
.sft file – Microsoft Application Virtualization-enabled application
.sprj file – Microsoft Application Virtualization project file
Manifest.xml - Used in package distribution
.sft and .sprj
Manifest.xml

97. Application Updates Update Updates Update once on server
Seamless update to clients
Update

98. Application Support Support Support Reduced application conflicts
Reduced help desk calls
Increased license compliance

99. Reducing Application Conflicts
.sft and .sprj
.OSD and .ICO
.osd and .ico
3rd party app
.osd and .ico
.sft and .sprj
Manifest.xml
Manifest.xml
Application Virtualization packages contain the complete environment
for the application ü
Potentially conflicting applications have
their own environment ü
Applications in a suite can
share the environment ü

100. Delivering Pre-Configured Applications
Sequencing Engineer builds the package and configures the application to address user requirements

101. Running Multiple Versions of a Single Application on the Same Computer
Virtual Environment 1
Each application runs in its own virtual environment, which allows different applications to share the same hardware with two versions of the same application
Virtual Environment 2
2003

102. Providing Centrally-Managed Application Deployment and Maintenance
The Management Console is used to connect to the Web Service, which is the central component for all Microsoft Application Virtualization

103. Full Infrastructure Application Virtualization System

104. Full Infrastructure Application Virtualization System
Administrator computer
Active Directory
Management
Web Service
Data Store
/content
Client
Application Virtualization Management Server
Sequencer

105. Microsoft Application Virtualization Management Components
Administrator computer
with Application Virtualization
Management Console
MMC snap-in installed
Active Directory
ADSI
Authentication
Port 80/443
Management Interface
ODBC
Application Virtualization Management
Web Service
(IIS Server)
Application Virtualization Data Store
Configuration Location
Configuration Storage

106. Microsoft Application Virtualization Sequencer
/content
Application Virtualization-Enabled
Application
(.sft, .sprj, .osd, .ico, Manifest.xml, .msi)
Application Virtualization Management Server
(Windows Server 2003)
Application Virtualization Sequencer
(Windows XP, Windows Vista or 2003)

107. Microsoft Application Virtualization Management Server
Database
Application Virtualization Management Server
(Windows 2003 Server)
Package Look-ups
ODBC
/content

108. Microsoft Application Virtualization Client
Application Virtualization Management Server
/content
RTSP/RTSPS
Authentication
requests for MIME settings
application delivery
Application Virtualization Client
(Windows Desktop
or Terminal Server)

109. Microsoft Application Virtualization Streaming Server
Streaming Server features:
No Management Console,
SQL database, etc.
/content ü
Detects new packages on a configurable interval ü
Uses NT File System (NTFS)
access control list (ACL) for authorization ü
Responds to Client requests ü

110. Files Used to Add or Import an Application
File type
Description
.sprj
Describes which applications are part of a specific application suite
Contains parse items and exclusions
Is XML based
.osd
Specifies application launch information to the virtualization client
Provides application virtualization settings
Is XML-based
.sft
Up to 4 gigabyte (GB) application storage file
Contains application assets that make up the application
Separated into multiple feature blocks
.ico
Used to represent application shortcut icons
Manifest.xml
Used in specific streaming infrastructure scenarios to inform clients how to access sequenced applications
.SPRJ
.XML

111. Considerations for Importing Applications
.osd Path
Make sure the path specified in the .osd file matches the content path to the server
Server name may be specified as a system variable
For example:
Where will the application shortcuts go?
What file type associations will the application use?
Which security groups need access to the application?
Considerations to keep in mind:

112. Importing Applications
Import applications by:
Using Action menu option, Import Applications Wizard
Specifying the .sprj or .osd file provided by the Sequencer

113. What Is a Package? Packages are:
Created automatically when an applications are imported
Used to control the versions associated with a virtualized application
Configured to perform Active Upgrades on clients
Packages are:

114. Overview of the Active Upgrade Process
Sequencing Administrator provides updates to the application package
Select package to be updated, and then add new version
Type in updated .sft file path
Type in the relative path
Confirm package
Ask client to reload application

115. Desktop Virtualization Overview
Server-Based Virtualization
Runs virtual images on a server, and provides remote access from any endpoint (with zero-touch deployment)
Client-Hosted Virtualization
Creates a local copy of the virtual image, available to work offline, and with no servers
Server Client
Client
VDI (Windows VECD – Windows Vista Enterprise Centralized Desktop), Terminal Services
Microsoft® Enterprise Desktop Virtualization based on Microsoft Virtual PC 2007

116. Desktop vs. Application Virtualization
What it does
Creates a package with a full OS
What it is good for
Resolve incompatibility between applications and a new OS
Run two environments on a single PC
What it does
Creates a package of a single application
Eliminates software install
What it is good for
Resolve conflicts between applications
Simplify application delivery and testing
Applications
Operating System
Hardware

117. Key usage scenarios for Desktop Virtualization
Current focus: Accelerate upgrade to Windows Vista or to Windows 7:
Enable legacy applications that requires (Windows XP/2000) to run on the new OS platform
Jumpstart to future OS deployments
Future focus: Deliver a corporate-managed virtual desktop to unmanaged PCs
Increase manageability and usability of employee laptops
Drive business continuity and migration of new subsidiaries
Increase productivity for contractors, offshore, branch offices
Enable work-at-home and increased mobility

118. Accelerate upgrade to Windows Vista or Windows 7
Application-to-OS Compatibility Solution: Run legacy applications in a Windows® XP/2000 environment
Applications OS
Applications
Virtual PC
Operating System
Hardware

119. What Does MED-V Add To VPC?
MED-V upgrades an industry-standard virtual machine…
… to an enterprise-managed workspace:
Image Creation, Delivery and Update
Centralized Management and Monitoring
Usage Policy and Data Transfer Control
End-user Experience and Usability
Virtual Machine (residing and operating on the endpoint)

120. User experience with Virtual PC
An additional desktop (start menu, taskbar…)
Introduction of “Virtual Machine” concepts

121. …with MED-V
Applications installed in the VM, appear on the desktop as if they were running natively.

122. MED-V Architecture
Applications
Operating System
Virtual PC OS

123. MED-V v1 Server Requirements
OS: Windows Server 2008 (Standard/Enterprise)
Recommended HW: Dual Processor (2.8ghz), 4GB RAM
Active-directory: Joined to domain for user authentication
Image repository: IIS web server
Reporting database (optional): MS SQL Server (2005 SP2 Enterprise or Express/Standard/Enterprise)
Scale:
Up to 5000 users for the management server
Use IIS web proxies to off-load image delivery from the management server

124. MED-V v1 Client Requirements
Host:
Windows 7 – 32 bit (2GB RAM Recommended
Windows Vista SP1 – 32 bit (2GB RAM Recommended)
Windows XP SP2/3 – 32 bit (1GB RAM Recommended)
Guest: Windows XP Pro SP2/3 , Win2000 SP4
Virtualization engine: VPC 2007 SP1
Languages: English UI
Browsers:
Host – Internet Explorer 7 or 8
Guest – Internet Explorer 7 or 6 SP2

125. MED-V v1 – Features
Virtual images repository and deployment
Centralized virtual images repository for image creation/testing
Standard MSI for corporate software distribution
Auto-install package for self deployment via removable media (e.g. DVD) or from a website
Efficient image delivery and updates over LAN or WAN (using TrimTransfer de-duplication technology based on IIS)
Centralized management and monitoring
Centralized management server to control deployed VMs
Image provisioning based on Microsoft Active Directory® users/groups
User authentication (online over SSL or offline based on local cache)
Automate first-time virtual machine setups (e.g. initial network setup, unique computer name, domain join)
Adjust VPC memory allocation based on available RAM on host
Centralized database for client activity and events

126. MED-V v1 – Features (cont.)
Usage policy and data transfer control
Per user/group usage policies (e.g. expiration, time limits for offline work)
Host-guest data transfer control (e.g. copy-paste, file transfer, printing)
Automatic redirection of predefined websites (e.g. corporate intranet) to the virtual environment
End-user experience
Background VM management - hide the Virtual PC session from the user, and automatically troubleshoot
“Publish” applications from VPC image to host Start Menu
Single desktop experience – applications that run in the VPC seamlessly appear side-by-side with native applications (including task-bar, tray-icons)
File transfer tool – share files between host and guest

127. Increase desktop computing flexibility
Deliver corporate-managed desktops to unmanaged PCs
Increase productivity for contractors, offshore, branch offices
Enable work-at-home and increased mobility
Drive business continuity
Rapidly reconstitute corporate desktops on any PC in case of emergency
Increase manageability and usability of corporate laptops
Eliminate historic trade off between IT control and user flexibility
Enable employee-owned model, using a virtual corporate desktop

128. MED-V TrimTransfer Image Delivery

129. How to update/patch virtual images?
Initial delivery (using TrimTransfer)
Alt. I: update the “Master” image once and deliver image differences to endpoints
Alt. II: connect to Active Directory domain and use standard software delivery
Easy to manage
User data and settings must be saved on the network
Standard! (use WSUS, SCCM, etc)

130. MDOP Roadmap H2 CY08 CY 09 CY 10+ App Virtualization 4.5 Dynamic Suite
Scalability
Lightweight server
Localization
App Virtualization v.Next
64-bit support
Win7/ Win2008R2
Globalization
Feature enhancements
AGPM 3.0
Flexible security
WS08 support
Enhanced UI
AGPM 4.0
(cross-forest mgmt)
Automation
Win7 support
DaRT 7.0
Network service
USB boot
AIS 1.5
License reconciliation
UI enhancements
SCCM Integration
AIS 2.0
Virtual App Inventory
HW Inventory
Console Localization
Scalability (100k)
Enhanced data export
DEM 3.0 SP2
Enhanced reporting
MED-V 1.0
VM on client provisioning
Usage Policy
VM Management
MED-V 2.0
Vista in guest

131. Online Resources Microsoft Virtualization Home:
Windows Server Virtualization Blog Site:
Virtualization Solution Accelerators
Converting Physical Computers to Virtual Machines in VMM (P2V Conversions)
Converting VMware Virtual Machines in VMM (V2V Conversions)
Troubleshooting Virtual Machine Conversion Issues
System Center Virtual Machine Manager 2008 R2

132. Online Resources Application Virtualization
a-microsoft-application-virtualization.mspx
Virtual Desktop Infrastructure
Remote Desktop Services

133. Online Resources Virtualizzare Office 2010 con App-V 4.6
Office 2010 – System Requirements:
Application Virtualization:
application-virtualization.mspx
Prescriptive guidance for sequencing Office 2010 in Microsoft App-V
Office Activation Technologies:
Office Customization Tool:
Virtualizzare Office 2010 con App-V 4.6
Office 2010 con App-V 4.6.pdf

134. Virtual Labs Application Virtualization
TechNet Virtual Lab: Learning App-V Basics
TechNet Virtual Lab: Learning App-V Intermediate Skills
TechNet Virtual Lab: Learning to Configure App-V for Standalone Client Mode
TechNet Virtual Lab Express: Windows 7: Microsoft Application Virtualization (APP-V)
Remote Desktop Services
TechNet Virtual Lab Express: Windows Server 2008 R2: Remote Desktop Services

135. Nicola Ferrini’s white papers
noramica/introduzione-a-microsoft-application- virtualization.mspx
013C B4B-147D5F60FCE2/MED-V%20lab.docx
id/313/Default.aspx
Office con App-V 4.6.pdf

136. Module x: Title
Thank you!
Course xxxxy