I had been trying to configure and install SharePoint 2010 VHD which is available online on my newly upgraded (matter of fact, assembled from scratch) machine. Configuration of the machine is as under.
- AMD Phenom 9750 Quad-Core Processor 2.40 GHz
- 8.00 GB RAM
- 1 TB 7600 RPM Hard Disk
- Windows 7 Professional OS
MOSS 2007 VHD would run just fine on Sun Virtual Box, without any problems. But, the new SharePoint 2010 VHD would not. I guess some kind of driver missing on Windows 2008 R2 Server provided with it. This could be because of the new mobo I installed myself. As soon as this Virtual Machine is started, in about couple of minutes, CPU goes up to 100% and it is impossible even to wait for complete shutdown.
So, enough of virtual machine setup efforts, I decided to build my own box including Windows 2008 Enterprise Server R2. So here is the sequence of steps I followed.
- Install Windows 2008 Enterprise Server R2
- Update with patches using Windows Update
- Install Microsoft SQL Server 2008 R2 (64-bit)
- Run Windows Update to make sure PC is up to date.
- Start SharePoint 2010 installation process.
- After prerequisites are installed machine needs to be rebooted. (including Microsoft "Geneva" Framework Runtime)
- Start SharePoint 2010 installation process again with product key (BV7VC-RMR6B-26P6Y-BTQDG-DX2KQ)
- The above product key only works for internal sites version of SharePoint 2010.
- If we run into the following error while creating Sample data (step 8), we need to install this hot fix.
"An exception of type Microsoft.Office.Server.UserProfiles.UserProfileException was thrown. Additional exception information: Unrecognized attribute 'allowInsecureTransport'. Note that attribute names are case-sensitive. (F:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\WebClients\Profile\client.config line 56)"
- Start SharePoint 2010 Configuration Wizard again. This time it should be successful.
Post Installation Configuration
Configure the following using Central Administration
- Configure usage and health data collection. Usage data collection can be configured using Central Administration as well as Power Shell script. Health data collection configuration can only be set using Central Admin.
- Configure diagnostic logging if required. In most cases, accepting default values will be sufficient. By default, diagnostic logs are stored in \14\LOGS
- Configure Incoming/ Outgoing mails as necessary
- Configure mobile account so that SharePoint can send SMS messages to mobile phones
- Configure Search Settings
- Configure and use Exchange connector so that we can create a crawl rule and add a content source for crawling Microsoft Exchange Server public folders.