citrix web interface for microsoft sharepoint...

Citrix Web Interface for Microsoft® SharePoint™Administrator’s Guide

Citrix Web Interface for Microsoft® SharePoint™Citrix® Access Suite™ 4.2

Use of the product documented in this guide is subject to your prior acceptance of the End User License Agreement. Note that copies of the End User License Agreement are included in the root directory of the installation media.

Copyright and Trademark Notice

Information in this document is subject to change without notice. Companies, names, and data used in examples herein are fictitious unless otherwise noted. Other than printing one copy for personal use, no part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Citrix Systems, Inc.

Copyright © 2006 Citrix Systems, Inc. All rights reserved.

Citrix, ICA (Independent Computing Architecture), Citrix Solutions Network, MetaFrame, MetaFrame XP, Program Neighborhood, and SpeedScreen are registered trademarks or trademarks of Citrix Systems, Inc. in the United States and other countries.

Trademark Acknowledgements

Java, Sun, and SunOS are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries.

Microsoft, MS-DOS, Windows, Windows NT, Win32, Outlook, Office, Internet Information Services, SharePoint, SQL Server, ActiveX, and Active Directory are either registered trademarks or trademarks of Microsoft Corp. in the United States and/or other countries.

Novell Directory Services, NDS, and NetWare are registered trademarks of Novell, Inc. in the United States and other countries. Novell Client is a trademark of Novell, Inc.

UNIX is a registered trademark of The Open Group.

This product incorporates IBM's XML Parser for Java Edition, © 1999, 2000 IBM Corporation.

All other trademarks and registered trademarks are the property of their owners.

Last Updated: August 3, 2006 (IAT)

Contents 3

Contents

Chapter 1 IntroductionHow to Use this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Accessing Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Introducing the Web Interface for Microsoft SharePoint . . . . . . . . . . . . . . . . . . . . . 8The Web Interface for Microsoft SharePoint Features . . . . . . . . . . . . . . . . . . . . . . . 8

Citrix Presentation Server Web Part. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Content Redirection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Citrix Custom Menu Web Part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Administration Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Other Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Excluded Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

File Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Chapter 2 Planning Your DeploymentDeployments Specifically Supported by SharePoint. . . . . . . . . . . . . . . . . . . . . . . . 11

Supported Deployments Quick Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Deployment Reference for SharePoint Services . . . . . . . . . . . . . . . . . . . 12Deployment Reference for SharePoint Portal Server. . . . . . . . . . . . . . . . 13

Points to Note . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Single Server Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Small Server Farm Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Medium Server Farm Deployment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Large Server Farm Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Deployments Specifically Supported by Citrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Secure Gateway Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Secure Gateway and Proxy Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Additional Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Access Gateway with Advanced Access Control Deployment . . . . . . . . . . . . . 19

Unsupported Deployments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

4 Administrator’s Guide

Chapter 3 Installing the Web Interface for Microsoft SharePointSystem Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Operating System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Other Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22SQL Server Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

About the Web Interface for Microsoft SharePoint Installer . . . . . . . . . . . . . . . . . 22Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Single Server and Small SharePoint Server Farm . . . . . . . . . . . . . . . . . . . . . . . 23Load Balanced SharePoint Portal Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Choosing Your Installation Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Installing the Web Interface for Microsoft SharePoint . . . . . . . . . . . . . . . . . . . . . . 25Post-Installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Editing the wisp_trust.config file to support site access through FQDNs or IP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Adding the Web Interface for Microsoft SharePoint Web Part to a Web Part Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Adding the Citrix Custom Menu Web Part to a Web Part Page . . . . . . . . . . . . 29Adding the Citrix Custom Menu Web Part to Document Library or Shared Documents Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Merging the Context Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Customizing the Appearance of the Web Part . . . . . . . . . . . . . . . . . . . . . . . . . . 34Advanced Customization of the Web Part User Interface . . . . . . . . . . . . . . . . . 35

Repairing the Web Interface for Microsoft SharePoint Installation . . . . . . . . . . . . 36Missing WebParts and Unloaded Configuration . . . . . . . . . . . . . . . . . . . . . . . . 37

Uninstalling the Web Interface for Microsoft SharePoint. . . . . . . . . . . . . . . . . . . . 38Before Uninstalling the Web Interface for Microsoft SharePoint . . . . . . . . . . . 38Uninstalling the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Changes to Security Configuration Information . . . . . . . . . . . . . . . . . . . . . . . . 39

Contents 5

Chapter 4 Configuring the Web Interface for Microsoft SharePointConfiguring the Web Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41About the Administration Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Prerequisites for Windows 2003 Server Users. . . . . . . . . . . . . . . . . . . . . . . . . . 42Accessing the Administration Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Layout and Usage of the Administration Tool. . . . . . . . . . . . . . . . . . . . . . . . . . 44

Managing Web Interface for Microsoft SharePoint Using the Administration Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Managing Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Setting Anonymous Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Setting Single Sign-On in a Pass-Through Environment . . . . . . . . . . . . . 47Setting Single Sign-On in a Kerberos Environment. . . . . . . . . . . . . . . . . 47Setting Single Sign-On in a SharePoint Portal Server Environment . . . . 48

Managing Client Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Configuring Automatic Client Download . . . . . . . . . . . . . . . . . . . . . . . . 50Configuring Legacy Client Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Managing Client Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Enabling or Disabling Bandwidth Control . . . . . . . . . . . . . . . . . . . . . . . . 53Enabling or Disabling PDA Synchronization. . . . . . . . . . . . . . . . . . . . . . 53Configuring Windows Key Behavior. . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Managing Server Farms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Adding Server Farms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Renaming Server Farms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Removing Server Farms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Modifying the Failover Order of Server Farms . . . . . . . . . . . . . . . . . . . . 57Adding Servers to Server Farms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Renaming Servers in Server Farms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Removing Servers from Server Farms . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Managing Global Farm Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Managing Global Server Settings per Farm . . . . . . . . . . . . . . . . . . . . . . . 60

Managing Smooth Roaming (Workspace Control) . . . . . . . . . . . . . . . . . . . . . . 62Configuring Workspace Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Managing Content Redirection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Adding a New File Extension. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Removing an Existing File Extension . . . . . . . . . . . . . . . . . . . . . . . . . . . 64


Manually Editing WebInterface.conf File Parameters . . . . . . . . . . . . . . . . . . . . . . 65Exporting the WebInterface.conf file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Importing a .conf file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Using Reload after Manual Changes to Configuration . . . . . . . . . . . . . . . . . . . 68Using Resave after Changes to Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 68Configuring Web Interface for Microsoft SharePoint with Secure Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Configuring Web Interface for Microsoft SharePoint with Access Gateway with Advanced Access Control . . . . . . . . . . . . . . . . . . . . . . . 70Configuring Web Interface for Microsoft SharePoint with Access Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Configuring Web Interface for Microsoft SharePoint with HTTP or SOCKS Proxies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Changing the File Exchange Protocol and Port Number in Web Interface for Microsoft SharePoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Configuring Content Redirection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Disabling Content Redirection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Reestablishing Content Redirection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Removing Content Redirection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Restoring Content Redirection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Appendix A Web Interface Configuration File Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Web Interface for Microsoft SharePoint Settings . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Appendix B Configuring the Single Sign-On Service with SharePoint Portal Server . . . . . . . . . 87Correcting the ImagePath Value for the Microsoft Single Sign-on Service. . . . . . 87Configuring Single Sign-On . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

CHAPTER 1

Introduction

The Citrix Web Interface for Microsoft SharePoint allows you to deploy Presentation Server published applications and resources in a SharePoint environment. You embed the Web Interface for Microsoft SharePoint Web Part in the relevant pages within your SharePoint site, allowing users to access their published applications and content.

Use this document to find information about:

• The deployments specifically supported by Microsoft SharePoint and other considerations and requirements specific to Web Interface for Microsoft SharePoint.

• The features that are included in this release of the Web Interface for Microsoft SharePoint.

• How to install and configure the Web Interface for Microsoft SharePoint.

• How to use this documentation and obtain technical support. For details about technical support, see “Obtaining Technical Support” on page 9.

How to Use this GuideThe Web Interface for Microsoft SharePoint Administrator’s Guide is for Citrix administrators and Web masters responsible for installing, configuring, and maintaining Citrix Presentation Server and Web Interface for Microsoft SharePoint. This is a task-based guide to help you set up the Web Interface for Microsoft SharePoint quickly and easily.

This chapter introduces the documentation and the Web Interface for Microsoft SharePoint features. Subsequent chapters explain how to deploy and configure the Web Interface for Microsoft SharePoint.

This guide assumes knowledge of Citrix Presentation Server, Microsoft SharePoint, and Internet Information Services (IIS) Manager.


Accessing DocumentationTo view, search, and print the PDF documentation, you need to have the Adobe Reader 5.0.5 with Search or Adobe Reader 6.0 through 7.0. You can download Adobe Reader for free from Adobe Systems’ Web site at http://www.adobe.com/.

Introducing the Web Interface for Microsoft SharePointThe Web Interface for Microsoft SharePoint provides SharePoint users with access to Citrix Presentation Server resources using one of the following Web browsers:

• Microsoft Internet Explorer 5.01 with Service Pack 2

• Internet Explorer 5.5 with Service Pack 2

• Internet Explorer 6

• Netscape Navigator 6.2 or later

• Mozilla 1.4 or later

You can deploy the Web Interface for Microsoft SharePoint on Microsoft Windows SharePoint Services 2.0 and Microsoft Office SharePoint Portal Server 2003.

The Web Interface for Microsoft SharePoint FeaturesThis release of the Web Interface for Microsoft SharePoint includes the following features.

Citrix Presentation Server Web PartThe Citrix Presentation Server Web Part displays resources to users, which they can access in a server farm. It also allows them to launch these resources. Packaging this as a Web Part allows a SharePoint Web Designer to add the ability to access these resources from any page in the SharePoint site.

Content RedirectionContent Redirection allows users to access content stored in the SharePoint site using published applications. This is important if users cannot install applications locally. This feature works over the whole SharePoint site and integrates with HTML anchor to (<a>) tag links and Document Library Web Parts.

Chapter 1 Introduction 9

Note Content Redirection does not work as expected with Clients that use any version of the Windows 2000 operating system, due to the way that Windows 2000 interoperates with Microsoft Office. You will note different behavior between Web Part pages that contain uploaded documents and the Document Library Web Part. Documents uploaded to a Web Part page appear in both the Web Part page and the Document Library Web Part, as expected. Clicking on a document within the Document Library Web Part opens the document using the application on the local client as expected. However, clicking on a document within the Web Parts page opens the document using the published application on the server running Citrix Presentation Server, instead of the local application on the client.

Citrix Custom Menu Web PartThe Microsoft SharePoint standard Document Library Web Part provides a menu that lets users edit files using applications installed locally. The Citrix Custom Menu Web Part modifies the existing Document Library menu, allowing users to open and edit documents using published applications. This gives users explicit control over how they access their documents.

Administration ToolThe Administration Tool is a Web-based tool that allows you to manage all aspects of Web Interface for Microsoft SharePoint.

Other FeaturesThe Web Interface for Microsoft SharePoint also includes the following functionality currently available in the Web Interface and Citrix Presentation Server:

• Display of published resources available for the user organized into Program Neighborhood folders

• Access to published resources, including anonymous resources, using seamless connections

• Integrated Windows Authentication

• Anonymous Authentication

• Workspace Control functionality, as follows:

• Reconnect

• Disconnect

• Logout


• Zone Preference and failover

• Secure Gateway support for accessing published resources

• Session Reliability (not for sessions routed through Secure Gateway)

• Access Gateway with Advanced Access Control support

• Farm Aggregation, assuming a single set of credentials for all farms

• Secure SSL communication with Citrix Presentation Server and the Secure Ticket Authority

• Network address translation (NAT) firewall support

• Client-side proxy support

• Automatic client download of the Win32 Client

• PDA Synchronization

Excluded FeaturesThe following Web Interface and Citrix Presentation Server features are not included in this version of the Web Interface for Microsoft SharePoint:

• Client for Java support

• Reconnect at Login functionality if using Workspace Control

• Explicit, Forms-based authentication

• NDS authentication

• Smart card authentication

• Explicit support for Non-Win32 client devices

File LocationsThroughout this document, the following file locations are used:

• common files usually C:\Program Files\Common Files\

• webroot usually C:\inetpub

• sharepoint usually common files\Microsoft Shared\web server extensions\60\

CHAPTER 2

Planning Your Deployment

This chapter describes deployments supported by the Web Interface for Microsoft SharePoint. It provides details about deployments specifically supported by SharePoint, and also contains information about other considerations and requirements specific to the Web Interface for Microsoft SharePoint.

Microsoft Windows SharePoint Services 2.0 is a collection of services for Microsoft Server 2003 used to share information and foster collaboration with other users. Microsoft Office SharePoint Portal Server 2003 is a scalable, enterprise portal server built upon SharePoint Services that allows aggregation of services and content.

Deployments Specifically Supported by SharePointMicrosoft SharePoint Portal Server supports many different deployment scenarios, or topologies, including deployments on SharePoint server farms. Some topologies are also valid for Microsoft SharePoint Services deployments. Topologies not supported by Microsoft are not suitable for running the Web Interface for Microsoft SharePoint components.

The Topology Manager allows different physical servers within a Sharepoint server farm to run different components. These components are as follows:

• Web. Servers running this component provide access to the portal from Internet browsers.

• Search. Servers running this component provide functionality to search the portal.

• Index. Servers running this component provide functionality to index the content of a portal.

• Job. Servers running this component manage additional services that are available only for Portal Server, including:

• Hosting Single Sign-On pages


• Importing user profiles

• Performing audience calculations

• Crawling and indexing the portal site content

• Hosting the Alerts Service

If you are running SharePoint Portal Server in a load balanced environment, you must ensure that the host header in Internet Information Services is set on all of the servers.

Supported Deployments Quick ReferenceDeployment Reference for SharePoint ServicesThe table below shows valid and invalid deployments for SharePoint Services. It also shows where to deploy each software component for specific deployments.

Type Valid? Web Search Index Job WMSDE SQL Server

Single Server

Yes Single server assigned all components Install on same server as Microsoft SharePoint

No

Small Server Farm

Yes Single server assigned all components No Install on separate server

Medium Server Farm

No N/A N/A N/A N/A N/A N/A

Large Server Farm

No N/A N/A N/A N/A N/A N/A

Chapter 2 Planning Your Deployment 13

Deployment Reference for SharePoint Portal ServerThe table below shows valid deployments for SharePoint Portal Server. It also shows where to deploy each software component for specific deployments.

Important If you are running Windows Server 2003, Web Edition, you must ensure Microsoft SQL Server 2000 with Service Pack 3a is deployed on a separate computer.

Points to NoteNote the following:

• Sharepoint can be installed on all editions of Microsoft Windows Server 2003.

• Single server deployment (which uses WMSDE on the same computer) is not supported on Microsoft Windows Server 2003, Web Edition. This is because Microsoft SQL Server 2000 with Service Pack 3a must be deployed on a separate computer for Microsoft Windows Server 2003, Web Edition.

• You must be running Microsoft SQL Server 2000 Service Pack 3a or higher.

• The Job server must be running the Index component.

• There can be only one Job server in the SharePoint server farm.

Type Valid? Web Search Index Job WMSDE SQL Server

Single Server

Yes Single server assigned all components Install on same server as Microsoft SharePoint

No

Small Server Farm

Yes Single server assigned all components No Install on separate server

Medium Server Farm

Yes 1 or 2 servers assigned both components

Single server assigned both components

No Install on separate server

Large Server Farm

Yes 2-8 servers assigned Web component

2-4 servers assigned Search component

1-4 servers assigned Index component

Assigned to a single server also assigned the Index component.

No Install on any number of separate servers


• The single server scenario is not recommended for any Portal Server deployment that utilizes the Microsoft Single Sign-On Service.

• For a medium or large farm deployment that utilizes the Single Sign-On Service, Microsoft recommends that the Index/Job Server component is located on a different machine from the Web Component.

• To obtain the highest level of security for the Single Sign-On Service, locate the Web components, Index Component, and SQL Servers on different machines.

Single Server Deployment

The simplest deployment is the single server deployment. This deployment is valid for SharePoint Services and SharePoint Portal Server.

• One computer is assigned Web, Search, and Index components. This computer also runs as the Job server.

• Windows Microsoft SQL Server 2000 Desktop Engine (WMSDE) is also installed. SQL Server 2000 Desktop Engine differs from standard MSDE in that it is not limited to five concurrent connections or a database size of 5GB. However, SQL Server 2000 Desktop Engine allows no access for remote users and allows only database schemas signed by Microsoft.

• Microsoft Small Business Server 2003 is included in this scenario. SharePoint Services is installed by default with a Small Business Server deployment.


Small Server Farm Deployment

The simplest farm deployment is the small server farm deployment. This deployment is valid for SharePoint Services and SharePoint Portal Server.

• One computer is assigned Web, Search, and Index components. This computer also runs as the Job server.

• One or more computers runs SQL Server 2000.

This is the minimum case. The SQL Server can be clustered over many physical servers for failover, but the deployment will still remain a small server farm.

Note SQL Server Desktop Engine (WMSDE) is not supported in this configuration because it cannot be accessed remotely.


Medium Server Farm Deployment

This deployment is valid only for SharePoint Portal Server.

• One or two computers are assigned the Web and Search components. If there are two servers, these can be load balanced using the stateless Network Load Balancing component built into Windows Server 2003, or another load balancing product.

• One computer is assigned the Index component. This computer also runs as the Job server.

• One or more computers runs SQL Server 2000.


Large Server Farm Deployment

This deployment is valid only for SharePoint Portal Server.

• Between two and eight load balanced servers are assigned the Web component.

• Between two and four servers are assigned the Search component.

• Between one and four computers are assigned the Index component. One of these computers also runs as the Job server.

• Any number of computers run SQL Server 2000. These are clustered together to form a single, load balanced, fault tolerant database.


Deployments Specifically Supported by CitrixThe following sections relate to deployments specifically supported by Citrix. In each case where SharePoint is referenced, it refers to any of the deployments specifically supported by SharePoint.

Secure Gateway Deployment

The use of SharePoint as an alternate user interface for Secure Gateway is supported. This allows users to securely access applications and content stored in SharePoint from remote devices.

Note Secure Gateway support is not available through the Web Interface for Microsoft SharePoint Administration Tool. See “Using Resave after Changes to Configuration” on page 68.


Secure Gateway and Proxy ServersThe Web Interface for Microsoft SharePoint supports the use of Secure Gateway in single and double hop mode. It also supports the use of client-side HTTP or SOCKS proxies in much the same manner as the Web Interface.

Note Proxy server support is not available through the Web Interface for Microsoft SharePoint Administration Tool. See “Configuring Web Interface for Microsoft SharePoint with HTTP or SOCKS Proxies” on page 73.

Additional RestrictionsTo simplify the deployment process for Citrix Web Interface for Microsoft SharePoint, there is a restriction that only one Internet Information Services virtual server per physical machine can be deployed with SharePoint Services or SharePoint Portal Server.

Access Gateway with Advanced Access Control DeploymentThe Web Interface for Microsoft SharePoint can also be deployed in an environment that uses Access Gateway with Advanced Access Control.


In this scenario, the Access Gateway with Advanced Access Control must be configured with a Web resource pointing to Web Interface for Microsoft SharePoint, and must be running in Secure Gateway emulation mode. Citrix only supports the Access Gateway with Advanced Access Control deployment with external SharePoint clients, and deployments that use internal SharePoint clients are not supported.

Note Access Gateway with Advanced Access Control support is not available through the Web Interface for Microsoft SharePoint Administration Tool, but can be configured manually. For more information, see “Configuring Web Interface for Microsoft SharePoint with Access Gateway with Advanced Access Control” on page 70.Access Gateway without Advanced Access Control is also supported by manual configuration. For more information, see “Configuring Web Interface for Microsoft SharePoint with Access Gateway” on page 72.

Unsupported DeploymentsThe following deployments are explicitly unsupported and should be avoided.

• Installing SQL Server on a server running a component of SharePoint Portal Server

• Installing Web, Search, and Index components on the same servers in a SharePoint server farm

• An Access Gateway with Advanced Access Control deployment with internal SharePoint clients

CHAPTER 3

Installing the Web Interface for Microsoft SharePoint

This chapter explains how to install and configure the Web Interface for Microsoft SharePoint.

Topics in this chapter include:

• System Requirements

• Installing the Web Interface for Microsoft SharePoint

• Post-Installation Tasks

• Repairing the Web Interface for Microsoft SharePoint Installation

• Uninstalling the Web Interface for Microsoft SharePoint

System RequirementsBefore installing the Web Interface for Microsoft SharePoint, you must ensure your servers meet all the system requirements.

Operating System RequirementsYou can run the Web Interface for Microsoft SharePoint on Windows Server 2003 (Standard, Enterprise, Datacenter, or Web Edition).

Important If you are running Windows Server 2003, Web Edition, you must ensure Microsoft SQL Server 2000 with Service Pack 3a is deployed on a separate computer.


Other RequirementsThe following software must be installed prior to installing the Web Interface for Microsoft SharePoint:

• Visual J#.NET Version 1.1

• .NET Framework 1.1 Service Pack 1

• Windows SharePoint Services 2.0 with WSS Service Pack 1—or—Microsoft Office SharePoint Portal Server 2003 with WSS Service Pack 1 and SPS Service Pack 1

You must also ensure that the server on which you want to run the Web Interface for Microsoft SharePoint is configured as an Application Server with Internet Information Services 6.0 and ASP.NET, but without FrontPage extensions.

SQL Server RequirementsIf you are using an environment that uses Microsoft SQL Server 2000 for the SharePoint database, then you must ensure that the local administrator you intend to use to run the installation has System Administrator rights to the SharePoint configuration database running on Microsoft SQL Server 2000.

About the Web Interface for Microsoft SharePoint InstallerThe installer overwrites SharePoint’s existing security settings. SharePoint is installed with locked down security permissions. By default two “WSS_Minimal” and “WSS_Medium” profiles are created, which have corresponding security configurations located in the sharepoint\CONFIG directory named wss_minimaltrust.config and wss_mediumtrust.config, respectively. The permissions contained within these default profiles are insufficient for Web Interface for Microsoft SharePoint to operate correctly. When Web Interface for SharePoint is installed, it creates two files, wisp_minimaltrust.config and wisp_mediumtrust.config. These are templates used to generate the final file wisp_trust.config. These files contain the same permissions as the corresponding default WSS files but with the following additional SecurityClass Names:

• EnvironmentPermission

• FileIOPermission

• SharePointPermission

• WebPermission

• SingleSignonPermission (SharePoint Portal Server only)

Chapter 3 Installing the Web Interface for Microsoft SharePoint 23

In the ASP.Net NamedPermissionSet the above SecurityClass Names are utilized.

As part of the install procedure the WebPermission IPermission class is modified so that the URI reflects the actual value that will be used when the WebPart communicates with the back-end service provider. If you want the SharePoint site to be accessed using Fully Qualified Domain Names then these must be manually added as additional URI elements. For more information, see “Editing the wisp_trust.config file to support site access through FQDNs or IP Addresses” on page 27.

Installation OverviewThe installation procedure differs depending on your SharePoint deployment:

Single Server and Small SharePoint Server FarmIn a single server environment or a small SharePoint server farm environment, you run the installer on the server running SharePoint. In the single server environment, the configuration settings are stored on the local database. In a small SharePoint server farm, the Job Server and Web Server are on the server running SharePoint and the configuration settings are stored on a separate database server.

Load Balanced SharePoint Portal ServerIn a load balanced SharePoint Portal Server environment, you install the Administration Tool on the Job Server and you install the other components on the relevant front-end Web Servers. The configuration settings are stored on a separate database server. The Administration Tool on the Job Server has read/write access to the database. The components on the front-end Web Servers have read only access to the database. When you make changes to the configuration using the Administration Tool, the front-end Web Servers read the latest configuration information from the database. Therefore, you must ensure that the database is running before you install the product or make any configuration changes. In this environment, you must install and configure the deployment in the following order:

• Run the Installer to install the Administration Tool component on the Job Server. For more information, see “Installing the Web Interface for Microsoft SharePoint” on page 25.

• Use the Administration Tool to configure your Web Interface for Microsoft SharePoint settings to suit your environment. For more information, refer to Chapter 4, “Installing the Web Interface for Microsoft SharePoint.”

• Run the installer to install the other components on the front-end Web Servers. For more information, see “Installing the Web Interface for Microsoft SharePoint” on page 25.


Choosing Your Installation TypeThe Installer allows you to choose between the following installation options:

• Typical or Complete. Installs the Web Interface for Microsoft SharePoint Administration Tool, Content Redirection, and the Web Parts components. This option is appropriate when you are running Windows SharePoint Services or SharePoint Portal Server in a single server configuration.

• Custom. Allows you to choose to install the Administration Tool component, Content Redirection component, and/or the Web Parts component. This option is appropriate when you are running a load balanced SharePoint Portal Server environment or an environment that uses the Access Gateway with Advanced Access Control.

Typically, the Administration Tool component must be installed only on one server in the deployment. In a load balanced SharePoint Portal Server environment and an environment that uses the Access Gateway with Advanced Access Control, the Administration Tool component is installed on the Job Server. In a load balanced SharePoint Portal Server environment Citrix recommends that you install the Administration Tool component on the Job server before you install the other components on the front-end Web servers.

When using Access Gateway with Advanced Access Control, Content Redirection is performed by the Access Gateway with Advanced Access Control. Therefore, the content redirection component is applicable only to deployments that do not use the Access Gateway with Advanced Access Control. The content redirection component is applicable only to either the single server SharePoint environment or the load balanced SharePoint Portal Server environment, where it is installed only on the front end Web Servers and not on the Job Servers.

Note The custom Installer option allows you to choose the different components that are installed. However, when you re-run the installer it does not allow you to install a new component and uninstall an existing component at the same time. In the case where you want to install a new component and uninstall an existing component, you must run the Installer to remove the desired components, and then re-run the Installer and select the required components for installation.


Installing the Web Interface for Microsoft SharePointThis explains how to install the Web Interface for Microsoft SharePoint on your server.

If your deployment consists of a small SharePoint server farm, install the Web Interface for Microsoft SharePoint on a single server only. If your deployment consists of a medium or large SharePoint server farm, install the Web Parts and Infrastructure component on each server running the Web component, and the Administration Tool component on the Job Server.

For more information about SharePoint server farms and server components, see Chapter 2, “Planning Your Deployment.”

To install the Web Interface for Microsoft SharePoint

1. Log on as a local administrator.

2. Run WISP.msi.

3. On the Welcome to the Citrix Web Interface for Microsoft SharePoint Installation Wizard screen, click Next.

4. On the License Agreement screen, select I accept the license agreement and click Next.

5. On the Select Installation Type screen, select one of the following installation options:

• Typical or Complete. Installs all of the components (that is, the Web Interface for Microsoft SharePoint Administration Tool, the Content Redirection component, and the Web Parts component). This option is appropriate when you are running Windows SharePoint Services or SharePoint Portal Server in a single server configuration. Go to step 7.

• Custom. Allows you to install the Web Interface for Microsoft SharePoint Administration Tool, Content Redirection component, and/or the Web Parts component. This option is appropriate when you are running a load balanced SharePoint Portal Server environment or an environment that uses the Access Gateway with Advanced Access Control. Go to step 6.

6. If you selected the Custom installation option, enable one or more of the following options:

• Administration Tool. Enable this option if you want to run the Web Interface for Microsoft SharePoint Administration Tool on the server. In a load balanced SharePoint Portal Server environment or an environment that uses the Access Gateway with Advanced Access Control, this should be enabled on the server running as the Job Server.


• Content Redirection. Enable this option if you want to enable content redirection on the server. In a load balanced SharePoint Portal Server environment, this should be enabled on all the front end Web servers running SharePoint, and not on the Job servers. In an environment that uses the Access Gateway with Advanced Access Control, this should not be enabled on any of the servers (Job servers and Web servers) running SharePoint.

• Web Parts and Infrastructure. Enable this option in situations where you want the Citrix-specific Web Parts installed and integrated into the server running SharePoint. In a load balanced SharePoint Portal Server environment or an environment that uses the Access Gateway with Advanced Access Control, this should be enabled on all the Web servers running SharePoint, and not on the Job servers.

7. On the Specify Citrix Presentation Server screen, enter the following information and click Next:

• The name of the computer running the Citrix XML Service. This may be the NetBIOS name, fully qualified domain name (FQDN), or the IP address.

• The port number of the computer running the Citrix XML Service.

Note To provide failover capability, you can enter a comma-separated list of other servers running the XML Service in the farm. You must ensure all servers running the XML Service share the same port number.

Note In a load balanced SharePoint Portal Server environment you need only specify valid Citrix XML Service values on the Job Server through the Administration Tool and not on the front-end Web Servers. This is because the installation on the front-end Web Servers import the Citrix XML Service values (along with the other Web Interface for Microsoft SharePoint configuration settings) from the SQL Server 2000 database.

8. On the Ready to Install the Application screen, click Next.

9. On the Citrix Web Interface for Microsoft SharePoint has been Successfully Installed screen, click Finish.

If you want the SharePoint site to be accessed using fully qualified domain names you must edit the wisp_trust.config file to support FQDN access. For more information, see “Editing the wisp_trust.config file to support site access through FQDNs or IP Addresses” on page 27.


Post-Installation TasksAfter installing the Web Interface for Microsoft SharePoint, you can optionally complete one or more of the following post installation tasks:

• Edit the wisp_trust.config file to support site access through FQDNs or IP Addresses

• Add the Web Interface for Microsoft SharePoint Web Part to a Web Part page• Add the Citrix Custom Menu Web Part to a Web Part page• Add the Citrix Custom Menu Web Part to a Document Library or Shared

Documents page• Customize the appearance of the Web Part

Editing the wisp_trust.config file to support site access through FQDNs or IP AddressesBy default the wisp_trust.config file only allows published applications to display if users access the site using the Web server’s NetBIOS name. If you plan to have users access your SharePoint site using other identifiers (for example a fully qualified domain name or IP address), you must edit the sharepoint\CONFIG\wisp_trust.config file to support the required access.

To edit wisp_trust.config file to support additional access

1. Open the sharepoint\CONFIG\wisp_trust.config file in a text editor. The location of the file is:%Program Files\common files\Microsoft Shared\web server extensions\60\CONFIG

2. Scroll down to the area surrounded by ConnectAccess tags, where computer name is the computer name of the server running SharePoint.<ConnectAccess>

<URI uri=https?://computer name/_layouts/WISP/.*” />

</ConnectAccess>

3. Add additional URI lines between the <ConnectAccess> and </ConnectAccess> tags in the following manner;<ConnectAccess>

<URI uri=https?://computer name/_layouts/WISP/.*” />

<URI uri=https?://FQDN/_layouts/WISP/.*” />

<URI uri=https?://IPAddress/_layouts/WISP/.*” />

</ConnectAccess>

where FQDN is the FQDN of the server running SharePoint.

4. Save the sharepoint\CONFIG\wisp_trust.config file, and close text editor.


5. Restart IIS Services to apply the settings. From the Internet Information Services (IIS) Manager, select the computer name (local computer) item, and from the Action menu, choose All Tasks > Restart IIS....

Adding the Web Interface for Microsoft SharePoint Web Part to a Web Part PageTo allow users to access Citrix Presentation Server resources from a SharePoint site, you must add the Web Interface for Microsoft SharePoint Web Part to a Web Part Page. For more information, see your SharePoint documentation.

To add the Web Interface for Microsoft SharePoint Web Part to a Web Part page

1. Ensure you are logged in to the SharePoint site as either an Administrator or Web Designer.

2. Select the page you want to edit.3. If you are running SharePoint Portal Server, from the Actions menu, choose

Edit Page and go to Step 4. If you are running Windows SharePoint Services, go to Step 4.

4. From the Modify Shared Page menu, choose Add Web Parts > Browse.5. In the Add Web Parts tool pane, select Virtual Server Gallery.6. In the Web Part list, click Citrix Presentation Server Launcher.7. In the Add to box, select the zone to which you want to add the Web Part.8. Click Add.In circumstances including the following, the Web Interface for Microsoft SharePoint Web Part may not appear in the Virtual Server Gallery:

• The site is being accessed using a Fully Qualified Domain Name

• The site is being accessed with https and the virtual server was not extended as an https site

• The machine is part of a SharePoint Farm

This situation is partially described by the Microsoft Knowledge Base article 832816, which can be found at: http://support.microsoft.com and is usually resolved by including a hostname header as described in the article. If it is not possible to correct this issue then you can alternatively import the Web Interface for Microsoft SharePoint Web Part’s DataViewWebPart file (Launcher.dwp) into SharePoint and add it to a Web Part page.


To import the Web Interface for Microsoft SharePoint Web Part and add it to a Web Part page




4. From the Modify Shared Page menu, choose Add Web Parts > Import.5. In the Add Web Parts tool pane, click Browse.6. From the Choose file dialog box that appears, navigate to C:\Program

Files\Citrix\WISP\WebParts, select Launcher.dwp, and click Open. The path of the Launcher.dwp file appears in the Add Web Parts tool pane.

7. In the Add Web Parts tool pane, click Upload. The Citrix Presentation Server Launcher Web Part appears in the Uploaded Web Part list.

8. In the Uploaded Web Part list, click Citrix Presentation Server Launcher.9. In the Add to box, select the zone to which you want to add the Web Part.10. Click Add.

Adding the Citrix Custom Menu Web Part to a Web Part PageYou can customize the standard Document Library Web Part by adding the Citrix Custom Menu Web Part from the Virtual Server Gallery. This Web Part adds a new item to the context menu, allowing the user to edit a document using an application published in a farm running Citrix Presentation Server. You may want to include this feature if users cannot access applications locally or if bandwidth is an issue.

To allow users to access the Citrix Context Menu, you must add the Citrix Custom Menu Web Part to a Web Part Page that includes the Document Library Web Part (with SharePoint Portal Server) or the Shared Documents Web Part (with Windows SharePoint Services). For more information, see your SharePoint documentation.

To add the Citrix Custom Menu Web Part to a Web Part page


2. Select the page you want to edit.

3. If you are running SharePoint Portal Server, from the Actions menu, choose Edit Page and go to Step 4. If you are running Windows SharePoint Services, go to Step 4.


4. From the Modify Shared Page menu, choose Add Web Parts > Browse.

5. In the Add Web Parts tool pane, select Virtual Server Gallery.

6. In the Web Part list, click Citrix Custom Menu Web Part.

7. In the Add to box, select the zone to which you want to add the Web Part. This does not have to be the same zone where the Document Library Web Part or the Shared Documents Web Part exists.

8. Click Add.

After you add the Citrix Custom Menu Web Part to a Web Part Page, you must ensure that the view settings for either the Document Library Web Part (with SharePoint Portal Server) or the Shared Documents Web Part (with Windows SharePoint Services) is set to All Documents. For more information about changing the view settings for the Document Library Web Part or the Shared Documents Web Part, refer to your SharePoint documentation.

Note The Citrix Custom Menu Web Part is a hidden Web Part and will remain hidden in SharePoint’s normal view.

In circumstances including the following, the Citrix Custom Menu Web Part may not appear in the Virtual Server Gallery:

• The site is being accessed using a Fully Qualified Domain Name

• The site is being accessed with https and the virtual server was not extended as an https site

• The machine is part of a SharePoint Farm

This situation is partially described the Microsoft Knowledge Base article 832816, which can be found at: http://support.microsoft.com and is usually resolved by including a hostname header as described in the article. If it is not possible to correct this issue then you can alternatively import the Citrix Custom Menu Web Part’s DataViewWebPart file (CustomMenu.dwp) into SharePoint and add it to a Web Part page.

To import the Citrix Custom Menu Web Part and add it to a Web Part page




4. From the Modify Shared Page menu, choose Add Web Parts > Import.


5. In the Add Web Parts tool pane, click Browse.6. From the Choose file dialog box that appears, navigate to C:\Program

Files\Citrix\WISP\WebParts, select CustomMenu.dwp, and click Open. The path of the CustomMenu.dwp file appears in the Add Web Parts tool pane.

7. In the Add Web Parts tool pane, click Upload. The Citrix Custom Menu Web Part appears in the Uploaded Web Part list.

8. In the Uploaded Web Part list, click Citrix Custom Menu.9. In the Add to box, select the zone to which you want to add the Web Part.10. Click Add.

Adding the Citrix Custom Menu Web Part to Document Library or Shared Documents PagesMany SharePoint users navigate to the main Document Library page (with SharePoint Portal Server) or Shared Documents page (with Windows SharePoint Services).

The main Document Library page (http://server/Document%20Library/) and the Document Library’s Forms pages are not Web Part pages and so it is not possible to add a Web Part to these pages through the usual supported methods within SharePoint Portal Server.

The main Shared Documents page (http://server/Shared%20Documents/) and the Shared Document’s Forms pages are not Web Part pages and so it is not possible to add a Web Part to these pages through the usual supported methods within Windows SharePoint Services.

These pages are ASPX pages, but they are different from the Default [Home] site page in that they do not contain Web Part zones nor do they contain the Modify Page link for designing the page or adding Web Parts.

This section describes a method, unsupported by Microsoft, that integrates the Citrix Custom Web Part into the Document Library or Shared Documents page.

Note The Citrix Custom Menu Web Part is a hidden Web Part and will remain hidden in SharePoint’s normal view.

Note If you undertake the tasks in this section and then repair your original SharePoint installation, the settings you make are lost and need to be reapplied.


To add the Citrix Custom Menu Web Part to the Document Library page

1. Ensure you are logged in to the SharePoint site as either an Administrator or Web Designer, and specify the following URL:

http://server/Document%20Library/Forms/AllItems.aspx?ToolPaneView=2

where server is the computer name, FQDN, or IP address of the server hosting SharePoint Portal Server.



4. In the Add to box, select the zone to which you want to add the Web Part.

5. Click Add.

To add the Citrix Custom Menu Web Part to the Shared Documents page

1. Open a Web browser, and specify the following URL:

http://server/Shared%20Documents/Forms/AllItems.aspx?ToolPaneView=2

where server is the computer name, FQDN, or IP address of the server hosting Windows SharePoint Services.



4. In the Add to box, select the zone to which you want to add the Web Part.

5. Click Add.

Merging the Context MenuThe second method for embedding the Citrix Custom Menu Web Part in the Form pages involves adding it to a SharePoint custom site definition. If there are existing customizations to the Document Library context menu, you must merge the Citrix Custom Menu Web Part with these existing items. The Citrix Custom Menu Web Part contains a script that allows users to open documents using applications published by Citrix Presentation Server. Merge this script with any existing customizations.

To merge the Citrix Custom Menu Web Part

1. Take the JavaScript from the Citrix Custom Menu Web Part and add this directly to the Forms ASPX pages throughout the site definition. Each time a new site is created from that site definition, the document library on the Form pages will include the Citrix Custom Menu Web Part.

2. Open up a Forms ASPX page in your custom site definition using an editor such as Notepad or Visual Studio.NET 2003. An example would be CUSTOM SITE DEFINITION NAME\LISTS\DOCLIB\ALLITEMS.ASPX, typically a copy of the SharePoint default STS site definition.

3. Add the following JavaScript (shown in bold) into the <HEAD> section of the Forms ASPX page:<HEAD> <META Name="GENERATOR" Content="Microsoft SharePoint"> <META Name="ProgId" Content="SharePoint.WebPartPage.Document"> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8"> <META HTTP-EQUIV="Expires" content="0"> <Title ID=onetidTitle><SharePoint:ListProperty Property="Title" runat="server"/></Title>

<script language="javascript"></script>

4. Save the file and then navigate to the modified Forms page. The Citrix Custom Menu Web Part is now included within the Document Library and all new sites created using the site definition will include that functionality.


Customizing the Appearance of the Web PartYou can customize the appearance of the Web Interface for Microsoft SharePoint Web Part after installation.

The standard SharePoint Tool Part consists of Appearance, Layout, and Advanced sections. These allow you to modify the size of a Web Part, where it appears on the screen, and whether it can be minimized or closed by a user.

For more information, see your SharePoint documentation.

If you are using the Web Interface for Microsoft SharePoint, the Tool Part also includes Preferences and General Display Preferences sections. These allow you to test for Single Sign-On availability, show or hide Citrix Presentation Server resources, show application names or descriptions, and set the size of application icons.

To modify the appearance of the Web Part



3. From the Actions menu, choose Edit Page.

4. Click the arrow for the Web Part you want to modify.

5. Click Modify Shared Web Part.

6. Choose from the following:

To... Do this...

Display the Citrix Presentation Server resources available to users

Expand Preferences and select Show the Citrix Presentation Server Resources.

Display the last folder opened by a user Expand Preferences and select Remember Folder.

Display the current folder opened by a user Expand Preferences and select Show Folder.

Test for the availability of the Single Sign-On service, check it is configured for use by the Web Interface for Microsoft SharePoint, and check that the user has stored their credentials

Expand Preferences and select Test for Single Sign On.You should enable this option if you want to use Single Sign-On.

Specify the default folder displayed to users Expand Preferences and enter the name of the folder in the Current Folder box.The default for this option is the root folder.


Advanced Customization of the Web Part User InterfaceYou can also modify the appearance of the Web Part by making changes to the XML style sheet. This style sheet is in the following location:

webroot\wpresources\CPSWIMSP.WebPart\en\transform\wisp.xslt

Note You must restart Internet Information Services after modifying the style sheet for the changes to take effect.

Constrain traffic between the Web Part and Web application to use HTTPS

Expand Preferences and select Use https to obtain resources

Change the height of the application window area

Expand Application Display Preferences and enter the height (in pixels) in the Height of Applications area box.The default height for the Applications area is 320 pixels. The minimum value is 75 pixels.

Change the number of applications displayed in a row

Expand Application Display Preferences and enter the number of applications to display in the Number of Applications per row box.The default number of applications per row is 3.

Display application icons Expand Application Display Preferences and select Show the Application Icons.

Display large application icons Expand Application Display Preferences and select Use Large Icons.

Display the names of applications on-screen

Expand Application Display Preferences and select Show Application Names.

Display descriptions for applications Expand Application Display Preferences and select Show Application Descriptions.Note: You can enable this option only if Use Large Icons is enabled.

To... Do this...


Repairing the Web Interface for Microsoft SharePoint InstallationIf you experience problems with the Web Interface for Microsoft SharePoint installation, try using the Repair option of the Installer to fix the problem. You can use the Repair option through Add or Remove Programs or by rerunning the WISP.msi file.

You typically use the Repair option when you want to re-install content redirection filters that you may have manually removed in IIS Manager.

To repair the Web Interface for Microsoft SharePoint installation through Add or Remove Programs

1. Log on as a local administrator.

2. From the Start menu, choose Settings > Control Panel.

3. In Control Panel, open Add or Remove Programs.

4. Select Citrix Web Interface for Microsoft SharePoint and click Change.

5. On the Application Maintenance page, select Repair and click Next.

6. On the Ready to Repair the Application page, click Next.


To repair the Web Interface for Microsoft SharePoint installation using WISP.msi

1. Log on as an administrator.

2. Run WISP.msi.

3. On the Application Maintenance page, select Repair and click Next.

4. On the Ready to Repair the Application page, click Next.



Missing WebParts and Unloaded ConfigurationWeb Interface for Microsoft SharePoint installation will fail, generating an error message, in the following scenario:

• The machine that Web Interface for Microsoft SharePoint is being installed on has Terminal Services installed, and — And —

• The machine is connecting to a remote SQL database.

If this occurs, Web Interface for Microsoft SharePoint WebParts are not installed, and the configuration is not loaded into the SharePoint configuration database.

To correct this, you must run the command-line programs WebPartMgr.exe and SPConfigure.exe.

To install missing WebParts using WebPartMgr.exe

1. Launch a command window.

2. Navigate to C:\Program Files\Citrix\WISP\WebParts.

3. Type webpartmgr /a:e and press Enter.This lists all the WebParts that have been successfully installed.

4. Type dir *.cab and press Enter.This lists all the WebParts that are available.

5. Compare the list of installed WebParts (displayed in Step 3) to the list of those available (displayed in Step 4).

6. Add the missing WebParts using the following format:webpartmgr /a:a <WebPart name>.cabFor example, to install the Launcher Web Part:webpartmgr /a:a /f:WISP.Launcher.cab

7. Close the command window.

To load the configuration using SPConfigure

1. Open a text editor (for example, Notepad).

2. Open the file C:\windows\system32\SPConfigure.log.

3. Examine the line starting with SPConfigure.EXE: Command:

4. Launch a command window.

5. Navigate to C:\Program Files\Citrix\WISP\Configure.

6. Run the commands indicated by the SPConfigure.EXE: Command entry.


Uninstalling the Web Interface for Microsoft SharePointThis section explains how to uninstall Web Interface for Microsoft SharePoint.

In a load balanced SharePoint Portal Server environment, Citrix recommends that you uninstall the components from the front-end Web servers first, and then uninstall the Administration Tool from the Job server.

Before Uninstalling the Web Interface for Microsoft SharePointCitrix recommends you remove the Web Interface for Microsoft SharePoint and Citrix Context Menu Web Parts from any Web Part pages before uninstalling the software.

You must also remove the file specified under Client Deployment Settings as the file name of the Web client to be used for launches and auto–deploying the Web client. See “Managing Client Deployment” on page 49).

To remove a Web Part from a Web Part page



3. If you are running SharePoint Portal Server, from the Actions menu, choose Edit Page and go to Step 3.

4. From the Modify Shared Page menu, choose Design this page.

5. Click the downward arrow for the Web Part you want to remove, and choose Delete.

6. At the dialog box prompting you to confirm the permanent removal of the Web Part, click OK.


Uninstalling the SoftwareYou can uninstall the Web Interface for Microsoft SharePoint using Add or Remove Programs in Control Panel.

To uninstall the Web Interface for Microsoft SharePoint


2. In Control Panel, open Add or Remove Programs.

3. Select Citrix Web Interface for Microsoft SharePoint and click Remove.

4. In the Add or Remove Programs dialog box, click Yes.

If you are using Microsoft Office Portal Server 2003 and created a Single Sign-On application definition, the installer attempts to remove this definition during the removal process. If the installer cannot remove the application definition, you must remove it manually. This will remove all the credentials stored for this enterprise application definition.

To remove the application definition manually

1. From the Start menu, choose Program > SharePoint Portal Server > SharePoint Portal Server Single Sign-On Administration.

2. Select Manage settings for enterprise application definitions.

3. Rest the pointer on the display name created for the application definition, and click the arrow that appears.

4. From the drop-down menu, choose Delete.

Changes to Security Configuration InformationThe removal process attempts to restore the security configuration of the Internet Information Services virtual server hosting SharePoint to the configuration that was present when the Web Interface for Microsoft SharePoint was originally installed.

The removal process also does the following:

• Saves a copy of the security configuration present immediately before uninstallation to a file located at webroot\UNINSTALLED_web.config

• Saves a copy the modified security configuration after uninstallation to a file located at sharepoint\CONFIG\WISP_Trust.config

Web Parts added to the Web site after you install the Web Interface for Microsoft SharePoint cease to function after you uninstall the software. You can fix this problem by deleting the <SafeControl> tag associated with the Web Interface for Microsoft SharePoint Web Part from the UNINSTALLED_web.config file.


To delete the <SafeControl > tag

1. Open the UNINSTALLED_web.config file using a text editor such as Notepad.

2. Delete the following tag:<SafeControl Assembly="CPSWIMSP.WebPart, Version=1.0.4.xxxx, Culture=neutral, PublicKeyToken=4f93eb6865bf85f4" Namespace="com.citrix.CPSWebPart" TypeName="*" Safe="True" />

3. Save the modified file as webroot\web.config.

Note You must restart Internet Information Services for these changes to take effect.

CHAPTER 4

Configuring the Web Interface for Microsoft SharePoint

This chapter describes the administration and configuration of the Web Interface for Microsoft SharePoint. This chapter also describes the Web Interface for Microsoft SharePoint Administration Tool, which for conciseness is referred to as the Administration Tool.

Topics in the chapter include:

• Configuring the Web Application

• About the Administration Tool

• Managing Web Interface for Microsoft SharePoint Using the Administration Tool

• Manually Editing WebInterface.conf File Parameters

• Changing the File Exchange Protocol and Port Number in Web Interface for Microsoft SharePoint

Configuring the Web ApplicationAll access and communication with Citrix Presentation Server is through the Web application installed as part of the Web Interface for Microsoft SharePoint, found in the following location:sharepoint\TEMPLATE\LAYOUTS\WISPThe Web application is configured by the WebInterface.conf file found in the following location:

sharepoint\TEMPLATE\LAYOUTS\WISP\conf\WebInterface.conf

If you repair the installation using the installer, the WebInterface.conf file is overwritten with your current configuration and the current configuration is retained.


Important You must not modify the bootstrap.conf file contained in the conf\ directory.

Note You do not need to restart Internet Information Services for changes to WebInterface.conf to take effect.

Most of the relevant parameters in the WebInterface.conf file are managed by the Administration Tool. The full list of parameters in the WebInterface.conf file that apply to the Web Interface for Microsoft SharePoint are described in Appendix A.

A small number of parameters in the WebInterface.conf file are not managed by the Administration Tool, and must be managed manually.

Note Manual changes made to the WebInterface.conf file are not permanent until they are imported. For more information, see “Manually Editing WebInterface.conf File Parameters” on page 65.

About the Administration ToolThe Administration Tool is a Web-based tool that allows you to manage all aspects of Web Interface for Microsoft SharePoint.

The Administration Tool uses integrated Windows authentication. This means that only users belonging to the local administrator group account on the SharePoint server can use the Administration Tool. This can be changed by altering the <authorization> section of the configuration file located at C:\program files\Citrix\WISP\AdminApp\web.config.

Prerequisites for Windows 2003 Server UsersIf you plan to remotely access the Administration Tool on a computer running the Windows 2003 Server operating system, you must change the security settings of Internet Explorer. You must either:

• Remove the Windows Internet Explorer Enhanced Security Configuration component.

— Or —

• Add the URL of the server running SharePoint to the list of trusted sites.

Chapter 4 Configuring the Web Interface for Microsoft SharePoint 43

Accessing the Administration ToolYou can access the Administration Tool locally on the server running SharePoint or remotely through a Web browser.

Note If you are accessing the Administration Tool for the first time, it will take slightly longer to appear in your Web browser while the ASP pages are compiled.

To access the Administration Tool locally

1. Log on to the local SharePoint server as a local administrator.

2. Select Start > All Programs > Citrix > WISP > Administration Tool.

The Administration Tool main page appears in a Web browser.

To access the Administration Tool remotely

1. Open a Web browser, and specify the following URL:

http://SharePoint Server:8988/Admin/

where SharePoint Server is the computer name or IP address of the server hosting SharePoint.

2. If you are not logged on as a user who belongs to the SharePoint server’s local administrators group, a Connect to dialog box appears. At the Connect to dialog box, specify an appropriate Username and Password of a user who belongs to the SharePoint server’s local administrators group and click OK.

The Administration Tool main page appears in the Web browser.


Layout and Usage of the Administration ToolThe figure below shows the general layout of the Administration Tool.

Typical layout of the Administration Tool

The horizontal bar across the Administration Tool contains links to different tasks, allowing you to manage the configuration parameters directly. These tasks are described in the section “Managing Web Interface for Microsoft SharePoint Using the Administration Tool” on page 45.

The configuration parameters that are not managed directly by the Administration Tool are still managed indirectly through the Import/Export feature. For these parameters, you must edit them manually and then use the Import/Export feature to replicate the settings to all of the servers in the SharePoint Server farm. For more information, see “Manually Editing WebInterface.conf File Parameters” on page 65.

Reload and Resave buttons are provided to update the Administration Tool with configuration file changes, and update off-line machines when they are back on-line (see “Using Reload after Manual Changes to Configuration” on page 68 and “Using Resave after Changes to Configuration” on page 68).

A Status area exists at the bottom of each page, which tells you whether or not any changes were made on the existing page or any of the other pages. If changes were made to one or more of the pages, Save and Revert buttons are visible, and the area is shaded red. Clicking the Save button saves the settings on all of the pages that were changed. Clicking the Revert button reverts the settings on all of the changed pages to their original settings.


Managing Web Interface for Microsoft SharePoint Using the Administration Tool

This section describes the task-oriented procedures that you can undertake to manage the Web Interface for Microsoft SharePoint.

Managing AuthenticationThe Authentication Settings page allows you to modify the permitted authentication (logon) methods used by the Web Interface for Microsoft SharePoint.

Layout of the Authentication Settings page when deployed on SharePoint Portal Server

Because network environments can use both anonymous and Single Sign-On. authentication, you can choose Anonymous Access to Citrix Resources, Single Sign-on using the Citrix Client, and/or Single Sign-on using SharePoint authentication methods. For example, you may want to have two different user communities where one set of users anonymously connects to generic published applications such as Notepad or Calculator, and where another set of users connects to identity or role-based applications such as financial accounting applications.

You must select the Enable Anonymous Access to Citrix Resources check box in situations where anonymous authentication is enabled in Citrix Presentation Server.


You must select the Enable Single Sign-on using the Citrix Client check box in situations where Single Sign-On is configured in your environment. Single Sign-On through the Citrix Client allows users to access applications published using Citrix Presentation Server without having to reenter their credentials.

When you select the Enable Single Sign-on using the Citrix Client authentication method, you must then choose the appropriate Enable Sign-on using the Citrix Client method to use, as follows:

• In situations where you are using the pass-through authentication feature with Citrix Presentation Server, choose the Pass-through option.

• In situations where Kerberos authentication is configured within your environment, choose the Kerberos option.

Note If you are using SharePoint Services, enable pass-through authentication or Kerberos authentication for clients. If neither of these is enabled, the user is prompted for credentials when a Citrix Presentation Server session is started.

You must select the Enable Single Sign-on using SharePoint check box in situations where Single Sign-On is configured in your SharePoint Portal Server environment, and is not available in deployments that use Windows SharePoint Services. The Enable Single Sign-on using SharePoint option lets you store and map user credentials. After a users’ credentials are stored, they can access applications published using Citrix Presentation Server without having to reenter those credentials.

Note Windows Share Point Services does not support Single Sign-On through the Enable Single Sign-on using SharePoint option. The Enable Single Sign-on using SharePoint option can be used only with SharePoint Portal Server. If you are using SharePoint Portal Server, you can use the Microsoft Single Sign-on Service to allow users to store and retrieve their credentials for Citrix Presentation Server. If you choose the Enable Single Sign-on using SharePoint Single Sign-On option, ensure that the Microsoft Single Sign-on Service is correctly configured in SharePoint Portal Server according to the summary in Appendix B, “Configuring the Single Sign-On Service with SharePoint Portal Server”.

Setting Anonymous AuthenticationIf you want to configure anonymous authentication, you must ensure that the appropriate published applications and/or desktop are set to use anonymous authentication through the Management Console for Citrix Presentation Server. For more information, see Chapter 10 in the Citrix Presentation Server Administrator’s Guide.


To set anonymous authentication

1. If necessary, launch the Administration Tool. See “Accessing the Administration Tool” on page 43.

2. Click Authentication.

3. From the Authentication Settings page, ensure that the Enable Anonymous Access to Citrix Resources check box is selected, and if necessary, click Save.

Setting Single Sign-On in a Pass-Through EnvironmentIf you want to configure pass-through authentication, ensure that pass-through authentication is enabled for the logon method through the Management Console for Citrix Presentation Server. For more information, refer to Chapters 5 and 10 in the Citrix Presentation Server Administrator’s Guide.

To set Single Sign-On in a pass-through environment



3. From the Authentication Settings page:

A. Ensure that the Enable Single Sign-on using the Citrix Client check box is selected.

B. Ensure that the Pass-through option is selected.

C. If necessary, click Save.

Setting Single Sign-On in a Kerberos EnvironmentIf you want to configure Kerberos authentication, ensure that Kerberos is enabled on both Citrix Presentation Server and the 32-bit Client for Windows. For more information, refer to the Client for 32-bit Windows Administrator’s Guide and Chapter 7 in the Citrix Presentation Server Administrator’s Guide.

To set single sign-on in a Kerberos environment




3. From the Authentication Settings page:

A. Ensure that the Enable Single Sign-on using the Citrix Client check box is selected.

B. Ensure that the Kerberos option is selected.

C. If necessary, click Save.

Setting Single Sign-On in a SharePoint Portal Server EnvironmentIf you want to configure Single Sign-On in a SharePoint Portal Server environment, you must ensure that SharePoint Portal Server is already configured with the Microsoft Single Sign-on service before you use the Administration Tool. For more information, refer to Appendix B, “Configuring the Single Sign-On Service with SharePoint Portal Server” and your SharePoint documentation.

After the Single Sign-On service is configured and enabled in SharePoint Portal Server, you can use the Administration Tool to set the SharePoint Single Sign-On option and create a Citrix Presentation Server application definition.

Note You must use the Administration Tool to create a Presentation Server application definition rather than the SharePoint Portal Server administration pages.

To configure Single Sign-On in a SharePoint Portal Server environment


Note You must ensure that you are logged on as the user or user belonging to the user group that was defined in SharePoint Portal Server as either the Single Sign-On administrator or Enterprise Application Definitions administrator.

2. Click Authentication. An Authentication Settings page appears.

3. Ensure that the Single sign-on check box in the Authentication methods section is selected.

4. Ensure that the Enable Single Sign-on using SharePoint option is selected. A SharePoint single sign-on section appears.

5. In the Application Definition section of the SharePoint single sign-on section, type an appropriate display name (for example, Citrix Presentation Server) in the Display Name box and an appropriate email address in the Contact Email box.


6. Click Create to create an application definition. The application definition for Citrix Presentation Server is created, and the SharePoint single sign-on section updates with a Manage and Delete link, allowing you to manage and delete the Presentation Server application definition.

Note Clicking the Manage link opens the Manage Account Information for an Enterprise Application Definition SharePoint Portal Server page in a separate Web browser, which allows you to manage (remove and reset) the users credentials that are stored for different application definitions. For more information refer to your SharePoint Portal Server documentation.

7. If necessary, click Save.

Managing Client DeploymentThe Client Deployment Settings page allows you to determine which Citrix Presentation Server Clients are supported by Web Interface and whether legacy Clients are supported. The Web Interface for Microsoft SharePoint supports only the full version of the Client for Win32 and the Web versions of the client. It does not support the Program Neighborhood Agent.

Layout of the Client Deployment Settings page

In the Automatic client deployment section, you must do the following:


• If you want the Citrix Client to be installed automatically on the client device, ensure that the Enable automatic deployment check box is selected.

• Make sure the Class ID is set to 238f6f83-b8b4-11cf-8771-00a024541ee3, which is the default unique identifier for the Web client.

• Specify an appropriate file name (for example, Ica32t.exe) for the File name. This value determines the file name of the Web client used for launches and auto-deploying the Web client. You must also ensure that the file you specify exists in the webroot\wpresources\CPSWIMSP.WebPart\en\ica32 directory of the server running SharePoint and Web Interface.

Note You must ensure that this file is removed before you uninstall Web Interface for Microsoft SharePoint.

• Specify an appropriate Web client version number for the Version. You can find the version number from the Client CD.

Note To check the version number of the client, right-click the client installer and select Properties. Select the Version tab to display the version number for the client.

The Legacy client support section allows you to determine whether older Citrix Presentation Server Clients that cannot read UTF-8 ICA files are supported. If you select the Support all client versions option, the Web Interface will not produce ICA files in UTF-8 encoding. If you select the Support only client versions 8 or newer option, the Web Interface produces ICA files in UTF-8 encoding.

Configuring Automatic Client DownloadYou can determine whether or not the Citrix Client is downloaded automatically and deployed onto the client device in cases where the remote client does not currently have the Citrix Client installed. By default automatic client download is disabled when the Web Interface for Microsoft SharePoint is installed.

To enable (and configure) automatic client download


2. Click Client Deployment.

3. From the Client Deployment Settings page:

A. Select the Enable automatic client deployment check box.

B. Leave the Class ID set to 238f6f83-b8b4-11cf-8771-00a024541ee3.


C. Specify an appropriate file name (for example, Ica32t.exe) for the File name. This value determines the file name of the Web client used for native embedded launches and auto-deploying the Web client. You must also ensure that the file you specify exists in the webroot\wpresources\CPSWIMSP.WebPart\en\ica32 directory of the server running SharePoint and Web Interface.

D. Specify an appropriate Web client version number for the Version.

Note You can find the version number from the Client CD. Alternatively, to check the version number of the client, right-click the client installer and select Properties. Select the Version tab to display the version number for the client.


To disable automatic client download



3. From the Client Deployment Settings page ensure that the Enable automatic client deployment check box is cleared.


Configuring Legacy Client SupportYou can determine whether or not legacy clients are supported.

To enable legacy client support


2. Click Client Deployment.3. From the Client Deployment Settings page, ensure that Support all client

versions is selected, and if necessary, click Save.

To disable legacy client support



3. From the Client Deployment Settings page, ensure that Support only client versions 8 or newer is selected, and if necessary, click Save.


Managing Client ConnectionsThe Client Connection Settings page allows you to modify the Client Connection features available to users of the Web Interface for Microsoft SharePoint.

Layout of the Client Connection Settings page

The Enable bandwidth control check box determines whether or not users can specify the type of connection between their Web browser and servers running Citrix Presentation Server.

The Enable PDA synchronization check box determines whether or not PDA synchronization is enabled between the client device and servers running Citrix Presentation Server.

The Windows key behavior section determines whether or not the Windows key combinations are enabled and active, and how the key behavior is passed on to the remote server running Citrix Presentation Server. You must select one of the following options:

• On the remote desktop. If you want the Windows key behavior enabled on the remote desktop running Citrix Presentation Server.

• In full screen desktop only. If you want the Windows key behavior enabled on the remote server running Citrix Presentation Server when the local client device is running in full screen desktop mode.

• On the local desktop. If you want the Windows key behavior enabled on the local desktop running the published application.


Enabling or Disabling Bandwidth ControlYou can determine whether or not users can specify the type of connection between their Web browser and servers running Citrix Presentation Server.

To enable bandwidth control for users


2. Click Client Connection.

3. From the Client Connection Settings page, ensure that the Enable bandwidth control check box is selected, and if necessary, click Save.

To disable bandwidth control for users



3. From the Client Connection Settings page, ensure that the Enable bandwidth control check box is cleared, and if necessary, click Save.

Enabling or Disabling PDA SynchronizationYou can determine whether or not PDA synchronization is enabled between the client device and servers running Citrix Presentation Server.

To enable PDA synchronization



3. From the Client Connection Settings page, ensure that the PDA synchronization control check box is selected, and if necessary, click Save.

To disable PDA synchronization



3. From the Client Connection Settings page, ensure that the PDA synchronization check box is cleared, and if necessary, click Save.


Configuring Windows Key BehaviorYou can determine whether or not the Windows key combinations are enabled and active. By default the Windows key behavior is enabled on the local desktop running the published application.

To configure Windows key behavior



3. From the Client Connection Settings page, select the appropriate option:

• On the remote desktop. If you want the Windows key behavior enabled on the remote desktop running Citrix Presentation Server.

• In full screen desktop only. If you want the Windows key behavior enabled on the remote server running Citrix Presentation Server when the local client device is running in full screen desktop mode.

• On the local desktop. If you want the Windows key behavior enabled on the local desktop running the published application.


Note This procedure is only relevant for non–seamless Windows applications. This is set when publishing the application. See your Citrix Presentation Server user documentation for more information.


Managing Server FarmsThe Server Farm Settings page allows you to manage various aspects of your Citrix Presentation Server farm.

Layout of the Manage Server Farms page

The Farms section allows you to add, remove, and rename server farms, and rearrange the failover order in which those farms are accessed.

The Servers in farm selected farm name section is visible only when a server farm has been selected. It allows you to add, remove, and rename servers running Citrix Presentation Server for a selected server farm, and rearrange the failover order in which those servers are accessed within the farm.


The Settings for all farms section allows you to define the general failover parameters that are applied to all of the server farms. The Settings for all farms section allows you to configure the following for all the farms:

• Determine whether or not socket pooling is enabled or disabled

• Set the socket time-out value

• Set the number of retry attempts before the XML service for the farms is considered to have failed

The Settings for all servers in the farm section allows you to define the general failover parameters and other parameters that are applied to all servers within a selected server farm. The Settings for all servers in the farm section allows you to configure the following for all the servers within the selected farm:

• Determine whether or not the server list is used for load balancing

• Set the length of time for which a failed server is bypassed

• Set the XML service port number

• Set the transport type

• Set the SSL relay port number for the server farm’s SSL service

• Determine whether ICA authentication tickets are enabled or disabled

• Set the time to live for ICA authentication tickets

Adding Server FarmsThe Farms section of the Server Farms page allows you to add new server farms. The farms that you add must already be deployed and administered using the Citrix Presentation Server Management Console. After you add a farm, you can add servers to the farm.

To add a new server farm


2. Click Server Farms.

3. In the Farms section of the Server Farms Settings page, type an appropriate farm name in the box to the left of the Add button and click Add. The specified farm name appears in the list of farms.

4. Click Save.


Renaming Server FarmsThe Farms section of the Server Farms page allows you to rename existing server farms.

To rename an existing server farm



3. In the Farms section of the Server Farms Settings page:

A. Select the server farm name you intend to rename.

B. Type an appropriate farm name in the box to the left of the Rename button, and click Rename. The specified farm name updates in the list of farms.

4. Click Save.

Removing Server FarmsThe Farms section of the Server Farms page allows you to remove existing server farms.

To remove an existing server farm



3. In the Farms section of the Server Farms Settings page, select the server farm name you intend to remove and click Remove. The specified farm name is removed from the list of farms.

4. Click Save.

Modifying the Failover Order of Server FarmsThe Farms section of the Server Farms page allows you to modify the failover order in which the server farms are accessed by the Web Interface for Microsoft SharePoint.

To modify the failover order of existing server farms



3. In the Farms section of the Server Farms Settings page:


A. Select the required server farm.

B. Either click Move up to move the selected server farm up a level within the list, or click Move down to move the selected server farm down a level within the list.

Note You can click Move up or Move down more than one time to move the selected farm by more than one level.

4. If necessary, repeat Step 3 for a different farm.

5. When you are done reordering the server farms, click Save.

Adding Servers to Server FarmsAfter you create a farm, you must add servers to the existing farm. The Servers in farm selected server farm section of the Server Farms page allows you to add new servers to an existing server farms. The servers that you add must already have been deployed and administered using the Citrix Presentation Server Management Console.

To add a new server to an existing farm



3. In the Farms section of the Server Farms Settings page, select the required farm. The specified farm name appears in the Servers in farm selected farm name section, along with a list (if any) of servers that were added to that farm.

4. In the Servers in farm selected farm name section of the Server Farms Settings page:

A. Select the server name you intend to rename.

B. Type an appropriate server name in the box to the left of the Rename button, and click Rename. The sever name must be either a valid computer name, IP address, or FQDN of a server running Citrix Presentation Server. The specified name updates in the list of servers for the selected farm.

5. If necessary, repeat Step 4 to rename other servers within the selected farm.

6. Click Save.


Renaming Servers in Server FarmsThe Servers in farm selected server farm section of the Server Farms page allows you to rename servers in existing server farms. Renaming an existing server has the effect of specifying a different server.

To rename an existing server within a farm



3. In the Farms section of the Server Farms Settings page, select the required farm. The specified farm name appears in the Servers in farm selected farm name section, along with a list (if any) of servers in the farm.

4. In the Servers in farm selected farm name section of the Server Farms Settings page, type an appropriate server name in the box to the left of the Add button, and click Add. The sever name must be either a valid computer name, IP address, or FQDN of a server running Citrix Presentation Server. The specified farm name appears in the list of servers for the existing farm.

5. If necessary, repeat Step 4 to add additional servers to the selected farm.

6. Click Save.

Removing Servers from Server FarmsThe Servers in farm selected server farm section of the Server Farms page allows you to remove existing servers from server farms.

To remove an existing server from a farm



3. In the Farms section of the Server Farms Settings page, select the required farm. The specified farm name appears in the Servers in farm selected farm name section, along with a list (if any) of servers in the farm.

4. In the Servers in farm selected farm name section of the Server Farms Settings page, select the server you intend to remove and click Remove. The specified server name is removed from the list of servers for the selected farm.

5. If necessary, repeat Step 4 to remove additional servers to the selected farm.

6. Click Save.


Managing Global Farm SettingsThe Settings for all servers in the farm selected server farm section allows you to define the general failover parameters that are applied to all of the server farms. The Settings for all servers in the farm selected server farm section allows you to configure the following for all the farms:

• Determine whether or not socket pooling is enabled or disabled

• Set the socket time-out value

• Set the number of retry attempts before the XML service fails

To manage the global farm settings



3. Within Settings for all servers in the farm selected server farm section:

A. If you want to enable socket pooling, select the Enable socket pooling check box. If you want to disable socket pooling, clear the Enable socket pooling check box.

B. If you want to modify the existing socket pooling time-out value, type a new numeric value in the Socket time out box, and select an appropriate unit of time (Seconds, Minutes, Hours, Days, or Weeks).

C. If you want to change the number of retry attempts before the XML service for the farms is considered to have failed, type a new numeric value in the Number of attempts before XML service fails box.


Managing Global Server Settings per FarmThe Settings for all servers in the farm selected server farm section allows you to define the general failover parameters and other parameters that are applied to all servers within a selected server farm. The Settings for all servers in the farm <selected server farm> section allows you to configure the following for all the servers within the selected farm:

• Determine whether or not the server list is used for load balancing

• Set the length of time for which a failed server is bypassed

• Set the XML service port number

• Set the transport type

• Set the SSL relay port number for the server farm’s SSL service


• Determine whether ICA authentication tickets are enabled or disabled

• Set the time to live for ICA authentication tickets

To manage the global server settings per farm



3. Within Settings for all servers in the farm selected server farm section:

A. If you want the server list to be used for load balancing, select the Use the server list for load balancing check box. If you do not want the server list to be used for load balancing, clear the Use the server list for load balancing check box.

B. If you want to change the length of time for which a failed server is bypassed, type a new numeric value in the Bypass any failed server box, and select an appropriate unit of time (Minutes, Hours, Days, or Weeks).

C. If you want to change the XML service port used by all the servers in the selected farm (the default value is 80), type another numeric value in the XML service port box.

D. If you want to change the transport type used by all the servers in the selected farm (the default value is HTTP), select an appropriate Transport Type.

E. If you want to change the SSL relay port used by all the servers in the selected farm (the default value is 443), type another numeric value in the SSL relay port box.

F. If you want to enable ICA authentication tickets, select the Enable ICA authentication tickets check box. If you want disable ICA authentication tickets, clear the Enable ICA authentication tickets check box.

G. If you want to change the life time for an ICA authentication ticket, type a new numeric value in the Ticket time to live box, and select an appropriate unit of time (Seconds, Minutes, Hours, Days or Weeks).



Managing Smooth Roaming (Workspace Control)The Workspace Control Settings page allows you to modify the Smooth Roaming features available to users of the Web Interface.

Layout of the Workspace Control Settings page

The Enable workspace control check box in the Workspace control options determines whether or not the Workspace Control feature is available to Web Interface users.

Configuring Workspace ControlYou can determine whether Workspace Control should be enabled or disabled.

To enable and configure Workspace Control


2. Click Workspace Control.

3. From the Workspace Control Settings page, ensure that the Enable workspace control check box is selected, and if necessary, click Save.

To disable Workspace Control


2. Click Workspace Control.

3. From the Workspace Control Settings page, ensure that the Enable workspace control check box is cleared, and if necessary, click Save.


Managing Content RedirectionContent Redirection allows you to open content published in SharePoint using applications published by Citrix Presentation Server. The Content Redirection Settings page manages (adds and removes) the file extensions that are supported by the content redirection feature.

Layout of the Content Redirection Settings page

By default, the doc, pps, ppt, and xls file extensions exist when the Web Interface for Microsoft SharePoint is installed. You can add other file extensions that you want to be supported by the Content Redirection feature. The Content Redirection Settings page comprises:

• A File extension area that allows you to add new file extensions and remove existing file extensions. File extensions are not case sensitive. The Add button allows you to add the file extension currently specified in the box to the left. Selecting an existing file extension enables the Remove button, allowing you to remove existing file extensions.


• A Redirect script area that describes the name of the redirect script (located in the WISPAUX\Redirect directory) to be used by the content redirection feature, and is usually set to WISPRedirect. In this case, any requests ending with the defined file extensions (for example, doc, pps, ppt, xls, and so on) are redirected to the aspx page located at: sharepoint\TEMPLATE\LAYOUT\WISPAux\Redirect\WISPRedirect.aspx.

Note Content redirection relies on file name extensions being associated with published applications. Therefore, you must ensure that published applications support any of the filename extensions that you plan to create. For more information, see the Citrix Presentation Server Administrator’s Guide.

Adding a New File ExtensionTo add a new file extension


2. Click Content Redirection.

3. In the box to the left of the Add button, type your intended file extension (for example doc, xls, ppt).

Note Do not include the dot (.) with the file extension.

4. Click Add. The new file extension updates in the list of file extensions.

5. If necessary, repeat Steps 3 and 4 to add additional file extensions.

6. When you are finished adding your required new file extensions, click Save.

Removing an Existing File ExtensionTo remove an existing file extension


2. Click Content Redirection.

3. From the Content Redirection Settings page, select an existing file extension from the list of existing file extensions.

4. Click Remove.

5. If necessary, repeat Steps 3 and 4 to remove other existing file extensions.


6. When you are finished deleting the required file extensions, click Save.

Manually Editing WebInterface.conf File ParametersThis section describes how to edit the configuration parameters that are not managed directly by the Administration Tool. The table below summarizes the WebInterface.conf file’s parameters that are not managed directly by the Administration Tool.

Setting Description Values

AddressResolutionType Specifies what type of address to use for the NFuse_AppServerAddress tag in Template.ica.

Ipv4-port, ipv4, dns, dns-port

Note: Setting Kerberos sets this value to dns-port.

AlternateAddress Specifies whether or not to return the alternate server address of the server running Citrix Presentation Server in the ICA file.

Off, Mapped, On

ClientAddressMap Part of the server side firewall configuration. A list of client address, address type pairings. The first may be a partial address, or a subnet address and mask, while the latter may take the values: Normal, Alternate, Translated, SG, SGAlternate, and SGTranslated. Using an asterisk (*) in place of a client address or subnet indicates the default for all otherwise unspecified clients.

<ClientAddress>|<Subnet Address>/<Subnet Mask>|*, Normal|Alternate|Translated|SG|SGTranslated|SGAlternate, …

ClientProxy Client-side firewall option. Specifies a list of client subnet addresses and masks, or address “prefixes”, and associated proxy settings. The client address in the returned ICA file is determined by these settings. Using an asterisk (*) in place of a client address or subnet indicates the default for all otherwise unspecified clients. The value of the third field (proxy address) in each set of three is ignored unless the second field (proxy type) is an explicit proxy type (SOCKS or Secure), but it must always be present; the default value for this field is the minus sign (-).

<ClientAddress>|<Subnet Address>/<Subnet Mask>|*, Auto|Client|None|SOCKS|Secure,-|<ProxyAddress>|<ProxyAddress>:<ProxyPort>, …

CSG_Server Specifies the address of the Secure Gateway.

None. Server address as a FQDN.

CSG_ServerPort Specifies the port of the Secure Gateway. None. Server port.


Note The parameters listed above my not be present in the file you export from the Administration Tool. To effect manual configuration you may need to add the necessary parameters as required.

To make manual changes to the WebInterface.conf file, you:

1. Use the export tool to export your system’s existing configuration to another name and location on your local computer. See “Exporting the WebInterface.conf file” below for more information.

2. Use a text editor to edit the exported .conf file with the appropriate Web Interface parameters.

3. Use the import tool to import and deploy the modified .conf file throughout your SharePoint environment. See “Importing a .conf file” below for more information.

CSG_STA_URL<n> Server providing the Secure Ticket Authority function.

None. A URL to an STA.

EnableSTALoadBalancing Permits requests to multiple Secure Ticket Authority servers to be load balanced in a round-robin manner.

On, Off

InternalServerAddressMap A list of normal, translated address pairings. The normal address identifies the Secure Gateway server address and the translated address is the address that is returned to the client. Note: If you set this parameter you must also set the ServerAddressMap parameter.

NormalAddress = TranslatedAddress, …

RequestICAClientSecureChannel Controls Transport Layer Security settings. Detect-AnyCiphers,TLS-GovCiphers, SSL-AnyCiphers

ServerAddressMap Part of server-side firewall support. A list of normal, translated address pairings. The normal address identifies the address of the server running Citrix Presentation Server and the translated address is the address that is returned to the client.Note: If you set this parameter you must also set the InternalServerAddressMap parameter.

NormalAddress, TranslatedAddress,...

Version Not used. 4.0

Setting Description Values


Note Manual changes to configuration are not automatically loaded into the Administration Tool. You must use the Reload function to update the Administration Tool with these changes. See “Using Reload after Manual Changes to Configuration” on page 68.

Also, in a load balanced SharePoint portal environment, if a server is out of action when configuration changes are made and reloaded, this machine will not receive those changes until a manual Resave is performed. See “Using Resave after Changes to Configuration” on page 68.

Exporting the WebInterface.conf fileThe export tool allows you to export the current WebInterface.conf configuration file from the local machine, and save that file with a different file name in a location of your choice. You typically use the export tool when you want to manually edit/create a WebInterface.conf file, based upon your system’s existing configuration.

To export a configuration file

1. Launch the export tool (Start > All Programs > Citrix > WISP > Configure > Export).

2. From the Export the WISP configuration dialog box that appears, select the appropriate destination and click Save.

The selected file is exported to the location you specified.

Importing a .conf fileThe import tool allows you to import a configuration file (any text file with a .conf file extension) from another location, and replace the existing WebInterface.conf file(s) within your SharePoint environment. You use the import tool when you manually create or edit a .conf file that you need to deploy across your SharePoint environment.

Caution The import tool overwrites all of the WebInterface.conf files in your SharePoint environment with the .conf file you select.

To import a configuration file

1. If necessary, use a text editor to create or edit a .conf file with the appropriate Web Interface parameters. This .conf file can be a file you previously exported.

2. Launch the import tool (Start > All Programs > Citrix > WISP > Configure > Import).


3. From the Import the WISP configuration dialog box that appears, select the appropriate .conf file and click Open.

The selected file overwrites all of the WebInterface.conf files in your SharePoint environment.

Using Reload after Manual Changes to ConfigurationManual changes to WebInterface.conf files are not automatically loaded into the Administration Tool. You must Reload the changes into the Administration Tool.

To reload manual configuration changes

1. Export the required .conf file (see “Exporting the WebInterface.conf file” on page 67).

2. Make the required changes to the file.

3. Import the .conf file to register your configuration changes (“Importing a .conf file” on page 67).

4. Launch the Administration Tool (see “Accessing the Administration Tool” on page 43).

5. Click Reload.

Using Resave after Changes to ConfigurationIf a server is off–line when configuration changes are made, the off–line server will not automatically receive those changes.

You must Resave the configuration changes for them to be transferred to the off–line machines.

To resave configuration changes

1. Make the required configuration changes (see “Configuring the Web Application” on page 41 and “Manually Editing WebInterface.conf File Parameters” on page 65).

2. Launch the Administration Tool (see “Accessing the Administration Tool” on page 43).

3. Check that the off–line machines are now operational.

4. Click Resave.


Configuring Web Interface for Microsoft SharePoint with Secure GatewayYou can configure the Web Interface for Microsoft SharePoint to work with Secure Gateway by manually editing the WebInterface.conf file and importing the amended file.

To configure Web Interface for Microsoft SharePoint with Secure Gateway


2. Export the WebInterface.conf file. For more information, see “Exporting the WebInterface.conf file” on page 67.

3. Open the exported WebInterface.conf file in a text editor.

4. Add the parameter CSG_Server and set it to the FQDN of the Secure Gateway.

5. Add the parameter CSG_ServerPort and set it to the port number of the Secure Gateway’s inbound client connections port. The port number (usually 443) must match the inbound client connections port number that is configured on the Secure Gateway.

6. Add the parameter CSG_STA_URLn and set it to the same value for the Secure Ticket Authority URL that is set within the Secure Gateway.

Note You can have multiple Secure Ticket Authorities configured. In which case you need to define a CSG_STA_URL parameter for each one, using the format CSG_STA_URLn, where n is an integer identifying each STA configured. For example:

CSG_STA_URL1=http://firststabox.citrix.com:4567/scripts/ctxsta.dll

CSG_STA_URL2=http://secondstabox.citrix.com:4567/scripts/ctxsta.dll

CSG_STA_URL3=http://thirdstabox.citrix.com:4567/scripts/ctxsta.dll

7. Add the parameter ClientAddressMap=*, SG.

8. Save the WebInterface.conf file and close the text editor.

9. Import the WebInterface.conf file you just modified. For more information, see “Importing a .conf file” on page 67.


For example, if you have Secure Gateway with a FQDN of mycsgbox.citrix.com listening on standard port 443 with unsecured Secure Ticket Authority on separate box listening on port 4567, your entries would be:

CSG_Server=mycsgbox.citrix.com

CSG_ServerPort=443

CSG_STA_URL1=http://mystabox.citrix.com:4567/scripts/ctxsta.dll

ClientAddressMap=*, SG

For another example, if you have Secure Gateway with a FQDN of mycsgbox.citrix.com listening on non-standard port 449 with secured STA on separate box listening on standard port 80, your entries would be:

CSG_Server=mycsgbox.citrix.com

CSG_ServerPort=449

CSG_STA_URL1=https://mystabox.citrix.com/scripts/ctxsta.dll

ClientAddressMap=*, SG

Configuring Web Interface for Microsoft SharePoint with Access Gateway with Advanced Access ControlYou can configure the Web Interface for Microsoft SharePoint to work with Access Gateway with Advanced Access Control by manually editing the WebInterface.conf file and importing it to the other SharePoint servers in your deployment. Before doing this, you must ensure that:

• The Access Gateway with Advanced Access Control is configured with a Web resource pointing to Web Interface for Microsoft SharePoint. For more information, refer to Chapter 8 of the Access Gateway with Advanced Access Control - Administrator’s Guide.

• The Access Gateway is configured and running in Secure Gateway emulation mode (that is, set the Access Gateway to use the Secure Ticket Authority). For more information, refer to Chapter 7 of the Access Gateway Administrator’s Guide.

• Single Sign-On is enabled through the Microsoft Single Sign-on Service.

• Web Interface for Microsoft SharePoint is installed on the SharePoint server(s) without the content redirection component.


To configure Web Interface for Microsoft SharePoint with Access Gateway with Advanced Access Control




4. Add the parameter CSG_Server and set it to the FQDN of the Access Gateway.

5. Add the parameter CSG_ServerPort and set it to the port number of the Access Gateway’s inbound client connections port. The port number (usually 443) must match the VPN port number that is configured on the Access Gateway.

6. Add the parameter CSG_STA_URLn and set it to the same value for the Secure Ticket Authority URL that is set within the Access Gateway.







9. If you are running a SharePoint farm configuration, import the WebInterface.conf file you just modified. For more information, see “Importing a .conf file” on page 67.


Configuring Web Interface for Microsoft SharePoint with Access GatewayYou can configure the Web Interface for Microsoft SharePoint to work with Access Gateway by manually editing the WebInterface.conf file and importing it to the other SharePoint servers in your deployment. Before doing this, you must ensure that:

• The Access Gateway is configured and running in Secure Gateway emulation mode (that is, set the Access Gateway to use the Secure Ticket Authority). For more information, refer to Chapter 7 of the Access Gateway Administrator’s Guide.

• Single Sign-On is enabled through the Microsoft Single Sign-on Service.

• Web Interface for Microsoft SharePoint is installed on the SharePoint server(s) without the content redirection component.

To configure Web Interface for Microsoft SharePoint with Access Gateway




4. Add the parameter CSG_Server and set it to the FQDN of the Access Gateway.

5. Add the parameter CSG_ServerPort and set it to the port number of the Access Gateway’s inbound client connections port. The port number (usually 443) must match the VPN port number that is configured on the Access Gateway.

6. Add the parameter CSG_STA_URLn and set it to the same value for the Secure Ticket Authority URL that is set within the Access Gateway.









Configuring Web Interface for Microsoft SharePoint with HTTP or SOCKS ProxiesYou can configure the Web Interface for Microsoft SharePoint to work with HTTP or SOCKS proxies by manually editing the WebInterface.conf file and importing it to the other SharePoint servers in your deployment. HTTP and SOCKS proxies can be used on their own or in conjunction with the Secure Gateway or Access Gateway.

To configure Web Interface for Microsoft SharePoint with an HTTP or SOCKS proxy




4. Change the existing value of the ClientProxy parameter to match your network configuration. The ClientProxy parameter must be made up of one or more sets of the following three comma-separated fields:

• The value of the first field specifies a list of client subnet addresses and masks, or address “prefixes” and associated proxy settings. The client address in the returned ICA file is determined by these settings. Using an asterisk (*) in place of a client address or subnet indicates the default for all otherwise unspecified clients.

• The value of the second field defines the proxy type in use (Auto, Client, None, SOCKS, Secure). If you are using a client-side HTTP proxy, set this field to Client. If you are using a SOCKS proxy, set this field to SOCKS.

• The value of the third field defines the proxy address in each set of the three fields, and is ignored unless the second field (proxy type) is an explicit proxy type (SOCKS or Secure). It must always be present; the default value for this field is the minus sign (-).




Changing the File Exchange Protocol and Port Number in Web Interface for Microsoft SharePointBy editing the WebInterface.conf file, you can:

• Change the file exchange protocol type for Web Interface for Microsoft SharePoint. You can set the protocol to either http or https.

• Change the port number for Web Interface for Microsoft SharePoint. Port numbers should be changed whenever there are port clashes on the Front End Web Server machines.

Note These changes are not automatically updated in the Administration Tool. You must use the Reload function to update these WebInterface.conf edits in the Administration Tool

To change protocol and port numbers




4. Change the value of the WISP_Secure_Reload parameter to either On (for https) or Off (for http).

5. Change the value of the WISP_Reload_Port parameter to the port number required. Accepted values are between one and 65535.


7. Import the WebInterface.conf file you just modified. For more information, see “Importing a .conf file” on page 67.

8. Launch the Administration Tool. See “Accessing the Administration Tool” on page 43.

9. Click Reload to update the Administration Tool with your configuration changes.


Configuring Content RedirectionAdditional configuration (that is disabling, removing, or restoring) of Content Redirection can be undertaken outside of the Administration Tool, using standard Windows Tools. This section describes how to disable, remove, and restore content redirection.

You typically use the procedures in the section when you want to temporarily disable the content redirection feature for troubleshooting purposes.

Disabling Content RedirectionYou can disable Content Redirection by changing the order of the ISAPI filters using Internet Information Services Manager. Changing the order of the filters means that redirection requests are intercepted before they reach the Web Interface for Microsoft SharePoint Filter.

To disable content redirection


2. In Control Panel, open Administrative Tools.

3. Open Internet Information Services.

4. Right-click the SharePoint Extended Site folder and select Properties.

5. Click the ISAPI Filters tab.

6. Select the WispRedirectFilter and click Move Down.

Note You must ensure the WispRedirectFilter entry is moved below the stsfltr entry. The stsfltr filter is a SharePoint component that returns document content stored in Document Libraries.

7. Click OK.


Reestablishing Content RedirectionAfter disabling Content Redirection, you can reestablish it by changing the order of the ISAPI filters using Internet Information Services Manager. Changing the order of the filters means that redirection requests are undertaken by the Web Interface for Microsoft SharePoint Filter.

To re-enable content redirection

1. From the Start menu, choose Settings > Control Panel.2. In Control Panel, open Administrative Tools.3. Open Internet Information Services.4. Right-click the Default Web Site folder and select Properties.5. Click the ISAPI Filters tab.6. Select the WispRedirectFilter and click Move Up.

Note You must ensure the WispRedirectFilter entry is moved above the stsfltr entry. The stsfltr filter is a SharePoint component that returns document content stored in Document Libraries.

7. Click OK.


Removing Content RedirectionYou can remove the content redirection functionality by deleting the WispRedirectFilter. If you remove content redirection, users can access content displayed in SharePoint using only applications installed locally.

To remove content redirection

1. From the Start menu, choose Settings > Control Panel.2. In Control Panel, open Administrative Tools.3. Open Internet Information Services.4. Right-click the Default Web Site folder and select Properties.5. Click the ISAPI Filters tab.6. Select the WispRedirectFilter and click Remove.7. Click OK.

Note You must restart Internet Information Services after removing the WispRedirectFilter.

Restoring Content RedirectionYou can restore content redirection functionality by using the Repair option available from Add/Remove Programs in Control Panel. This reinstalls the WispRedirectFilter.

For more information, see “Repairing the Web Interface for Microsoft SharePoint Installation” on page 36.

APPENDIX A

Web Interface Configuration File Settings

This chapter describes the configuration file settings you can set in the WebInterface.conf file used to configure Web Interface for Microsoft SharePoint. It also highlights the parameters that are managed by the Web Interface for Microsoft SharePoint Administration Tool, and the parameters that must be configured manually.

Note If you manually edit the WebInterface.conf file using a text editor, you must always use the import tool to replicate the WebInterface.conf file to all of the servers in the SharePoint server farm. For more information, refer to “Manually Editing WebInterface.conf File Parameters” on page 65.


Web Interface for Microsoft SharePoint SettingsThe settings below are valid for use by the Web Interface for Microsoft SharePoint.

The default value (if any) for a setting is shown in bold. Values not valid for use by the Web Interface for Microsoft SharePoint are shown in italics.

Setting (managed by tool) Description Values

AddressResolutionType N Specifies what type of address to use for the NFuse_AppServerAddress tag in Template.ica.

Ipv4-port, ipv4, dns, dns-port

Note: Setting Kerberos sets this value to dns-port.

AllowBandwidthSelection Y Specifies whether or not users can provide Web Interface with the type of connection between their Web browser and Citrix Presentation Server, to optimize ICA settings. This parameter is managed by the Administration Tool’s Client Connection Settings page. For more information, see “Managing Client Connections” on page 52.

Off, On

AlternateAddress N Specifies whether or not to return the alternate server address of the server running Citrix Presentation Server in the ICA file.

Off, Mapped, On

AuthenticationMethods Y Defines the permitted logon methods. This is a comma-separated list that can contain any of the specified values in any order.This parameter is managed by the Administration Tool’s Authentication Settings page. For more information, see “Managing Authentication” on page 45.

Explicit, Anonymous, CertificateSingleSignOn, Certificate, SingleSignOn

ClientAddressMap N Part of the server-side firewall configuration. A list of client address, address type pairings. The first may be a partial address, or a subnet address and mask, while the latter may take the values: Normal, Alternate, Translated, SG, SGAlternate, and SGTranslated. Using an asterisk (*) in place of a client address or subnet indicates the default for all otherwise unspecified clients.

<ClientAddress>|<Subnet Address>/<Subnet Mask>|*, Normal|Alternate|Translated|SG|SGTranslated|SGAlternate, …

Appendix A 81

ClientProxy N Client-side firewall option. Specifies a list of client subnet addresses and masks, or address “prefixes”, and associated proxy settings. The client address in the returned ICA file is determined by these settings. Using an asterisk (*) in place of a client address or subnet indicates the default for all otherwise unspecified clients. The value of the third field (proxy address) in each set of three is ignored unless the second field (proxy type) is an explicit proxy type (SOCKS or Secure), but it must always be present; the default value for this field is the minus sign (-).

<ClientAddress>|<Subnet Address>/<Subnet Mask>|*, Auto|Client|None|SOCKS|Secure,-|<ProxyAddress>|<ProxyAddress>:<ProxyPort>, …

CSG_Server N Specifies the address of the Secure Gateway.

None. Server address as a FQDN.

CSG_ServerPort N Specifies the port of the Secure Gateway.

None. Server port.

CSG_STA_URL<n> N Server providing the Secure Ticketing Authority function.

None. A URL to an STA.

EnableLegacyICAClientSupport Y Specifies whether or not older Citrix Presentation Server Clients that cannot read UTF-8 ICA files are supported. If this is set to Off, the Web Interface produces ICA files in UTF-8 encoding. This parameter is managed by the Administration Tool’s Client Deployment Settings page. For more information, see “Managing Client Deployment” on page 49.

On, Off

EnableLogoffApplications N Specifies whether or not the Workspace Control feature should log off active applications when the user logs off from the Web Interface.

On, Off

Note: These settings are ignored.

EnableSTALoadBalancing N Permits requests to multiple Secure Ticket Authority servers to be load balanced in a round-robin manner.

On, Off



EnableVirtualCOMPortEmulation Y Specifies whether or not the PDA Synchronization through tethered USB connection feature is available to Web Interface users. This parameter is managed by the Administration Tool’s Client Connection Settings page. For more information, see “Managing Client Connections” on page 52.

On, Off

EnableWorkspaceControl Y Specifies whether or not the Workspace Control feature is available to Web Interface users.This parameter is managed by the Administration Tool’s Work Space Settings page. For more information, see “Managing Smooth Roaming (Workspace Control)” on page 62.

On, Off

Farm<n> Y Specifies all the information for a farm.

This parameter is managed by the Administration Tool’s Server Farm Settings page. For more information, see “Managing Server Farms” on page 55.

XML service address [,XML service address,...] [,Name:<name>] [,XMLPort:<port>] [,Transport:<HTTP|HTTPS|SSL>] [,SSLRelayPort:<port>] [,BypassDuration:<duration>] [,LoadBalance:<on|off>] [,ECSUrlURL>][,AuthenticationTickets:<on|off>] [TicketTimeToLive:<seconds (200)>]

ICAWebClient Y File name of the Web Client used for native embedded launches and auto-deploying the Web Client.This parameter is managed by the Administration Tool’s Client Deployment Settings page. For more information, see “Managing Client Deployment” on page 49.

Ica32t.exe

IcaWebClientClassID Y Class ID of the Client for ActiveX. This parameter is managed by the Administration Tool’s Client Deployment Settings page. For more information, see “Managing Client Deployment” on page 49.

238f6f83-b8b4-11cf-8771-00a024541ee3


Appendix A 83

ICAWebClientVersion Y Version number of client (from Client CD). Used with autoWebClientDownload. This parameter is managed by the Administration Tool’s Client Deployment Settings page. For more information, see “Managing Client Deployment” on page 49.

The latest version of the client.

InternalServerAddressMap N A list of normal, translated address pairings. The normal address identifies the Secure Gateway server address and the translated address is the address that should be returned to the client.Note: If you set this parameter you must also set the ServerAddressMap parameter.

NormalAddress = TranslatedAddress, …

LaunchClients N Defines from which clients the user is allowed to select.

Ica-Local, Ica-Java, Ica-Embedded, Rdp-Embedded Note: These values are ignored.

LaunchMethod N Preferred client to use for launches. Ica-Local, Ica-Java, Ica-Embedded, Rdp-Embedded Note: These values are ignored.

PooledSockets Y Specifies whether or not to use socket pooling. This parameter is managed by the Administration Tool’s Server Farm Settings page. For more information, see “Managing Server Farms” on page 55.

Off, On

ReconnectButton N Specifies whether or not Workspace Control should reconnect to applications when the Web Interface user presses the reconnect button, and if so, whether to reconnect to disconnected and active applications, or only disconnected ones.

DisconnectedAndActive, Disconnected, None

Note: These values are ignored.

RequestICAClientSecureChannel N Controls Transport Layer Security settings.

Detect-AnyCiphers,TLS-GovCiphers, SSL-AnyCiphers



RetryCount Y The number of times a failed request to the Citrix XML Service is retried before the service is deemed to have failed. This parameter is managed by the Administration Tool’s Server Farm Settings page. For more information, see “Managing Server Farms” on page 55.

Integer greater than 0. The default is 5.

ServerAddressMap N Part of server-side firewall support. A list of normal, translated address pairings. The normal address identifies the address of the server running Citrix Presentation Server and the translated address is the address that is returned to the client.Note: If you set this parameter you must also set the InternalServerAddressMap parameter.

NormalAddress, TranslatedAddress,...

Timeout Y Specifies the time-out value to use when communicating with the Citrix XML Service.This parameter is managed by the Administration Tool’s Server Farm Settings page. For more information, see “Managing Server Farms” on page 55.

Timeout in seconds. The default is 60.

TranspentKeyPassthrough Y Specifies the mode of the Windows key behavior passed through to the server running Citrix Presentation Server.This parameter is managed by the Administration Tool’s Client Connection Settings page. For more information, see “Managing Client Connections” on page 52.

FullScreenOnly, Local, Remote


Appendix A 85

Version N Not used. 4.0

WISP_Redirect_Extensions Y Specifies the list of file name extensions to be redirected and opened in published applications.This parameter is managed by the Administration Tool’s Content Redirection Settings page. For more information, see “Managing Content Redirection” on page 63.

None

WISP_Redirect_Page Y Specifies the aspx file to which to redirect requests. This file is in the following directory:sharepoint\TEMPLATE\LAYOUTS\WISPAux\Redirect\This parameter is managed by the Administration Tool’s Content Redirection Settings page. For more information, see “Managing Content Redirection” on page 63.

None


APPENDIX B

Configuring the Single Sign-On Service with SharePoint Portal Server

This appendix explain how to configure the Single Sign-on Service with SharePoint Portal Server. The Single Sign-on Service must be correctly configured and running before you use the Web Interface for Microsoft SharePoint Administration Tool to configure application definitions for Citrix Presentation Server.

Topics in this appendix includes:

• Correcting the ImagePath Value for the Microsoft Single Sign-on Service

• Configuring Single Sign-On

Correcting the ImagePath Value for the Microsoft Single Sign-on Service

At present most Windows 2003 Server deployments have Service Pack 1 installed. However, the version of Windows Installer 3.1 that gets bundled with Service Pack 1 sometimes erroneously puts quotation marks around the ImagePath values of the executable files for services installed with software products. This affects the Microsoft Single Sign-on service that gets installed with SharePoint Portal Server 2003. As a result, the path to the executable value contains quotation marks, whereas it must contain no quotes for the Microsoft Single Sign-on service to work correctly. If you are running Windows 2003 Server with Service Pack 1 you must perform a registry edit to remove the quotes, otherwise the SharePoint Portal configuration pages report that your configuration account does not have the correct rights to access the database, and you cannot complete the configuration of Single Sign-On. For more information, refer to the Microsoft knowledge base article 901203, which can be found at http://support.microsoft.com.


Configuring Single Sign-OnBefore you can create an application definition for Citrix Presentation Server, you must configure and enable the Single Sign-on service for SharePoint Portal Server. This section describes an overview of the process to configure and enable the Single Sign-on Service. For detailed information about configuring and enabling the Single Sign-on Service, see your SharePoint documentation.

The high-level process to configure Single Sign-On is as follows:

1. Ensure that the server(s) running SharePoint Portal Server 2003 are added to a domain.

2. Create the following SharePoint accounts on the domain controller in the network:

• Configuration account (this must be a domain account and not a local account and is used for the general administration of SharePoint Portal Server 2003)

• Single Sign-On administrator account (this must be a domain account, and not a local account, and is used to configure the Single Sign-on Service within SharePoint Portal Server 2003)

• Single Sign-On Service account (this must be a domain account and not a local account and is used to run the Microsoft Single Sign-on Service)

• Enterprise application manager account (this must be a domain account and not a local account and is used to create and manage application definitions within SharePoint Portal Server 2003)

3. Add the configuration account to the local administrators group on the local machine(s) running SharePoint Portal Server 2003.

4. Use the Windows Services Manager to configure the Microsoft Single Sign-on Service to log on using the Single Sign-On Service account and ensure that the Microsoft Single Sign-on Service is running. If you have SharePoint server farm, you must do this on the server running the Job component and on each server running the Web component.

5. Use the SharePoint Portal Server Single Sign-On Administration Tool to configure:

• The Single Sign-On settings to use the sign-on administrator account

• The Enterprise Application Definition Settings to use the enterprise application manager account

If you have SharePoint server farm, you must do this on the server running the Job component.

Appendix B 89

Note If the SharePoint Portal Server Single Sign-On Administration Tool reports that you do not have permission to access the database you must edit the Windows Registry according to “Correcting the ImagePath Value for the Microsoft Single Sign-on Service” on page 87.

After the Single Sign-on Service is configured and enabled according to the high-level process above, you can create the application definition for Citrix Presentation Server according to the steps described in “Setting Single Sign-On in a SharePoint Portal Server Environment” on page 48.

Index 91

Index

Aaccessing

documentation 8, 11the administration tool 43

addingCitrix Custom Menu web parts to pages 29file extensions 63–64server farms 56servers to server farms 58Web Interface web parts to pages 28

administration toolabout 44accessing 43

anonymous authenticationconfiguring 46

application definitionscreating 48removing manually 39

authenticationanonymous 45kerberos 46single sign-on 45

authentication settingsmanaging 45

automatic client downloadconfiguring 50disabling 51enabling 50

Bbandwidth control

disabling 53enabling 53

CCitrix Custom Menu web part

adding to pages 29merging 32

client connectionsmanaging 52

client deployment settingsmanaging 49

client supportlocal 49web 49

configuringanonymous authentication 46authentication settings 45automatic client download 50client connections 52client deployment settings 49content redirection 63, 75failover order of server farms 57kerberos authentication 47pass-through authentication 47SharePoint single sign-on 88SharePoint single sign-on authentication 48socket pooling timeout value 60the web application 41web parts 34workspace control 62

content redirection 8configuring 63, 75disabling 75file extensions 63managing 63redirect script 64removing 77restoring 77

creatingapplication definitions 48

customizingdocument library context menu 31the web part appearance 34


Ddisabling

automatic client download 51bandwidth control 53content redirection 75legacy client support 51PDA synchronization 53socket pooling 60workspace control 62

document library context menucustomizing 31

documentationaccessing 8, 11

Eenabling

automatic client download 50bandwidth control 53legacy client support 51PDA synchronization 53socket pooling 60workspace control 62

Ffailover parameters 56, 60

retry attempts 56, 60socket pooling 56, 60socket timeout value 56, 60

featuresWeb Interface for Microsoft SharePoint 8

File Exchange Protocol 74file extensions

adding 63–64removing 64

file locations 10

IICA authentication tickets 56installing

Web Interface for Microsoft SharePoint 25

Kkerberos authentication

configuring 47

Llegacy client support


Mmanaging

authentication settings 45client connections 52client deployment settings 49content redirection 63failover order of server farms 57server farms 55servers 56, 60workspace control 62

mergingCitrix Custom Menu web part 32

Ppass-through authentication

configuring 47PDA synchronization


Port Number 74post installation tasks 27

Rredirect script 64Reload 68removing

application definitions manually 39content redirection 77file extensions 64server farms 57servers from server farms 59Web Interface for Microsoft SharePoint 38web parts from pages 38

renamingserver farms 57servers in server farms 59

repairingWeb Interface for Microsoft SharePoint 36

Resave 68restoring

content redirection 77

Index 93

Sserver farms

adding 56adding servers to 58failover order 57general failover parameters 56, 60managing 55per farm settings 56, 60

failover bypass time 60SSL port number 60transport type 60XML service port number 60

removing 57removing servers from 59renaming 57renaming servers in 59

serversgeneral failover parameters 56general parameters 56managing 56, 60settings per farm 56, 60

SharePoint single sign-on authenticationconfiguring 48, 88pre-requisites 88

single sign-on authenticationkerberos 46pass-through 45–46SharePoint 46

socket poolingdisabling 60enabling 60setting the timeout value 60

SPConfigure 37system requirements 21

Uuninstalling

Web Interface for Microsoft SharePoint 38

Wweb application

configuring 41Web Interface for Microsoft SharePoint

features 8installing 25introduction 8post installation tasks 27repairing 36system requirements 21uninstalling 38

web partsadding Citrix Custom Menu to pages 29adding Web Interface web parts to pages 28advanced customization of 35configuring 34customizing appearance of 34removing from pages 38

WebPartsmissing 37

workspace controldisabling 62enabling 62managing 62