Tuesday, June 28, 2011

WSS 3.0 MOSS 2007 Installation Steps

Single Server (Non-Standalone install) on a new domain.
Backup and restore few site collections from an existing SharePoint farm to new farm.


Current SharePoint Farm
- Note version of current farm from Central Admin-> Operations -> Servers in farm-> version column. Mine is hence August 2010 CU patch.

- Since all site collections to be backed up are under 15GB used stsadm -o backup to perform backup.

- Copied backup files over to destination server

New Server Configuration

-Accounts needed
--> Setup account (dbcreator and securityadmin SQL permissions, Local admin on SP server)
--farm account
--pool account(s)
--mysite pool account
--ssp admin pool account
--search access account (used while starting office search service)
--ssp service account (used while provisionsing ssp)

- Web Apps needed
--> Collaboration web apps
--> Central Admin Web App
--> SSP Web App
--> Mysite web app

-install powershell on windows server 2003 which has a dependency on .net framework 2.0 sp1
powershell: http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=10512
.net framework 2.0 sp1:


- Restart server

- Install SQL Server 2005 SP3

- Download and install windows imaging component en-us from here,

- Download and install .net framework 3. Remember .net framework 4 will not suffice the prerequisite. If this is not installed it throws a windows workflow foundation exception, http://msdn.microsoft.com/en-us/netframework/bb264589

- Download and install wss 3.0 sp2 from here,

--> Remember to install Advanced -> Web Front End.
--> Do not run PSConfig now

- Download and install moss 2007 with sp2 full version from your msdn subscription
MOSS 2007 with SP2 includes WSS 3.0.

- Run PSConfig and provide Central Admin details and farm account.

- Install WSS / MOSS Aug 2010 CU
Download and install WSS update: (do not run psconfig)

Download and install moss update

- Run psconfig or "SharePoint Products and Technologies Configuration Wizard"

- Create web application, e.g. http://sharepointsite.com
-- make sure to host IIS local folder on seperate drive other than c:\
--> NTLM
--> Non-HTTPS
--> New App Pool with independent identity
--> Unique database name

- IISReset /noforce

- Add host file entry to point hostheader "sharepointsite" to current server IP ""

-Add stsadm as environment variable,

- Add managed paths if required. In my case I had to.

- Create a site collection

- Configure host file on server to point all web application host headers to

- Configure site collection quotas from Central Administration or powershell

At this point you are ready to use this site on the server.

- Add DNS entries for using site's hostheader and server IP address and this site is good to go.

The current identity “domain\username” does not have write access to ‘C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files’.


Basically asp.net is not correctly installed on the server. hence perform the steps mentioned in this blog to fix. I did not have to add my app pool account to IIS_IUser group.


- Set up IIS Logs to a drive which has ample space.
- Set up diagnostic logging to a drive which has ample space.

- If there are multiple domains involved with one-way trust, setup people-picker to read from all domains using,
STSADM.EXE -o setproperty -pn peoplepicker-searchadforests

For me there are some more steps:

- Deploy custom solutions from source farm to destination farm
- Restore site collection to new webapplication using stsadm -o restore

Error: default.aspx is corrupt and site collection root page is returning HTTP 404

- setup SSP

- Disable SharePoint designer,

- If you ever need to change the IIS local folder of a sharepoint web application,



Navigate to Central Admin -> Application management
Click on Delete Web application
Drop IIS only! Not Content database
Create new web application with some temp database name and same host header as before.
Do not create any site collections
Navigate to content databases -> remove temp database. You can ask your DBA to permanently remove the temp db later
Open command prompt under farm account and type,
stsadm -o addcontentdb -databasename "old db name" -url "url name"

- SSP Creation:
-- pre-req: create mysite, ssp admin webapp, start office sharepoint search service and set indexing server.
-- change index file location to a drive with max space.
-- set ssp account which is different from admin pool account and search access account.

- Configure User profile synchronization
-- configure import connections, if it is the same domain then no need to specify account
-- setup import schedule
--start import

- Configure Search
-- setup content sources
-- setup crawl schedules
-start crawl

-Configure email settings.
Incoming: http://technet.microsoft.com/en-us/library/cc262947(office.12).aspx
Outgoing: http://technet.microsoft.com/en-us/library/cc263462(office.12).aspx
--Exchange connector settings
--SMTP Relay


No comments:

Post a Comment