The PressPass Q&A we posted today addressed a number of questions around Windows XP Mode. I wanted to clarify in more detail the differences between Windows XP Mode and MED-V and how specifically MED-V v2, a component of the Microsoft Desktop Optimization Pack (MDOP), adds management to Windows XP Mode.

The main facts:

Windows XP Mode is specifically designed to help small-business users to run their Windows XP applications on their Windows 7 desktop.

• Windows XP Mode is available for Windows 7 Professional, Windows 7 Ultimate and Windows 7 Enterprise customers.
• Windows XP Mode combines Windows Virtual PC and a pre-installed virtual Windows XP environment to allow users run many older applications.
• Windows Virtual PC will enable users to launch virtual applications seamlessly from the Windows 7 Start menu.
• Windows Virtual PC includes support for USB devices and is based on a new core that includes multi-threading support.

Microsoft Enterprise Desktop Virtualization (MED-V) is designed for IT Professionals.

• MED-V enables Virtual PC deployment in larger organizations.
• MED-V provides centralized management, policy-based provisioning and virtual image delivery to reduce the cost of Virtual PC deployment.
• MED-V v1 builds on Microsoft Virtual PC 2007 to help enterprises with their upgrade to Windows Vista when applications are not yet compatible.
• MED-V v2 will add support for Windows 7 (both 32 bit and 64bit) and Windows Virtual PC.
• MED-V v2 beta will be available within 90 days of Windows 7 GA.

How MED-V adds management to Windows XP Mode and Windows Virtual PC?

To provide a managed, scalable solution for running virtual Windows XP applications, MED-V addresses many of the IT challenges around deployment and management including:

Deployment – deliver virtual Windows images and customize per user and device settings

• Automate first-time virtual PC setup based on an IT customized script – including assignment of a unique computer name, joining to AD domain
  (for instance: assign the virtual PC a name that is derived from the physical device name or the username to simplify identification and management)
• Adjust virtual PC memory allocation based on available RAM on host, so that the virtual PC does not take significant resources from the user

Provisioning – define which applications and websites are available to different users

• Assign virtual PC images according to users and groups
• Define which Windows XP applications will be available to the user through the start menu
• Define which websites (e.g. internal sites that requires a previous version of Internet Explorer) are redirected automatically to Windows XP

Control – assign and expire usage permissions and Virtual PC settings

• Control the network settings of the Virtual PC (e.g. whether it connects through NAT or DHCP, whether its DNS is synchronized with host)
• Authenticate user before granting access to the Virtual PC
• Set expiration date, after which the Virtual PC is not accessible to the end user

Maintenance and Support - update images, monitor users and remotely troubleshoot

• Update images using TrimTransfer network image delivery – update a master Virtual PC image, and MED-V will automatically distribute and apply the changes to all endpoints
• Centralized database aggregates events from all users, and provides troubleshooting information on malfunctioning virtual PCs
• Administrator diagnostics mode allows faster resolution of Virtual PC issues

Run on multiple platforms – MED-V will work on both Windows 7 and Windows Vista.

Which customers should use Windows XP Mode standalone?

Windows XP Mode standalone is suitable for small and medium business users, who are able to set their XP applications themselves and may or may not have IT Professional staff. Each PC has its own virtual Windows XP environment that is controlled and managed by the end user. Windows XP Mode standalone is not designed for large, centrally managed deployments that have widely deployed business applications that require Windows XP.

So in summary MED-V builds on top of Windows Virtual PC and adds important management capabilities.

A few weeks ago I discovered Nikon had released a new version of their Nikon RAW Codec for download - Version 1.4.0. This new version adds support for Windows Vista SP1. The Nikon RAW Codec is for users shooting in the RAW photo format with Nikon cameras to view Nikon's RAW .NEF files in using Windows Live Photo Gallery.

Download: Nikon RAW Codec Version 1.4.0

I discovered a hidden "gem" with this new release however. It runs on PCs running 64-bit versions of Windows Vista.  Apparently, this version of Nikon's RAW Codec takes advantage of Windows Vista's built in 32-bit emulation feature called WOW64. I've got it installed on my Windows Vista 64-bit PC and am able to import and view RAW images (.NEF files) off my Nikon D40 into Windows Live Photo Gallery and view them just fine. I've confirmed this works with a few friends of mine who also use Nikon cameras and running a 64-bit version of Windows Vista.

If you shoot photos with a Nikon digital camera, use the RAW file format and run a 64-bit version of Windows Vista - definitely give this version of the Nikon RAW Codec a try. It worked for me, I'm hoping it works for you!

There appears to be a shift taking place in the PC industry: the move from 32-bit to 64-bit PCs.

We've been tracking the change by looking at the percentage of 64-bit PCs connecting to Windows Update, and have seen a dramatic increase in recent months. The installed base of 64-bit Windows Vista PCs, as a percentage of all Windows Vista systems, has more than tripled in the U.S. in the last three months, while worldwide adoption has more than doubled during the same period.  Another view shows that 20% of new Windows Vista PCs in the U.S. connecting to Windows Update in June were 64-bit PCs, up from just 3% in March. Put more simply, usage of 64-bit Windows Vista is growing much more rapidly than 32-bit. Based on current trends, this growth will accelerate as the retail channel shifts to supplying a rapidly increasing assortment of 64-bit desktops and laptops.

64-bit PCs running 64-bit editions of Windows Vista typically have 4GB of memory or more. Compared to 32-bit systems, which top out at around 3GB of memory, 64-bit PCs can offer added responsiveness when running a lot of applications at the same time and have the potential for greater performance and new experiences as next-generations applications are written to take advantage of this new platform.

What started out as a gradual (some would say "glacial") movement toward 64-bit PCs, driven primarily by technology enthusiasts, seems to have turned into a swift transition, likely fueled by the falling cost of memory and consumers' desire to get the most out of their PCs.

This change begs a few questions:

Is the 64 bit market ready to go mainstream?

Will consumers realize the benefits from larger chips and 4GB or more of memory?

The answer to both of these questions is yes - but a qualified yes.

Preconfigured 64-bit PCs obtained from retailers or PC manufacturers should work quite well.  This is in stark contrast to the experience of many technology enthusiasts who built their 64-bit PC from scratch and may have had to scour the Web looking for drivers.  So, unless you really love to tinker with your PC, we suggest you buy a pre-built 64-bit PC at retail or directly from a PC manufacturer.

Beyond the box, you also need to consider the hardware peripherals and software programs you plan on using with your new PC. Any hardware or software product displaying the ‘Works with Windows Vista' or ‘Certified for Windows Vista' logo must be compatible with both the 32-bit and 64-bit editions of Windows Vista in order to warrant the use of the logo. If you don't see the logo, visit the Windows Vista Compatibility Center and check the 64-bit compatibility status. Hardware and software vendors continue to test and improve their products. Please note that the Windows Vista Compatibility Center is currently in beta. In some cases it is possible that a device may be marked as not compatible when in fact it is. I recommend that you also check with the device manufacturer to see if the compatibility status of your desired device has changed.

On the performance front, 64-bit PCs can provide a more responsive experience when running many applications simultaneously. Websites such as Bit.Tech.Net and Tom's Hardware have published performance benchmarks detailing some of the improvements realized from running the 64-bit PCs. In addition, PC Accelerators built into Windows Vista, such as Windows SuperFetch, improve performance by keeping commonly used programs in memory, even when the program is closed. More memory capacity on 64-bit PCs allows SuperFetch to do its job more efficiently.  

But if you only use your PC for a few tasks, and rarely do them at the same time, then you're unlikely to realize a measurable performance benefit today.  Of course, buying extra capacity for your future, unplanned needs is always worth considering.

In the future, we expect both compatibility and performance of 64-bit PCs to continue to improve. Most hardware devices have 64-bit drivers today and most software products work unmodified because of the 32-bit emulation technology in 64-bit Windows Vista (called WOW64). But there are some gaps, especially in the long tail of the market, but we expect rapid improvement now that 64-bit PCs are getting so popular.

Over time we'll see more 64-bit-optimized programs hit the market, which promise dramatic performance and experience improvements. A few key ones, like Adobe Lightroom & Photoshop and Sony Vegas Pro video editing software, are due to be released this fall. If you're a software or hardware developer, visit our 64-bit readiness page to learn more about 64-bit compatibility and optimization.

Today, the Windows Home Server Team has announced the availability of the Windows Home Server Power Pack 1 Release Candidate for download on Microsoft Connect. You can read Charlie Kindel's post announcing today's release on the Windows Home Server Team Blog.

Microsoft Connect: Windows Home Server

Power Pack 1 for Windows Home Server contains numerous bug fixes - including the data corruption issue - as well as many new enhancements to Windows Home Server many users will enjoy:

• Support for PCs running Windows Vista x64 editions
• Backup of Windows Home Server Shared Folders
• Easier, enhanced remote access capabilities
• Better energy efficiency
• Improved performance
• Chinese and Japanese versions

I'm currently running the Power Pack 1 Release Candidate on my HP MediaSmart Server and enjoying new functionality Power Pack 1 adds to my Windows Home Server. I recently added several harddrives putting my storage at 1.1TB. Having more storage allows me to utilize Folder Duplication for my Shared Folders. I also have 1 drive setup specifically for backups of my Shared Folders. I utilize my Shared Folders for quite a bit of data storage so I really appreciate having this functionality to ensure the data is safe (on top of Folder Duplication). Having more storage also lets me store my CompletePC Backups from my Windows Vista PCs on my Windows Home Server as well - but I will talk more about this in a later blog post. I am also enjoying the ability to backup my PCs to my Windows Home Server running Windows Vista Ultimate x64 with the Windows Home Server Connector that now runs on 64-bit versions of Windows Vista. On top of data storage and backups, I utilize my Windows Home Server for remote access when traveling as well.

Your testing of the Windows Home Server Power Pack 1 Release Candidate is very important to the Windows Home Server Team. They will not ship the final release of Power Pack 1 until the community validates their work in Power Pack 1.

Remember - Power Pack 1 is a Release Candidate and is not the final version - essentially it's a beta. If you choose to run the Release Candidate on your main Windows Home Server (aka your "production" Windows Home Server) you should make a backup of everything prior to installing the Power Pack 1 Release Candidate.

To leave feedback for the Windows Home Server Team - you can head on over to the public Windows Home Server Forums. Make sure you file any bugs you find with Power Pack 1 on Microsoft Connect.

I’m happy to tell you that WSUS version 3.0 has been released! The release day was April 30th 2007 - a day to remember…

This version bring lots of goodies compared to it’s younger brother WSUS 2.0 (who did a great job in my opinion).

So, what’s new? Well, let my try to wrap up some of the really good stuff:
- Inplace upgrade over WSUS 2.0 SP1
- New setup and configuration wizard
- New MMC (Microsoft Management Console) GUI
- New views and reports (and faster reports - up to 50%)
- Cleanup wizard for management of stale clients and content
- Built-in email notifications
- New approvement rules
- Enhanced target group concepts (eg. overlapping group membership)
- Support for language sub-setting for downstream replica servers
- Peer caching
- Syncronization with MS down to every 1 hour now
- Native support for x64 platform
- NLB (Network Load balancing) and SQL Cluster support
- MOM Management Pack (will be released very soon)
- Client ‘Sync me now’ quick check-in
- and all the other stuff…

Download:
x86/x64 package
WSUS 3.0 Release Notes
WSUS 3.0 on SBS 2003
Deployment Guide for WSUS 3.0
Step-by-step Guide: Getting Started with WSUS 3.0

Go to WSUS Technical Library for more information, guides etc.

I think we will all benefit from this release - well, maybe not the penguin guys :)