
I had planned on updating my previous installation script just after B2TR was released, but I was too busy doing Touchdown redeliveries and MOSS seminars.
Anyway, here it is: An installation script telling you how I installed my demo laptop with the following products:
- Windows Server 2003 Enterprise Edition R2
- .NET 3.0 RC Framework
- SQL Server 2005
- SQL Server 2005 Reporting Services
- SQL Server 2005 Analysis Services
- Office 2007 Professional Beta 2 TR
- Sharepoint Designer B2TR
- Microsoft Office Sharepoint Server 2007 B2TR
- Visual Studio .NET 2005
- Visual Studio Tools for Office 2005 SE Beta
You can use this installation guide if you want to create your own MOSS installation. (Make sure you got a good system with a lot of memory if you want to have all these products on a single system!)
Installing Windows Server 2003
- Start with a default installation of Windows Server
- Install all the available updates from Windows Update
- Add the following components:
- IIS 6
- ASP.NET
- DNS
- SMTP
- Install the Microsoft Loopback network adapter and assign it a fixed IP address of 192.168.1.1
- Start DCPromo and create a new Active Directory Forest
- For my setup , I created a moss.contoso.com AD
- If the Wizard asks you for the DNS settings, allow it to create and set up your DNS
- Start the DNS MMC
- In the DNS MMC, create three new CNAME Records pointing to your DC A record for the 192.168.1.1 IP, call them:
- Portal.moss.contoso.com
- Team.moss.contoso.com
- Mysite.moss.contosos.com
- SharedServices.moss.contoso.com
- Start the Active Directory Users And Computers Snap-in
- Add a new user
- Name: SqlService
- Member of:
- Distributed COM Users
- Create a copy of this user and call it
- Name: MossService
- Add the pop3 component from Add / Remove Programs
- Setup the pop3 component, make sure it is integrated with your active directory
- Create a mailbox for administrator
- Start the service from the pop3 mmc snap-in
- Edit the 'Microsoft POP3 Service' in the Services Snap-in, set it to start automatically.
- Open the Domain Controller Security Policy from Administrative Tools
- At the Local Policies, User Rights Assignment level
- Allow SqlService and MossService to act as part of the Operating System
- Allow Domain Users to log on locally
- Download and install the StandAloneDCWorkaround.msi here
Installing SQL Server 2005
- Start the setup.exe for SQL Server and install all products. Make sure you install the Adventureworks sample databases as well!
Installing Visual Studio .NET 2005
- Install Visual Studio make sure you install:
- C# and / or VB.NET
- Install .NET 3.0 Framework RC which you can download here
- Install Microsoft® Visual Studio® 2005 Extensions for Windows® Workflow Foundation Release Candidate 5 (download here)
Installing Office 2007 Professional Beta 2
- Install a normal Office 2007 professional installation
- Start at least one application and activate the installation.
- Go to Add / Remove programs and select 'Change' for the Office 2007 Professional installation
- Select the Infopath .NET Programmability feature to be installed.
- Start the Office System 2007 Beta 2 Technical Refresh setup (click here)
Installing VSTO
- Download and Run the vsto2kSEBetaSetup (download here)
Installing ECM Starter kit
- Download and run the ECM Starter kit (download here)
Installing Sharepoint Designer
- Install the Sharepoint designer Beta 2
- Update the Sharepoint designer with Beta 2 TR (download here)
Installing MOSS
- Start the MOSS installation.
- Update MOSS Installation to B2TR using the streamline document (download here)
- In the Wizard select the 'Complete Installation' option
- In the Database screen:
- Use the default instance for the MOSS database (name is: SharedServices.moss.contoso.com)
- Use SQLService as the account to connect to this instance
Setting additional user rights
- Because of a bug in Beta 2 it is necessary for the app pool account of the Shared Services website to be an administrator on the Web server (according to this readme: click here) In our case, that is the SqlService account.
Configuring MOSS Services
- On the Sharepoint Central Administration 3.0 site:
- Select Operations
- Select Services on Server
- Start the "Windows Sharepoint Services Web Application"
- Start the "Windows Sharepoint Services Search"
- Use the MossService account for all the credential questions
- Start the Office Sharepoint Server Search
- Set administrator@moss.contoso.com for the e-mail address
- Use the SqlService account for the credential question
- Start the Excel Calculation Services
Note: After installation of the MOSS Services I got 500 errors when I accessed the Central Administration site. Waiting for a few minutes resolved this.
Configuration MOSS Shared Services
- On the Sharepoint Central Administration 3.0 site:
- Select Application Management
- Select "Create or configure this farm's shared services"
- Select "New SSP"
- Select "Create a new web application"
- Setup the new webapplication:
- Use port 80
- Use SharedServices.moss.contoso.com as the hostheader name
- Use the MossService account for the Application Pool credentials
- Repeat the steps above to create another web application for the mysite.moss.contoso.com hostheader.
- Press Ok, you'll see a new screen now in which you can create the Shared Service Provider
- Use the SqlService account for the SSP Credentials
- Select the mysite.moss.contoso.com as the web application you want to host your mysites on.
After you finished this screen, the server will take some time to create your shared services!
Using the DCWorkAround
- In %PROGRAMFILES%DCWorkAround start the Workaround.bat
- Make sure MossService has full DCOM rights on your windows 2003 installation.
Creating the Team site
- On the Sharepoint Central Administration 3.0 site:
- Select Application Management
- Select "Create or extend Web Application"
- Select the default web application
- Set the host header for the default web application to Team.moss.contoso.com
- Press Ok
- Create a new Site Collection
- Set the title to "WSS Team site"
- Set the owner to administrator
- Select the Team site template
Creating the Portal site
- On the Sharepoint Central Administration 3.0 site:
- Select Application Management
- Select "Create or extend Web Application"
- Select "Create a new web application"
- Setup the new webapplication:
- Use port 80
- Use portal.moss.contoso.com as the hostheader name
- Use the MossService account for the Application Pool credentials
- Select the available index from the dropdown box
- Press Ok
- Create a new Site Collection
- Set the title to "Portal"
- Set the owner to administrator
- Select the enterprise tab and select the collaboration portal site template
Now you have created:
A team site at http://team.moss.contoso.com
A portal site at http://portal.moss.contoso.com
A Shared Services provider at http://sharedservices.moss.contoso.com
Your mysites are hosted at http://mysite.moss.contoso.com
Now finish your installation by creating demo users to use on your portal and team sites. You can use Outlook 2007 to connect to the pop3 and smtp services to use the alert and e-mail functionality.
16 comments
You will not need the StandAloneDCWorkaround.msi anymore when doing a slipstream install of MOSS 2007. Another note : the ECM starter kit has not been updated for Beta2TR yet, … so you will not be able to use SharePoint Sequential Workflow and State Machine library projects …
Joris
Ah, didn’t know about the standalonedcworkaround, thanks!
About the not working workflows…I didn’t notice any problems doing the redelivery, so are you sure?
bartg
What I don’t see in here is installing WSS v3. When should that happen? Also, apparently by default WSS v3 uses msde…?
dennis
Dennis,
Part of the installation of MOSS involves installing WSS v3. You do not need to do this separately.
About MSDE -> This is the SQL 2000 desktop engine which is no longer used by Microsoft for WSS. Instead they opt for the Sql Server Express edition. It is possible to install WSS v3 with Sql Server Express.
bartg
I tried to create SSP. I enterd all the field and after taking long time it was showing error “Thread was aborted”.
Neha
Neha,
It’s not possible to say anything about your problem with this amount of information 🙂 However, I noticed during my installation that “Thread was aborted” messages were caused by timeouts of the system. These timeouts occurred because my computer was just to slow to do all the work in the allowed time.
Killing a few processes and freeing up some memory did the trick for me in most cases.
You can also check the eventlog if there is any more information displayed over there.
Good luck!
Bart
bartg
I installed the MOSS beta2 but I am getting “Could not load Microsoft.reportviewer.webforms” at the event log. How can I fix it? Thanks.
David
David,
Are you sure you are using the right pre-release version of .NET 3.0?
bartg
I have reinstalled the .net 3.0 and it was downloaded at http://msdn.microsoft.com/windowsvista/support/relnotes/netfx3/default.aspx
. I think it is the right version. Do I need to install Visual Studio 2005 as well?
David
David,
You’ll need the PRE-release linked in my install script above.
You don’t need to install VS 2005.
bartg
I did use the uninstall tool to remove the .NET 3.0 and reinstalled the dotnetfx3.exe but still have the same error. Please help. THANKS.
David
Sorry David, I don’t think I can help you out any further. Why don’t you try the RTM version of MOSS? This way you can use all the released products which might solve your problem.
Good luck!
bartg
That was GREAT! Thanks a bunch!!1 ^_^
Sammy Tattersill
In MOSS 2007 I donot find the collaboration portal site template in Enterprise tab. What should i choose to create a portal site same as SPS 2003
Girija Shankar
Girija,
You need to look at the publishing tab. sorry! 🙂
bartg
Hi,
Can u guide me in creating Custom and Portal templates for MOSS 2007.
Aarthi