Microsoft 70-982 - Questions & Answers

App-V maintains local resources on the client whereas RemoteApp utilizes resources on the backend RDS Server.
The network data sent to the client is also different, App-V has two feature packs that contain all binaries of the streamed app. Remote Apps utilizes RDP, so only the picture information, mouse, keyboard etc are transmitted.
Actually they can be combined, applications can be streamed to a RDS server and published to the client via RemoteApp. For more information, please see
http://blogs.msdn.com/b/rds/archive/2009/10/14/whitepaperrelease-applicationvirtualization-4-5-for-terminal-services.aspx
For more information about App-V, I suggest that you post to the App-V forum:
http://social.technet.microsoft.com/Forums/en-US/category/appvirtualization
Hope the information is helpful for your work.

Ensure that updates for App1 are applied to all of the new virtual desktops.
Rolling Out Updates to a Pooled Virtual Desktop Collection
A Master or Gold VM is formally referred to as "virtual desktop template" in the WS2012 Server Manager UI console and the cmdlets in Remote Desktop Services module for Windows PowerShell. It is an input to the managed virtual desktop collection creation process that allows an admin to manage a virtual desktop collection. The Master VM is created and managed by the admin and it specifies the hardware properties and software contents of all the automatically created VMs in that managed virtual desktop collection.
For example, if the master VM is assigned 2GB of RAM, then each of the automatically created VMs in the managed virtual desktop collection will be assigned 2GB RAM. In this section, I will describe the various supported options and requirements for the Master VM.
Virtual Hard Disk
The Master VM can only have one virtual hard disk (VHD) attached to it; more than one VHD attached to the Master VM is not supported.
The VHD attached to the Master VM must have either a Windows 7 SP1 or Windows 8 image in sysprep generalized state.
A diff disk chain attached to the Master VM as its VHD is supported.
Although the VHD can have more than one logical partition defined in it, it can have only one Windows OS image installed in it.

http://blogs.msdn.com/b/rds/archive/2012/10/29/single-image-management-for-virtualdesktop-collections-inwindows-server-2012.aspx

The assumption is we only want to use the WAN link when absolutely required. If we create a Linked Deployment Share, all selected data would be replicated to Moscow from New York.
By managing the Task Sequence/Share locally in Moscow with no link to New York, you're only downloading the media and software one time.
Solution: Use MDT to create a bootable image for a DVD or external drive.
Step 1: Create selection profiles.
Step 2: Create your media.
Step 3: Update your media.
Step 4: Prepare your media.
Step 5: Use your media on the client machine.
Optional: Customize or automate your media.

You'd first allow installation of specific classes and then prevent all others.
Prevent installation of devices not described by other policy settings.
This policy setting controls the installation of devices that are not specifically described by any other policy setting. If you enable this policy setting, users cannot install or update the driver for devices unless they are described by either the Allow installation of devices that match these device IDs policy setting or the Allow installation of devices for these device classes policy setting. If you disable or do not configure this policy setting, users can install and update the driver for any device that is not described by the Prevent installation of devices that match these device IDs policy setting, the Prevent installation of devices for these device classes policy setting, or the Prevent installation of removable devices policy setting.

http://msdn.microsoft.com/en-us/library/bb530324.aspx

Replace the client computers in the New York office. Migrate the user settings during the migration to the new hardware.

Virtual Desktop Collection
There are two types of virtual desktop collections available: personal and pooled. You have the option to let Remote Desktop Services automatically manage pooled virtual desktops in a collection, or you can manually manage them. We will concentrate on automatically managed pooled virtual desktop collections.
A managed pooled virtual desktop collection offers the following capabilities: Automatically create pooled virtual desktops based on a virtual desktop template.
Automatically install security updates and applications based on a virtual desktop template.
Live migration with local caching.
User profile disk support. A user profile disk stores user profile information in a separate virtual hard disk so that user profile settings are persistent across pooled virtual desktops.
With either managed or unmanaged, the administrator can configure the pool to store the user profiles on User Profile disks separate from the machines.
http://blogs.technet.com/b/canitpro/archive/2013/04/25/step-by-step-deploying-virtualdesktops-with-windowsserver-2012.aspx
Virtual Machine-based desktop Deployment is of two types: Personal Virtual Desktop Collection - Administrators manually assign virtual desktops to the users.
Pooled Virtual Desktop Collection - Administrators deploy virtual desktops and users are randomly assigned virtual desktops. At log off virtual desktops are generally rolled back (rollback is optional).
Creating a Pooled Virtual Desktop Collection There are two types of Pooled Virtual desktop Collections: Pooled Managed The Virtual desktop machine is created using the Sysprep Template of a virtual machine.
We can recreate the virtual desktops from this image at will.
Pooled Unmanaged We can add the existing virtual machine to this virtual desktop collection from Hyper V pool.
With either option, the administrator can configure the pool to store the user profiles on User Profile disks separate from the machines.
http://blogs.technet.com/b/askperf/archive/2012/10/31/windows-8-windows-server-2012-pooled-virtualdesktop-infrastructure.aspx

http://technet.microsoft.com/en-us/library/ee216741.aspx

Topic 2, Contoso, Ltd
Overview
Contoso, Ltd., is a pharmaceutical company. The company has an office in Seattle.
Existing Environment
The network contains a single-domain Active Directory forest named contoso.com.
The relevant servers in the network are configured as shown in the following table.

All client computers run Windows XP. All client computers are configured to receive automatic updates from SRV-WSUS.
All users have desktop computers. Users in the sales department also have laptop computers. The laptop computers are used by the sales users to remotely access the internal network by using a VPN connection.
The sales users use several line-of-business applications.
Requirements
Planned Changes
The company plans to deploy a Microsoft System Center 2012 Configuration Manager infrastructure that will contain two servers. The servers will be configured as shown in the following table.

The company plans to deploy a Remote Desktop Services (RDS) infrastructure that will contain the following servers:

Two Remote Desktop Connection Broker (RD Connection Broker) servers configured for high-availability
Two Remote Desktop Visualization Host (RD Virtualization Host) servers
Two Remote Desktop Web Access (RD Web Access) servers
Two Remote Desktop Gateway (RD Gateway) servers
Technical Requirements
The company identifies the following technical requirements:

Configuration Manager must be used to deploy operating systems and patches.
An existing virtual machine that runs Windows 8 must be used as the reference computer for the deployment of new client computers.
To troubleshoot installation issues, technicians must be able to open a Command Prompt window during the deployment of Windows 8 to the new client computers.
Sales Department Requirements
The company identifies the following requirements for the sales users:

All of the files on the laptop computers must be encrypted.
The amount of administrative effort must be minimized whenever possible.
Certificate warnings must not be displayed when connecting to virtual desktops.
The availability of the virtual desktops must not be affected by a single server failure.
The desktop computers of the sales users must be replaced by virtual desktops that run Windows 8.
The contents of each sales user's Documents folder must be the same on the virtual desktop and the laptop computer.
The sales users must be able to connect to their virtual desktop from their laptop computer without using a VPN connection.
The sales users must be able to configure their user settings independently on their virtual desktop and their laptop computer.
The line-of-business applications must be installed on the virtual desktops only.
The line-of-business applications require hardware acceleration to run.