EXCM 2010 - Prerequisite Checklist for Paid Implementations

  • IMPORTANT - Your site MUST be running Claims Based Authentication and be completely TESTED and STABLE before installing ExCM 2010.  You can either create a new Web Application and select "Claims Based Authentication" as the authentication type, or convert your existing "Classic" mode Web Application to Claims Based by running the following commands within the SharePoint 2010 Management Shell.
  • Please be sure to BACKUP YOUR CURRENT ENVIRONMENT FIRST!  Microsoft DOES NOT SUPPORT reverting back to Classic authentication after migrating to Claims.
  • Converting Classic to Claims Based Authentication with SharePoint Management Shell:
  • $w = Get-SPWebApplication "http://<server>/"
    $w.UseClaimsAuthentication = 1
  • Please note that you may need to run the "MigrateUsers" command several times in order for all users to be converted
  • You can run the following command to check the status of migrated users - "Get-SPWeb -Identity http://<siteurl> | % {$_.AllUsers} | Select LoginName".  All migrated accounts will show up with a Claims "prefix" before the username (0#.w for Windows Users and 0#.f for Forms Based Users)
  • Install .NET Framework 3.5 on each Windows Front End (WFE) server
  • Setup and test outgoing email (SMTP) from within SharePoint
  • If you are evaluating the product, request a trial license and evaluation download from here (http://sharepointsolutions.com/SharePoint-Add-ons/Pages/Request-Licensing-Key.aspx?productKey=ExCM2010)
  • If you have purchased the full product, your license key and download link for ExCM 2010 can be found in the order confirmation e-mail
  • Determine the host header (most common) or port number for the URL for the new Web Application
  • If using host headers, make the necessary changes to your local and public DNS records
  • Ensure that any required SSL certificates have been properly installed in IIS (if applicable)
  • Ensure availability and remote administrative access to the SQL Server database via SQL Management Studio
  • If you need to access the site directly from the server, please make the registry changes outlined here in Method 1 (http://support.microsoft.com/kb/896861).  This will correct a common issue of the SharePoint server not being able to access its own IIS sites using a FQDN or CNAME alias.
  • Ensure the person responsible for your firewall solution can be available during the implementation if needed.  We cannot assist in any configuration of firewall devices or software (Cisco, F5, ISA, TMG, UAG, etc.).
Have more questions? Submit a request


Article is closed for comments.