Building a single server Project Server 2010 with SQL Server for use as a development environment. Part 1

Part 1 Setting up SQL Server for a Project Server 2010
This article describes how to install and configure Microsoft SQL Server 2008 R2 for use with Project Server 2010. Project Server 2010 requires one of the following versions of SQL Server:
   Microsoft SQL Server 2008 with Service Pack 1 (SP1) and Cumulative Update 2
   Microsoft SQL Server 2008 R2

   Microsoft SQL Server 2005 SP3 with Cumulative update package 3 for SQL Server 2005 Service Pack 3

This article describes installing and configuring SQL Server 2008 R2. 

Configure a local administrator
It is recommended to install SQL Server 2008 R2 while logged on with the SQL Server administrator domain account (SDREDDeveloper). Prior to doing this, you must add this account to the local Administrators group on the virtual machine.
Log on to the virtual machine with the domain administrator account (SDREDAdministrator) and perform the following procedure to add the SDREDDeveloper account to the local Administrators group.
To add a local administrator
1.Log on to the virtual machine where you want to install SQL Server as a domain administrator.
2.Click Start, click Administrative tools, and then click Computer Management.
3.Expand Local Users and Groups, and then click Groups.
4.In the right pane, right-click Administrators, and then click Properties.
5.Click Add.
6.Type the name of the SQL Server administrator account (SDREDDeveloper), and then click OK.
7.Click OK.
8.Log off the virtual machine.
To perform the remaining procedures in this article, log on to virtual machine with the SDREDDeveloper account.
Install SQL Server 2008
Perform the following procedure to install SQL Server 2008 R2 on the virtual machine.
To install SQL Server 2008
1.Attach the SQL Server 2008 R2 DVD or image file to the virtual machine DVD drive.
2.Log on to the virtual machine where you want to install SQL Server as the SQL Server administrator.
3.On the SQL Server DVD, double-click setup.exe
4. The first step is to install SQL Server 2008 R2. SQL Server 2008 R2 requires the NET Framework version 3.5. If the .NET Framework 3.5 is currently not installed, you must install it or enable it as a feature in Windows Server 2008 before you continue.
5.If a compatibility warning is displayed, click Run program.
6. In the SQL Server Installation Center, in the left pane, click Installation.
7.In the right pane, click New SQL Server stand-alone installation or add features to an existing installation.
8.If a compatibility warning is displayed, click Run program.
9.On the Setup Support Rules page, click OK.
10.         On the Product Key page, type your product key, and then click Next.
11.         On the License Terms page, review the license agreement and, if you agree, select the I accept the license terms check box, and then click Next.
12.         On the Setup Support Files page, click Install.
13.         On the Setup Support Rules page, click Next.
14.         On the Setup Role click on the SQL Server Feature Installation.
15.         On the Feature Selection page, select the following check boxes:
                     Database Engine Services
                     Analysis Services
                     Reporting Services
                     Management Tools – Complete
16.         Click Next.
17.         On the Installation Rules Click Next.
18.         On the Instance Configuration page, leave the Default instance option selected or name your own instance, and then click Next. (Because this development VM will be supporting various production environments I prefer to have an instance for each production environment I’ll be supporting)
19.         On the Disk Space Requirements page, click Next.
20.         On the Database Engine Configuration page, select the Mixed Mode option, and type and confirm a password for the built-in SQL Server administrator account.
21.         Click Add Current User to add the current user account as a SQL Server administrator.
22.         On the Data Directories Tab, enter the database directories or leave the defaults
23.         Click Next.
24.         On the Analysis Services Configuration page, click Add Current User to add the current user account as an Analysis Services administrator.
25.         Click Next.
26.         On the Reporting Services Configuration page, select the Install the SharePoint integrated mode default configuration option, and then click Next.
27.         On the Error and Usage Reporting page, leave the default values and then click Next.
28.         On the Installation Rules page, click Next.
29.         On the Ready to Install page, click Install.
30.         When the setup process is complete, click Next.
On the Complete page, click Close.

Microsoft Project 2010 Demonstration and Evaluation Installation Pack on VMware with a Bridged Network Adaptor


If you have installed the 2010 Information Worker Demonstration and Evaluation Virtual Machine on VMware and want to add the Project 2010 Demonstration and Evaluation Pack.  The installation wizard is simple to follow and generally works well.
There are two things you must due to ensure the installation goes well.  First thing is that you must activate the VM or you may get an ‘Unexpected Error’.
The instructions recommend installing a second network adaptor but what I did was simply to add an alternate DNS to the existing one. It appeared to me that the only purpose of the second adaptor was for the outbound HTTP traffic during the activation of the VM, therefore simply adding one of my Internet Providers external DNS was sufficient for this purpose. You can find your own provider’s DNS from the configuration settings of your router.
The second thing to keep in mind is the network configuration.  The Information Worker VM is configured with an Internal Virtual Network and expects the address of the DEMO2010A VM to be
I like to set my network in Bridged (Autodetect) mode to more closely resemble my production environment and therefore required modifications to the DNS of the DEMO2010-a VM
If you notice right after the installation of the Information Worker VM the Forward Lookup Zones have the entries for the DEMO2010-a and DEMO2010-b as and
You will find corresponding entries in the GC records on the DNS.
Since I had modified the IP settings of both VMs machines I need to update the GC, Forward Lookup and Backward Lookup Zones accordingly.
After downloading  the Project2010Project2010DemoPack.iso and mounting the volume you will have the following files. Copy them into a temporary folder.
Mount the Project2010DemoPack disk image and the run the Projct2010DemoPack in the AutoPlay dialog window.
Click on the Install button in the Welcome Screen.
06project 2010_demonstration_installer_pack.png
Allow it to unpack and execute the installation.
07project 2010_demonstration_installation.png
The PowerShell of the installation wizard will use the entries in the DNS to set up the
If you did not update your GC, Forward Lookup and Backward Lookup records to your Bridged IP addresses then the installation wizard will fail when it tries to connect to because it will be looking for it in the address.
and when you try to connect to PWA you will not be able to find the page
When this happens simple update your DNS entries with the IP addresses of the machine.  I have set up both of my DEMO2010 VMs to have static addresses
I removed the GC records and added the new ones with the designated IP addresses.
You need to also update the ForwardLookup and Reverse Lookup Zones in the DNS
After making these updates to the DNS I ran the installation wizard again and the  Project Server 2010 PWA Home Page came up right this time.
For additional SharePoint and Project Server related articles visit my website at


Converting the 2010 Information Worker Demonstration and Evaluation Virtual Machine into a VMWare Virtual Machine.

You will need StarWind V2V converter and a Windows 7 Repair CD in addition to the 2010 Information Worker Demonstration and Evaluation Virtual Machine.

Download the 2010 Information Worker VM from the Microsoft Download Center and unpack the rar files into a folder.

2010 Information Worker Files.png

First thing to do is to convert the virtual image from a vhd into vmx. StarWind Software V2V Image Converter is a free utility that will do this conversion.

StarWind V2V Image Converter.png

Click Next to begin the conversion

StarWind V2V Source Image Dialog Window.png

Select the VHD to convert

Information Worker Files.png

StarWind V2V Source Image.png

Select VMWare growable image otherwise. The pre-Allocated image option will create a fixed size 127G

StarWind V2V Growable Image.png

Select SCSI Disk Type

StarWind V2V SCSI Type.png

Select the output destination for the VMX virtual drive.

StarWind Image Converter Destination.png

Depending on the hardware the conversion will take several minutes

StarWind V2V Conversion in Progress.png

At the end of the process the VMWare virtual disk will be created.

2010 Information Worker VMDK.png

Create a new VMWare virtual machine.  For this example Workstation 6.5 is being used but Fusion 3.0 Workstation 7.0 and VMWare Server has been used as well

VMWare New VM Wizard.png

VMWare VM Hardware Compatibility.png

Do not install an operating system on the new VMWare Virtual Machine

VMWare Guest Operating System Installation.png

Choose Windows Server 2008 x64 Edition.

VMWare Windows 2008 Guest.png

Give your virtual machine a name and location where to store it.

Select the number of processors.

VMWare Processor Configuration.png

Chose the amount of memory you want to assign to the new VMWare Virtual Machine. Anywhere from 2G to a max of 8G.

VMWare New Machine Memory Configuration.png

VMWare New VM Network Type.png

Choose SCSI Adapter

VMWare new VM IO Adapter.png

When selecting a disk choose the existing virtual disk option.

VMWare New VM Select Disk.png

Browse to to the Information Worker Virtual machine. There are two of them 2010-7a and 20107-7b.  This procedure will need to be executed for each one of them.

VMWare new VM Browse Existing Disk Wizard.png

Select the Virtual Hard Drive to be converted into a VMWare Virtual Machine.

VMWare New VM Existing Disk.png

Either  format will work.

VMWorkstation conversion to new format.png

Any additional hardware configuration settings can be made here if needed, otherwise finish the creation of the new VMWare Virtual Machine.

VMWare New VM Confirmation.png

Do not start the new Virtual Machine just yet. We need to make some registry modifications otherwise it will freeze on boot.

I normally go to File -> Boot from BIOS and disable the serial and parallel ports for performance purposes. I also change the booting option to first boot from CD. This makes it easier to boot into the Windows 7 repair disk  CD so that I can load the registry and make the necessary change.

VMWare Windows 2008 Server Guest.png

VMWare VM BIOS Survival Port.png

I like to disable Diskette A and B on my Virtual Machines.

VMWare VM Bios Legacy Diskettes.png

VMWare VM Bios Legacy Diskettes Disabled.png

I also disable the Serial Ports and the floppy disk controller.

VMWare VM Bios Floppy disk controller Disabled.png

Press F10 and save the configuration, but before you exit make sure the Windows 7 Repair CD is on your DVD drive otherwise the VMWare machine will want to start from the hard drive and will get a 7B BSOD

VMWare VM Save BIOS.png

Exit the BIOS setup and allow your new VMWare  virtual machine to boot from the CD.

VMWare VM Bios Boot Order.png

When prompted press any key to boot from CD… do not allow it to boot from the hard drive.

VMWare New VM Booting from CD.png

Choose your Windows 7 language.

VMWare New VM Booting from Win7 CD.png

Select your Windows Server 2008 R2 for repairing.

VMWare New VM Recovery Options.png

This screen will just flash for a second since there are nothing to repair at this point and proceed with the ‘Choose a recovery tool’ dialog window.

VMWare Win7 Recovery Disk Setup repair.png

In the System Recovery Options window select Command Prompt

VMWare Win7 System Recovery Options.png

From the DOS prompt launch the registry editor


Select the HKEY Local Machine and click on Menu -> File -> Load Hive

VMWare New VM Registry.png

Navigate to WindowsSystem32 but DO NOT choose the Boot (X:) drive.

That drive belongs to your Windows7.

Select the C:WidowsSystem32 of the Virtual Machine.

VMWare New VM CD Boot Registry.png

VMWare New VM System Registry File.png

In the pop up prompt type p2v

VMWare New VM Load Hive.png

Navigate to ControlSet001/Services/LSI_SAS

VMWare New VM LSI_SAS Key.png

VMWare New VM LSI_SAS Type Key.png

Modify the Type  value to 0

VMWare New VM LSI_SAS Type New Value.png

Go to File -> Unload Hive

VMWare New VM Unload Hive.png

Click on the Yes button to confirm your update.

VMWare New VM Unload Hive Confirmation.png

VMWare New VM Hive Unloaded.png

Close the registry window and close the DOS Window.  The Shut Down.

VMWare New VM Recovery Options 2.png

If you set up your boot order to begin with the DVD you will need to boot into the BIOS again and change it to boot from your Hard Drive now. Otherwise remove the Windows 7 recovery CD and boot normally

2010 Information Worker VMware booting up.png

Hit fn+CTRL+Option+Delete on Mac or Ctrl+Alt+Insert on Windows 7

2010 Information Worker VMware ctr alt del.png

Accept the EULA

2010 Information Worker VMware EULA.png

Enter pass@word1 for password and let the ‘Warmup’ script run before accessing the http:intranet sites.

2010 Information Worker VMware password.png

A restart of the Virtual Machine will be required after the first boot.

2010 Information Worker VMware Restart.png

For related articles visit my website