More Advanced Settings for MOSS and WSS


SharePoint 2007 is full of configuration settings, more than this book can cover. You have now seen most of them described in detail, but there are some more that are valuable to understand.

Information Rights Management

This is a separate Microsoft application, also known as Rights Management Server (RMS). Its purpose is to enable users to define the permissions for an MS Office document or an Outlook e-mail in much greater detail than is normally possible. This requires that the RMS server be installed and configured in your network, but not necessarily on the SharePoint server. However, the SharePoint administrator must install the RMS client on the MOSS server in order to activate the IRM features in SharePoint.

Note 

Download this RMS client with Service Pack 2 from http://www.microsoft.com.

When the RMS client is installed, you must configure SharePoint to enable the Information Rights Management feature, as illustrated in the following Try It Out.

Try It Out Configure IRM

image from book
  1. Open the Central Administration tool, and switch to the Operations page.

  2. Click Information Rights Management.

  3. Select the RMS server to be used. Typically, you will use the option Use the default RMS server specified in Active Directory.

  4. Click OK to save and close the page.

image from book

When this is done, you can configure document libraries to enable IRM permissions, such as Prohibit Save, and Prohibit Printing of Office documents. These permission settings will still be valid even if this document is moved or copied to another location; for example, if it used as an e-mail attachment. This is an important requirement in many situations; for example, for compliance with the Sarbanes-Oxley Act and the Health Insurance Portability and Accountability Act (HIPAA).

Managing Blocked File Types

Since SharePoint will replace your file servers, at least partly, Microsoft has made it possible to prohibit users from uploading all types of files. This is done mainly to ensure that no file type that could carry a virus or Trojan horse can be stored inside SharePoint. But in some situations, this is not acceptable. For example, users may need to store EXE files in a SharePoint document library. The following Try It Out shows how to manage these blocked file types.

Try It Out Configure Blocked File Types

image from book
  1. Open the Central Administration tool, and switch to the Operations page.

  2. Click on Blocked file types.

  3. On the next page, you will see a list with all the file types that are blocked. Mark the file type you want to unblock, and then press the Delete button on your keyboard.

  4. If you want to block another file type, such as .mp3 or .avi, simply add them anywhere in this list. Just make sure that there is only one file type per line.

  5. Click OK to save and close this page.

image from book

The new settings will be active immediately. Note that if you have blocked a file type, and there are such files already stored in SharePoint, they will still be stored, but you cannot store any new files of this type.

Important 

Save a copy of all the default blocked file types. Place the cursor anywhere in the list, press Control+A to mark them all, and press Control+C to copy them. Then open Notepad and paste this information in it.

Managing Diagnostic Logging

An important task for any administrator is to check the health of the system; this is definitely true also for SharePoint 2007. Using the Diagnostic Logging feature in the Central Administration tool allows the administrator to configure what types of errors are stored in the Windows 2003 Event Log, and in SharePoint's own Trace Log. Use the steps in the following Try It Out to configure diagnostic logging.

Try It Out Configure Diagnostic Logging

image from book
  1. Open the Central Administration tool, and switch to the Operations page. Click Diagnostic logging in the Logging and Reporting section.

  2. The two first sections on this page allow you to configure if the server will participate in Microsoft's Customer Experience Improvement program, and if error reports should be collected. These two settings are used by Microsoft to understand what may go wrong and help them design a better SharePoint server. If you do not mind, then enable these features.

  3. The third section, Event Throttling, is about what level of severity of events you want to store in the Windows event log, and in SharePoint's trace logs, using these settings:

    1. In the Select a category menu, select the type of service or feature to be configured; for example, Backup and Restore.

    2. In the Least critical event to report to the event log menu, chose one of the severity levels: None, Error, Warning, Audit Failure, Audit Success, or Information.

    3. In the Least critical event to report to the trace log menu, chose between None, Unexpected, Monitorable, High, Medium, and Verbose.

  4. The fourth section; Trace Log allows you to configure the trace log settings:

    1. In the Path field, enter the file path to the folder where these trace log files will be stored. The default is: c:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Logs\.

    2. In the Number of log files setting, define how many of these trace log files to store. When this number is reached, the oldest log files will be deleted.

    3. In the Number of minutes to use a log file setting, define how many minutes a log file will be used. When this number is exceeded, the log file is closed, and a new log file is created.

Important 

These trace log files will typically be many megabytes in size; you may want to reduce the number of log files to avoid filling up your disk space. You may also want to change the path for these log files to avoid storing them under \Program Files.

image from book



Beginning SharePoint 2007 Administration. Windows SharePoint Services 3 and Microsoft Office SharePoint Server 2007
Software Testing Fundamentals: Methods and Metrics
ISBN: 047143020X
EAN: 2147483647
Year: 2004
Pages: 119

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net