Steps to Configure a basic MOSS 2007 Farm (RTM)
I have finally gathered all the required resources to build my test server for MOSS 2007 (Microsoft Office SharePoint Server 2007) RTM.
This includes hardware (an HP notebook with 2GB of RAM), software (Windows Server 2003 SP1, SQL Server 2005 SP1 and the RTM release of MOSS 2007) and time :-).
My goal is to set up a complete environment from scratch, including Active Directory, SQL, IIS and MOSS itself, including an SSP.
1) Installing Windows Server 2003 SP1
1a) Installing the Operating System
The first step is to install the Windows Server 2003 SP1 or Windows Server 2003 R2 operating system.
You cannot run this from Windows XP or Windows 2000.
I highly recommend that you run this on real hardware instead of a virtual machine, since we're installing a lot of software here.
If you must run on a virtual environment, make sure you have lots of RAM, at least 1.5 GB.
My approach was to do a clean install (from CD) of Windows Server 2003 SP1.
I used the default settings for network, which gave me a DHCP-enabled network client, with internet access.
Important decision on this step: where to install the system (delete all partitions, install on free space), server name (demoserver1), adminstrator password (?), network configuration (default)
Item that you will need: Windows Server 2003 SP1 CD, Windows Server 2003 product key.
1b) Installing the required patches
After the install of the base OS, please take the time to download and install all Windows Updates.
It's also a good idea to enable Microsoft Update, so you can get the updates for other Microsoft products as well (like SQL Server).
You will need to reboot after install and you will need to run the update again to get the .NET Framework 2.0 patches after the initial install.
After this is done, make sure to click on the "Finish" button of the post-setup security windows that show every time the Administrator logs on.
This will remove the temporary blocking put by setup.
Important decision on this step: what patches to install (install everything, including the .NET Framework 2.0 and Internet Explorer 7.0)
Item that you will need: Internet access
1c) Configuring a fixed IP address
To use Active Directory, you will need at least one network adapter with a fixed IP address.
If you can, configure this server with a fixed IP address that is routable to the Internet (being behind a NAT is OK).
You should also set your Preferred DNS to your server's own IP address.
If your test server is a notebook that you need to move around, consider the item below).
1d) Installing the loopback adapter with a fixed IP address
If you need to move your test server between your company's network, your home network and your customer's network, having a fixed IP can be a problem.
In order to have internet access in all those places you will likely need to have a DHCP-enabled network adapter.
However you cannot configure DNS and Active Directory for a server if your network interface is set as a DHCP client.
Since most people do not have two network adapters in their test machines, you can use a Loopback Adapter for your fixed-ip network.
To install Microsoft Loopback Adapter, go to Start, Control Panel, Add Hardware. Click Next.
When the Is the hardware connected? dialog box appears, click Yes, I have already connected the hardware, and then click Next.
In the Installed hardware list, click Add a new hardware device, and then click Next.
In the What do you want the wizard to do? list, click Install the hardware that I manually select from a list (Advanced), and then click Next.
In the Common hardware types list, click Network adapters, and then click Next.
In the Manufacturer list, click Microsoft.
In the Network Adapter list, click Microsoft Loopback Adapter, and then click Next twice.
If a message about driver signing appears, click Continue Anyway.
In the Completing the Add Hardware Wizard dialog box, click Finish, and then click OK.
To configure the adapter settings, go to Start, Control Panel, Network Connections, Loopback Adapter Connection.
Then click properties, click on "Internet Properties (TCP/IP)" and click Properties.
I configured my Loopback adapter with a fixed IP of 10.255.255.1 with a 255.255.255.0 mask and a Preferred DNS configured to point to itself (10.255.255.1).
I left the default gateway blank on that adapter, so that it uses the other (DHCP-enabled) adapter to get out.
Important decision on this step: TCP/IP configuration (ip address, net mask, default gateway).
Item that you will need: -
2) Installing DNS and Active Directory
2a) Installing the DNS Service
Use the Control Panel, Add/Remove Program, Add/Remove Windows Components, Networking, DNS to install the DNS Server. This is needed for Active Directory. Note that if you have not configured a fixed-IP address, the DNS configuration will complain about it.
Important decision on this step: -
Item that you will need: Windows Server 2003 SP1 CD
2b) Configuring the DNS zones required by Active Directory
Before you can set up Active Directory, you need to configure you DNS zone. Add the DNS service, use the DNS tool to add a primary forward zone (I named my demo.local). Make sure to allow dynamic updates for the zone (both secure or not).
Important decision on this step: DNS zone name (demo.local)
Item that you will need: -
2c) Configuring DNS entries for your host headers and e-mail
Open the DNS management tool and expand the server node, the forward lookup zones and select your zone (demo.local).
Right-click the zone and select "New Alias (CNAME)". Enter "team" as the alias name and your server's FQDN (demoserver1.demo.local).
Right-click the zone and select "New Alias (CNAME)". Enter "my" as the alias name and your server's FQDN (demoserver1.demo.local).
Right-click the zone and select "New Alias (CNAME)". Enter "ssp" as the alias name and your server's FQDN (demoserver1.demo.local).
Right-click the zone and select "New Mail Exchanger (MX)". Leave the child domain or host field blank, enter your server's FQDN (demoserver1.demo.local) and leave the default priority.
Important decision on this step: Host header entries (team, my, ssp)
Item that you will need: -
2d) Changing the server's DNS suffix
Next you will need to go to computer properties, click on the button to change the name and click on the "More" button to find the DNS suffix property. You will need to reboot after that. After the reboot, check the DNS tool again to see if your computer name shows in the zone (this confirms you used the right DNS zone and that dynamic updates are working).
Important decision on this step: -
Item that you will need: -
2e) Installing Active Directory itself
Run DCPROMO.EXE and create a new fores and domain at demo.local. All other settings can be left at the default. You will need to reboot again. After the reboot, check DNS again to see confirm that all the AD-specific service settings are showing there.
Important decision on this step: Domain name (same as DNS zone), folder for Active Directory (default), recovery mode password (?)
Item that you will need: -
2f) Creating Service Accounts and Organization Units
Use the Active Directory Users and Computers to create the required OUs and accounts.
Important decision on this step: Service accounts names and passwords (sql, sps, spa, spp), OU names (Service Accounts, SharePoint)
Item that you will need: -
3) Installing Internet Information Server and the .NET Framework
3a) Installing IIS
Install ASP.NET and SMTP service.
Important decision on this step: -
Item that you will need: Windows Server 2003 SP1 CD
3b) Making sure the .NET Framework 2.0 is enabled in IIS
Check in IIS manager if ASP.NET 2.0 is showing in the list. If not, run "ASPNET_REGIIS.EXE -i" from the C:WINDOWSMicrosoft.NETFrameworkv2.0.50727 folder.
You can also disable ASP.NET 1.1.
Important decision on this step: -
Item that you will need: -
3c) Downloading and Installing the RTM release of the .NET Framework 3.0
Go to https://msdn.microsoft.com/netframework/ and download the RTM released of the distributable package for the .NET Framework 3.0.
This includes the Windows Workflow Foundation and is required for MOSS 2007 installs.
Important decision on this step: -
Item that you will need: Internet Access
3d) Additional IIS Configuration
I recommend that you remove all default application pools and web applications that are configured by default in IIS. None of those are required for your MOSS 2007 install. I like to keep track of all web apps and app pools and keep them to a minimum.
You should also configure an SMTP alias for your domain.
Important decision on this step: SMTP alias for your domain (same as DNS zone).
Item that you will need: -
4) Installing SQL Server 2005 SP1
4a) Installing SQL Server 2005
Important decision on this step: Authentication mode (Windows only), SQL Server service account (sql), start SQL Server agent and SQL Server browser, components to install (database, SQL client, documentation, sample databases)
Item that you will need: SQL Server 2005 CD
4b) Installing SQL Server 2005 Service Pack 1
Download SQL Server 2005 SP1 or use the Microsoft Update tool to get it.
Important decision on this step: -
Item that you will need: Internet Access
4c) Grant permission to SharePoint service account
Open the Microsoft SQL Server Management Studio, connect to the demoserver1 server.
Expand the tree into demoserver1, Security, Logins.
Right-click "Logins" and select "New Login".
Specify the SharePoint Service Account (demosps).
In the "Server Roles" page, check the boxes for dbcreator and securityadmin.
Important decision on this step: -
Item that you will need: -
5) Installing Microsoft Office SharePoint Server 2007
5a) Installing MOSS 2007
Download the trail RTM version of MOSS 2007.
You will also need a trial product key available from that URL.
Run the OfficeServer.exe. Enter the Enterprise Trial product key.
On the "Choose the installation you want" window, select "Advanced".
On the "Server Type" tab, select "Complete".
On the "File Location" tab, select the folders to use. Defaults should be fine, unless you're using multiple drives.
Click the "Install Now" button.
Important decision on this step: Type of install to perform.
Item that you will need: MOSS 2007 CD and key, or Internet Access
5b) Running the Configuration Wizard
On the "Connect to a new farm" window, specify "No, I want to create a new server farm."
On the "Specify Configuration Database Settings" window, specify the server name (demoserver1), database name (SharePoint_Config), database access username (demosps, the SharePoint Service account) and password (?).
Specify the port number for the SharePoint Administration web application (?) and specify Negotiate (Kerberos) as the Authentication provider.
Click OK to confirm using Kerberos.
The wizard will then take some time to create the database and configure the SharePoint Administration site.
Important decision on this step: Configuration database settings, SharePoint Administrator web application settings.
Item that you will need: -
5c) Configuring MOSS 2007 Services
Click, Start, All Programs, Microsoft Office Server, SharePoint 3.0 Central Administration.
On the Operations tab, select "Services on Server". Select the "Custom" radio button to see all settings.
Central Administration, WSS Incoming E-mail Services and WSS Web Applications should be started already.
Click Start for the WSS Search Service.
Specify the WSS Service Accont (demospa) the Content Access account (demospa), the database server name (demoserver1), the WSS Search database name (SharePoint_WSS_Search), SQL Server authentication (Windows) and the indexing schedule (every 5 minutes).
Click Start and wait for processing to complete, taking you back to the "Services on Server" page.
Click Start for the MOSS Search Service.
Check the boxes for "Use this server for indexing content" and "Use this server for serving search queries".
Specify the e-mail address (sharepoint@demo.local), service account (demospa) and default settings otherwise.
Click Start and wait for processing to complete, taking you back to the "Services on Server" page.
Click Start for the Excel Calculations Service and wait for processing to complete, taking you back to the "Services on Server" page.
Click on the "Operations" tab and then click on "Outgoing E-mail Settings".
Specify the outbound STMP server (demoserver1.demo.local), the From e-mail address (sharepoint@demo.local) and click OK.
Click on the "Operations" tab and then click on "Incoming E-mail Settings".
Select "Yes" to enable receiving e-mails, keep the "Automatic" option to use the local SMTP service.
Select "Yes" to use the SharePoint Directory Management Service and specify the container (OU=SharePoint, DC=demo, DC=local) and SMTP server (demoserver1.demo.local).
Specify the e-mail server display address to use the SMTP domain instead of the server name (demo.local).
Click OK.
P.S.: Please note that the Search Service account needs to be the Content Access account (demospa) or the Search Service will be unable to access the content and you will run into errors with event ID 2424.
5d) Configuring MOSS 2007 Web Application
Click Start, All Programs, Microsoft Office Server, SharePoint 3.0 Central Administration.
Click on the "Application Management" tab, click on "Create or extend Web Application" and click on "Create a new web application".
Use the default port 80, enter "team" in the host header field, select "Negotiate (Kerberos)" for authentication.
Specify the application pool account (demospp), password (?) and the database name (SharePoint_Content_Team).
Leave all other settings as default and Click OK. Click OK again to confirm using Kerberos. Wait for processing, which will take a while.
5e) Configuring the Shared Services Provider
Click, Start, All Programs, Microsoft Office Server, SharePoint 3.0 Central Administration.
Click on the "Application Management" tab, click on "Create or extend Web Application" and click on "Create a new web application".
Use the default port 80, enter "my" in the host header field, select "Negotiate (Kerberos)" for authentication.
Specify the application pool account (demospp), password (?) and the database name (SharePoint_Content_My).
Leave all other settings as default and Click OK. Click OK again to confirm using Kerberos. Wait for processing, which will take a while.
Click on the "Application Management" tab, click on "Create or extend Web Application" and click on "Create a new web application".
Use the default port 80, enter "ssp" in the host header field, select "Negotiate (Kerberos)" for authentication.
Specify the application pool account (demospp), password (?) and the database name (SharePoint_Content_SSP).
Leave all other settings as default and Click OK. Click OK again to confirm using Kerberos. Wait for processing, which will take a while.
Click on the "Application Management" tab, click on "Manage this Farm's Shared Services".
Click on the "New SSP" link on the bar.
Select a web app for the SSP (SharePoint - ssp80) and for the my site (SharePoint - my80).
Select the SSP service account (demosps) and password (?).
Select the database server (demoserver1) the main SSP database name (SharePoint_SSP) and the SSP Search database name (SharePoint_SSP_Search).
Keep all other settings as default and click OK. Wait for processing, which will take a while.
Click on the "Application Management" tab, click on "Self-Service Site Management".
Select https://my as the web application, select the "On" radio button and click OK.
5e) Configuring the main site collection and the portal site
Click, Start, All Programs, Microsoft Office Server, SharePoint 3.0 Central Administration.
Click on the "Application Management" tab, click on "Quota Templates".
Select the "Create a new quota template" radio button and enter the template name (Team Quota).
Set the "Limit site storage to a maximum of" (100 MB) and "Send warning E-mail when site storage reaches" (90 MB).
Click OK.
Click on the "Application Management" tab, click on "Create Site Collection".
Specify the Web Application (https://team), the title/description (SharePoint Portal), the URL (/), the template (Blank Site), administrator (demoadministrator) and quota template (Team Quota).
Click OK.
Click on the "Application Management" tab, click on "Self-Service Site Management".
Select https://team as the web application, select the "On" radio button and click OK.
Go to the main site URL at https://teamClick on the "Site Actions" button and select "Edit Page".
Go to the main site URL at https://teamClick on "People and Groups" on the Quick Launch menu (on the left).
Click on the visitor's group (SharePoint Portal Visitors) on the menu on the left.
On the menu bar, click on "New" and select "Add Users".
Click on the link named "Add all authenticated users", uncheck the box to send a welcome message and click "OK"
Click on "Add Web Part" button on the left Web Part are and add a "Content Editor Web Part".
Enter some text to introduce SharePoint to your users.
Be sure to include a link to the Self-Service site creation page at https://team/_layouts/scsignup.aspx
5e) Configuring the Search SSP
Click, Start, All Programs, Microsoft Office Server, SharePoint 3.0 Central Administration.
On the left side menu, under "Shared Services Administration", click on the name of your Shared Services providers (SharedServices1).
Click on "Search Settings", then click on "Content sources and crawl schedules".
On the list of content sources, click on the one created automatically (Local Office SharePoint Server sites).
Click on the "Create Schedule" link under the Full Crawl to create a schedule (Daily starting at 12AM).
Click on the "Create Schedule" link under the Incremental Crawl to create a schedule (Daily starting at 1AM, repeating every 5 minutes).
Check the "Start full crawl of this content source" and click OK to start the first full crawl.
5e) Configuring the Excel Services SSP
Click, Start, All Programs, Microsoft Office Server, SharePoint 3.0 Central Administration.
On the left side menu, under "Shared Services Administration", click on the name of your Shared Services providers (SharedServices1).
Click on "Excel Services Settings", then click on "Trusted File Locations".
On the list of Trusted Locations (which should be empty), click on "Add Trusted File Location".
Enter the Address (https://team), the type (Windows SharePoint Services), check "Children Trusted" and click "OK".
Comments
- Anonymous
January 01, 2003
PingBack from http://mikewalsh.bilsimser.com/PermaLink,guid,6e67b9fc-a0c8-4356-b628-38b43dea3649.aspx