Using a Task Sequence to Build a MED-V SOE

After spending some time building and rebuilding a SOE to be used with MED-V  I have decided to create a Task Sequence in SCCM to build a MED-V SOE.

The only manual step is running sysprep. So let's have a look what we need in the Task Sequence.

I'm using a MDT TS but you could do it using a SCCM TS as well.

A few specifications are required in the Task Sequence:

Join Workgroup

Product Key
Do not specify an Administrator password.

WSUS Server (if you want to apply the updates during the task sequence)
You can specify the WSUS Server in a variable, in the collection settings or in a CustomSettings.ini file.

Customize the image the way you want using the unattend.txt

With the SCCM client you can deploy applications to the workspace on demand.

Now a few packages are required:

Integration Features - msiexec /i IntegrationComponents.msi /qn
.NET Framework 3.5 SP1 - dotnetfx35.exe /q /norestart
Update to the .NET Framework - NDP35SP1-KB958484-x86.exe /quiet /norestart
Hotfix to enable RemoteApp - KB961742-v3.exe /quiet /norestart
Copy the sysprep files including the sysprep.inf file customized for MED-V and the i386 folder (you can find instructions about that here.)

I also disable the firewall, install an anti-virus and install all updates.

After you deploy it just run sysprep and the VHD is ready to be used within a MED-V workspace.

More information on how to build the workspace here.