Early this week (Monday), I had tweeted that SharePoint 2010 Beta and Exchange 2010 Download was available for Microsoft Partners – SDPS. If you are following me on http://twitter.com/alpesh you know about it! This download has now been made available for everyone.

To quote from the download page:


This download contains a two Virtual Machine set for evaluating and demonstrating Office 2010 and SharePoint 2010.

Virtual machine “a” contains the following pre-configured software:

1. Windows Server 2008 SP2 Standard Edition x64, running as an Active Directory Domain Controller for the “CONTOSO.COM” domain with DNS and WINS

2. Microsoft SQL Server 2008 SP2 Enterprise Edition with Analysis, Notification, and Reporting Services

3. Microsoft Office Communication Server 2007 R2

4. Visual Studio 2010 Beta 2 Ultimate Edition

5. Microsoft SharePoint Server 2010 Enterprise Edition Beta 2

6. Microsoft Office Web Applications Beta 2

7. FAST Search for SharePoint 2010 Beta 2

8. Microsoft Project Server 2010 Beta 2

9. Microsoft Office 2010 Beta 2

10. Microsoft Office Communicator 2007 R2

Virtual machine “b” contains the following pre-configured software:

1. Windows Server 2008 R2 Standard Evaluation Edition x64, joined to the “CONTOSO.COM” domain

2. Microsoft Exchange Server 2010 Active directory has been preconfigured over 200 “demo” users with metadata in an organizational structure.

All of these user profiles have been imported and indexed for search within SharePoint Server 2010, with “contoso\administrator” granted administrator permissions.

SharePoint Server 2010 has been configured in a “Complete” farm using Kerberos authentication and the default SQL Server 2008 instance for data, and has a site collection created using the Team Site template at http://intranet.contoso.com/ and a FAST Search Center at http://intranet.contoso.com/search/.

Performance Considerations

1. If possible, unpack and run the VM image on a separate, fast hard drive (7200 RPM or better) from the operating system of the host machine. If this is being done on a laptop, a second internal drive or external eSATA drive works best, though USB 2.0 (make sure it’s 2.0, 1.1 is too slow) or Firewire is acceptable.

For absolute best performance use a second internal SSD drive.



a. Start Hyper-V Manager from Control Panel -> Administrative Tools

b. Confirm that the local host machine appears in the Hyper-V Manager list and select it if not already done

c. Under Actions, click Virtual Network Manager…

d. Confirm that you have created an Internal virtual network named “Internal”. Internal networks limit connectivity to only VMs and the host.

If a suitable not, create one now using the following steps:

i. Click on Virtual Network Manager in the Actions pane

ii. Choose New virtual network in the Virtual Networks pane

iii. Choose Internal from the type list and click Add

iv. Enter a name of Internal and click OK v. Start menu -> right-click Network –> Properties

vi. Click Change adapter settings

vii. Find the adapter with a description of Internal, right-click and choose Properties

viii. Double-click on Internet Protocol Version 4 and enter the following values: 1. IP address: 2. Subnet mask: 3. Default gateway: (leave blank) 4. Preferred DNS server:

ix. Click OK

e. Close the Virtual Network Manager dialog.

a. Under Actions, click Import Virtual Machine…

b. Use the Browse button to select the folder where the virtual machine package was extracted. Do not check

c. Click Import and wait for the Import to complete – the import status will appear in the Operations column

d. Select the newly imported virtual machine and click Settings in the right pane of the Hyper-V Manager

e. Confirm (and correct if necessary) that the Network Adapter is connected to the Internal network from step 1d.

f. Close the virtual machine Settings dialog.


Download 2010 Information Worker Demonstration Virtual Machine (Beta)