Ok, here we go with part 2 of this tutorial. The part where we actually do the MOSS installation. If you missed part 1, you can find it here: Tutorial: Creating A MOSS Development Environment Part I – SQL Installation. If you’re back after doing part 1 and are ready for part 2, "Welcome back!" So without any further ado and hoopla, I’m just going to copy and past the Disclaimer and The Environments from part one for your perusal, and jump right into the MOSS Installation.
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 if you have questions, post them in comments and I will try to answer them as best I can. 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.
I would advise having the installation bits (media via ISO, CD, DVD, etc.) for the Enterprise Edition as well as the Enterprise Edition key. Installing this version will give you all of the features that a client (internal or external, they are all clients) may be interested in using, and therefore the ability to develop against it. If you only have the media and key for the Standard Edition, don’t worry, it’s very easy to upgrade the key after the fact using SharePoint Central Administration. I would also advise downloading the latest media from MSDN or acquiring media that has the service pack (1 currently) included. This saves some work.
I hope you’re ready to get your hands dirty, because this is the hard part. <kidding> Again, I’ll write the instructions and follow them up with a screenshot of the touch points.
So we’ve just finished installing SQL Server. We’re going to need to do some SQL Server configuration, install the .NET Framework 3.5, and then finally move on to installing MOSS.
Go to Start > All Programs > Microsoft SQL Server 2005 > SQL Server Management Studio.
When SQL Server Management Studio opens, on the Connect to Server window, accept the default entries and click Connect.
When you’ve connected to the server, in the left pane of the window, click the + sign next to Security to expand the node and do the same for Logins. Your screen should look similar to the one attached below.
Highlight the Logins folder in the left pane, and the right pane should change to show the SQL Server logins. Right click in the open area of the right pane, and select New Login.
In the Login name box, enter the credentials of the account that you are planning to use as the MOSS farm administrator in the format <domainName><userName>. If you did part I of the tutorial, it’s the account that we created during the Prework, titled mossFarmAdmin.
In the select a page section of the Login – New window, click on Server Roles. In the right pane, click on dbcreator, securityadmin, and serveradmin. These are the permissions that MOSS farm administrator account needs to manage the MOSS databases that will be stored in SQL Server.
After clicking OK, the new account should appear in the list on the right. Keep in mind that we did not create a new windows account in these steps, we just added a windows account to SQL server’s user structure.
Moving right along, now we’ll close the SQL Server Management Studio. Download the Microsoft .NET Framework 3.5 Redistributable, and start the installer. OK, I don’t have screenshots for closing SQL MS or searching google and downloading the installer. Nobody’s perfect. :P.
When the .NET Framework 3.5 Setup window appears, read the license agreement >.<, select the radio button marked ‘I have read and ACCEPT the terms of the license agreement’, and click on Install.
You’ll get a loading window similar to the one below. This will likely take a few minutes, so time for another coffee run, smoke, drink, or whatever else you do besides watch an installer run. AND NO, I’m in no way condoning any of the aforementioned activities. When the installer finishes, click on Exit. You’ll also, likely need to restart your computer.
After your system reboots, if you had to reboot, insert your media and autorun should bring up the MOSS installer. Enter your product key, again – preferably the Enterprise key, but not necessary, and click Continue. I’d share the product key but that would be a direct violation of the license agreement that I’ve entered into with Microsoft, well my company has at least, so I will not be providing that information. Apologies.
On the next screen, click the checkbox to accept the licensing terms, after reading them >.<, and click on Continue. You, of course, realize that if the devil wanted to take all the souls of mankind, all that would have to be done was for him/her to create some software, and include the soul agreement inside the licensing agreement. (O.O). But I digress… moving along…
VERY IMPORTANT: On the next screen, make certain that you choose Advanced. This allows for the complete installation of the MOSS components.
On the next screen, make sure that Complete – Install all components is selected on the Server Type tab.
Click on the File Location tab and adjust your installation paths as necessary. As I advised in part 1 of this tutorial, I always seek to install all products besides the OS to a data drive or separate partition. It’s good practice and will help to keep your OS safe.
Click on the Feedback pane and decide how you want to handle it. Then click on Install Now.
Now you’ve got another waiting screen. Think you’ve spend a lot of time at waiting screens so far? Wait until we install VS.NET. hahaha. Anyway…
After the installer completes, choose to Run the SharePoint Products and Technologies Configuration Wizard by checking the checkbox and clicking on Close.
Take a quick break again, stretch your legs, but don’t worry, we’re on the home stretch for this part of the series. Almost done.
When the SharePoint Products and Technologies Configuration Wizard starts, click Next.
Click Yes when warned that some services will need to be reset or restarted during installation.
On the screen titled, Connect to a server farm, choose No, I want to create a new server farm. Click Next.
The next page, Specify Configuration Database Settings requires you to enter your database server name (use the netbios name, not localhost), the database name which you can leave as default, the user name of the account that you granted access to earlier in this tutorial, ie. <domain>mossFarmAdmin, and that accounts password. After entering this information, click Next.
On the page marked, Configure SharePoint Central Administration Web Application, check the Specify port number box and use something easy to remember. Personally, I typically use: 12345. Confirm that NTLM is selected and click Next.
Again, you’ve reached a point where you’re at your last opportunity to make changes before continuing on with this installation. Review the settings listed on the screen and when you’re ready, click Next.
Coffee, Beer, Wine, Water, Exercise, Call a loved one, Prank call an unloved one, or something else creative to pass the time. Unless it’s a really cool installer, which most of them aren’t, it’s really not worth watching.
Finally you’ll arrive at the Configuration Successful page where your settings are listed again. No need to recall the settings, as you can always run SharePoint Central Administration from the start menu. (Start > All Programs > Microsoft Office Server > SharePoint 3.0 Central Administration). Click Finish, and your Central Administration Site should open.
Again, I hope you’ve learned something here, or just reviewed what you already know. If not and you’re all the way down here, I’d hope that you’d leave a comment with suggestions.
During the next part we’ll actually go about configuring a basic MOSS portal for development on, and after that, we’ll be standing up VS.NET and other associated development software.