One of the questions I get the most is how exactly do you create a Microsoft Office SharePoint Server 2007 (MOSS) development environment and what software should be used / included. Since I usually create a new environment for every client, I get a lot of practice at it and I thought I’d document the process. I’ve included screenshots for every touch point in the SQL install and will do the same for the following Parts. You can click on the thumbnails to view a larger version. I assume no prior knowledge of SQL, MOSS, or Visual Studio in these tutorials. If anything I’ve noticed out there is most tutorials assume product familiarity. This will help novices as well. 🙂
Disclaimer: This process can be followed loosely for a production build, however I would advise further evaluation of the farm architecture and accounts that are used. MOSS isn’t a product I would recommend standing up in production unless you know what you’re doing. In this case RTFM doesn’t really provide enough information. I would suggest training, or reading a compendium of books / blogs on the content because every production deployment is different.
The environment that I am building will consist of 2 servers, which can be and are virtualized in this case using VMware Workstation. The first server is a domain controller, Active Directory, and the second server will host SQL Server, MOSS, and Visual Studio. Building the domain controller and the VMware Workstation configuration are beyond the scope of this document, but I did create another post about building out a domain controller. MOSS is almost never deployed without being on a domain, therefore I’d advise always having a DC running to simulate a production deployment. For the MOSS Server, I would also advise installing all software to a separate data drive, or at least a separate partition on your main drive. Don’t risk filling up the OS’s drive / partition.
Prework for Part I:
On your domain controller, using Active Directory Users and Computers, create an OU titled ‘Service Accounts’. Creating a separate OU will allow you to manage policy separately from the rest of the domain if necessary. Inside the OU, create 2 user accounts, ‘sqlAdmin’ and ‘mossFarmAdmin’. You can actually name these accounts whatever you like. When setting the password, be sure to uncheck ‘User must change password’, and check ‘User cannot change password’ and ‘Password Never Expires’.
I suggest using the SQL Developer or Enterprise Edition (if you have an MSDN license) so that you can install SQL’s full set of features. You can then use this development environment for things beyond the scope of MOSS.
Log onto the MOSS server and install IIS and .NET Framework 2.0. Do not bother looking for updates for the .NET framework because we’ll be running the 3.5 installer between the SQL installation and the MOSS installation. Why not install 3.5 straight away, you ask? 2.0 is on the Windows Server 2003 R2 media, which will make your download smaller / faster for the 3.5 Framework. That’s the only reason… I don’t like to wait. 😉
Insert your SQL media and you should get the autorun. Click on ‘Server Controls, Tools, and Books Online‘ under the Install header:
On the next screen, read (>.<) and accept the license agreement and click next.
You’ll see an installing prerequisites screen (which may be different than the one below). When it’s completed, click Next.
On the ‘Welcome to the Microsoft SQL Server Installation Wizard’ page, click next.
The next screen runs through a checklist of requirements. In my case, there were no deficiencies to correct. If you run into any, you should correct them and rerun the installation wizard. If there are no deficiencies, click next.
On the Registration information page, enter your name, company, and license key if required, and click next. The information is not sent to Microsoft so you don’t have to worry about whether the information matches your license agreement.
For this installation, on the ‘Components to install’ page, considering this is a development environment that can be reused for various projects, select all the checkboxes, then click on Advanced.
Click on the dropdown next to ‘Documentation and Samples’ and select ‘This entire feature will be installed to local drive’. Note the installation path is on the ‘C’ drive. Click the Browse button.
Change the installation drive letter to your data drive, ‘L’ in my case, while keeping the rest of the path intact. Click on OK.
Back on the Feature Selection screen, click Next.
On the Instance Name screen, confirm that the Default instance radio button is highlighted and click Next.
On the Service Account screen, fill in your service account information that you created in the PreWork section of this document for the ‘sqlAdmin‘ account. Then click Next.
On the Authentication Mode screen, confirm that Windows Authentication Mode is selected and click Next. Then can always be changed at a later date if you determine that you need to enable Mixed Mode.
On the Collation Settings page, leave the default settings and click Next.
On the Report Server Installation Options screen, confirm that Install the default configuration is selected and then click on Details.
On the Report Server Installation Information screen, copy the information to the clipboard (highlight it and press CTRL-C) and paste that information into a notepad document that you can save to your desktop. Then click Close.
Back to the Report Server Installation Options screen, click Next.
On the Error and Usage Report settings screen, I make sure both checkboxes on the left are unchecked and click Next. As a developer, you’re likely going to generate errors very often and usage is going to not be information that Microsoft is interested in, so I don’t even wonder whether to report it or not. My 2 cents on that.
This is your last chance to make changes to your configuration, so think a moment before continuing. On the Ready to Install screen, review what you’re installing and click Next.
Next you’ll have a long wait (depending on your hardware), while the SQL Server installer conducts it’s business on your system. Go get some coffee if it’s the AM, a beer or glass of wine if it’s the PM, call your buddies and tell them about this great article, check your email, or anything else. ‘A watched pot never boils’ – old school, ‘An installer never finishes while being observed’ – new school. :) Either way, this part takes a while.
When the installer finishes, and hopefully you didn’t watch it all, the next button will be click-able. Click on Next.
On the Completing Microsoft SQL Server 2005 Setup screen, you can review your setup, or just click Finish.
Congratulations! You just finished setting up SQL Server, one third of your development environment. Now you can move on and install .NET framework 3.5 if you like, or wait for the next blog entry, which will be soon, and I’d be more than happy to walk you through it. 🙂