- User interface changes in response to feedback we received from beta testers
- Support for dynamic memory on Standard & Web editions of Windows Server
When installed in a supported Linux virtual machine running on Hyper-V, the Linux Integration Components provide:
• Driver support for synthetic devices: The Linux integration components include support for both the synthetic network controller and synthetic storage controller that have been developed specifically for Hyper-V. These components take advantage of the new high-speed bus, VMBus, which was developed for Hyper-V.
• Fastpath Boot Support: Boot devices now take advantage of the storage VSC to provide enhanced performance.
• Timesync: The clock inside the virtual machine will remain synchronized with the clock on the host.
• Integrated Shutdown: Virtual machines running Linux can be shut down from either Hyper-V Manager or System Center Virtual Machine Manager, using the “Shut Down” command.
• Symmetric Multi-Processing (SMP) Support: Supported Linux distributions can use up to 4 virtual processors (VP) per virtual machine.
• Heartbeat: Allows the host to detect whether the guest is running and responsive.
• Pluggable Time Source: A pluggable clock source module is included to provide a more accurate time source to the guest.
Although this version of the integration services for Hyper-V supports Novell SUSE Linux Enterprise Server 10 SP3, SUSE Linux Enterprise Server 11, and Red Hat Enterprise Linux 5.2 / 5.3 / 5.4 / 5.5, Red Hat Enterprise Linux 5 x64 editions do not support using the Pluggable Time Source component.
However, you can use the existing timesync component with the adjtimex RPM package, to compensate for time drift:
If using the x64 version of Red Hat Enterprise Linux, follow these additional instructions:
1. Attach the Red Hat Enterprise Linux ISO that was used for installation in the virtual machine, and mount it using the following commands at a shell prompt:
# mkdir /mnt/cdrom
# mount /dev/cdrom /mnt/cdrom
2. Install the adjtimex RPM for more accurate time keeping in the virtual machine:
# rpm –ivh /mnt/cdrom/Server/adjtimex-1.20-2.1.x86_64.rpm
To install the Linux IC.
After the ISO is “available”.
Firstly, install the Required Components via Command Line
Red Hat updates
# yum install kernel-devel
# yum groupinstall “development tools”
# yum update
Restart the VM and then, insert the LinuxIC iso into the DVD drive and copy the contents to /opt/linuxic directory.
Run the commands below, to install the IC:
# mount /dev/cdrom /mnt
# mkdir /opt/linux_is
# cp –r /mnt/* /opt/linux_is
# cd /opt/linux_is
# make install
To verify that the Linux ICs are working.
# /sbin/lsmod | grep vsc
# modinfo vmbus
To verify the Synthetic Ethernet adapter is working
# ifconfig seth0 Note: Article also published by myself at http://social.technet.microsoft.com/wiki/contents/articles/workaround-for-pluggable-time-source-support-for-rhel-5-x-64-bit-hyper-v-guests.aspx My thanks to Sumesh P - MSFT, who helped with the tip.
Windows 7 SP1: RemoteFX. Steps to provide the same user experience as though they were running on a physical computer
The RemoteFX feature allows Windows 7 SP1 and applications running in virtual machines to provide the same user experience as though they were running on a physical computer.
The RemoteFX feature also allows remote users to redirect local USB devices to their Remote Desktop sessions.( I will talk about this in my next article )
The following steps will help you understand how RemoteFX improves the user experience when running Windows 7 and applications in a virtualized environment :
1. Install Windows Server 2008 R2 SP1
- Verify that the appropriate device drivers have been installed for the 3D accelerated video display adapter.Unless the appropriate device drivers are installed for the 3D accelerated video display adapter, you cannot start the Windows 7 virtual machine with the RemoteFX 3D Video Adapter Support enabled
- Install the Hyper-V server role.
- Install the Remote Desktop Services server role with the following role services:
Remote Desktop Virtualization Host
2.Install Windows 7 SP1.
- Enable Remote Desktop connections
- Shutdown the Windows 7 virtual machine.
3. Enable RemoteFX 3D Video Adapter Support on Windows 7 Virtual Machine.
The RemoteFX 3D Video Adapter Support must be added to the Windows 7 virtual machine by performing the following steps on the computer running Windows Server 2008 R2 SP1:
- Start Hyper-V Manager.
- In Hyper-V Manager, select the Windows 7 virtual machine and in the Actions pane click Settings.
- In the navigation pane, under the Hardware section, click Add Hardware.
- Add the adapter; start the virtual machine; verify that the adapter is installed and then restart the machine.
- In the properties pane, click RemoteFX 3D Video Adapter, and then click Add.
- The RemoteFX 3D Video Adapter appears in the list of hardware in the Hardware section as show in the following figure.
- Start the virtual machine; verify that you can login and that you have loaded the driver. The VM will ask to be restarted at this point, perform the restart.
4. To checkout that RemoteFX is properly installed and configured :
Start the virtual machine running Windows 7 SP1.
Establish a Remote Desktop session with Windows 7 SP1 by using the Remote Desktop Connection client in Windows Server 2008 R2 SP1
- On the Local Resources tab(Remote Desktop Connection client), in Apply Windows key combinations, select one of the following:
- Only when using full screen. Select this option if you are going to run the Remote Desktop session in full screen.
- On the remote computer. Select this option if you are going to run the Remote Desktop session in a window.
- On the Experience tab, in Performance section, select LAN (10Mbps or higher) and verify that all the check boxes are selected.
- Log on Windows 7 SP1.
- Change the theme for the Windows 7 to use an Aero theme. The desktop theme should appear with all the Aero features, such as transparency.
As you can see the RemoteFX feature allows Windows 7 SP1 and applications running in virtual machines to provide the same user experience as though they were running on a physical computer.
Other improvements in Windows 7 SP1 :
· Additional support for communication with third-party federation services – Additional support has been added to allow Windows 7 clients to effectively communicate with third-party identity federation services (those supporting the WS-Federation passive profile protocol).
· Improved HDMI audio device performance – Updates have been incorporated into SP1 to ensure that connections between Windows 7 computers and HDMI audio devices are consistently maintained.
· Corrected behavior when printing mixed-orientation XPS documents – Prior to the release of SP1, some customers have reported difficulty when printing mixed-orientation XPS documents (documents containing pages in both portrait and landscape orientation) using the XPS Viewer, resulting in all pages being printed entirely in either portrait or landscape mode. This issue has been addressed in SP1, allowing users to correctly print mixed-orientation documents using the XPS Viewer.
Download from here: http://www.microsoft.com/windowsserver2008/en/us/sp1.aspx
Some of the improvements for Windows Server 2008 R2 SP1 include:
• Dynamic Memory – Dynamic Memory allows for memory on a host machine to be pooled and dynamically distributed to virtual machines as necessary. Memory is dynamically added or removed based on current workloads, and is done so without service interruption.
• Microsoft RemoteFX – a new set of remote user experience capabilities that enable a media-rich user environment for virtual desktops, session-based desktops and remote applications
• Enhancements to scalability and high availability when using DirectAccess – improvements have been made to enhance scalability and high availability when using DirectAccess, through the addition of support for 6to4 and ISATAP addresses when using DirectAccess in conjunction with Network Load Balancing (NLB).
• Support for Managed Service Accounts (MSAs) in secure branch office scenarios – enhanced support for managed service accounts (MSAs) to be used on domain-member services located in perimeter networks (also known as DMZs or extranets).
• Support for increased volume of authentication traffic on domain controllers connected to high-latency networks – more granular control of the maximum number of possible concurrent connections to a domain controller, enabling a greater degree of performance tuning for service providers.
• Enhancements to Failover Clustering with Storage – SP1 enables enhanced support for how Failover Clustering works with storage that is not visible for all cluster nodes. In SP1, improvements have been made to the Cluster Validation and multiple Failover Cluster Manager wizards to allow workloads to use disks that are shared between a subset of cluster nodes.
Note : once the final build of SP1 ships, you’ll need to uninstall the RC version in order to upgrade.
|Elevate the security of Windows Server 2008 R2.
The Windows Server 2008 R2 Security Baseline, in combination with the Security Compliance Manager tool, is designed to help your organization plan, deploy, and monitor the security of Windows Server 2008 R2. This release also includes a Windows Server 2008 R2 settings pack, enabling you to define baselines that include settings outside the scope of the security baselines from Microsoft.
To get the public release of this security baseline, download the Security Compliance Manager.
New security baselines for SQL Server 2008 and SQL Server 2008 R2 now available for beta download.
The latest security baselines in this beta review program are designed to help you plan, deploy, and monitor the security of Microsoft SQL Server 2008 and SQL Server 2008 R2.
The baselines are formatted for import using the Security Compliance Manager, which provides guidance and tools to help you balance your organization’s needs for security and functionality.
The following Windows server operating systems support Dynamic Memory when installed as the guest operating system on a virtual machine:
- Windows Server 2008 R2 Standard Edition SP1*
- Windows Server 2008 R2 Enterprise Edition SP1
- Windows Server 2008 R2 Datacenter Edition SP1
- Windows Server 2008 R2 Web Edition SP1*
- Windows Server 2008 Standard Edition SP2*
- Windows Server 2008 Enterprise Edition SP2
- Windows Server 2008 Datacenter Edition SP2
- Windows Server 2008 Web Edition SP2*
- Windows Server 2003 R2 Standard Edition SP2 or higher*
- Windows Server 2003 R2 Enterprise Edition SP2 or higher
- Windows Server 2003 R2 Datacenter Edition SP2 or higher
- Windows Server 2003 R2 Web Edition SP2 or higher*
- Windows Server 2003 Standard Edition SP2 or higher*
- Windows Server 2003 Enterprise Edition SP2 or higher
- Windows Server 2003 Datacenter Edition SP2 or higher
- Windows Server 2003 Web Edition SP2 or higher*
Note: The Beta release of Service Pack 1 does not support Dynamic Memory for the operating systems marked with an asterisk (*) above. However, support for Dynamic Memory for these operating systems will be added in a future release of SP1.
Note: Dynamic Memory is supported for both the x86 and x64 architectures of Windows Server 2003, Windows Server 2003 R2 and Windows Server 2008.
The following Windows client operating systems for both x86 and x64 architecture also support Dynamic Memory when installed as the guest operating system on a virtual machine:
- Windows® 7 Enterprise Edition
- Windows 7 Ultimate Edition
- Windows Vista® Enterprise Edition SP2
- Windows Vista Ultimate Edition SP2
Ben Armstrong ( Virtual PC Guy ), Virtualization Program Manager at Microsoft, wrote a good article about this.