The Windows Server Migration team's been cooking...no, not cranberry sauce and stuffing, but a new Windows Server Migration Utilities download package that lets you use the Windows Server Migration Tools to migrate Hyper-V and Routing and Remote Access Services (RRAS). Brand-spankin'-new beta migration guides are available for both Hyper-V and RRAS, with detailed, step-by-step guidance about how to use the Windows Server Migration Tools (after the Utilities package is installed, of course) to migrate to servers that are running Windows Server 2008 R2.

Still not feeling the love? We've got new beta migration guides for Active Directory Certificate Services (AD CS), Health Registration Authority (HRA), Network Policy Server (NPS), and Windows Server Update Services 3.0 SP2 (WSUS). AD CS, HRA, NPS, and WSUS don't even require the Windows Server Migration Tools; you can migrate from prep to production, just by following the guides.

We can't say it enough: your feedback rocks. The Windows Server Migration team is collecting feedback about the beta guides and the Utilities download package through the end of 2009. You can use the following methods to speak your mind about Migration Guides and the Windows Server 2008 R2 Migration Utilities Beta package. Share your migration experiences; they're critical to the quality of the Migration Guides, Windows Server 2008 R2 Migration Utilities, and the whole Migration solution for WS08 R2!

  • Take the Windows Server 2008 R2 Migration Utilities Beta Survey. Nothing goes better with a cup of coffee.
  • Got an earful about how to improve Migration guides or utilities? Reply to the Windows Server 2008 R2 Migration Utilities release announcement on the Windows Server Migration forum.
  • Found a bug in our migration guides? Send e-mail to smcpe at Microsoft.com. Include a description of your migration scenario (especially the operating systems that are running on your source and destination servers), and any workarounds that you used to resolve the problem. Unless the problem defied workarounds, of course; in that case, you can just send us a hard luck story and/or flame mail, we still want to hear from you.
  • Found a bug in the tools? Send e-mail to smcpe at Microsoft.com. Include a description of your migration scenario (especially the operating systems that are running on your source and destination servers), the steps to reproduce the bug, and the following logs:
    • %windir%\Logs\SmigDeploy.log
    • %windir%\Logs\ServerMigration.log
    • On Windows Server 2008 and Windows Server 2008 R2: %localappdata%\SvrMig\Log
    • On Windows Server 2003: %userprofile%\Local Settings\Application Data\SvrMig\Log

Visit the Windows Server Migration Portal on TechCenter to see the complete collection of Windows Server 2008 R2 Migration Guides, and a truckload of other migration resources, too.

-- Cheers from the Windows Server Migration team!