Client Component Installation

After you run SharePoint Portal Server setup, you can install the client components of SharePoint Portal Server on client computers across your network. The client functionality of SharePoint Portal Server is included with Office XP.

The client components are extensions to Windows Explorer and Office applications. There is no individual client application. These extensions integrate SharePoint Portal Server commands with Windows Explorer and Office applications. Note that to take advantage of the Microsoft Office integration features of SharePoint Portal Server, Office 2000 or later is required. You can use other applications to create documents, but you cannot access SharePoint Portal Server commands from the menus within those applications. You must use Windows Explorer or a Web browser to perform SharePoint Portal Server document management tasks on documents created by using those applications.

You can install the client components by running setup either from the server or from the SharePoint Portal Server CD. By default, the SharePoint Portal Server Setup Wizard installs client installation files to the following location on the server: Program Files\SharePoint Portal Server\ClientDrop\Languages\Lang, where Lang corresponds to the language of the client. For information about installing additional languages, see Installing the Client Components in Additional Languages later in this chapter.

To install the client components:

1. Review client hardware and software requirements outlined earlier in this chapter.
2. Install the client components by running the Client Components for SharePoint Portal Server Setup Wizard from one of the locations described previously.
3. Add a Web folder that points to the workspace.

There is a setup.ini file for the client components in Program Files\SharePoint Portal Server\ClientDrop\Languages\Lang. You can edit this file to specify the location of the SPSClient.msi file. You can also edit this file to specify the path and file name for the log file.

If you want to install the client components of SharePoint Portal Server in unattended mode, see Using Unattended Installation Options for the Client later in this section. If you want to uninstall or repair the client components, see Uninstalling or Repairing Client Components later in this section.

Installing the Client Components

The following steps describe how to install the client components.

To install the client components:

1. Log on to the client computer as a user with administrator privileges.
2. Connect to the location on the server where the client installation files are located. These files must be shared or otherwise available. By default, these files are located at Program Files\SharePoint Portal Server\ClientDrop\Languages\Lang, where Lang corresponds to the language of the client. If you want to install the client components from the CD, see the comments following this procedure.
3. Double-click Setup.exe. The Client Components for SharePoint Portal Server Setup Wizard appears.
4. Follow the instructions that appear in the wizard.

If you want to install the client components from the SharePoint Portal Server CD, insert the SharePoint Portal Server CD into your CD-ROM drive, and then click Client Installation. The Client Components for the SharePoint Portal Server Setup Wizard appears. You can also go to the Client folder on the CD, and then double-click Setup.exe.

The client components require Microsoft Data Access Components (MDAC) version 2.5 or later. If this is not already present on the computer, the client installation process installs MDAC 2.5 SP1.

Adding a Web Folder

After you install the client components, you must add a Web folder that points to the workspace. The address of the workspace is http://server_name/workspace_name.

The procedure for adding a Web folder varies depending on your operating system. For detailed instructions, see your operating system Help. For example, in Windows 2000 Professional, go to My Network Places and use the Add Network Place Wizard to add a Web folder that points to http://server_name/workspace_name. In Windows 98, go to Web Folders in My Computer, and use Add Web Folder to add a Web folder that points to http://server_name/workspace_name.

Using Unattended Installation Options for the Client

By default, you can install the client components by running the Client Components for SharePoint Portal Server Setup Wizard, which guides you through the installation process. You can also use Systems Management Server to install a client remotely on multiple computers in your organization. In addition, you can use Windows Installer directly to conduct an unattended installation of the client components.

If your server and client computers are both running Windows 2000 and are on a Windows 2000 domain, you can use the Active Directory^™ directory service to make the SharePoint Portal Server client setup program available to your users automatically.

Systems Management Server

SharePoint Portal Server provides a .pdf file that can be used with Systems Management Server to install the client components on multiple computers. The file SPSClient.pdf is located in the Client directory on the SharePoint Portal Server CD. SharePoint Portal Server also installs it on the server by default in Program Files\SharePoint Portal Server\ClientDrop\Languages\Lang, where Lang corresponds to the language of the client.

For more information about Systems Management Server, see Appendix B.

After you install the client components, you must add a Web folder that points to the workspace. The address of the workspace is http://server_name/workspace_name.

Windows Installer

You can use Windows Installer to conduct an unattended installation of the client components if you are running Windows 2000 or Windows Millennium Edition, or if Windows Installer is present. By default, Windows Installer is installed with Office 2000 or later. Windows Installer is also installed by some other applications.

To install the client by using Windows Installer:

1. On the taskbar, click Start, and then click Run.
2. In the Open box, type msiexec /qn /I "path\SPSClient.msi"

   The quotation marks are required only if the path contains spaces. For example, if SPSClient.msi is on a file share called \\ServerName\SharePoint Portal Server Client Setup, quotation marks are required because of the spaces in "SharePoint Portal Server Client Setup." You would type the following:

   msiexec /qn /I "\\ServerName\SharePoint Portal Server Client Setup\SPSClient.msi"

   If your operating system is Windows 98 and Windows Installer is present, include the path to Msiexec.exe. For example, if Msiexec.exe is located in C:\Windows\System, type:

   C:\Windows\System\msiexec /qn /I "C:\SharePoint Portal Server Client\SPSClient.msi"

   You can also add the directory that contains Msiexec.exe to the system path.

3. Click OK. SharePoint Portal Server installs the client without displaying user interface messages. Note that if the computer must be restarted, it is restarted automatically.

After you install the client components, you must add a Web folder that points to the workspace. The address of the workspace is http://server_name/workspace_name.

For more information about Windows Installer, including options other than unattended installations, see Appendix B.

Supported Command Line Parameters

The following table documents additional parameters available for both attended and unattended installation.

The command line parameters in the following table are supported for installing the client components of SharePoint Portal Server setup. No other parameters are supported.

Specifying path_to_SPSClient.msi is optional if Setup.exe, Setup.ini, and SPSClient.msi are all in the same directory, and you execute the setup command from within that directory.

Command Line Parameters

To do this	Type this at the command prompt
Install from the Setup.ini file, which you have modified.	"path_to_client_setup.exe" /settings
User interaction is required.	"path_to_setup.ini"
Install the client components.	"path_to_client_setup.exe" /i
User interaction is required.	"path_to_SPSClient.msi"
Repair the installation of the client components.	"path_to_client_setup.exe" /f
For this option to work properly, you must specify the path_to_SPSClient.msi or you receive an error.	"path_to_SPSClient.msi"
Uninstall the client components.	"path_to_client_setup.exe" /x
User interaction is required.	"path_to_SPSClient.msi"
Display no user interface. Optionally, display completion notice.	With any of the previous parameters, insert /qn[+]. For example,
No user interaction is required unless you choose to display the completion notice.	"path_to_client_setup.exe" /qn+ /i "path_to_SPSClient.msi"
Display basic user interface. Optionally, display completion notice.	With any of the previous parameters, insert /qb[+]. For example,
No user interaction is required unless you choose to display the completion notice. You see a status bar as the process progresses.	"path_to_client_setup.exe" /qb /f "path_to_SPSClient.msi"
Display reduced user interface. No user interaction is required. You see the user interface, but it automatically progresses through the steps.	With any of the previous parameters, insert /qr. For example, "path_to_client_setup.exe" /qr /x "path_to_SPSClient.msi"
Specify logging modes.	With any of the previous parameters, insert /L[logging_modes|*] path_to_the_log_file to specify logging modes. For more information about logging modes, see Windows Help. Use * to log all information except for the v option. Using /Lv* path_to_the_log_file creates the most verbose logging available. For example, "path_to_client_setup.exe" /qr /i "path_to_SPSClient.msi" /Lv* "path_to_the_log_file"
Access help for using the parameters.	"path_to_client_setup.exe" /?

Group Policy and Active Directory

If you are a domain administrator on a Windows 2000 domain, you can use Group Policy and Active Directory to make the Client Components for the SharePoint Portal Server setup program available to users. The program appears in the Control Panel under Add/Remove Programs. Both the server and the client computers must be running Windows 2000.

Group Policy settings define the various components of the user's desktop environment that a system administrator can manage. To create a specific desktop configuration for a particular group of users, you use the Group Policy snap-in. Group Policy settings that you specify are contained in a Group Policy object, which is in turn associated with selected Active Directory objects—sites, domains, or organizational units.

Group Policy includes settings for User Configuration, which affects users, and Computer Configuration, which affects computers.

• User policy settings are located under User Configuration and are obtained when a user logs on.
• Computer policy settings are located under Computer Configuration and are obtained when a computer starts up.

You can use Group Policy to publish the client under User Configuration or Computer Configuration.

To publish the client under User Configuration:

When you publish the client under User Configuration, the user can then install the client components by using Add/Remove Programs in the Control Panel.

Read the following known issues before publishing the client under User Configuration:

• After one user on a particular computer adds the client by using Add/Remove Programs in the Control Panel, the client files are present on the computer. However, another user cannot access Web folders until she adds the client also; the user receives an error stating that the folder entered does not appear to be valid even for valid folders.
• If one user on a particular computer adds the client, and a new user attempts to add the client on that computer, the new user may see a screen prompting for uninstall or repair. The user sees this screen if you select Maximum for the Installation user interface options on the Deployment tab of the Properties page of the client package. Choosing repair activates client functionality for the new user. If you select Basic for the user interface option, the user sees only a progress bar when the client repairs. Each user of the computer must perform this action once. By default, only members of the local Administrators group can add the client.
• If any user on the computer uninstalls the client, each user experiences automatic client repair upon the next access of the client components by opening a Web folder pointing to the workspace. If the user examines Add/Remove Programs in the Control Panel prior to this automatic repair, the client is present, but the Change button is disabled (therefore preventing manual repair). The user corrects this by triggering the automatic repair, which is triggered by opening a Web folder. The user who uninstalled the client will still be unable to access client functionality unless he installs the client components again.
• To see the client entry in Add/Remove Programs, the user may need to log off and then log on to the computer.
• You can exclude specific users by denying them read access to the client package. See the following procedure to learn how to do this. The excluded users will not see the client components package in the Add Programs portion of Add/Remove Programs. Excluding computers in this way, for this type of deployment, has no effect (users on that computer can see and add the client). For computer exclusion, see To assign the client under Computer Configuration: later in this section.
• If the client is manually installed on a computer (for example, from the SharePoint Portal Server CD) prior to the client being published, the client functionality is accessible to all users on the computer. If any user adds the program, they are prompted for repair or uninstall.

To use Active Directory (User Configuration) to make the client setup program available to users:

1. Read the preceding known issues.
2. Copy the folder containing the client files to the domain controller computer.

   You can copy the Client folder from the SharePoint Portal Server CD.

   You can also find the folder containing the client files on the SharePoint Portal Server computer. SharePoint Portal Server installs this folder by default on the operating system drive under Program Files\SharePoint Portal Server\ClientDrop\Languages\Lang, where Lang corresponds to the language of the client. For example, on an English version of SharePoint Portal Server, you would copy the "enu" directory to the domain controller.

3. Share the folder containing the client files. When sharing, specify that anyone installing from the share has read access to it. You can use standard Windows 2000 security groups, or you can create your own specific groups. You can optionally enable or disable the other privileges, depending on the policy of your organization.
4. Add the Group Policy snap-in:
   • On the taskbar, click Start, and then click Run.
   • In the Open box, type MMC and then click OK. The MMC console opens.
   • On the Console menu, click Add/Remove Snap-in. The Add/Remove Snap-in dialog box appears.
   • On the Standalone tab, click Add. The Add Standalone Snap-in dialog box appears.
   • Under Available Standalone Snap-ins, click Group Policy, and then click Add. The Select Group Policy Object dialog box appears.
   • Click Browse. The Browse for a Group Policy Object dialog box appears.
   • On the Domains/OUs tab, click Default Domain Policy, and then click OK.
   • Click Finish to close the Select Group Policy Object dialog box. The Group Policy Object (Default Domain Policy) appears on the Standalone tab in the Add/Remove Snap-in dialog box.
   • Click Close to close the Add Standalone Snap-in dialog box.
   • Click OK.
5. Add the SharePoint Portal Server client package by using the Group Policy snap-in.
   • Expand the Default Domain Policy node.
   • Expand the User Configuration node.
   • Expand the Software Settings node.
   • Right-click Software installation, point to New, and then click Package.
   • Type the path to the folder that you copied in step 2, and then click Open.

     Do not use local references such as C:\share. Type a share location, such as \\server\share. Otherwise, some users may not be able to access the deployed application.

   • Do not browse to this path.
   • Double-click SPSClient.msi. The Deploy Software dialog box appears.
   • Click Published, and then click OK.

   Do not choose the Assign option for the package. This option causes a program to be automatically installed when a shortcut to its application, or an associated file type, is accessed. The client components of SharePoint Portal Server do not have associated file types, nor is there any shortcut to activate the installation. Therefore, the installation would never be triggered. If you want to automatically install the client for all users, see the next section, To assign the client under Computer Configuration:.

To exclude specific users, do the following:

1. Expand the Default Domain Policy node.
2. Expand the User Configuration node.
3. Expand the Software Settings node.
4. Click Software installation.
5. In the details pane, right-click Client Components for Microsoft SharePoint Portal Server 2001, and then click Properties.
6. Click the Security tab, and then click Add.
7. Click the user to exclude, click Add, and then click OK.
8. On the Security tab, click the excluded user, select the Deny check box for the Read permission, and then click Apply.
9. Click Yes to continue when the caution message appears.
10. Click OK to close the Properties page.

To install the client components, the user uses Add/Remove Programs in the Control Panel.

After installing the client components, the user must add a Web folder that points to the workspace. The address of the workspace is http://server_name/workspace_name.

To assign the client under Computer Configuration:

When you assign the client under Computer Configuration, the client software installs the next time that any computer managed by this group policy is restarted.

Read the following known issues before assigning the client under Computer Configuration:

• If the client is deployed in this way, it is not installed on any computer affected by the deployment until that computer is restarted. It is recommended that only one application be assigned per restart in this way. Therefore, to deploy three applications, you would deploy one, restart the computer, deploy another, restart, deploy the third, and restart. This minimizes any interactions between the deployments.
• You must exclude the following from the deployment by creating an excluded group: computers with SharePoint Portal Server installed; computers on which you want to install SharePoint Portal Server; other computers on which you do not want to install the client components.

  After creating the group, you must deny access to it from the client package. See the following procedures for an explanation of how to do this.

• If you do not add current SharePoint Portal Server computers to the excluded group and you deploy the client, the server functions properly until the next restart. After restarting, you cannot access properties on workspaces while working on the server. In addition, the Web folders on the server will lack SharePoint functionality. To correct this situation, add the server to the excluded group. Repair the server that was impaired, and then restart it. The server should now function properly.
• If you add a SharePoint Portal Server computer to the domain without adding it to the excluded group, the server will not function properly when you restart it. You must add the server to the excluded group, repair the server, and then restart the server.
• If you want to install SharePoint Portal Server on a computer that already has the client installed, you must add the computer to the excluded group, ensure that the excluded group is denied access to the client package, and then restart the computer before installing SharePoint Portal Server.

To use Active Directory (Computer Configuration) to make the client setup program available to users:

1. Read the preceding known issues.
2. Copy the folder containing the client files to the domain controller computer.

   You can copy the Client folder from the SharePoint Portal Server CD.

   You can also find the folder containing the client files on the SharePoint Portal Server computer. SharePoint Portal Server installs this folder by default on the operating system drive under Program Files\SharePoint Portal Server\ClientDrop\Languages\Lang, where Lang corresponds to the language of the client. For example, on an English version of SharePoint Portal Server, you would copy the "enu" directory to the domain controller.

3. Create the excluded group.
   • On the taskbar, click Start, point to Programs, point to Administrative Tools, and then click Active Directory Users and Computers. If the Active Directory Users and Computers does not appear under Administrative Tools, you can add it manually.
   • Expand the Active Directory Users and Computers node.
   • Right-click the domain name, point to New, and then click Group.
   • In the Group name box, type a name for the group.
   • Do not change the default Group scope and Group type.
   • Click OK.
   • Click the domain name node. The new group appears in the details pane.
4. Add members to the excluded group.
   • Right-click the group that you created in the previous step, and then click Properties.
   • Click the Members tab, and then click Add.
   • Select the computer to add, and then click Add. Add any servers on which you intend to install SharePoint Portal Server. In addition, add any servers on which you have already installed SharePoint Portal Server. You can also add other computers on which you do not want the client to install.
   • Click OK.
   • Click OK to close the Properties page.
   • Close Active Directory Users and Computers.
5. Add the Group Policy snap-in.
   • On the taskbar, click Start, and then click Run.
   • In the Open box, type MMC and then click OK. The MMC console opens.
   • On the Console menu, click Add/Remove Snap-in. The Add/Remove Snap-in dialog box appears.
   • On the Standalone tab, click Add. The Add Standalone Snap-in dialog box appears.
   • Under Available Standalone Snap-ins, click Group Policy, and then click Add. The Select Group Policy Object dialog box appears.
   • Click Browse. The Browse for a Group Policy Object dialog box appears.
   • On the Domains/OUs tab, click Default Domain Policy, and then click OK.
   • Click Finish to close the Select Group Policy Object dialog box. The Group Policy Object (Default Domain Policy) appears on the Standalone tab in the Add/Remove Snap-in dialog box.
   • Click Close to close the Add Standalone Snap-in dialog box.
   • Click OK.
6. Add the SharePoint Portal Server client package by using the Group Policy snap-in.
   • Expand the Default Domain Policy node.
   • Expand the Computer Configuration node.
   • Expand the Software Settings node.
   • Right-click Software installation, point to New, and then click Package.
   • Type the path to the folder that you copied in step 2, and then click Open.

     Do not use local references such as C:\share. Type a share location, such as \\server\share. Otherwise, some users may not be able to access the deployed application. Do not browse to this path.

   • Double-click SPSClient.msi. The Deploy Software dialog box appears.
   • Click Advanced published or assigned, and then click OK. The Properties page for the new package appears.

     If you close the Properties page at this point, you can later configure the settings in the steps described in the following procedure by reopening the Properties page.

   • On the Properties page, click the Deployment tab, and then click Advanced.
   • Clear both check boxes under Advanced deployment options, and then click OK.
   • Click the Security tab, and then click Add.
   • Click the excluded group that you created in step 3, click Add, and then click OK.
   • On the Security tab, click the excluded group, select the Deny check box for all permissions, and then click Apply.
   • Click Yes to continue when the caution message appears.
   • Click OK to close the Properties page.

The client software is installed the next time the computer is restarted.

After installing the client components, you must add a Web folder that points to the workspace. The address of the workspace is http://server_name/workspace_name.

Uninstalling or Repairing Client Components

You can uninstall or repair client components of SharePoint Portal Server by using Add/Remove Programs in the Control Panel. You can also use the command line to remove or repair client components.

To remove or repair the client components by using the command line:

1. On the taskbar, click Start, point to Programs, point to Accessories, and then click Command Prompt.
2. Type "path\setup" switch "path\SPSClient.msi" where path is the path to the Setup.exe and SPSClient.msi files. Use the /x switch to uninstall the client components. Use the /f switch to repair the client components.

   For example, to remove the client components, where Setup.exe and SPSClient.msi are in E:\Client Files, you would type

   "E:\Client Files\setup" /x "E:\Client Files\SPSClient.msi"

   To repair the components in the preceding example, you would type

   "E:\Client Files\setup" /f "E:\Client Files\SPSClient.msi"

   When you uninstall the client components, the User's Help (webfoldr.chm) file remains. It replaces the original Web folders Help file.

   If you remove one or more of the installation prerequisites, you cannot uninstall or repair the client components unless you disable the prerequisite check.

   You disable the prerequisite check by adding DISABLEPREREQ=1 to the command line. To disable the prerequisite check in the preceding examples:

   • To remove the client components, type

     "E:\Client Files\setup" /x "E:\Client Files\SPSClient.msi" DISABLEPREREQ=1

   • To repair the client components, type

     "E:\Client Files\setup" /f "E:\Client Files\SPSClient.msi" DISABLEPREREQ=1

Installing the Client Components in Additional Languages

SharePoint Portal Server includes a client install for a single language. Users can install any language of the client to operate against a server. You can download client installations for additional languages from http://www.microsoft.com/Sharepoint.

If you install Office XP in one language and the client components of SharePoint Portal Server in another language, the user interface may appear in either of the two languages.