Hi,

I downloaded both VMs and, after the big download, I got it converted to VMWare format using the evaluation version of WinImage. You have to be VERY patient, since the conversion process takes so much time.
But I was disapointed to see that you cannot just go and use it. There is a lot of configuration that you have to do in order to get this working, which is (for a non pro/guru SysAdmin guy like me) painful at best.
There are no documents that explain how to browse this even locally (from the VM host) from the PC where you install the VM.
Thanks to the spirits and some magic happening when you have a SysAdmin friend, there was a change to make to the DNS on the VM itself and also on the VM host (in the hosts file). After doing these changes you are only able to browse the different domains in the VM (itweb.contoso.com, hrweb.contoso.com, etc.).
BUT.... here is the pretty bad part, you ALSO need the second VM (!!!!) because it has all the user accounts in there.

This is just so painful and I really do not understand the move in having this inside another VM.
Maybe it was for performance reasons ? I will never know because I am just an analyst/developer and not an Admin....
but it just makes it very hard for developers or business users who want to try the information worker VM "as-is"

I hope this can help someone because I lost so much time making this work.
If you want to know exactly what I changed drop me an email and I will gladly share the (painful) experience I just had.

Regards

JL, Montreal - Canada

The user accounts are in an AD domain controller running on image A, the use of image B is only required if you want the Exchange functionality.

You shouldnt need to touch DNS, all the sites are running on 192.168.150.1 which is the IP address of the network card on the VM. The DNS on image A has the site names configured to reflect this.

If you import into Hyper-V - it just works.