When I go here I get to the Overview and it’s missing suitable line breaks. Maybe it was written in the SharePoint 2007 rich text editor.

So I’m going to reformat it for you here:

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 SP1 + CU2 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.

2. 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.

3. For absolute best performance use a second internal SSD drive.

Passwords for all users in the CONTOSO AD are “pass@word1” (remove quotes) (including the Administrator account).

Then the instructions:

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: 192.168.150.6

2. Subnet mask: 255.255.255.0

3. Default gateway: (leave blank)

4. Preferred DNS server: 192.168.150.1

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.

Now the “4a” machine amounts to an .exe file and 14 .rar files all but one of which is 700 Mb. So if you’re going to dowload them, give yourself some time.

You’re welcome.

-robot

I gotta be honest; I outsourced this server build.

What I did was go to the Dell.com clearance rack and found a refurbished PowerEdge 300 with the Quad-Core Xeon 2.8 gHz, 8 gb RAM and two 250 gb hard drives for less than $1000

I got my tech guy to install Server 2008 R2 x64 and Sql Server 2008 x64.  This software cost me $1750 through my local reseller. The install took a week (I was out of town) and I bought dinner him dinner at The Pit in exchange for the effort. You might think that was a deal but he’s actually a family of four and the BBQ there beat Bobby Flay on the Food Network.

Though the T300 is no longer available but you can find similar deals here on Dell.Com’s Deals space.

So let’s just say I got here under my previously stated budget of $3K. I did not get the cool $150 monitor though I wish I had. Continuing with this honesty thing, can we really have enough flat screen monitors? In many respects, I think the flat-screen, more than just about anything else (besides Flash) made geeks cool. If you disagree, think about what dorks we’d look like staring at those big monster, sterilizer CRTs all day.

So I’ve got this machine and it’s hooked to my router at home. I have static IP DSL through AT&T. On Server 2008, you get this “Initial Configuration Tasks” page where you get links to Configure Networking, Add Roles, and Enable Remote Control.

On networking, I added the machine’s local IP addresses, default gateway and DNS servers to the two connections.

The Add Roles link points to the Add Roles Wizard. This will allow you to check the Application Server, File Services, Hyper-V, and Web Server (IIS) roles that we’ll need. Check them and click through the wizard.

The Enable Remote Desktop link points to the Remote tab of the system properties where you can check allow connections… 

On my router, on the Port Forwarding tab, I point port 3389 to one of the IP addresses. Now, I can access my new server from anywhere on the internet.

The only thing I can’t do is connect to shares on other LAN computers. I’m not running a domain so when I get prompted for user name and password, nothing I enter allows me to connect. These other computers are a mix of XP and Server 2000 and connecting from them to this server seems to work just fine. Frustrating but I’m not sure this is a priority.

So with all this in place, let mess it all up. Stay tuned…

-robot