Steps to installing MOSS 2010 on Windows 2008 R2 running SQL Server 2008 R2

I have just completed a milestone for my organization giving a sneak peak into the new SharePoint 2010. I was able to achieve this on SQL Server 2008 R2 Enterprise Edition running on Windows Server 2008 R2 x64. I faced some very key challenges but with the help of some reference sites and google :) capped with some ingenuity, I was able to persevere and complete this milestone. It is clear that there are no blogs or forums out there that will work you through the entire steps on the platforms I used and time has not been my friend so I wasn't able to capture my entire process but I will include the reference sites to help ease your pain and mine as I outline the steps below:

1. I went straight for the proven virtual platform that works on workstations with 64 bit OS requirements in the name of Vmware 7. I downloaded the trail version and installed it on an already configured windows 2003 server x64 OS Intel box. My company will sure do well to purchase eventually :)
2. The first obvious observation you would encounter is the Vmware installation doesn’t work properly for a common reason. For an Intel box, you are required to enable the VT option (disabled by default) which aids third party virtualized solutions.
3. Enabling VT: The VT option is located in F10 Setup under the following selections:

Security > OS Security > Intel Virtualization Technology (Enable it).

If this doesn't work for your system do feel free to drop a line and would state an alternate option if google hasn't already helped :)

4. Once this is done, restart your system and proceed to configure an x64 OS VM. Install the windows 2008 server R2 which is pretty straight forward.
5. Once you have successfully configured your VM, proceed to install the relevant prerequisites before installing SQL Server 2008 R2. A very helpful post is the famous INSOMNIAC GEEK:

http://insomniacgeek.com/blog/installing-sql-server-2008-on-windows-server-2008-r2/

His post is helpful for two reasons: it works you through the prerequisites and provides screen shots for installing SQL Server 2008. The only observations you would make once the process starts is that the screenshots are quite different for SQL Server 2008 R2. Do not be afraid, common sense which is not really common sometimes will see you through. Trust me!!

6. Please if you choose to run SQL Server 2008 R2, do not install SQL Server Database Engine and the Reporting Server at the same time. Install the Engine first then proceed to Install the Reporting Server using the configuration tools. If you do not heed this my humble advice, you will spend the next few days wondering while your system has refused to proceed beyond a particular stage. I would spare you the details. The Microsoft team is looking into this.
7. Once you have successfully configured SQL Server 2008 R2 with your desired specifications, you can proceed to install MOSS 2010. A very helpful post is that of Marc Chamois: http://mosshowto.blogspot.com/2009/11/installing-sharepoint-2010-windows-2008.html

He killed it!!! If you stick to his experience all through with focus on the MOSS 2010, you will have a smooth ride. The tips I will highlight below are generally must haves which would help through the process:

1. If your VM doesn't connect to the internet for one reason or the other, sure do well to download all the prerequisites for MOSS 2010 and install manually. It works!! If you are not on this boat then I guess your journey was made in heaven.
2. Create a domain account (or just another account depending on your approach) and run the installation with that account. This will eliminate some bottlenecks which you will definitely encounter running the installation with the admin account. Remember to grant the choice account the admin rights.
3. I believe the rest will be driven by common sense which I believe will be in abundance.

I hope this helps. I am off to complete the key configurations which would definitely involve clustering my SQL Server 2008 R2 which is standard practice for my organization and creating a load balanced farm on MOSS 2010. I hope to do a better documentation on my observations and trials. Later…….

Installing Office Communication Server (OCS) 2007 R2 on Windows Server 2008 R2

I have installed OCS on various platforms and i can conclude that some additions or adjustments are just unnecessary.

Have you completed installation of OCS R2 on Windows Server 2008 R2 and realized that you cannot find the Administrator's console for OCS? Funny though but for some reason Microsoft did not think it was neccessary anymore for the snap-ins to be installed automatically.

So to save you your blushes, refer to the image below:

From My Arena

You would have observed by looking to your right that a separate step is required to install the admin tools. Believe me its a cumpolsory step to firing up the system.

Installing MOSS 2007 R2 on Windows Server 2008 R2

Have you had trouble creating a root site after installing MOSS 2007 R2 on Windows Server 2008 R2? Suprisingly i have. My implementation required i setup on Windows Server 2008 R2. The first issue i had to deal with was to upgrade MOSS 2007 realease 1 to release 2 (or what is commonly refered to as slipstream) since MOSS 2007 R1 could not be installed on 2008 Server R2. Refer to http://insomniacgeek.com/blog/how-to-install-moss-on-windows-server-2008-r2/ . The real surprise comes after successfully installing MOSS and you try to create a Sharepoint root site collection. Bang!!! you see a WSS 3.0 site.

I tried googling to confirm if this is a known bug with no much success. I eventually went for the jugular and created a site collection the old way. STSADM. Voolaaa!!! it worked. The root site collection was up and running in no time.

A sample command you can use is :
stsadm -o createsite -url "http://mysite/test" -owneremail "myemail@yahoo.com" -ownername "testdomain\real" -ownerlogin "testdomain\real" -title "Home" -description "A test site"

Remember to change the directory on the command prompt to locate your stsadm.exe.
Have fun!!!