← Return to doc.sitecore.com

Valid for Sitecore 6.x
37.  Sitecore CMS 6.2.0 Update rev.091012 (6.2 Initial Release)
Prev Next
Print this page (opens in new window) Print

Instructions for downloading and installing Sitecore CMS 6.2.0 rev.091012.
This is an old CMS 6.2.0 update.
You should only use this update as an interim update when upgrading from Sitecore CMS 6.1 to 6.2 Update-2 or later.

Important: If you are upgrading from Sitecore CMS 6.1.0, you should continue upgrading to version 6.3.0 or later and not stop the upgrade process at version 6.2.0.

Notice: This page was updated on November 26, 2009 with a new update package:

  1. The update package will no longer try to add or change items in the "web" database.
  2. The file size of the update package is now considerably smaller.
  3. A new step about moving the /data/webdav.lic file was added to the instructions. This file was missing from the previous 6.1 to 6.2 update package. If you used the old update package to upgrade your solution, download the webdav.lic file and place it in your data folder (the folder that contains the regular Sitecore license).

Prerequisites

This upgrade requires the following files:

Follow the steps below to upgrade an existing Sitecore CMS 6.1.0 installation to Sitecore CMS 6.2.0 rev. 091012:

  1. Important: If you are upgrading from Sitecore CMS 6.1.0, you should continue upgrading to version 6.3.0 or later after installing this update. The system will not work as expected if you stop the upgrade process at version 6.2.0.
  2. Back up the site.
  3. Open the Update Installation Wizard by entering the following URL in your browser: http://<hostname>/sitecore/admin/UpdateInstallationWizard.html.
    See the Update Installation Wizard Guide for more information about how to use the Wizard.
  4. Install the Sitecore CMS 6.2.0 rev. 091012 update package using the Wizard. Some expected collisions may occur, see the “Note about expected collisions” below for details.
    1. Upload the update package using the wizard.
      Note: The upload might fail due to the large file size. If you run into this problem, move the update package manually to the /sitecore/admin/Packages folder. Alternatively, you can increase the value of the maxRequestLength attribute of the configuration\system.web\httpRuntime element in the web.config file to allow upload of the large update package.
    2. Analyze the package.
    3. Install the package.
  5. Rename the following files:
    1. Rename "/App_Config/Security/Domains.config.xml" to "Domains.config"
    2. Rename "/App_Config/Security/GlobalRoles.config.xml" to "GlobalRoles.config"
  6. Update the following configuration files. You can find the exact strings to update on the Web.config Changes page.
    1. /Web.config
    2. /App_Config/Commands.config
    3. /App_Config/FieldTypes.config
  7. Configure the Analytics Data Provider (App_Confog/Include/Sitecore.Analytics.config):
    • For SQL server:
      <analyticsManager defaultProvider="default">
      <providers>
      <clear/>
      <add name="default" 
      type="Sitecore.Analytics.Data.DataProviders.AnalyticsProviderSqlServer,  
      Sitecore.Analytics"/>
      </providers>
      </analyticsManager>
    • For Oracle:
      <analyticsManager defaultProvider="default">
      <providers>
      <clear/>
      <add name="default" 
      type="Sitecore.Analytics.Data.DataProviders.AnalyticsProviderOracle, 
      Sitecore.Oracle"/>
      </providers>
      </analyticsManager>"
  8. If you are upgrading from Sitecore 6.1.0 rev. 090630, you must also apply the changes mentioned on the Web.config Changes in rev. 090722 compared to rev. 090630 page. This step is not necessary if you are upgrading from 6.1.0 rev.090722 or 6.1.0 rev.090821.
  9. Move the /indexes folder to your "data" folder (the folder that is defined in the dataFolder variable in the web.config file).
    Alternatively, change the new IndexFolder setting from "$(dataFolder)/indexes" to "/indexes" and keep the folder in its current location.
  10. If your data folder is placed outside the webroot, move the file <webroot>/data/webdav.lic to your data folder (the folder that is defined in the dataFolder variable in the web.config file).
  11. Clear your browser’s cache. For instance, in Internet Explorer this is done via the menu Tools » Internet Options » Browsing History » Delete » Delete Temporary Internet Files.
  12. Rebuild search indexes and the link database in the master and in the core databases. You can do this using the wizards available via the Sitecore desktop link Sitecore » Control Panel » Database.
  13. Consider to perform the optional steps below, including the clean-up.
  14. Reiterate the update procedure for every Sitecore instance in your Sitecore environment.

Optional steps

  1. The /sitecore/shell/Security.templates.xml file is no longer used by Sitecore and can be deleted.
  2. The following files in the /sitecore/admin folder are obsolete and should be deleted if you don't use them:
    • CompareSubtrees.html
    • DumpIndex.html
    • Reflect.html
    • SizeTester.html
    • UnitTestCacheClear.html
    • UnitTestLogin.html
  3. By default, Sitecore CMS 6.2.0 will use theme icons stored in zip-files. You can delete old icons and folders in the \sitecore\shell\Themes\Standard folder if they are not used for custom purposes and if you haven't added custom icons to any of the folders. Be careful not to delete any of the following folders:
    • ComponentArt
    • Custom
    • Default
    • Firefox
    • Gradients
    • Images
    • Internet Explorer
    • Reports  

Clean-up

The update package installs *.config files side-by-side to the original files to make it easier to merge configuration file changes. It is recommended to remove these extra config files after updating. This typically applies to the following files:

Note about expected collisions

If you are upgrading from a release later than Sitecore CMS 6.1.0 rev. 090630, you will see warnings that a number of files have been modified and will be overwritten. This is expected behavior for the following files (you might only see some of the warnings, depending on which release you are upgrading from)


Prev Next