Downloads required to install SharePoint 2007

Just a quick post. I keep emailing these links to people so I thought I would write them down and just post them.

Prerequisites:

Microsoft Office SharePoint Server 2007 180 day trial When you download this you will need to register to get a registration key (PID)

Windows SharePoint Service 3.0 For those of you who don’t want portal product. No key required.

A good resource for install documents can be found on the SharePoint Team Blog

Hope this helps!

 

Shane – SharePoint Help

Upgrade from TR to RTM Work Around

Looks like at least one problem has snuck through that needs a work around. If you are getting errors like:

User Profiles and Properties Page: An error has occurred while accessing the SQL Server database or the Office SharePoint Server Search service. If this is the first time you have seen this message, try again later. If this problem persists, contact your administrator.

Or

Search Settings: The search service is currently offline. Visit the Services on Server page in SharePoint Central Administration to verify whether the service is enabled. This might also be because an indexer move is in progress.

Then you need to perform the following work around.

  1. Go to the operations tab in Central Administration
  2. Click on services on server
  3. Find the Office SharePoint Server Search and click the Stop button to its right

  4. You will get a message asking “Are you sure you want to uninstall the Office SharePoint Server Search service from this server?” Click OK.
  5. Now go back and start the Office SharePoint Server Search and click Start
  6. Now perform an iisreset.
  7. It sometimes takes up to 5 minutes for search and profiles to begin working.

 

Shane SharePoint Help

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

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.


  1. 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.
  2. 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.

  3. 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.
  4. 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.
  5. 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.)

  6. 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.
  7. 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.
  8. Reboot your server
  9. 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.
  10. 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.
  11. 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.
  12. 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).

                  


  1. Return to the Services on Server page and click Office SharePoint Server Search to go to the settings screen

  2. 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.
  3. If the box to the left of Use this server for serving search queries is checked your server is a Query server

  1. 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
  2. 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.

         

  3. 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


Consolidating Site Collections After Upgrading SharePoint

As you start to explore Microsoft Office SharePoint Server 2007 you are going to find lots of new features and ways of doing things. One that has caused a bit of stir in the upgrading classes I have taught (to roughly 60 people already WOW!) is the fact that when you create a site through the site directory it becomes a sub site, not a separate site collection as it did in SPS 2003. My understanding of the reasons behind this is the rollup and aggregation web parts do not work across site collections. Also, the handy feature Manage Content and Structure is only valid within the same site collection. So that is great for new sites you create but what about when I upgrade?


In SPS 2003 all of our sites created from the site directory were separate site collections. So when we finish upgrading we are left with 1 site collection that encompasses our portal (and future sites we create from the portal) and then all of these upgraded collaborative sites that live each in its own site collection. What are we to do?


Well, thanks to some persistent students in my Denver class last week I have sat down and figured out how to rearrange things if you are so inclined. (Ok, ok I actually sent an email and had the answer sent to me but such is life, at least I am going to document it. Thanks Joel)


So just a couple of basics before we start.


  • My portal is located at http://portal.abc.local
  • I have a team site (standalone site collection) located at http://portal.abc.local/sites/hr

If I wanted to see a list of all of the site collections below my portal I can do that. The easy, out of the box way is to use stsadm.exe –o enumsites –url http://portal.abc.local




You will also notice from the screen shot that stsadm gives us more details in this version. ContentDatabase, StorageUsedMB, StorageWarningMB, and StorageMaxMB are all new pieces of information that could be handy in a pinch.


Anyway, back to the task at hand. How are we going to move HR to be part of the portal site collection? How about using stsadm.exe –o export



From the screen shot we can see at a minimum we will need to use the –url and –fliename options. So we probably want to run stsadm –o export –url http://portal.abc.local/sites/hr -filename HRsite.bak



Depending on the size of your site collection this command may run for several minutes. Once it finishes you will get a message saying Operation Completed Successful. Now we need to figure out how to get the site collection back in. To do this let’s look at the command stsadm –o import



From this screen shot we can now see that we just need to do is import our previous file to a url inside our portal site collection. Something like stsadm –o import –url http://portal.abc.local/HR -filename HRsite.bak



Once again you should get a Operation Completed Successfully message. If you did then you should now be able to browse to http://portal.abc.local/sites/hr. Now don’t forget to also go back and manually deleted your old site collection http://portal.abc.local/sites/hr once you are sure you have successfully moved everything. I will leave how to delete to you. It always scares me to give out instructions on deleting things because you never know who might only half way read this article and mindlessly delete something on accident. It happens!


Once you finish all of this moving around you will need to do a little navigation cleanup but nothing we can’t do through site settings these days.


Shane SharePoint Help

Farm performance level: PartylReduced

The first time I encountered the screenshot below I was very confused.

I received this message after running the command: stsadm.exe –o osearch –action list

For the life of me I couldn’t figure out what I had broke. Well after a while I gave up and blamed it on the beta. ;) Later that night I was playing with the Office SharePoint Server Search when I found this configuration option for defining the indexer performance.

The rest isn’t rocket science. I am just hoping the next person who freaks out at 2 AM because they think their MOSS farm performance level is running partly reduced they can find out why.

Shane – SharePoint Help