When installing software on terminal servers there are a few peculiarities that you need to be aware of. Essentially, terminal servers distinguish between two possible operational states: Installation mode and execution mode. If you wish to install software on a terminal server so that it can be used by multiple users you have to switch to installation mode before attempting the installation. This enables it to record the software settings, the added .ini files and the modified registry and to use this as the template for all users.
You either go to Control Panel -> Add/Remove Programs and select the path to DWSetup.exe, or you enter the Change user/install command on the command line before executing the file.
Always install direct on the console, i.e. on the terminal server itself, as the session will suppress certain things such as error messages, or similar. However, Windows Server 2003 offers the option of
establishing a console session on a client, with the console screen being routed to the client. For this purpose, add the /console parameter t the mstsc command. Thus, always use the console when installing DocuWare.
Tablet PC:
We recommend installing the Tablet PC element of the DocuWare client only on a Terminal Server, and only if someone in your organization actually uses DocuWare with a Tablet PC.
Background: Even after you close DocuWare the Microsoft Wisptis.exe component required for a Tablet PC remains open and so the DocuWare session continues to be listed in the user’s management console.
3.8.1
Configuring DocuWare with a single terminal server
Decide whether you will be installing DocuWare on a single terminal server, or in a farm – and use the appropriate configuration. When using a single terminal server rather than an explicit DocuWare server, you must install both the server modules and the client directly on the terminal server.
In order to take account of user-specific settings, set up a central user directory on the terminal server itself in order to store the user date from baskets, pending boxes and the trash can.
Example:
C:\DocuWare\Users\
This directory is where DocuWare baskets, pending boxes, and trash cans are set up for specific users.
There are two ways of setting up baskets:
Set up baskets centrally (from DocuWare 5.1b SP1)
You can easily set up baskets for all users in a central location by using variables.
Installation and Update of DocuWare
Example for two baskets:
C:\DocuWare\Users\%USERNAME%\Baskets\Store\
C:\DocuWare\Users\%USERNAME%\Baskets\Scan\
The "%USERNAME%" variable is then replaced by the Windows user name. You can also use system or user variables. See also Baskets (on page 92).
If you wish to use baskets for TIFFMAKER applications, however, the basket paths must not contain any user variables.
Baskets with system variables or the "USERNAME" variable in the basket path on the other hand can be used without any additional TIFFMAKER settings.
Set up baskets for specific users (old variant, still possible)
Example for two baskets:C:\DocuWare\Users\miller\Baskets\Store\
C:\DocuWare\Users\miller\Baskets\Scan\
These directories must be added for each user under "Miscellaneous" in DocuWare Administration.
You must switch TIFFMAKER to ASP mode by using the port settings. This mode gives you the option of using environment variables in order to read the user names.
Use the following path, for example:
C:\DocuWare\Users\Baskets\%USERNAME%\Store\
This will cause all documents printed by user miller to go straight into his basket. The user variable path must be entered manually via the DWORD KonvPath into the registry under
HKEY_LOCAL_MACHINE\SOFTWARE\DocuWare\DocuWare\
TIFFMAKER\500\port. Adjust the name of the port according to the TIFFMAKER that you are using.
But note that TIFFMAKER in ASP mode cannot store the documents into an archive, nor send them via DocuWare email. Error messages are not output to screen, instead they are logged into the Server's event log.
Set up pending box and trash can
Example for the pending box and the trash can:
C:\DocuWare\Users\miller\PendingBox\
C:\DocuWare\Users\miller\TrashCan\
These directories must be added for each user under "Miscellaneous" in DocuWare Administration.
This type of installation is recommended only if a single terminal server is in use and if you are not planning to add another one in the near future. Otherwise, use this procedure.
3.8.2
Configuring DocuWare with a terminal server farm
With farms, we recommend the use of a special server on which you install the server modules. This can be an existing Application or File Server, or a dedicated DocuWare Server, as in the following example:
Specifying paths (e.g.: document storage path) ought to be done via UNC. In addition, each terminal server has a client installation. As can be seen in the picture, terminal servers are installed just like regular DocuWare clients. The central user directory on the DocuWare Server contains the data of the users' baskets, pending boxes and trash cans.
Example:
\\TerminalServer\DocuWare\Users\
This directory is where DocuWare baskets, pending boxes, and trash cans are set up for specific users.
There are two ways of setting up baskets:
Set up baskets centrally (from DocuWare 5.1b SP1)
You can easily set up baskets for all users in a central location by using variables.
Example for two baskets:
C:\DocuWare\Users\%USERNAME%\Baskets\Store\
C:\DocuWare\Users\%USERNAME%\Baskets\Scan\
The "%USERNAME%" variable is then replaced by the Windows user name. You can also use system or user variables. See also Baskets (on page 92).
IIf you wish to use baskets for TIFFMAKER applications, however, the basket paths must not contain any user variables.
Baskets with system variables or the "USERNAME" variable in the basket path on the other hand can be used without any additional TIFFMAKER settings.
Set up baskets for specific users (old variant, still possible)
Example for two baskets:C:\DocuWare\Users\miller\Baskets\Store\
C:\DocuWare\Users\miller\Baskets\Scan\
These directories must be added for each user under "Miscellaneous" in DocuWare Administration.
You must switch TIFFMAKER to ASP mode by using the port settings. This mode gives you the option of using environment variables in order to read the user names.
Use the following path, for example:
C:\DocuWare\Users\Baskets\%USERNAME%\Store\
This will cause all documents printed by user miller to go straight into his basket. The user variable path must be entered manually via the DWORD KonvPath into the registry under
HKEY_LOCAL_MACHINE\SOFTWARE\DocuWare\DocuWare\
TIFFMAKER\500\port. Adjust the name of the port according to the TIFFMAKER that you are using.
But note that TIFFMAKER in ASP mode cannot store the documents into an archive, nor send them via DocuWare email. Error messages are not output to screen, instead they are logged into the Server's event log.
Installation and Update of DocuWare
Set up pending box and trash can
Example for the pending box and the trash can:
C:\DocuWare\Users\miller\PendingBox\
C:\DocuWare\Users\miller\TrashCan\
These directories must be added for each user under "Miscellaneous" in DocuWare Administration.
3.8.3
Last Login Information
The last login information are stored in the file DocuWare.Administration.exe.settings and in the registry. The information in the registry is needed for Terminal Server environment.
The registry entries concerning the login information are:
HKCU\Software\DocuWare\DocuWare\LastLogin\Username (string) HKCU\Software\DocuWare\DocuWare\LastLogin\Connection (string)
3.8.4
Scanning in terminal server environment
Scanning is not an option that is available when using terminal servers – and it is not mentioned in the manufacturers description. However, we have worked out three methods which will allow you to use a scanner in combination with DocuWare even within a server-based environment.
Network scanner and ACTIVE IMPORT 3:
In this scenario, create user profiles on the network scanner and configure the scanner in such a way that scanned documents are stored direct in the user-specific folders on the network. These folders are monitored by ACTIVE IMPORT 3, and you have the possibility of storing the documents for each job direct in a file cabinet, or to import them into a user-specific basket.
Local scanner and ACTIVE IMPORT 3:
Configure a server that is connected locally to a client in such a way that all documents are scanned into a local folder. The terminal services of Windows Server 2003 and the Citrix MetaFrame
Presentation Server 3.0 allow access to client resources such as hard disks. Thus, ACTIVE IMPORT 3 as a published application can monitor this local directory and import documents from there into a central basket, or store them in the file cabinet.
3.8.5
Using Add-On Modules
Using DocuWare modules works without any problems, though depending on the environment one or two adjustments may be required.
CONTENT FOLDER:
Using CONTENT FOLDER you need to decide on a strategy of how users will be working. One strategy is for the Administrator to only publish certain CFF or CF5 files for the users. To do this, he can specify
the path to the CONTENT FOLDER on the Citrix management console, followed by the path to the CFF or CF5 file.
Example:
C:\Program Files\DocuWare\DWCTFApp.exe C:\DocuWare\Users\schmidt\meetings.cf5
In addition, as mentioned earlier, users can access the client resources starting with Windows Server 2003 and also with Citrix Meta-Frame Presentation Server 3.0. It is also possible to store the CFF or CF5 files locally on the client. There is a Citrix client named Citrix Program Neighborhood Agent, which masters an operation called "content routing". This means that when calling a local file a program can be invoked from the terminal server, which then displays that file.
COLD/READ and AUTOINDEX:
These are 16 bit applications that have the property of working with .INI files for storing values and settings. In the case of COLD/READ and AUTOINDEX this is the Docuware.ini, which is stored in the root directory of each client (e.g..: C:\WINDOWS). When working on terminal servers these .INI files are stored user-specifically in C:\Documents and Settings\%User%\Windows\. So, if users receive a
message that no path was found for COLD/READ, this .INI file needs to be checked an any entries need to be made.
Smart Connect
Smart Connect can only be used in terminal server environments when only one user is active.