[70-631] TS: Configuring Microsoft Windows SharePoint Services (WSS) 3.0 - Exam Notes

The list below is a summary of what we (probably) need to know for the 70-631 exam (configuring WSS 3.0).  More items and details on each item will come later.

  1. Use Unicast mode to solve IP address conflict problem for intra-array communication.
  2. NLB (Network Load Balancing) help distribute loads/requests across servers.
  3. Install Web server certificate from WSS server on ISA to ensure that all external requests are inspected and encrypted.
  4. Deploy ISA and publish WSS web site to prevent direct access from outside of the network to the WSS server.
  5. To decommission and migrate all sites from one server to another on a different farm, edit the host record of the old server and configure IP address of the new server.
  6. Configure AAM (Alternate Access Mapping) to allow remote users to access WSS Web site via a specific URL.
    ThinkingA SharePoint site can respond to more than one URL. In this aspect, it's similar to setting multiple URLs for a Web site in IIS.
  7. Create a host record in DNS zone with a name value of WSS that maps to the IP address of the NLB cluster to ensure that each server in the cluster receives requests for WSS content.
  8. Configure Event Throttling to write events to Windows event log.
  9. We can review the IIS logs to verify that all access to the WSS Web site is encrypted.
  10. Enabling Diagnostic Logging to have a WSS server create trace logs.
    Vampire BatTracing involves occurrences of particular events.
  11. Let MOM (Microsoft Operations Manager) take care of the services across all WSS servers.
    ChickenDon't forget to install WSS management pack for her.
  12. Also let MOM take care of the HTTP errors.
    ChickenDon't forget to install IIS management pack for her.
  13. Include Network Interface, Processor, and Physical Memory objects in a counter log to identify potential hardware bottlenecks.
  14. To remove all customizations on a page without losing any data, enable the "Reset specific page to site definition version" option in the site settings.
  15. To create a Web page with custom Web Part zone layout, use Microsoft Office SharePoint Designer 2007.
  16. An image put in the default.master file will appear on all pages in a WSS Web site.
    Light bulbA master page helps keep consistency across multiple pages.
  17. For developers - Always include error handling in the code when creating a custom Web Part.
  18. To have requests distributed across multiple servers while having the content centralized, deploy 2+ front-end servers and store content database on a single instance of SQL Server.
  19. To upgrade from WSS 2.0 to WSS 3.0 without losing any existing URL, just install WSS 3.0 over the existing WSS 2.0 deployment.
  20. To be able to access sites in languages other than English after an upgrade, we need to install the language pack template pack on WSS 3.0 server and run the SharePoint Products and Technologies Configuration wizard.
  21. If multiple WSS Web sites are run on the same WSS server, be sure to configure each Web application to run in its own application pool so that they don't affect each other.
  22. Installing WRM (Windows Right Management) client SP2+ on each front-end Web server can help prevent users from printing or saving documents.
  23. You can create a custom group and allow requests to join or leave the group so that users can automatically submit a request to obtain elevated permission levels and only approved users are granted.
  24. To ensure that external users can authenticate before they're grated access to a Web site, specify the authenticate provider in the web.config file.
  25. Enable anonymous access to Web application and Web site so that all Internet users have access to the WSS Web site.
  26. To have SSL encryption enabled for all requests, install a certificate on each front-end server that receives the requests.
  27. Obtaining a certificate from a trusted certification authority (CA) ensures that users do not receive SSL errors from their Web browser.
  28. "Members" permission level users can only view and add content to a document library. Gift with a bowRead more...
  29. Using a member of dbcreator and securityadmin SQL Server 2005 server roles as the database installation account when installing SQL Server will minimize the amount of permissions provided to all users.
  30. When using a custom authentication provider, be sure that the connection string details, membership, and role information in web.config file are for the custom authentication provider.
  31. You can add content types to a document library to specify what types of documents a user will see when he clicks on the "New" menu item.
  32. Backing up your Web application and content database using Central Administration helps minimize the time required to restore in the event of server failure.
  33. You can use STSADM.EXE to add and deploy .wsp customization file.
  34. You can also use STSADM.EXE to backup a site from one server and restore it on another server.
  35. A deleted document stays in the stage-1 (site-level) recycle bin for 30 days by default before getting purged to the stage-2 (site collection-level) recycle bin.
  36. In the case of pre-authentication failure for a specific application pool identity account, you'll need to reset the password for both the application pool identity account and the corresponding user account.
  37. To allow access to a Web site from a mobile device, activate the MobilityRedirect feature for that Web site.
  38. You can change a default database server in the Central Administration so that any new WSS Web site will store content on the new database server.
  39. You can use the Three-state workflow to ensure that operations run in order.
    PumpkinMOSS 2007 provides more OOB (out-of-box) workflow.
  40. To ensure that all users can view the public documents, in the Web application settings, configure the WSS server to use an HTML viewer server.
  41. PASSED! Peace Sign