Documentum Desktop Client on Windows 2000 Terminal Services

Documentum Desktop Client on Windows 2000 Terminal Services Docbase Version 1.0 May 10, 2001

Documentum Desktop Client on Windows Terminal Services Page 2 Revision History Docbase Version Revised Date Revised By Revision Description 1.0 5/10/01 Mitch Jerome Initial version

Documentum Desktop Client on Windows Terminal Services Page 3 Table of Contents 1. Overview... 4 1.1. Market Requirements... 4 1.2. Usage and Configuration Requirements... 5 2. Server Setup... 5 2.1. Windows 2000 Server and WTS Setup... 5 2.2. Microsoft Office 2000 Setup... 5 2.3. Adobe Acrobat Business Tools Setup... 6 2.4. Desktop Client Setup... 6 2.5. Other applications... 7 3. Client Setup... 7 3.1. Create the WTS Client Setup diskettes... 7 3.2. Install the WTS Client on the client machines... 7 4. Running the WTS Client... 8 5. Desktop Client 4.2.1 Test Results... 8

Documentum Desktop Client on Windows Terminal Services Page 4 1. Overview This document describes the results of a proof of concept exercise to verify that the Documentum Desktop Client will work under Microsoft Windows 2000 Terminal Services (WTS). One of the primary deliverables from this exercise is this document, which includes details on how to set up and use Documentum Desktop Client on WTS. This involves installing and setting up WTS, Microsoft Office 2000, Adobe Acrobat Business Tools and Documentum Desktop Client on a Windows 2000 Server system and installing the WTS client on client machines. This document does not discuss licensing, security, networking issues, or capacity planning with respect to the use of WTS. Information on these topics can be found at: http://www.microsoft.com/windows2000/terminalservices The proof of concept work done for this paper used a Windows 2000 Server system and clients that were all in the same Local Area Network, operating under the same Windows domain. A test was also successfully done to run Desktop Client on WTS over a dial-up connection outside the corporate firewall using Point To Point Tunneling Protocol (PPTP). Although Windows NT 4.0 Terminal Server Edition and Citrix Metaframe are similar products, this document does not address the installation or setup of either of these products. It is anticipated that Documentum s initial support for executing the Documentum Desktop Client under a terminal services scenario will only include Windows 2000 Terminal Services. 1.1. Market Requirements WTS addresses the following market requirements: The ability to run Desktop Client over a high latency, low bandwidth connection, including dial-up networking scenarios. The ability to run Desktop Client through an advanced firewall that prevents new connections after an initial connection. The ability to run Desktop Client on machines that do not meet the minimum system requirements for Desktop Client, but meet the minimum system requirements for a WTS client, which is substantially lower. The ability to deploy Desktop Client to numerous client machines without the need to install the Desktop Client software on those machines. Centralized control over Desktop Client configuration and customization, including the location of each user s working files.

Documentum Desktop Client on Windows Terminal Services Page 5 1.2. Usage and Configuration Requirements Documentum Desktop Client on Windows 2000 Terminal Services will have the following restrictions: 1. Clients must use a named user account to log in to WTS. Anonymous log in is not supported. 2. The initial release will support Office 2000 only. Office 97 has not been tested and will therefore not be supported. 3. Usage of the Desktop Client with applications that are not Windows 2000 Logo compliant will not be supported, except for those applications that are detailed in this document. The Documentum Desktop Client was successfully tested on run under a Windows 2000 Terminal Services client that was running on a 486DX2/66 computer with 16 MB of memory. However, it is recommended that the client machine support 256 colors at a resolution of at least 800x600. This resolution will allow the WTS client to be run at 640x480 without the need to frequently scroll. 2. Server Setup 2.1. Windows 2000 Server and WTS Setup Since all programs to be used by Windows Terminal Services must be added in a specific controlled manner, and to avoid any possibility of problems down the road due to DLL conflicts (a.k.a., DLL Hell ), the recommended procedure for setting up the Windows Terminal Services server on a Windows 2000 Server system is to start completely from scratch with a clean install of Windows 2000 Server. 1. Reformat the hard disk. Allow at least 8 GB of disk space in the primary C partition. 2. Install Windows 2000 Server on the hard disk. Choose to convert the C partition to the NTFS file system. 3. In the optional components dialog, check the Windows Terminal Services and Windows Terminal Services Licensing options. 4. Choose Application Mode for WTS. 5. Set WTS permissions to be compatible with Windows 2000 Users. (Note: If you have a customization to an application that does not comply with Windows 2000 Logo Compliance guidelines regarding Registry usage, then do not choose Windows 2000 Users.) 2.2. Microsoft Office 2000 Setup Before you install Microsoft Office 2000 on a WTS Server, you must copy the Terminal Server transform file, TERMSRVR.MST, to the Windows 2000 Server machine. This file is located on the Office 2000 Resource Kit CD in the following directory path: Pfiles\Orktools\Toolbox\Tools\Termsrvr

Documentum Desktop Client on Windows Terminal Services Page 6 For my proof of concept exercise, I did not customize the transform file. Instead, I just used the defaults set up by Microsoft. It is not necessary to modify anything in the transform file in order to get Microsoft Office 2000 to work under WTS. Microsoft describes the process of setting up Microsoft Office 2000 for use under Windows NT 4.0 Terminal Server Edition at the following Web address: http://www.microsoft.com/office/ork/2000/two/30t3.htm Although the article was written for Windows NT 4.0 Terminal Server Edition, it can be adopted for use with Widows 2000 Windows Terminal Services by following the steps outlined below. 1. Log in as the Administrator on the WTS Server system. 2. Open the Add / Remove Programs Control Panel. 3. Click Add New Programs. 4. Click CD or Floppy. 5. Click Next. 6. Click Browse. 7. In the Open edit field, if not already present, enter the path to the Setup.exe file on the Microsoft Office 2000 installation CD (Disc 1). You may use the Browse button if you wish. 8. Append the following string to the Setup.exe file path: TRANSFORMS= <path>\termsrvr.mst where <path> is the path to the folder to which you copied the TermSrvr.mst transform file. So, for example, if TermSrvr.mst was in C:\Temp, then the edit field would now contain: D:\SETUP.EXE TRANSFORMS=C:\Temp\TermSrvr.mst 9. Click Next. 10. At this point, you get a dialog telling you to click Next once the installation is complete. Complete the Office 2000 installation. Then click Next. 11. A second dialog appears urging you to click Next again only after you complete the installation of the program, even if you cancelled the installation, appears. Click Next. 2.3. Adobe Acrobat Business Tools Setup As with Microsoft Office and all other programs installed on the WTS Server, you must use the Add/Remove Programs Control Panel to install Adobe Acrobat Business Tools. Follow Steps 1 7 and Steps 9-11 in Section 2.2, Microsoft Office 2000 Setup, except enter the path to the setup program for Adobe Acrobat Business Tools. 2.4. Desktop Client Setup Once again, follow Steps 1 7 and Steps 9-11 in Section 2.2, Microsoft Office 2000 Setup, except enter the path to the setup program for the Documentum Desktop Client. Once those steps are complete, you must copy dmcl.ini from the true Windows 2000

Documentum Desktop Client on Windows Terminal Services Page 7 system root directory (e.g., C:\WINNT) to each WTS user s WINDOWS directory. In order to do this, you must have them log in first so that the directory gets created. Then, the directory path will be (assuming the C drive holds the \WINNT directory) C: \Documents and Settings\<username>\WINDOWS, where <username> is replaced with the log in name of the WTS user. (For example, you would copy C:\WINNT\dmcl.ini to C:\ Documents and Settings\ mitch\windows.) 2.5. Other applications Any other application that a customer installs on the WTS Server must Use HKEY_CURRENT_USER to store all data written to the registry by the application. Store any user generated files in My Documents or a subfolder of My Documents. Store application generated files that are not meant for end user use in the appropriate Application Data directory. Be installed by using the Add / Remove Programs Control Panel as described above. Be aware of the usage of a per-user Windows directory under WTS, and make installation modifications as appropriate. 3. Client Setup 3.1. Create the WTS Client Setup diskettes On the WTS Server machine, perform the following steps: 1. Create two blank floppies, formatting them if necessary. Label the first Windows Terminal Services Client Setup Disk 1 and the second Windows Terminal Services Client Setup Disk 2. 2. Click Start / Programs / Administrative Tools / Configure Your Server. 3. Click on Application Server in the left pane. 4. Click on Terminal Services in the left pane. 5. Click on Terminal Services Client Creator in the right pane. 6. Select Terminal Services for32-bit x86 Windows in the Create Installation Disk(s) window. 7. Insert the blank floppy labeled Windows Terminal Services Client Setup Disk 1. 8. Click OK. 9. Insert the blank floppy labeled Windows Terminal Services Client Setup Disk 2. 10. Click OK. 11. Click OK to dismiss the completion dialog. 12. Click Cancel to dismiss the Create Installation Disk(s) window. 13. Exit the Configure Your Server application. 3.2. Install the WTS Client on the client machines On the client machine, perform the following steps: 1. Insert the floppy labeled Windows Terminal Services Client Setup Disk 1. 2. Launch Setup.exe on drive A.

Documentum Desktop Client on Windows Terminal Services Page 8 3. Click Continue. 4. Enter your name and organization, if requested. Click OK. Click OK again. (Note: This step may be skipped on systems other than Windows 95/98.) 5. Click I Agree. 6. Click the big button on the left side of the dialog to start the installation. 7. Choose the program group and click Continue. (Note: This step may be skipped on systems other than Windows 95/98.) 8. When prompted, insert the floppy labeled Windows Terminal Services Client Setup Disk 2. 9. Click OK. 10. Click OK on completion message. 4. Running the WTS Client On the client machine, perform the following steps: 1. Click Start / Programs / Terminal Services Client / Terminal Services Client. 2. Choose the name of your WTS Server from the listbox. 3. Select your desired screen size. The screen size should be no more than one step smaller than the resolution used on the client system so that the entire WTS window can fit on the client screen without having to resort to scrolling. (Example: If the client machine is running at 1024x768, then select a screen size no larger than 800x600.) Also, the larger the size you choose, the slower your performance will be. Experiment to see which size fits your performance and UI needs. 4. Click Connect. 5. Desktop Client 4.2.1 Test Results Desktop Client 4.2.1 was installed on a WTS Server. Informal tests were then run by launching the WTS Client, connecting to the WTS Server, logging in under a non- Administrator account, launching Windows Explorer and opening the documentum namespace. These tests are by no means exhaustive and should not be taken as any form of certification of the WTS platform. Unless otherwise noted, commands worked on both plain and virtual documents. Functionality /Fail Comments Navigation File / Open File / Explore File / Print File / View File / Edit File / Quick View N/A Quick View not installed

Documentum Desktop Client on Windows Terminal Services Page 9 Functionality /Fail Comments File / Annotate File / Send To / Distribution List File / Send To / Folder / As Document File / Send To / Folder / As Locator File / Send To / Mail Recipient / As Document File / Send To / Mail Recipient / As Locator File / New / Document / Other File / New / Document / Empty Text Document File / New / Folder File / New / Cabinet File / New / PDF Rendition File / New / Workflow Template File / Check In File / Check Out File / Cancel Check Out File / Document Lifecycle / Apply File / Document Lifecycle / Remove File / Document Lifecycle / Promote File / Document Lifecycle / Demote File / Document Lifecycle / Suspend File / Document Lifecycle / Resume File / Freeze Assembly File / Unfreeze Assembly File / Convert Virtual Worked in both directions Document File / Delete File / Update File / Properties File / Page Setup N/A Printer not setup. Applicable in WTS environment?

Documentum Desktop Client on Windows Terminal Services Page 10 Functionality /Fail Comments File / Print Window Text N/A Printer not setup. Applicable in WTS environment? File / Work Offline Command doesn t make sense in a WTS environment. However, executing the command did work, and it didn t affect other WTS clients that were logged in at the same time. Note: Going from offline to online didn t update the Tree Pane properly. F5 (Refresh) had to be used to show the online abstractions. File / Close Edit / Cut Edit / Copy Edit / Paste Edit / Paste As Link Edit / Paste As Shortcut Drag / Drop create reference Drag / Drop move Drag / Drop copy Drag / Drop link Drag / Drop Export Drag / Drop Import Copy / Paste Export Copy / Paste Shortcut to create.lnk shortcut file Drag / Drop to create.lnk shortcut file Paste As Rendition Drag / Drop add rendition Edit / Select All Edit / Invert Selection View / Toolbars / <all cmds> View / Status Bar View / Document Info View / <icon settings> View / Arrange Icons / <all cmds> Click on column headers in Content Pane to sort View / Go To / <all cmds> View / Refresh

Documentum Desktop Client on Windows Terminal Services Page 11 Functionality /Fail Comments View / Refresh Window Favorites menu Tools / Find Documentum Items Find dialog displayed. A simple query worked. The buttons on the right all worked. Tools / Log On As Tools / Log Off Tools / Change word Tools / Virtual Document Manager Tools / Workflow Availability Tools / Synchronize Native Microsoft command. (Why do we have this command?) Tools / Folder Options Native Microsoft command. Help / Documentum Help Interactive Message Tester Help / View Manual / Introducing the Documentum Desktop Client Help / About Windows Native Microsoft command. Open a.drl file Bug: dmcl folder is created in the same folder as the.drl file. However,.drl file does open successfully. Inbox Used DM_BUGS96 successfully. Dynamic Component Delivery Microsoft Word and Excel: Documentum commands Microsoft PowerPoint Microsoft Outlook Fail Momentary busy cursor, then nothing happens. Docbase Browser Control Fail View command fails with Unable to get the contents of <document name> for viewing. However, all other commands succeed. Note: The Docbase Browser Control passed when using the version in DTC 4.3.

Documentum Desktop Client on Windows Terminal Services Page 12