Steps to Install SharePoint 2007

I did a MOSS 2007 install last week at  Ashish office and I Just want to do a recap post for all of you guys on the same as most of the guys become little more mumbling when it come to MOSS2007.

I’ve got two servers running Win 2K3 R2 in my domain.

To install IIS, you need the i386 folder off of the Server 2K3 installation disc.

I install MOSS on one and on the other, I run the Office SharePoint Server install and, of course I get the error:

Setup is unable to proceed due to the following error(s):
-This product requres .Net Framework 2.0 to install.
-This product requires at least Windows Workflow Foundation version 3.0.4203.2, which is part of the .Net Framework 3.0
-This product requires ASP.NET v2.0 to be set to ‘Allow’ in the list of Internet Information Services (IIS) Web Server Extensions.  If it is not available in the list, re-install ASP.NET v2.0.
Correct the issue(s) lsited above and re-run setup.

Now, I have to apologize to your people because I know I had covered each of these issues in detail, but we’re still looking to recover some of my old posts and, since you know robots have less than perfect memory, this is about all I can recall:

The .Net 2.0 install requirement can be stupid in that it can be installed but you have to uninstall it and reinstall it.

The WWF install is essentially a .Net 3.0 install.

Once you take care of those issues, the “Allow” configuration is probably resolved as well.

So, let’s see what we have to do…

I’m a little fuzzy on the difference between the .Net Framework 2.0 and ASP.Net v2.0 but I go to here:

http://www.microsoft.com/downloads/details.aspx?FamilyID=0856EACB-4362-4B0D-8EDD-AAB15C5E04F5&displaylang=en

And download dotnetfx.exe and run it.

“Set up is continuing the install.”  That’s great.

That’s almost as good as the dialog box in the SQL Server 2005 install that says “Setup is proceeding to continue with the install.”

The WWF install is really a .Net 3.0 install which you can get from here:

http://www.microsoft.com/downloads/details.aspx?FamilyId=10CC340B-F857-4A14-83F5-25634C3BF043&displaylang=en

So when those installs are completed, I run setup again, enter my product key and click next.

I tell it I want a complete install as opposed to a web-front end or stand-alone install.  It shows me an installation progress bar and it moves slowly to the left.

Then we get the success dialog box with a check mark to run the Configuration Wizard now.

The wizard fires up…

I dot the “No, I want to create a new farm.” option.

I specified my database server and my service account for connecting to the database server.  I went to my database server and created the login for my service account and gave it dbcreator and securityadmin roles.

I specified my Central Admin port number to my favorite: 63696 (use your number keypad) and NTLM authentication.

Reviewed the settings and clicked Next.

Now, it’s counting nine tasks with the little green floater moving repeatedly from left to right.

1, 2…, 3, 4, 5, 6…, 7.., 8, 9

Configuration Successful! and click Finish.

The Central Administration page loads.

So we’ve got these administrative tasks in a list.

Task One: Read the tasks – kind of like that old elementary school trick where they tell you to read all the instructions before you start.  It says to delete the item from the list when you’re done but I’ll just mark it completed.

Task Two: Add Servers to Farm – This is done.

Task Three: Assign Services to Servers – This one has an action link.  I click on the link and it takes me to the page in Operations.  Now I’m on a medium farm so that option is dotted and a set of services appear in the table below like a connectable web part. To see all the services, you have to dot the Custom option or select the All view.

You have to start the Document Conversions Load Balance Service first, because you need a load balancer server to run the launcher service.  The Load Balancer service starts and then you can start the Document Conversion service where you’ll select your Load Balancer server.  It chooses port 8082 for whatever reason.

I start the Excel Calculator.

I start MOSS search checking the options to Use this server for indexing content and Use this server for serving search queries.  I drop my own eMail address in the eMail address field for some reason and use my service account for crawling and set performance to Maximum

Finally, I start WSS Seach adding my service account and password in the service and content accounts and leave the rest unchanged.  All my services are started on this server.  I edit the task item and mark it completed.

Task Four: Configure Server Farm’s Share Services – This one has an action link to Applications Management.  This page has been trouble in the past so I’m a little trepidatious.  The first issue is the ShareService Provider and it needs a web application so I click Create a new web application. 

Now this page wants to create SharePoint – 80 on port 80, create a matching folder in the Virtual Servers folder and a new application pool and restart IIS.  I’ve been right here before and didn’t want to run SharedServices through port 80. But, I’m click OK all the same.  Now, I think this will just provision an IIS web site.  I do not have to use it for SharedServices.

So, this is taking forever.

Finally, it resets and it’s taking me back to the New Shared Service Provider page where my SharePoint – 80 web application is selected.  I’m going to create another web application.

Again, we’re taking forever.

Advertisements

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s