Today, we are announcing the general availability of Windows Server Microsoft Windows Server Blog. Jeffrey For Windows Server we listened to our customers and partners and added the most desired features and resolved the top pain points in Remote Desktop Services RDS.
In the previous release, we received consistent feedback that: RemoteFX was very popular however its underlying protocol RDP did not provide a great experience over Wide Area Networks WANs Session and virtual machine infrastructures were complicated and costly and The administration experience was not simple.
Specific improvements include: Adaptive Graphics. We support a mix and match approach, determining and using the right codec for the right content instead of one size fits all. We included codecs optimized for multimedia, images, and text. We improved caching as well as added progressive rendering. Progressive rendering allows RemoteFX to provide a responsive experience over a highly constrained network. Intelligent Transports. UDP provides a better experience over a lossy WAN network but, is not always possible dependent on the routers, and firewalls involved.
Optimized Media Streaming. Adaptive Network Auto Detect. In this release, the end user no longer has to set the network in the Remote Desktop Connection client: the client auto-detects the network type and, also adapts as the network changes.
Single Sign-On. In Windows Server R2, it was possible to configure an RDS deployment so that users will need to enter their credentials only once when connecting to RemoteApps and hosted desktops. However, this configuration was very cumbersome. In Windows Server we dramatically simplified this by eliminating the need to use multiple certificates.
We also made it possible to use locally logged on domain credentials so that users connecting from managed devices can connect seamlessly without any credential prompts. Email and web discovery of Remote Applications and desktops. Users now can find the correct remote workspace to connect to by just providing their email address.
This removes the requirement to remember a long website URL. Multi Touch. We support full remoting of gestures e. This provides for a consistent experience when using a touch enabled device locally or, over RemoteFX. As more apps are written supporting touch as the primary interface, this will become more important. USB Redirection. We have added support when using sessions and physical hosts which provides a consistent experience independent of physical, session, or virtual machine based host.
Metro-style Remote Desktop. Patching large numbers of VMs at the same time can significantly affect productivity. You may be unable to patch sleeping VMs or those in a saved state. Technical description Intelligent patching in Windows Server R2 solves numerous issues for both pooled and personal virtual desktop collections.
Pooled virtual desktop collections In Windows Server R2, you can use built-in tools to manage application installations and security updates for virtual desktops in a pooled virtual desktop collection.
You merely apply app installation and security updates to the master VM image, and then all virtual desktops in the pooled collection are switched with the master image.
Notify the user with a deadline, force the user to log off at that time, and then switch to the patched virtual desktop. Immediately force the user to log off, and then switch to the patched virtual desktop.
Doing so reduces the required downtime for patching and gives you the flexibility to choose how you want to roll out the patch, depending on the severity of the issue being patched. Personal virtual desktop collections For personal virtual desktops, you can apply application installations and security updates by using WSUS or another software update mechanism.
This approach is similar to the update process on a traditional desktop. In Windows Server R2, the RD Connection Broker works with a management system, such as System Center Configuration Manager, to patch the personal virtual desktops in a way that balances the load on the host to prevent disruptions to users. By default, Server Virtualization disables waking up virtual desktops from sleep, but in Windows Server R2, the RD Connection Broker has been modified to use the virtual desktop BIOS to wake up the virtual desktop to allow patching.
For pooled collections, you can patch the master image, which then becomes the new master image for the collection. When users log off, and then log on again, their desktops are automatically replaced with the patched version.
For personal collections, you can configure the Configuration Manager site server and deploy the Configuration Manager patching agent in each virtual desktop. System Center Configuration Manager can wake up virtual desktops during offbusiness hours, patch the images, and then return each virtual desktop to a saved state.
RemoteFX was integrated with RDP, which enabled shared encryption, authentication, management, and device support. RemoteFX also delivers a rich user experience for session-based desktops and RemoteApp programs to a broad range of client devices. Windows Server R2 builds on this platform to enable a far richer and easier experience on all types of networks and all types of devices.
Specifically, RDP in Windows Server R2 enables a more consistent user experience when connecting to centralized desktops, even on networks in which bandwidth is limited and end-to-end latency is high.
RemoteFX Media Streaming provides a smooth multimedia experience over variable or unreliable networks. RemoteFX Multitouch allows users to use touch-enabled and gesture-enabled apps in remote desktop environments. To support remote desktops and applications over WANs, Remote Desktop Services must be able to quickly adapt to different network conditions.
For enhanced performance, administrators should verify that this port is enabled on the network. Compensation for network packet loss. RDP uses several techniques for networks with packet loss, including Forward Error Correction FEC , to recover quickly from packet loss without requiring retransmission. Network auto-detect. RDP in Windows Server R2 detects end-to-end network speed by measuring latency and available bandwidth, and then adjusts the type of connection and the data transfer based on the available bandwidth and latency.
Using the Set RDP experience If this Group Policy setting is disabled or not configured, the graphics pipeline dynamically adjusts the configuration to give the user the best experience, but if the deployment is targeted toward supporting the maximum number of sessions, this Group Policy setting can be enabled and set to Optimize for Scale. In this case, bandwidth use could be high for some scenarios. However, if the deployment environment is such that users are on a bandwidth-limited link, you can set the Optimize for bandwidth option.
Note that in this case, CPU use may be high. Figure 6 demonstrates how RemoteFX Adaptive Graphics dynamically adapts to changing network conditions and optimizes encoding to the content. RemoteFX Adaptive Graphics selectively identifying and downloading content With progressive rendering, text remains clear while images are progressively refined, as shown in Figure 7. Figure 7. Users see the device within the remote session; the USB device, desktop, and apps all appear as local, integrated resources, creating a unified experience.
RemoteFX Multitouch Windows Server R2 introduces multitouch and gesture remoting with support for up to simultaneous touch inputs. This feature enables users to employ the new breed of touch-enabled and gestureenabled apps in remote desktop environments. Microsoft now supports multiple GPUs within one server and is seeing greater engagement with original equipment manufacturers to provide systems that support this capability. These and other enhancements in RemoteFX give remote users the same experience they have with locally installed desktops—from USBconnected devices to video streaming and advanced graphics rendering—even while connecting over WANs.
This means that after each session, user personalization settings and application cache data are lost. Any user state changes are stored in the User Profile Disk, and these changes are immediately available to users the next time they log on.
Technical description Windows Server R2 solves the problem of lost settings and application cache data with the new User Profile Disk. A User Profile Disk is created for each user and applies to a specific VM pool or session collection.
The User Profile Disk stores user personalization and application cache data so that it is maintained across user logon sessions.
When the user logs on to a session or within a pooled VM, the User Profile Disk is mounted and user personalization is quickly made available. Users benefit from faster startup times and personalization even within the shared environment of a VM pool or session. User Profile Disk can be configured during deployment in the Create Collection Wizard, as shown in Figure 8, or at a later time by using the Remote Desktop Services centralized management console.
If a virtual machine or session starts to use more resources than deemed safe by the system, Fair Share automatically throttles the resource in question, thereby dynamically distributing that resource across other virtual machines or sessions. RDS adds Fair Share to manage resources for sessions. Specifying User Disks Summary User Profile Disk provides users with the convenience of having their cached and personalized settings available each time they log on to their VM pools or sessions.
IT administrators can quickly and easily deploy User Profile Disk by using less expensive commodity hardware. Figure 9. You can reduce operation expenses management cost for Server Virtualization storage.
Figure The changes that each user makes during a session are stored on a transient VHD thats discarded when the user logs off although user profile changes are persisted. The main advantage of this model is having a single image to manage, which reduces storage requirements and simplifies management, thereby reducing deployment costs. In Windows Server R2, the entire model of deploying pooled VM collection is transparent to the administrator. Single-image management and administration are natively supported, and the entire process is simplified for ease of deployment.
Personal VM collections. Personal VMs are based on a master VM. Windows Server R2 automates the rollout process by copying the master image for each instance of the personal VM.
Session virtualization deployments. Remote Desktop Services session virtualization, formerly known as Terminal Services, is a proven and mature centralized desktop infrastructure that many organizations deploy instead of VDI to increase user density on the host and therefore reduce costs. Windows Server R2 makes it easier to deploy this architecture by offering a session virtualization deployment scenario. You can deploy session-based desktops or RemoteApp programs. For detailed information on publishing and managing RemoteApp programs, session-based desktops, and virtual desktops from a unified console, see Centralized publishing of RemoteApp and desktops later in this paper.
Summary In Windows Server R2, administrators have an easier and more cost-effective way to quickly deploy and manage virtual desktop, session-based, or RemoteApp collections from one management console. Remote users benefit from a local-like, personalized experience and network and processor optimizations.
User benefits are described in more detail in RemoteFX enhancements later in this paper. Centralized resource publishing presents a centralized desktop or app to users, providing a user experience that is similar to locally installed apps.
By using the new publishing features in Server Manager, you can view a history of the resources assigned to users, change the published resources for any given collection, and edit the properties of published resources. In addition to Server Manager, you can now configure a RemoteApp and desktop connection URL by using Group Policy, which allows users to subscribe to a desktop or application feed.
This means that by simply entering their email address, users can automatically gain access to their remote resources. Technical description You can use Server Manager to publish RemoteApp programs to either a session collection or virtual desktop collection, as shown in Figure 3.
You can also search for applications that do not appear in the Start menu. The file type association is used to assign the file association on the client device to the associated RemoteApp program. To configure the file type association for a published RemoteApp program, you must first ensure that the default connection URL is configured in the appropriate Group Policy setting.
After the default connection URL is configured, you can change the file type associations of a published RemoteApp program by using Server Manager, as shown in Figure 4. Requirements Centralized resource publishing requires the following configurations and permissions:. An installed and configured session virtualization or VDI deployment A configured session collection or virtual desktop collection If publishing RemoteApp programs from a virtual desktop collection, access to the Windows Management Instrumentation and file and printer sharing programs in Windows Firewall on each virtual desktop in the virtual desktop collection.
Summary With centralized resource publishing, you can publish RemoteApp programs and complete desktops, whether they are session based or VM based, from a single console with minimal need to run additional scripts, tools, or administrative applications. Users can more easily access relevant applications through the DNS feed lookup and automatic web page creation tools that are part of Windows Server R2. Intelligent patching simplifies the process of updating both pooled and personal virtual desktops with little impact on resource use or bandwidth.
Patching virtual desktops in a large deployment Administrators must address several obstacles when patching multiple VMs in a pooled or personal VM deployment:.
You have no control over when the user logs off, and then logs on again to begin using the patched operating system. You may have to enforce downtime for users while you are performing patch operations. Patching large numbers of VMs at the same time can significantly affect productivity.
You may be unable to patch sleeping VMs or those in a saved state. With intelligent patching in Windows Server R2, you can patch virtual desktop images in large deployments more easily and efficiently in an orchestrated way to reduce downtime and maintain high levels of productivity. Technical description Intelligent patching in Windows Server R2 solves numerous issues for both pooled and personal virtual desktop collections.
Pooled virtual desktop collections In Windows Server R2, you can use built-in tools to manage application installations and security updates for virtual desktops in a pooled virtual desktop collection. You merely apply app installation and security updates to the master VM image, and then all virtual desktops in the pooled collection are switched with the master image.
You can then select one of the following modes for patching the virtual desktops that fits the needs of your organization:. Wait for the user to log off, and then switch to the patched virtual desktop. Notify the user with a deadline, force the user to log off at that time, and then switch to the patched virtual desktop. Immediately force the user to log off, and then switch to the patched virtual desktop. You can reduce disruption to productivity by allowing active users to remain logged on and new users to connect while free virtual desktops in the pool are being patched.
Doing so reduces the required downtime for patching and gives you the flexibility to choose how you want to roll out the patch, depending on the severity of the issue being patched. Personal virtual desktop collections For personal virtual desktops, you can apply application installations and security updates by using WSUS or another software update mechanism. This approach is similar to the update process on a traditional desktop.
For personal virtual desktops, intelligent patching resolves several issues:. Simultaneous patching of virtual desktops causes a sudden increase in the load on the server. In Windows Server R2, the RD Connection Broker works with a management system, such as System Center Configuration Manager, to patch the personal virtual desktops in a way that balances the load on the host to prevent disruptions to users.
By default, Server Virtualization disables waking up virtual desktops from sleep, but in Windows Server R2, the RD Connection Broker has been modified to use the virtual desktop BIOS to wake up the virtual desktop to allow patching. The wake-up function also uses intelligent patching to reduce the load on the server thats running the virtual desktops.
Summary With Windows Server R2, you can easily patch virtual desktop images by using a centralized management console or the RD Connection Broker alongside your existing management system, such as System Center Configuration Manager. For pooled collections, you can patch the master image, which then becomes the new master image for the collection. When users log off, and then log on again, their desktops are automatically replaced with the patched version.
For personal collections, you can configure the Configuration Manager site server and deploy the Configuration Manager patching agent in each virtual desktop. System Center Configuration Manager can wake up virtual desktops during offbusiness hours, patch the images, and then return each virtual desktop to a saved state.
In Windows Server R2 with SP1 and Windows 7 with SP1, Microsoft introduced RemoteFX, which enables the delivery of a full-fidelity Windows user experience to a range of remote client devices, including rich clients, thin clients, and ultrathin clients. RemoteFX was integrated with RDP, which enabled shared encryption, authentication, management, and device support. RemoteFX also delivers a rich user experience for session-based desktops and RemoteApp programs to a broad range of client devices.
Windows Server R2 builds on this platform to enable a far richer and easier experience on all types of networks and all types of devices. Specifically, RDP in Windows Server R2 enables a more consistent user experience when connecting to centralized desktops, even on networks in which bandwidth is limited and end-to-end latency is high.
RemoteFX Media Streaming provides a smooth multimedia experience over variable or unreliable networks. RemoteFX Multitouch allows users to use touch-enabled and gesture-enabled apps in remote desktop environments.
RemoteFX for WAN With todays modern workforce, clients frequently need to connect from branch offices, homes, or hotels over low-bandwidth or high-latency connections. To support remote desktops and applications over WANs, Remote Desktop Services must be able to quickly adapt to different network conditions.
To help achieve this, RDP adds the following improvements:. Dynamic transport detection. For enhanced performance, administrators should verify that this port is enabled on the network. Compensation for network packet loss. RDP uses several techniques for networks with packet loss, including Forward Error Correction FEC , to recover quickly from packet loss without requiring retransmission. Network auto-detect. RDP in Windows Server R2 detects end-to-end network speed by measuring latency and available bandwidth, and then adjusts the type of connection and the data transfer based on the available bandwidth and latency.
RemoteFX Adaptive Graphics RemoteFX Adaptive Graphics provides graphics processing that enables higher-fidelity delivery of virtual desktop and RemoteApp programs, including video, text, Aero Glass, and 3D experience across various networks such as those where bandwidth is limited and latency is high.
By default, the RemoteFX graphics processing pipeline adaptively determines the optimal RDP experience level based on available bandwidth and server resources. If this Group Policy setting is disabled or not configured, the graphics pipeline dynamically adjusts the configuration to give the user the best experience, but if the deployment is targeted toward supporting the maximum number of sessions, this Group Policy setting can be enabled and set to Optimize for Scale.
In this case, bandwidth use could be high for some scenarios. However, if the deployment environment is such that users are on a bandwidth-limited link, you can set the Optimize for bandwidth option.
Note that in this case, CPU use may be high. Figure 6 demonstrates how RemoteFX Adaptive Graphics dynamically adapts to changing network conditions and optimizes encoding to the content.
With progressive rendering, text remains clear while images are progressively refined, as shown in Figure 7. Users see the device within the remote session; the USB device, desktop, and apps all appear as local, integrated resources, creating a unified experience. When a user plugs in a USB-based resource, it appears only within that users session and isnt visible to other users who connect to the same server.
RemoteFX Multitouch Windows Server R2 introduces multitouch and gesture remoting with support for up to simultaneous touch inputs. This feature enables users to employ the new breed of touch-enabled and gestureenabled apps in remote desktop environments.
Requirements This feature requires the following:. Microsoft now supports multiple GPUs within one server and is seeing greater engagement with original equipment manufacturers to provide systems that support this capability. Summary With RemoteFX, you can use Group Policy to configure USB redirection support to allow remote workers to plug in their USB flash drives and portable printers for quicker and easier access in their individual virtual desktop sessions.
The built-in WAN optimizations employ FEC, network auto-detection, and other techniques to compensate for variable network conditions and provide a positive user experience for his remote users.
These and other enhancements in RemoteFX give remote users the same experience they have with locally installed desktopsfrom USBconnected devices to video streaming and advanced graphics renderingeven while connecting over WANs.
0コメント