Preparing for the Sharepoint v3 upgrade

The following steps may be accomplished before production service outage begins:

  • Install OS Services in support of Sharepoint 
  • Install .NET 3.0 framework
    • ensure that ASP.NET is installed on IIS server, make sure that ASP.NET 2.0 is activated:
      (run C:WINDOWSMicrosoft.NETFrameworkv2.0.50727aspnet_regiis -i
  • Install WSSv3 (but cancel the configuration wizard)
  • Perform admin site config:
    • Configure to use NTLM authentication, NOT KERBEROS!
    • set incoming and outgoing email settings.
      • Requires SMTP server running on WSS server, mail domain set to be the same as that of the Sharepoint server config.
  • configure Search Services
  • define quota templates (create 5 and 10 Gb quotas)(cannot assign to application yet, but can create)

These procedures to be completed duing the announced service window:

  • Run the “prescan” tool from the “
    C:Program FilesCommon FilesMicrosoft Sharedweb server extensions12BIN>” directory on the wssv3 server on the production site
  • Set the production server DB to read-only
  • Back up the DB
  • Restore the DB to WinDB, set to SQL v9 compatibility, restore permissions to the DB for the new production server (wss content app pool and wss access accounts)
  • Create new “Web Application”:
    • Map search services to the application
    • Add SSL redirect to the IIS site that is created (replace the 403.4 error page with a custom Java Script redirect
  • Replace new content DB with copied content DB on WinDB.  Use command-line “STSADM” tool as Web GUI will not work here.
  • Extend the new application to allow for Extranet config:
    • Create an additional IIS web site which listens on an alternative IP address/port
    • In Application Management, click “Create of extend web application”
    • Click “Extend an existing web application”
    • Choose to use an existing IIS site, select the site you just created, and select this app as being in the “Extranet” zone.
    • return to IIS management, make sure the IIS site is configured to listen on the appropriate IP and ports, ensure SSL is enabled, and replace the 403.4 error page on this site, too.
      • Make sure that BOTH IIS sites have SSL bound to a specific IP address, otherwise port conflicts will occur!
    • Enter “Alternative Access Mappings” from the “Operations” page. Add a new “internal URL” for the extranet site.
    • Enter “Authentication Providers” from “Application Management”. For the “Extranet” zone, Specify “Windows Authentication”, “enable anonymous”, “basic authentication”… may also need to disable “client integration” features.
  • Restore custom settings to the site:
    • web application general settings – set Time Zone, default quota template, increase max upload size, activate Blog API auth, turn off “send password”.
    • Self-service site creation – activate, require secondary contact
    • Site use confirmation and deletion (set to 365, monthly, 3 notifications)
    • others?
    • Do “alternative access mappings” in Operations->Global Configuration. Use FQDN of service!
      • Add FQDN for extranet access as well, going to extranet zone.
  • Configure Search (only necessary if unable to map to an existing search service, above):
    • create service account
    • run stsadm -o spsearch -action attachcontentdatabase -databaseserver WINDB -databasename [DBname] -searchserver WSS3TEST
    • run stsadm -o spsearch -action start -farmserviceaccount campussa_wss3test_search -farm
      servicepassword [password] -databaseserver WINDB -databasename [searchDB]
    • install additional iFilters (?)
  • Install MindManager extension
  • Perform Extranet config… have not modeled this yet so steps TBD.
  • Fix self-service site creation link on home page, if necessary.
  • Add announcements to sites/ad/
  • Take down old Sharepoint server
  • Appropriate production IP addresses
  • Install site SSL cert from production site.
  • Testing:
    • Open several sites just to see if general functionality is present
    • Test URL redirection:
    • Test incoming e-mail
      • Activate on a site library and discussion list, attempt to post with e-mail
    • Test workflow
      • Create a workflow, assign to library, make mods which would trigger workflow.
    • Test recycle bin operations.
    • Test new site creation
    • Test backup AND MORE IMPORTANTLY restore of a single site
Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s