News

SP1 Hits RTM Status for Windows 7 and Windows Server 2008 R2

On Wednesday Microsoft released Service Pack 1 (SP1) for Windows 7 and Windows Server 2008 R2 to its equipment manufacturing partners.

SP1 has essentially hit the "RTM" milestone, in Microsoft's parlance, which is the time when hardware manufacturers start creating images of the software for their server products. The service pack will be available to Microsoft's TechNet and MSDN subscribers, as well as to Microsoft volume licensing customers, on Feb. 16, 2011. It will be generally available via the Microsoft Download Center and Windows Update on Feb. 22, according to an announcement on the Microsoft Server Division blog.

Windows 7 users won't see any new features from this service pack, which contains cumulative updates to the desktop operating system. However, for Windows Server 2008 R2 users, SP1 contains two new virtualization features: "dynamic memory" for Hyper-V and "RemoteFX" for Remote Desktop Services.

Dynamic memory allows operators to pool the memory available on hardware and allocate it to virtual machines as needed. The RemoteFX capability supports an improved graphics experience on thin-client devices when users connect remotely with servers in virtual desktop infrastructure (VDI) scenarios.

Microsoft claims that dynamic memory use can boost VDI density by 40 percent on Windows Server 2008 R2 SP1 compared with Windows Server 2008. The company's tests used Windows 7 as the guest operating system.

In a slam thrown in VMware's direction, Microsoft claims that dynamic memory can be used to boost VDI scenarios without compromising security. A Microsoft virtualization blog points to VMware, accusing the company of recommending disabling a Windows security feature called "Address Space Layout Randomization" (ASLR) as a best practice in VDI deployments. ASLR protects against malware-induced memory buffer attacks by loading DLL files into random memory on boot-up, making the APIs harder for malware to find. Microsoft doesn't recommend disabling ASLR and claims that using it does not slow VDI performance to a significant degree.

RemoteFX works with Microsoft's Remote Desktop Services (formerly known as "Terminal Services") and uses intellectual property that Microsoft acquired with it bought Callista Technologies in 2008. Microsoft's Server Division blog describes the RemoteFX technology as allowing IT shops to "virtualize the Graphical Processing Unit (GPU) on the server side and deliver next-generation rich media and 3D user experiences for VDI." The technology is described as allowing users remote access to graphics-intensive applications, such as CAD programs, on thin-client devices.

About the Author

Kurt Mackie is senior news producer for 1105 Media's Converge360 group.

comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube