Windows SharePoint Services, SharePoint Portal Server 2003, and Microsoft Office SharePoint Server 2007 Support boundaries for Active Directory Federation Services

Supported features

• Site navigation
• List and document viewing
• List item editing (including list editing by using the Edit in datasheet control)
• Search (supported for large farm deployments, but it is not functional for single server evaluation installation)
• File download
• File upload

Unsupported features

• Using Office 2003 (or comparable) clients to open and save documents on a SharePoint server is not a supported scenario, when SharePoint is running under ADFS authentication. Even if the file is opened successfully, problems may occur if the ADFS cookie times out. If the user attempts to save the document after the cookie has expired, errors during the redirects required to re-authenticate the user may make it impossible to save the document back to the server. In this case, the user could save the document locally, and then upload it back to the server using a browser. To avoid problems, we suggest that you turn off the Office 2003 open features in SharePoint, and revert to file download and file upload by using the Web browser.
• The SharePoint Office integration features which rely on SOAP Web services running outside of the browser will not work with ADFS and are not supported. These features include Outlook synchronization such as Linking to Outlook from a Contacts list or an Events list, Export to Spreadsheet, creating a new list by Importing Spreadsheet, Export to Access, and Editing in FrontPage.
• Windows shell commands to map a drive to a site or document library or perform other operations is not supported.
• Web Folders (such as by using Network Places) which rely on the DAV redirector, will no longer work as expected. Web folders are typically created in order to have a file explorer view of a site or document library to easily copy and move files. Using this feature when SharePoint is working with ADFS is not supported.
• Independently federating the SharePoint content site and SharePoint Central Admin sites.
• SharePoint Web Parts that utilize the SharePoint Portal Server single sign on (SSO) feature to access program data is unsupported.
• Due to limitations in how ADFS handles SOAP requests, programmatic access to SharePoint data and functionality via Web Services through ADFS is not supported except when the request comes from within the content of a browser session such as from an ActiveX control.
• SharePoint Portal Services Alternate Access Mappings are not supported with ADFS Web SSO. Alternate Access Mappings allow multiple URLs that correspond to the same Internet Information Services (IIS) virtual server, or Web site.
  
  You may want to deploy a SharePoint Portal Sever site that is accessible both internally (inside the intranet) and externally (from outside the corporate firewall), but not expose the same URL to clients in the different DNS "zones". The Internal URL is similar to https://myteam, but the external URL is similar to http://partners.extranet.company.com/myteam. ADFS does NOT support this feature; for security reasons it enforces a unique Return URL for a given site or program for added security.
  
  For more information about ADFS and the Return URL, visit the following Microsoft Web site:
  http://technet2.microsoft.com/WindowsServer/en/Library/bf0cf512-7468-4bfa-bc89-5e2da40e232f1033.mspx

Removing feature functionality that is not supported

Disabling the Edit in Office Application and New Document controls

    </ByProgID>
    <ByExtension>
        <Mapping Key="doc" Value="icdoc.gif" EditText="Microsoft Office Word" OpenControl="SharePoint.OpenDocuments"/>

    </ByProgID>
    <ByExtension>
        <Mapping Key="doc" Value="icdoc.gif"/>

1. In Microsoft Windows Explorer, find the Htmltransinfo.xml file. This file is located in the following folder on the Web server:
   driveletter:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\Template\Xml
2. Right-click Htmltransinfo.xml, and then click Edit.
3. Change the file to set ProgId to empty. For example, ProgId = "".

<HtmlTrInfo> <Mapping Extension="xls" AcceptHeader="application/vnd.ms-excel" HandlerUrl="HtmlTranslate.aspx" 
ProgId="SharePoint.OpenDocuments.2"/> <Mapping Extension="doc" AcceptHeader="application/msword" HandlerUrl="HtmlTranslate.aspx" 
ProgId=""/> <Mapping Extension="ppt" AcceptHeader="application/vnd.ms-powerpoint" HandlerUrl="HtmlTranslate.aspx" 
ProgId="SharePoint.OpenDocuments.2"/> <Mapping Extension="pps" 
AcceptHeader="application/vnd.ms-powerpoint" HandlerUrl="HtmlTranslate.aspx" 
ProgId=""/> <Mapping Extension="one" AcceptHeader="" HandlerUrl="" 
ProgId="SharePoint.OpenDocuments.2"/> </HtmlTrInfo> 

<HtmlTrInfo> <Mapping Extension="xls" AcceptHeader="application/vnd.ms-excel" HandlerUrl="HtmlTranslate.aspx" 
ProgId=""/> <Mapping Extension="doc" AcceptHeader="application/msword" HandlerUrl="HtmlTranslate.aspx" 
ProgId=""/> <Mapping Extension="ppt" AcceptHeader="application/vnd.ms-powerpoint" HandlerUrl="HtmlTranslate.aspx" 
ProgId=""/> <Mapping Extension="pps" AcceptHeader="application/vnd.ms-powerpoint" HandlerUrl="HtmlTranslate.aspx" 
ProgId=""/> <Mapping Extension="one" AcceptHeader="" HandlerUrl="" 
ProgId=""/> </HtmlTrInfo>

Removing other Client-Integration Functionality

1. Implement a custom .js file. Refer to the Customizing the Shortcut Menu for List Items topic in the SharePoint Products and Technologies SDK as a guide:
   http://msdn2.microsoft.com/en-us/library/ms868274.aspx
   Create a new .js file named Custom_ows.js as the article indicates, and reference it in the corresponding Onet.xml file for the site definition files that you will be customizing. It is not necessary to implement the custom Check Out & Save command that is described in the article.
2. Edit the custom .js file to remove or modify client-integration functionality. The following code snippet, which represents the entirety of the custom .js code needed for this step, can be added to the newly-created Custom_ows.js file, as-is:

   //begin code to modify client-integration
   	
   //disables "Export to Spreadsheet" functionality and returns friendly error to user 
   function ExportList(using)
   {
       var L_ExportListSpreadsheet_Text = "This feature has been disabled on your server.";
       alert(L_ExportListSpreadsheet_Text);
   }
   	
   //removes "Link to Outlook" link
   function GetStssyncAppName(strDefault)
   {
       return false;
   }
   
   //end code to modify client-integration
   

   After steps 1 and 2 have been completed, the "Export to Spreadsheet" and the "Link to Outlook" functionality will be modified or removed from any newly-created sites based on the site definition that references the custom .js file.
3. Optionally, remove "Import Contacts" links from the "Contacts" list definitions.
   
   Note The "Import Contacts" link cannot be removed or disabled by editing the custom .js file, and requires manual editing of every contacts-based list definition (where Type=105, or custom list definitions based on the same) on the server to remove the link. Additionally, the supportability guidelines that are outlined in KB article 898631 for editing site and list definitions require that changes to Schema.xml files only be made within custom site definitions. Because of this, and because this is a fairly intensive task, administrators are advised to consider educating users about the status of this functionality rather than implementing a system-wide change to every contacts-based list definition.
   
   To remove the "Import Contacts" link, open the corresponding Schema.xml file for editing. The Schema.xml file is located in the list definition folder within the respective site definition's Lists folder, such as
   C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\Template\1033\Custom_sts\Lists\Contacts
   Within the Schema.xml file, find the section of code that is relative to the "Import Contacts" link, by searching for the string ImportFromAddressBook within the file. Remove the contents of the "CDATA" block that contains the "Import Contacts" link. For example, in the default contacts list definition, the following example code represents the state of the list definition before removing the contents of the CDATA section

   </SCRIPT>]]></HTML><HTML><![CDATA[
       <TD class=ms-separator>|</TD>
          <TD class="ms-toolbar"> <table cellpadding=1 cellspacing=0 border=0> <tr> <td class="ms-toolbar" nowrap> <a tabindex=2 ID=diidIOImportFromAddressBook class="ms-toolbar" title=]]></HTML><HTML>"Import from Address Book"</HTML><HTML><![CDATA[ ACCESSKEY=I href="javaScript:ImportFromAddressBook()" target=_self> <img src="/_layouts/images/impitem.gif" ID="tbbuttonstart1" alt=]]></HTML><HTML>"Import from Address Book"</HTML><HTML><![CDATA[ border=0 width=16 height=16></a></td> <td nowrap> <a tabindex=2 ID=diidIOImportFromAddressBook class="ms-toolbar" ACCESSKEY=I href="javaScript:ImportFromAddressBook()" target=_self>
               <LocID ID="L_ImportFromAddressBook">]]></HTML><HTML>Import Contacts</HTML><HTML><![CDATA[</LocID>
          </a> </td> </tr> </table> </TD>
   ]]></HTML>
   

   After removing the relevant code, the same code would look like the following example code:

   </SCRIPT>]]></HTML><HTML><![CDATA[
   ]]></HTML>
   

   Again, this change would need to be made for every contacts-based list definition system-wide.