Your browser (Internet Explorer 6) is out of date. It has known security flaws and may not display all features of this and other websites. Learn how to update your browser.

Running Mac OS X on Windows VMware Workstation

DISCLAIMER: This post doesn’t express any warranties. It is provided as-is and you are proceeding at your own risk taking into consideration all license and legal ramifications. This post is meant to show you what is possible to do, not whether or not it is legal or allowed to be done.

Sometimes you just need the ability to test an Operating System.  For these purposes this blog post will show you how to run Mac OS X 10.8 in VMware Workstation for the purpose of testing Mac management with System Center 2012 Configuration Manager.  As a consultant,, I travel constantly, I can’t exactly carry around a Mac mini in my laptop bag, well I probably could but I have no desire to.  I already ditched my heavy laptop for an Ultrabook, rather than my previous Lenovo W520 that had a power supply I could crush most small rodents with.

There are numerous posts with various bits of information, but didn’t see one comprehensive guide. I’ve also seen pre-created VM’s that you can download and import into VMware Workstation, but I prefer to have my own clean VM that I built and don’t need to worry about where it came from. Call me crazy..

Files you will need:

Step 1: Install VMware Workstation on your machine.

Note that you cannot have Hyper-V and VMware Workstation installed on the same box 🙂

Step 2: Run VMware Unlocker 1.1.0.

1) Extract out VMware Unlocker.

2) Run the install.bat that is in the \windows folder. This will configure VMware Workstation to support Mac OS X.

3) You should now see Apple Mac OS X listed in the New Virtual Machine Wizard.


4) Create a new Virtual Machine for Mac OS X 10.8, Mac OS X will need a minimum of 2GB of RAM.

Step 3: Use 7Zip or a similar program to extract out the InstallESD.dmg from the Mac OS X 10.8 installation DVD.

Step 4: Using the dmg2img program, create a ISO of the Mac OS X install.

Example command line:

dmg2im -I "path\installesd.dmg" -o "path\macosxsetup.iso"


MacOSXSetup.iso successfully created.


Step 5: Extract out the to get the darwin.iso from under \payload.


Step 6: Mount the newly created MacOSXSetup.iso with the VMware Workstation VM.


Step 7: Start the VM and launch the Mac OS X Setup from the ISO we created.


1) Select the Disk Utility so we can format the drive before installing the OS


2) Select the disk and then select Erase, the format should be Mac OS Extended Journaled.


3) Select Erase on the prompt.


4) Close the Disk Utility and Select Reinstall OS X.


5) Select Continue.


6) Select Agree.


7) Select the disk and then Install.


8) Installation will start.


All installed!


9) You’ll have to continue through some additional setup and personalization and create your account.


Finally done and we can see our desktop!


Step 8: Install VMware tools.

1) Mount the darwin.iso to the VM, a restart might be required to get it to properly show up in the VM.

2) In order to see the icons on the desktop, go into Finder Preferences, and check the Hard Disks, External Disks, CD/DVD, and Connected Servers boxes.


3) You should now be able to see the VMWare tools DVD.


4) Double-click the VMware Tools DVD.  Double-Click Install VMware Tools.


5) Click Continue.


6) Click Continue.

7) Click Install.

8) Enter your password to install the software.


9) Select Continue Installation.

10) Restart upon completion.


After the reboot, you should see functional VMware tools. The window should resize etc. per standard VMware tools.

Step 9: Take a Snapshot!

It’s a good idea to have a clean slate to revert to if needed.

Step 10: Enjoy!


Migrating User Settings from Office 2003 to a Sequenced Version of Office 2010 running under App-V

Richard Smith has a nice post over on The Deployment Guys blog. 

Read the full post here.

Scenario1 – The Office Only Upgrade

You work in the IT department for large organisation which has an Standard Operating Environment (SOE) based on Windows XP and Office 2003. This is still a fairly common (although thankfully dying) situation. Your organisation is looking to upgrade to Office 2010, however there are some considerations. How do you know you’ve identified all critical Office files and checked their compatibility? Are you aware of every Office add-in being used in your environment? In order to proceed, you decide to leverage your investment in Software Assurance and MDOP, using App-V to deploy Office 2010 along side Office 2003. This will allow your users to get to know Office 2010 and identify any potential compatibility issues, without taking away their existing productivity suite. If something doesn’t work, you can instruct your users to simply keep editing that particular spreadsheet in Excel 2003 until the issue is resolved. This approach will also help you to support your  users adjustments to the change(s), by allowing them access to Office 2003 ‘just in case’.

Scenario 2 – The Windows 7 and Office 2010 Upgrade

OK, say you now work in the IT department for a different large organisation. Unfortunately, like in the first scenario, this company still has an SOE based on Windows XP and Office 2003. However this time you have the IT Director on your side and he/she is keen as mustard to upgrade the whole fleet to Windows 7 and Office 2010. Your organisation has a large number of sites, with varied desktop requirements, so you will need to deploy a light-weight, flexible SOE. You once again decide to leverage your investment in Software Assurance and MDOP. This time you can create a base Windows 7 image without any Microsoft Office products installed (as this will save you a few gigs in your WIM). You sequence Office 2010 using App-V with the intention of streaming the applications only to those PC’s that require them. Things are looking good… your department stands to realise significant savings from reduced software licenses, you have a flexible and efficient SOE ready to go…. the IT Director will be pleased…. maybe it’s time to ask for a pay rise?

So… do either of these scenarios sound familiar? If you’ve gone down these paths you’ve likely been faced with the challenge of migration settings from Office 2003. Take App-V out of the equation and this is a fairly straight forward concept, Office 2010 applications will migrate settings from previous versions the first time they launch… simple. With Office delivered through App-V however it’s a very different story. Sequence Office 2010 either by following the guidance on TechNet, or by using the new Package Accelerator (cool) and you’ll find that none of your user settings get migrated. Essentially, there are 2 reasons for this. First, during the sequencing process, we launch various Office applications a number of times. As such, when the applications launch for the first time on the user’s computer under App-V, they don’t exhibit their normal ‘first run’ behaviour, as it was performed already during sequencing. Second, even if the Office applications tried to perform their ‘first run’ actions, they wouldn’t be able to see the registry keys containing Office 2003 user settings, as these would be overridden by the Office 2010 information in the virtual registry.

In this post I will explain the steps required to deploy Office 2010 using App-V, in a manner that allows each user’s Office 2003 settings to be migrated across. To avoid re-inventing the wheel, I’m going to assume you are already familiar with the Microsoft Office Customization Tool (OCT), which we’ll use as part of the solution. If you haven’t used OCT before, I’d suggest take a look at this TechNet article, which has plenty of technical details and videos. I’m also going to assume that you are familiar with sequencing App-V packages, specifically Office 2010. Microsoft provide some fairly explicit guidance in this TechNet article. OK, let’s make this happen!! This solution is essentially a big ‘’Jedi Mind Trick’ (These aren’t the registry keys you’re looking for). We need to trick the sequenced version of Office 2010 into behaving the way we want. We need to trick it into thinking that Office 2003 was previously installed so it will attempt to migrate settings at ‘first run’. We also need to trick it into thinking that it has never launched before, even though it has, during the sequencing process.


Enabling Hyper-V Role Successfully via Operating System Deployment Task Sequence

Read the original post here.

During a ask-the-experts at Microsoft Management Summit (MMS) 2011 in Las Vegas, a customer asked a question of how to utilize Microsoft Deployment Toolkit (MDT) 2010 Update 1 to install Windows Server 2008/R2 and enable the Hyper-V role.  The customer had tried several things but to no avail as the customer was using ConfigMgr’s Operating System Deployment (OSD) feature and this wasn’t working.  In today’s post, I thought I would share how to easily do this.


Hyper-V new performance updates

Read the original post here by Michael Kleef.

Aussie legend Cameron McBride and good friend Tony Sanchez from Citrix sent a heads up to me recently on some performance related hotfixes. They are specific to proc and SP1. Nevertheless they are definitely worth applying for the best performance.

Issue 1: Performance is not as awesome as it could be on Westmere or Sandybridge chipsets


  • You have a Windows Server 2008 R2-based computer that has a large amount of physical memory and that has Intel Westmere or Sandy Bridge processors.
    For example, you have a computer that has Intel Xeon 5600 series processors and that has 48 gigabytes (GB) physical memory.
  • You install the Hyper-V role on the computer.

In this scenario, the performance of the computer may decrease.
For example, the following performance issues may be encountered:

  • The CPU usage is high and the server responds slowly when you copy large files on the computer. For example, you copy a 10-GB file.
  • The disk I/O performance of the virtual machines (VMs) is slow.
  • Windows takes a long time to start.

Issue 2: Networking Performance is not as awesome as it could be under load and is lost in certain scenarios

You install the Hyper-V role on a computer that is running Windows Server 2008 R2 Service Pack 1 (SP1).

  • You run a virtual machine on the computer.
  • You use a network adapter on the virtual machine to access a network.
  • You establish many concurrent network connections. Or, there is heavy outgoing network traffic.

In this scenario, the network connection on the virtual machine may be lost. Additionally, the network adapter may be disabled.

  • You must restart the virtual machine to recover from this issue.
  • This issue can also occur on versions of Windows Server 2008 R2 that do not have SP1 installed. To resolve the issue, apply the hotfix that is described in one of the following Microsoft Knowledge Base articles:

    974909 ( ) The network connection of a running Hyper-V virtual machine is lost under heavy outgoing network traffic on a Windows Server 2008 R2-based computer
    2264080 ( ) An update rollup package for the Hyper-V role in Windows Server 2008 R2: August 24, 2010

So theres hotfixes for both of these. Thanks Cam and Tony for the heads up on this!


Why Hyper-V for VDI whitepaper

Download the whitepaper here.

Brief Description

This whitepaper demonstrates why organizations should choose Microsoft® Hyper-V™ as their hypervisor when designing and implementing a Virtual Desktop Infrastructure (VDI) solution.


Choosing a hypervisor for deploying a VDI solution involves a number of important considerations, each of which can be fulfilled by using Microsoft’s Hyper-V 2008 R2 SP1 hypervisor-based virtualization technology. When implemented together with the Microsoft System Center family of products and desktop virtualization technologies from partners like Citrix, organizations can build integrated VDI solutions that can meet the needs of your business while keeping costs under control.Based on the results obtained from internal testing and because VM density has a significant influence on datacenter cost structures; an integrated Citrix/Microsoft VDI solution that includes Microsoft Hyper-V 2008 R2 SP1 and System Center delivers unique end-to-end business value for organizations planning on implementing VDI.


Breaking IT Down: Deploying MED-V with Existing Management Systems

Read the original post here.

Today’s post is from David Trupkin, Sr Product Manager from our Windows Virtualization Team.

As I’ve talked to IT pros at events around the world, many of you have told me that the biggest barrier to your Windows 7 deployments has been incompatible legacy applications. These applications may run on Windows XP or they might be browser-based applications that run in Internet Explorer 6 or 7. While many older applications just work in Windows 7, some may require compatibility shims. Others may require upgrades or patches. You may decide to replace some applications or retire them altogether. For those applications that are left – the ones that simply must run on Windows XP – you should know about Microsoft Enterprise Desktop Virtualization (MED-V) 2.0. MED-V bridges the “last mile” of application compatibility between Windows XP and Windows 7, allowing older applications to run inside Windows XP compatibility workspaces but integrate seamlessly into your users’ Windows 7 environment.

Don’t confuse MED-V with Microsoft’s consumer and small business compatibility tool, Windows XP Mode. MED-V expands on the capabilities in Windows XP Mode by adding enterprise features such as the ability to use a custom Windows XP image, automated first time setup, control of Internet Explorer URL redirection, automatic network printer mapping and easy packaging for enterprise distribution. MED-V version 1, first released in 2009, was based on a client-server model and required dedicated management servers. MED-V version 2, in Release Candidate status now and due for release before the end of March, 2011, is based on an application model which eliminates the need for a dedicated server. You can deploy and manage MED-V 2.0 with your existing software distribution management tools, like System Center Configuration Manager (SCCM).


Let’s spend some time looking at MED-V 2.0 and its requirements. On the client, the MED-V Host Agent installs on Windows 7 Professional, Enterprise or Ultimate with a minimum of 2GB RAM and will support either x86 or x64 architectures. At least 10 GB of disk space is recommended, although you may use more or less disk space depending on your particular workspace image and combination of applications. You’ll also need to deploy WVPC and WVPC KB977206 (which allows WVPC to run on systems without hardware-assisted virtualization) to systems that do not have them installed already.

MED-V Workspace Packager lets you package your Windows XP virtual machine for use as a MED-V workspace. The documentation included with the Workspace Packager will guide you through the process of:

•Preparing your Windows XP image
•Creating a MED-V Workspace package for deployment
•Testing and deploying your MED-V workspace
•Managing applications and software updates within MED-V and
•Managing MED-V settings after deployment
Often, you’ll deploy a management agent such as the SCCM client inside of your MED-V workspace to allow for application distribution and update along with patch management. The SCCM team has provided a client hotfix, to be installed on your SCCM SP2 Site Server, which improves SCCM functionality when you’ve configured your MED-V workspace to use network address translation (NAT). The hotfix allows a MED-V workspace that is also an SCCM client to use the same SCCM site and distribution point assignment as its host.

Once you’ve created your MED-V workspace package you’ll have a MED-V Workspace Package – a standard application file set that’s ready to deploy. You’ll find:

•A setup.exe
•A .medv file that is a compressed copy of your workspace VHD file and
•An .msi installer
You can create installation tasks within your software deployment tool to install MED-V and its prerequisites together, or you can create separate tasks that deploy the individual components. If you are using SCCM, you can create packages and a Task Sequence to install the MED-V and WVPC components.

In this sample batch script for MED-V component installation, the MED-V components are installed in inverted order, allowing the installation to complete with a single reboot. There are two things to keep in mind about this batch script. First, while the MED-V Client installer and MED-V workspace package installer will detect if they are running on an x86 or x64 system and will install the appropriate “bitness”, the WVPC update and associated hotfix are specific to x86 or x64 systems. Second, the MED-V installation will not be complete until the system is restarted.

REM install the MEDV Host Agent
start /WAIT msiexec /i MED-V_HostAgent_Setup.exe /qn IGNORE_PREREQUISITES=1
REM install the MED-V workspace package
start /WAIT .\setup.exe /qn OVERWRITEVHD=1
REM Install Windows Virtual PC (this example is for Windows Virtual PC x64)
start /WAIT Windows6.1-KB958559-x64.msu /norestart /quiet
REM Install Windows Virtual PC update (this example is for the x64 version of the update)
Windows6.1-KB977206-x64.msu /norestart /quiet

Here are command line examples for creating packages within SCCM:

•MED-V Host Agent
•msiexec /i MED-V_HostAgent_Setup.exe /qn IGNORE_PREREQUISITES=1
•MED-V workspace package
•setup.exe /qn
•WVPC installation (Note: This example shows the x64 version of WVPC. If installing within a Task Sequence, use “Run Command Line” instead of “Install Software” to avoid a reboot at this step.)
•wusa.exe Windows6.1-KB958559-x64.msu /norestart /quiet
•WVPC update (Note: This example shows the x64 version of the update. If installing within a Task Sequence, use “Run Command Line” instead of “Install Software” to avoid a reboot at this step.)
•wusa.exe Windows6.1-KB977206-x64.msu /norestart /quiet
Once MED-V 2.0 and Windows Virtual PC have been deployed, and any necessary reboot completed, the MED-V First Time Setup runs and legacy applications published from MED-V are available in the Windows 7 Start menu. Legacy web based applications or sites defined by the MED-V administrator are seamlessly redirected to Internet Explorer 6 or 7.

For more information on MED-V 2.0 and to try it yourself, register on Connect and check out the MED-V 2.0 Release Candidate today and for a complete library of information on MED-V, App-V, VDI and other desktop virtualization solutions, visit the Desktop Virtualization Zone on the Springboard Series on TechNet.



App-V: Why it should be the most important tool in your virtualization tool belt

Read the entire post here.

As discussed in previous posts, Microsoft’s Desktop Virtualization allows flexibility to deliver, test and manage the user settings, applications and your operating system, Windows 7, more easily. Today I’d like to further explore Application Virtualization, which is a key component to a complete desktop virtualization strategy. More specifically, I’ll review some of the business benefits customers are already experiencing today and how Microsoft partnerships can deliver added value.

Application virtualization helps to eliminate conflicts between applications, removes the need to install those applications on PCs, enables multiple versions of an application to coexist on the same machine and provides a faster, less intrusive way to deliver and update applications on demand. You can apply application virtualization to your local desktops, your RDS deployments, or your VDI desktops.

Based on the above, the benefits are clear and as a result we’re seeing that application virtualization, and specifically Microsoft‘s App-V, is quickly becoming a mainstream technology for organizations. Customers are indicating that App-V delivers savings throughout the application management lifecycle.


App-V with Appsense : Better Together

Read the entire post here.

I was talking with Stephen Rose, the owner of this blog, and he was saying that one of the top pain points that he hears from you frequently is transferring the user profiles when migrating from XP to Win7. In today’s blog post we are going to touch on Microsoft and its partner’s offerings that we feel will help solve that pain point.

This week, Karri Alexion-Tiernan posted a blog on the Windows For Your Business blog about the value of using App-V.For those not familiar, App-V is Microsoft’s flagship Application virtualization solution that enables you (IT pros) to deploy applications based on user’s identity and role, providing a more efficient way to deliver and mange applications centrally. Product Manager AJ Smith talked about User State Virtualization (USV) in his blog; how Microsoft’s USV technologies like Folder Redirection and Roaming Profiles empower you to provide users a consistent windows experience across multiple desktops and laptops, by separating user’s data and settings from the physical device and replicating it centrally.

One of Microsoft Premium partners Appsense provides user virtualization solutions that extends Microsoft’s USV offering by providing additional capabilities that’s helps in migration of XP profiles to Windows 7 profiles by seamlessly combining the two into a single version, thus accelerating Win 7 deployment in your organization. It can also abstracts both user’s desktop personalization and application settings, providing a consistent application experience across physical AND virtual applications. For additional info on Appsense, visit their website.

You can complement the benefits of both App-V and USV by deploying them together so that users can be provisioned both their applications and data on demand from multiple devices, thus reducing the dependency on one piece of hardware. In this blog we will go a level deeper and talk about what you should consider when implementing App-V with Appsense user virtualization. To get an overview – you can also watch this webinar from Appsense on App-V integration. Enough said on the value – let’s get into the technology piece!

I caught up with two Microsoft’s MVPs – Alaa Ajweh and Tim Mangan who shared some guidance and best practices on deploying App-V with Appsense to support user profile virtualization on Windows 7, so let’s hear in their own words!


Virtualizing Office 2010 with App-V 4.6

Nice document from the MSSpringboard Twitter.

Download the document here.

Frequently Asked Questions

The Microsoft Office 2010 Office Deployment Kit for App-V is required for sequencing and deploying Microsoft Office 2010. It enables specific features for 32-bit versions of Microsoft Office 2010, including:

  • Extend virtual Office 2010 usage via improved SharePoint integration to Open, Save, Edit files
  • Find your email items quickly with Outlook’s Fast Search
  • Connect to your inbox using Microsoft Outlook Send To functionality
  • Print your documents directly to OneNote
  • Find contents within your documents using Office Document Indexing
  • Open Web-based calendar items and RSS Feeds in Outlook
  • Perform advanced mail configuration using the Virtual Mail Applet
What benefits does the customer receive when using Office 2010 and App-V together?
Deploying Office 2010 with App-V 4.6 solves the top problems we hear from customers: 

1. Speeds up deployment time

2. Easier migration to the latest version of Office

3. Easier application patching and management

Additional benefits include: App-V packages (including Office 2010) can be sent to client machines running 64-bit operating systems.  App-V virtualized Outlook 2010 search is fast and instantaneous, just like non-virtualized Outlook search.

Can I use Click-to-Run to deploy Office 2010 with App-V to the enterprise?

Click-to-Run is a new delivery mechanism for certain retail Office 2010 SKUs intended for end users.  Click-to-Run Office products are not customizable and cannot be deployed in the enterprise like other App-V packages.  Enterprises interested in deploying Office 2010 via App-V must sequence their own Office 2010 packages.  Sequencing Office 2010 requires use of the Microsoft Office 2010 Deployment Kit for App-V, which enables the licensing platform to work with App-V virtualized Office applications.

What OS versions does the Deployment Kit work with?

The following list outlines the supported operating systems for running the Microsoft Office 2010 Office Deployment Kit for App-V.

Operating System


Service Pack

System Architecture

Windows XP


SP2 or SP3


Windows Vista

Business, Enterprise, or Ultimate

No service pack, SP1, or SP2

x86, x64

Windows 7

Professional, Enterprise, or Ultimate


x86, x64

Windows Server 2003 Remote Desktop Services

Standard Edition, Enterprise Edition, or Datacenter Edition

SP1 or SP2

x86, x64

Windows Server 2008 Remote Desktop Services

Standard, Enterprise, or Datacenter

SP1 or SP2

x86, x64

Windows Server 2008 R2 Remote Desktop Services

Standard, Enterprise, or Datacenter



Does this solve the existing problems with Office 2007 and App-V?

No. This solution does not correct the current limitations when using Office 2007 and App-V together.

Are administrative rights required to install the Deployment Kit? 

Yes. The Deployment Kit is an MSI that must be installed with administrative rights.

Can I deliver/install the Deployment Kit via System Center Configuration Manager or other software delivery tools?

The Deployment Kit can be deployed like any other MSI.  Software delivery tools like System Center Configuration Manager can deliver and install the MSI.

Can I sequence/launch Office 2010 with App-V 4.5x/4.2?

No. Office 2010 is supported only on versions App-V 4.6 and later. We are evaluating the cost of supporting Office 2010 with App-V 4.5, but there are no current plans for support at this time.

Can I deploy Office 2010 to production using App-V?

No.  Office 2010 Deployment Kit is pre-release.  Production deployments are not supported.

Can I upgrade my existing App-V 4.6 Beta Client to the App-V 4.6 Client?
No. The App-V 4.6 Beta Client should be uninstalled before installing the App-V 4.6 Client.

What versions of Office 2010 require use of the Deployment Kit when deployed with App-V?

All. The Deployment Kit serves two purposes: to enable Office 2010 licensing to work for virtualized Office and to enable certain integration features. Please note that all versions of Office 2010 require the Deployment Kit for the licensing components, but the integration features are optional and only supported for 32-bit versions of Office.

Which Office 2010 Beta products can I sequence and deploy with App-V?

The following Office 2010 Beta products may be deployed with App-V:

· Office Professional Plus 2010 Beta

· Office Visio 2010 Beta

· Office Project 2010 Beta

Will I need to redeploy the Deployment Kit when App-V and Office final versions are released?

Yes – this is standard procedure. All beta versions should be removed before RTM version is deployed. To re-deploy, make sure to uninstall the Deployment Kit before installing the latest version.

Why does Office 2010 use the new SPP licensing platform?
The Software Protection Platform (SPP) is new for Office 2010 and leverages the same licensing functionality introduced in Windows Vista and included in all versions of Windows 7. SPP is included in, and required for, all Office 2010 client skus and is an important part of the Office anti-piracy strategy.

To learn more about volume activation of Office 2010, here are some useful links:

· Office Volume Licensing:

· Microsoft Office 2010 Activation Guidelines:

· Overview of Volume Activation for Office 2010:

When will Office 2010 be generally available?

Office 2010 will be available in the first half of 2010.

How does the Deployment Kit enable SPP licensing and the virtualization proxies to work?

Certain Office components like the SPP licensing platform or the Outlook Fast Search indexer cannot work when virtualized. These components integrate with local system features and will not function if they stay in the virtual environment. The Deployment Kit installs Office SPP and proxy components to the machine that facilitate communication between the native environment and the virtual environment.

You indicate the SPP Service must be installed on the Sequencer machine. So why doesn’t the Sequencer capture the SPP service so that I don’t have to install it natively?
All technologies physical or virtual require the SPP component to be installed in order to be in compliance with Office 2010 licensing. Virtualized Office 2010 will not self-install the SPP component when sequencing. Hence, the SPP must be installed in order to sequence Office 2010. The Sequencer actually does not care if the SPP service exists or not. The SPP service must also be natively installed on client machines because the licensing activates itself uniquely with the hardware (i.e., the client machine), and hence, requires a native presence on the machine.

Will Office 2010 work when deployed with App-V to both 32-bit and 64-bit Windows?
Yes. The licensing component is supported for both 32-bit and 64-bit Office on any 32-bit and 64-bit operating systems. Hence, Office 2010 will work when deployed to 32-bit or 64-bit. The caveat to remember is that the Office 2010 proxies are supported for 32-bit Office only.

Do I have to use the 4.6 Sequencer to sequence Office 2010?
Yes, Office 2010 will only work with App-V versions 4.6 and greater, including the Sequencer.

Will Office 2010 on App-V work on XP, Vista, and Windows 7?
Yes, this will work on XP, Vista, and Windows 7. We also support Windows 2003 Remote Desktop Services, Windows 2008 Remote Desktop Services, and Windows 2008 R2 Remote Desktop Services.

Will you publish an App-V recipe for how to do this once generally available?
Absolutely. We understand that virtualizing Office 2010 Beta is important so we have designed, created, and tested a recipe to sequence Office 2010 Beta to facilitate virtualizing the product. You can download the recipe from

For normal MSI installations of Office 2010 Beta volume-license products, I need to have a Key Management Service (KMS) or Multiple Activation Key (MAK) volume activation solution. Does deploying Office 2010 Beta with App-V bypass these requirements?

No. Licensing for either MSI-deployed Office or App-V-deployed Office would require a MAK key(s) or activation against a KMS server. For more information, see

Is the Deployment Kit only to be used with App-V?

The Microsoft Office 2010 Deployment Kit for App-V is designed for App-V.


Automating Windows 7 Installation for Desktop and VDI Environments

Full Article and download is linked here.

Installing Windows 7 isn’t just about migrations. It’s about daily management. It’s about rapid deployment to fix problems. It’s about provisioning virtual desktops in a VDI infrastructure. With today’s technologies for user virtualization and application virtualization, fixing some IT problems can be fastest accomplished by simply rebuilding the computer. For all of these reasons, the outwardly simple process of installing Windows grows to become a much more critical activity than ever before. Installing Windows through automated means is even more important. That’s why this book exists. While installing Windows the manual way requires as few as seven clicks and a bit of time, fully automating its installation requires quite a bit more effort. You need a project plan to get you started and a cookbook of step-by-step solutions to finish the job.

In Automating Windows 7 Installation for Desktop and VDI Environments, you’ll deep dive into the steps required to automate Windows 7 installation. But you won’t stop there. You’ll dig deep into the ways in which that automated installation will fundamentally change how you do IT. You’ll learn exactly how to automate Windows for an OS migration project, whether from Windows XP or Windows Vista. You’ll discover the steps to wrap your automated installation into a VDI infrastructure, enabling virtual desktops to be provisioned automatically and on-demand. You’ll learn the tips and tricks for layering the Windows OS, enabling you to fix common IT problems by simply rebuilding the user’s computer – all while maintaining their applications and profile information and without needing to resort to roaming profiles.

Keep this book handy. You will find yourself turning back to it again and again as you fully automate one of the most time-consuming parts of your job: Windows 7 Installation.