The SharePoint Farmer's Almanac : Install

Install Guide: SP2 for SharePoint (WSS v3 and MOSS 2007)

Shane — Wed, 29 Apr 2009 03:53:17 GMT

Service Pack 2 was released today (as I am guessing the whole world knows by now). Instead of making that profound announcement I would recommend you check out this post on the SharePoint Team blog for the official announcement. I will spare you the crazy details other than you should install it. J

Just like when the last updates came out I figured I would write a quick guide on the steps I am taking to install. Something to ponder before you get started. When was the last time you did a backup? Knock on wood as you answer.

Start time 11:11 PM
I am checking Windows Update for the latest patches. Looks like SQL Server 2008 SP1, IE8, and a random other Office update is waiting to install. I think I will let them sit for another evening; I have to get up early in the morning.
This environment is a single box with both MOSS Enterprise and SQL Server 2008. MOSS is currently running the February cumulative updates build 12.0.0.6341.
Downloading WSS SP2. 32.9 MB in 29 seconds. Make sure you download the 32bit or 64bit version you need. Both are available from the linked page.
Downloading MOSS SP2. 270 MB in 3 minutes 54 seconds. Make sure you download the 32bit or 64bit version you need. Both are available from the linked page.
Launched the WSS SP2 EXE I just downloaded.
Agreed to the license terms and clicked Continue
Started 11:22 PM. Ended 11:24 PM.
When configuration wizard opens click Cancel and Yes at the warning. We will run config wizard after the MOSS update is installed also.
Launched the MOSS SP2 EXE I just downloaded
Agreed to the license terms and clicked Continue
Started 11:25 PM. Ended 11:36 PM.
Configuration Wizard opens automatically when the update finished installing.
Click Next at the welcome screen
Click Yes to stopping IIS, SharePoint Admin Service, and SharePoint Timer Service
Click Next at the completing screen
You will get a popup warning that you need to install the updates on all servers in your farm before continuing. Be sure to do that if you have multiple servers.
Click OK.
Start at 11:38 PM. About 3 GB of content in this farm. End at 11:48 PM.
Click Finish
Looks like I am left with build 12.0.0.6421

Remember these are the steps I took on my server. They are put here to give you basic guidance, if you feel you want to read about applying updates in excruationing details then check out these links from the Team blog.

Deploy software updates for Windows SharePoint Services 3.0
http://technet.microsoft.com/en-us/library/cc288269.aspx
Deploy software updates for Office SharePoint Server 2007
http://technet.microsoft.com/en-us/library/cc263467.aspx

OK so a question for you. Do you like these update install guides with so many details or would you prefer I leave out everything and just make it quick. You really don't care about my Windows updates or how long it takes to install?

Shane SharePoint Consulting

Install Guide: February Cumulative Updates

Shane — Wed, 11 Mar 2009 14:29:00 GMT

Whoops... because i am a big dummy I screwed up this post. Sorry, hope you weren't using it. :) Install SharePoint SP2 now instead.

Sorry

Shane SharePoint Consulting

How to install WSS and MOSS SP1

Shane — Fri, 14 Dec 2007 03:50:00 GMT

Service Pack 1 for SharePoint is here. The SharePoint Team blog has a great full length article on all of fixes and tweaks. You can read it here Announcing the Release of WSS 3.0 SP1 and Office SharePoint Server 2007 SP1.

This post is just meant to give you the easy version of the install instructions. If you have complex scenarios or have issues I highly recommend you read Planning and deploying SP1 for Microsoft Office SharePoint Server instead of my instructions. Cool?

Ok here is my setup that I am about to patch. Server 1 is the SQL 2005 SP2 database box. Server 2 is a Windows Server 2003 SP2 with MOSS 2007 Enterprise installed. I am doing everything on Server 2. I give you run times on the longer parts for reference points. Your times will vary!

Backup SharePoint! Seriously handy little paper here if you need help.
Download the software you need. For my servers I downloaded the 32 bit editions. You must install BOTH the WSS and MOSS update if you have MOSS installed.
1. WSS SP1 downloads
2. MOSS SP1 downloads
Stop the World Wide Web Publishing Services to keep your users off the server.
1. Start > Administrative Tools > Services
2. Scroll to the bottom of the list, click World Wide Web Publishing Service
3. Click the Stop button
Install the Windows SharePoint Services Service Pack (total time less than 2 minutes)
1. Find the downloaded file. For me this was wssv3sp1-kb936988-x86-fullfile-en-us.exe
2. Double click to run the file
3. Read the license terms, click accept
4. Click continue
5. At the reminder message click OK
6. Now it starts processing the update.
7. At the installation complete message click OK
Now if you have just WSS skip to step 8
If the configuration wizard opens close it.
Install the MOSS update (total time less than 2 minutes)
1. Find the downloaded file. For me this was officeserver2007sp1-kb936984-x86-fullfile-en-us.exe
2. Double click to run the file
3. Read the license terms, click accept
4. Click continue
5. At the reminder message click OK
6. Now the update processes…
Run SharePoint Configuration Wizard (15 minutes)
1. Start > All Programs > Microsoft Office Server > SharePoint Product and Technologies Configuration Wizard
2. Click Next at the Welcome screen
3. Click Yes at the warning about restarting services
4. Click Next at the Completing the SharePoint Product and Technologies Configuration Wizard
5. Your server is now processing step 1
6. You will be prompted to now install the updates on other servers in your farm. Click OK since you only have 1 SharePoint server.
  1. NOTE: If you did have multiple servers you would repeat all of the above steps on each of those servers before moving on. Also, if you are wondering you should probably start with the server that host central admin.
7. Now your server is processing steps 2 through 9.
8. Speaking of step 8 it took my server approximately 13 minutes to process 4.4 GB of content. I am sure your times will vary. Just don't panic on this step if it takes a while. It is essentially touching all of your content.
9. At Configuration Successful click Finish
Check out Central Admin
1. Restart the World Wide Web Publishing service you stopped in step 2. If you had to reboot this is not necessary.
2. Click Operations tab
3. Under Topologies and Services click Servers in farm
4. Next to your server you should see Version 12.0.0.6219 not 12.0.0.4518. If you do you should be good to go.

That is it. :)

Shane – SharePoint Help

Please install the SharePoint updates on your server

Shane — Thu, 18 Oct 2007 04:22:23 GMT

Seriously, you should install the updates before you have to set those clocks back an hour. Heck, if I am having to remind you this then I should also remind you to check the batteries in your smoke detectors. J

This is a security update! Yes, I know it fixes the annoying day light savings issues it also fixes some important security issues. Read the security bulletin. Does your server face the internet? Maybe as an extranet? Then you should of installed this yesterday.

Here are my brief yet kind of helpful instructions. There is nothing earth shattering here. I just know people like to know exactly what they are in for before doing an update. These instructions are only right if you are running One SharePoint Server. If you have multiple SharePoint servers you need to read these instructions. For WSS update and MOSS update. These instructions cover how to verify if you already have installed the patches, known issues, secure and farm scenarios, still in the middle of an upgrade from v2, how to use the updates folder for a fresh install, how to detach your content databases to speed up the update, and how to verify the install was successful.

If you have any issues after you install the updates then check out Bill Baer's post http://blogs.technet.com/wbaer/archive/2007/10/15/kb934525-troubleshooting.aspx It fixed one of my customer issues and some post on the MSDN Forums. But don't tell Bill it helped you, his head is getting too big already. ;)

You will have downtime while installing these updates! Plan accordingly. Some servers will even have to reboot, others will not. (I have been exactly 50-50 on this.)

Backup SharePoint!
Download the software you need. For my servers I downloaded the 32 bit editions. You must install BOTH the WSS and MOSS update if you have MOSS installed.
Stop the World Wide Web Publishing Services to keep your users off the server.
1. Start > Administrative Tools > Services
2. Scroll to the bottom of the list, click World Wide Web Publishing Service
3. Click the Stop button
Install the WSS update (total time less than 2 minutes)
1. Find the downloaded file. For me this was wssv3-kb934525-fullfile-x86-glb.exe
2. Double click to run the file
3. Read the license terms, click accept
4. Click continue
5. At the reminder message click OK
6. Now it starts processing the update.
7. At the installation complete message click OK
Now if you have just WSS skip to step 7
Install the MOSS update (total time less than 2 minutes)
1. Find the downloaded file. For me this was Officeserver2007-kb937832-fullfile-x86-glb.exe
2. Double click to run the file
3. Read the license terms, click accept
4. Click continue
5. At the reminder message click OK
6. Now the update process…
7. At the end of my update I was greeted with a REBOOT message. If you are then click Yes to reboot. If not click OK at the installation complete message.
Run SharePoint Configuration Wizard (15 minutes)
1. Start > All Programs > Microsoft Office Server > SharePoint Product and Technologies Configuration Wizard
2. Click Next at the Welcome screen
3. Click Yes at the warning about restarting services
4. Click Next at the Completing the SharePoint Product and Technologies Configuration Wizard
5. Your server is now processing step 1
6. You will be prompted to now install the updates on other servers in your farm. Click OK since you only have 1 SharePoint server.
7. Now your server is processing steps 2 through 9.
8. At step 8 I noticed this error. Best I can tell nothing bad happened. If you see this makes sure search still works. The install doc above covers how to restart search if you do have issues.
9. Speaking of step 8 it took my server approximately 13 minutes to process 4.4 GB of content. I am sure your times will vary. Just don't panic on this step if it takes a while. It is essentially touching all of your content.
10. At Configuration Successful click Finish
Check out Central Admin
1. Restart the World Wide Web Publishing service you stopped in step 2. If you had to reboot this is not necessary.
2. Click Operations tab
3. Under Topologies and Services click Servers in farm
4. Next to your server you should see Version 12.0.0.6039 not 12.0.0.4518. If you do you should be good to go.

That is it. :)

If you have question not covered contact me or check out Joel's Update FAQs

Shane – SharePoint Help

Typical problem with a least privileged install

Shane — Tue, 09 Oct 2007 03:51:48 GMT

If you are keeping with best practices and doing any type of install where security is important (shouldn't it always be) then you have probably done a least privileged install. Probably using these instructions Least-privilege administration requirements when using domain user accounts.

One of the challenges of this type of install is things don't always work as expected. Take for example the RADEditor for SharePoint 2007. This handy little tool allows cross-browser rich text edit. Huh? These lets your users with FireFox (or the other 2^nd tier browsers) go from an experience like this when editing a wiki

To something very similar to what the Internet Explorer users see

That is pretty cool huh?

The way it works is you download their WSS Solutions Package (WSP) and deploy it to your web application. Then you have a feature named Use RadEditor to edit List items available at the Web (single site) level. The first time you activate the feature it attempts to copy RadEditorList.ascx from c:\program files\common files\Microsoft Shared\web server extensions\12\Template\Features\RadEditorFeature\ to c:\program files\common files\Microsoft Shared\web server extensions\12\Template\ControlTemplates. The only problem is it requires administrator rights on the server to move the file. And the account that it is attempting to use to move the file is your application pool account. And if you did a "proper" install that account does not have local administrator permissions on the SharePoint Server.

The problem? You never get an error message to let you know the copy failed. :( So you are left guessing. Once you discover this problem simply move the file over to the proper directory. Now do an IISReset.exe and your non-IE users will be happy.

The main reason I bring up this issue is it is very common. Often when you do a least privileged install you will find little issues like this, so be prepared.

Shane – SharePoint Help

Setting up SharePoint? Accounts need their domain.

Shane — Wed, 07 Mar 2007 17:11:00 GMT

I have been meaning to post this forever and keep forgetting. A very common issue I am seeing people have when setting up and configuring SharePoint is the way they are specifying account names. You must always specify domain\username. Even though SharePoint will never tell you this is the problem it is. Many users are tempted to just type in username for a service and then the password then they are greeted with a random/cryptic error message. After about an hour (or a day of reinstalling) they realize it was because they forgot to specify the domain name.

I will attempt to compile a list of error messages that have been caused by this issue and post them here. If you have one please post it in the comments and I will update the post. Thanks

Sample Error:

An unhandled exception occurred in the user interface.Exception Information: OSearch (SPSearchAcct)

Anyway, just a heads up!

Shane – SharePoint Help

NT4 domain and SharePoint 2007 don’t play nice

Shane — Thu, 25 Jan 2007 02:53:09 GMT

So after really beating my head on the table for a while my conclusion is you cannot install MOSS 2007 or WSS v3 in an NT 4.0 domain as anything but a single server. If you choose multiserver you will get the error below. I got this error while trying to connect to the SQL Server using windows authentication in the configuration wizard. :(

01/09/2007 10:36:27 10 ERR Exception: System.Security.Principal.IdentityNotMappedException: Some or all identity references could not be translated.

at System.Security.Principal.NTAccount.Translate(IdentityReferenceCollection sourceAccounts, Type targetType, Boolean forceSuccess)

at System.Security.Principal.NTAccount.Translate(Type targetType)

at Microsoft.SharePoint.Administration.SPProcessIdentity.GetMachineRelativeSecurityIdentifier(SPServer server, Boolean& isMachineAccount)

at Microsoft.SharePoint.Administration.SPProcessIdentity.GrantIdentityDatabaseAccess()

at Microsoft.SharePoint.Administration.SPProcessIdentity.Update()

at Microsoft.SharePoint.Administration.SPWindowsService.Update()

at Microsoft.SharePoint.Administration.SPFarm.CreateBasicServices(SqlConnectionStringBuilder administrationContentDatabase, IdentityType identityType, String farmUser, SecureString farmPassword)

at Microsoft.SharePoint.Administration.SPFarm.Create(SqlConnectionStringBuilder configurationDatabase, SqlConnectionStringBuilder administrationContentDatabase, IdentityType identityType, String farmUser, SecureString farmPassword)

at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.CreateOrConnectConfigDb()

at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.Run()

at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()

Now this is my professional opinion because as best I can tell there is no official Microsoft position on this. If you are on an NT4 domain and really want to try using 1 SharePoint server and 1 SQL server you may be able to use SQL authentication but no promises there. It seems that SharePoint considers NT4 to be the same as a workgroup.

Hope this saves someone some grief.

Shane – SharePoint Help

Installing MOSS 2007 RTM on a farm running MOSS 2007 Beta2 TR

Shane — Wed, 15 Nov 2006 23:59:00 GMT

Tomorrow sometime Microsoft will release Office SharePoint Server 2007 for download at the Microsoft Download Center. Check out this post to find all of the details on downloading. In anticipation of the flood of demand for help on migrating away from TR and onto RTM I have decided to release so updated instructions a little early. Yes, Microsoft will publish the "official" instructions tomorrow I just thought you might appreciate a version with screen shots. And yes step 5 really says to uninstall MOSS. J It will be ok. Of course I never do something like this without doing a backup first. See this link for backup and restore guidance.

Let the fun begin!!!

For Microsoft's version of this instructions check out Joel's post.

Note which server is hosting SharePoint Central Administration and confirm that there are no pending or failed backup/restore or upgrade timer jobs.
1. Go to SharePoint Central Administration
2. Click the Operations Tab
3. From Global Configuration click Timer Job Definitions
4. Delete any failed or pending jobs referencing backup/restore, or upgrade. You may not have any of these but you need to check.
Write down some information about all of your servers in the farm
1. Make a list of every server that host SharePoint Central Administration. You may skip this step if you have a single server install.
  1. Go to SharePoint Central Administration
  2. Click the Operations Tab
  3. Click Services on server
  4. Now click the Custom radio button
  5. Look to the Central Administration service and see if it is started. If yes then record the server name as hosting Central Admin
  6. Now click Server name above and on the drop down select Change server. Repeat these steps checking each server in your farm.
2. Make a list of each servers role
  1. Click Start > Run
  2. Type regedit.exe and press OK
  3. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\WSS\ServerRole and record the value.
  4. Repeat these steps for each server with MOSS installed
3. Discover if you used a standard or enterprise key
  1. Go to SharePoint Central Administration
  2. Click the Operations Tab
  3. From Upgrade and Migration click Enable Enterprise Features. If you have the screen below then you used the Enterprise key. If you used the Enterprise key then you must use the Enterprise key when you enter the a key while installing the RTM bits. If you don't have the screen below then you used the Standard key to do your install and you may use either the Standard or Enterprise key when you install the RTM bits.
Backup the 12.0 hive from the registry. Warning: If you are unfamiliar with the registry proceed with caution as you can damage your system. For more information on editing the registry see KB322756.
1. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0
2. Right Click on 12.0 and click Export
3. Provide a filename, choose a safe location for the backup file and click save.
Now edit the registry key by renaming the dsn key
1. Navigate to [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\Secure\ConfigDB\dsn]
2. Right click on dsn and click rename
3. Enter dsn2 and click off the key making the change permanent
4. Close the registry editor.
Purge the old configuration wizard logs
1. Open windows explorer
2. Navigate to c:\program files\common files\Microsoft shared\web server extensions\12\logs
3. Delete all files that are psc*.log (These are just an example you may have more or less.)
Check to see if you have installed any language packs and uninstall them.
1. Open Control Panel
2. Click add/remove programs
3. If you have any language packs uninstall them at this time.
The next step is to uninstall MOSS Beta2 Technical Refresh. This will uninstall MOSS completely from your machine but will not delete any of your data.
1. Open Control Panel
2. Click add/remove programs
3. Scroll down to Microsoft Office SharePoint Server 2007 (Beta) and click Remove
4. At the "Are you sure you want to remove Microsoft Office SharePoint Server 2007 (Beta) from your Machine?" message click Yes.
5. At the warning message asking if you want to uninstall now click Ok.
6. When the uninstall is complete click Close.
Reboot your server
If you have more than one MOSS server repeat steps 6 – 8 for all servers in the farm. The order does not matter and you can do all of the servers at the same time or individually.
Now that all servers have had MOSS uninstalled from them and have been rebooted you need to install MOSS 2007 RTM. You will perform the following steps on one server at a time. Start with the web front end server that previously hosted Central Admin (noted in step 2a above) and then you may do all additional servers in any order. Perform only on one server at a time. If any server fails resolve the issue before continuing to the next server.
1. Run setup.exe from the RTM installation folder.
2. Enter your product key and click continue. Be sure that use the proper key based on your findings from step 2c above.
  1. SharePoint Server Standard Trial: XJMKW-8T7PR-76XT6-RTC8G-VVWCQ
  2. SharePoint Server Enterprise Trial: F2JBW-4PDJC-HKXTJ-YCKRP-T2J9D
3. Read the Microsoft Software License Terms, check the box beside I accept and click Continue.
4. At the choose the installation you want click the Advanced button.
5. At this server type screen you should choose the appropriate option for you. Also, if you would like to use a non-default installation folder then you will need to click the File Location tab and specify the directory of your choice. You recorded the server type in step 2 b above.
6. De-Select the box for running the Configuration Wizard and click Close.
7. Now install any necessary language packs on the server. Instructions found here.
Once all servers have been installed return to your original web front end server which will host SharePoint Central Administration.
1. Click Start > All Programs > Microsoft Office Server > SharePoint Configuration and Technologies Configuration Wizard.
2. Click Next at the Welcome screen.
3. At the warning message click Yes.
4. At the Completing SharePoint screen you should see your database and database server listed. Click Next.
5. You will see a warning message reminding you to install MOSS on all servers in your farm before proceeding. Ignore this warning message and click Ok
6. You may notice this message while configuration wizard is running. It is safe to ignore.
7. At the Configuration Successful screen click Finish.
Now find out what your servers search topology is.
1. Go to SharePoint Central Administration
2. Click the Operations Tab
3. From Topologies and Services click Services on Server
4. If the Office SharePoint Server Search is stopped go to step 13
5. If the Office SharePoint Server Search is started from the command line on this server you need to run the command stsadm -o osearch -action start (Make sure you navigate to the 12\bin directory as shown in the screen shot).

Return to the Services on Server page and click Office SharePoint Server Search to go to the settings screen
If the box to the left of Use this server for indexing content is checked your server is a Index server. Now perform the sub steps. If it is not enabled skip to step h.
1. Click Start > Run
2. Type regedit.exe and press OK
3. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\12.0\Search\Applications\{Application GUID} For each key that you find with this pattern do the following
  1. Set the default key to On
  2. Create a new subkey named Gathering Manager
  3. Under Gathering Manager create a DWORD value named UseClustering and set it to 0.
4. Now open a command prompt.
5. Run the command net stop osearch
6. Run the command net start osearch
7. Run iisreset on every server in your farm.
If the box to the left of Use this server for serving search queries is checked your server is a Query server

Now for the tricky part. If you are on a single server install then you can skip all of this. Perform the following steps only on servers that is either an Index server or a Query server but not both. So if the server had both boxes in step 12 f do not perform these steps. If the server had neither box checked in step 12 f checked do not perform these steps. If the server only had 1 box checked continue.
1. For every server that only has the Query role
  1. Go to SharePoint Central Administration
  2. Click the Operations Tab
  3. From Topologies and Services click Services on Server
  4. On the Office SharePoint Server Service click stop
  5. Wait for the status to change to Stopped
  6. Repeat these steps for any other server with the Query only role
2. For every server that has only the Index role
  1. Now open a command prompt.
  2. Run the command net stop osearch
  3. Run the command net start osearch
  4. Wait 5 minutes
3. Now once all servers are complete you can continue
  1. Go back to each of the servers you stopped in 13 a
  2. Go to SharePoint Central Administration
  3. Click the Operations Tab
  4. From Topologies and Services click Services on Server
  5. Click start on the Office SharePoint Server Search service
  6. Wait on each server to complete initializing before moving to the next
    1. To ensure that the server has initialized navigate to the SSP and click search settings
    2. Check that the propagation status is Idle
More than likely your search scopes are missing. To correct this problem
1. Open the home page of your portal in your browser
2. Right click on the search tab and chose Copy Shortcut
3. Click Site Actions> Site Settings > Modify all site settings
4. Under Site Collection Administration click Search Settings
5. Click Use custom scopes and then paste in the URL you copied in step b and click OK.
Now that all of SharePoint is upgraded and you have confirmed search is working you need to install the latest release of the Microsoft .NET Framework 3.0 on all servers in your farm.
1. Open control panel
2. Click Add or Remove Programs
3. Find Microsoft .NET Framework 3.0 in the list and click Remove
4. Install the latest release you just downloaded.

Shane – SharePoint Help