Terminal Services - Frequently Asked Windows Terminal Services Questions!

[12] Frequently Asked Asp Questions!
Updated: Jun 07, 2000
[188] Frequently Asked Citrix Questions!
Updated: Oct 10, 2006
[3] Frequently Asked Sco Tarentella Questions!
Updated: Aug 16, 2002
[260] Frequently Asked Windows Terminal Services Questions!
Updated: Aug 03, 2006
1 2 3 4 5 6 7 8 9 10 11 12 13 14 [15] 16 17 18 19 20 21 22 23 24 25 26
When my users click a Help topic or a program in one of the Microsoft Office 2000 programs, they receive a Windows Installer dialog box with the following text: Preparing to install... How do I prevent this? 

The below article from the MS KB may resolve your problem.

OFF2000: Windows Installer Runs Every Time Help Is Used on Windows Terminal Server or Windows 2000 Server

The information in this article applies to:
Microsoft Office 2000, on platform(s):
Microsoft Windows NT Server version 4.0, Terminal Server Edition
Microsoft Windows 2000 Server

IMPORTANT: This article contains information about editing the registry.
Before you edit the registry, make sure you understand how to restore it if
a problem occurs. For information about how to do this, view the "Restoring
the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key"
Help topic in Regedt32.exe.

When you click a Help topic in one of the Microsoft Office 2000 programs,
you receive a Windows Installer dialog box with the following text:

Preparing to install...
You then receive the following text in the dialog box:
Please wait while Windows configures Microsoft Office edition.
where edition is the edition of Microsoft Office that is installed. This
installation may take up to five minutes, and the installation source must
be available.

This behavior occurs when all of the following conditions are true:

Your computer is running Microsoft Office from Microsoft Windows NT Server
version 4.0, Terminal Server Edition, or Microsoft Windows 2000 with
Terminal Services enabled.

You are logged on as a user who did not install Microsoft Office.

Either the UserData system registry value or the OSAShortcut system registry
value is damaged or missing at the following registry key:

WARNING: Using Registry Editor incorrectly can cause serious problems that
may require you to reinstall your operating system. Microsoft cannot
guarantee that problems resulting from the incorrect use of Registry Editor
can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys and
Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete
Information in the Registry" and "Edit Registry Data" Help topics in
Regedt32.exe. Note that you should back up the registry before you edit it.
If you are running Windows NT or Windows 2000, you should also update your
Emergency Repair Disk (ERD).

For Existing Users
Follow these steps for each user who is experiencing the behavior:

Click Start, and then click Run.
In the Open box, type Regedit and then click OK.

Locate and select the following key in the registry:

On the Edit menu, point to New and then click DWORD Value.
With New Value #1 selected (highlighted), type UserData and then press
Double-click UserData, type 1 in the Data Value box, and then click OK.
On the Edit menu, point to New and then click DWORD Value.
With New Value #2 selected, type OSAShortcut and then press ENTER.
Double-click OSAShortcut, type 1 in the Data Value box, and then click OK.
On the Registry menu, click Exit.

For Future Users
To prevent this behavior for future users when they log on, follow these
Log on as an administrator of the computer.
Click Start, and then click Run.
In the Open box, type Regedit and then click OK.

Locate and select the following key in the registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal

On the Edit menu, point to New and then click DWORD Value.
With New Value #1 selected, type UserData and then press ENTER.
Double-click UserData, type 1 in the Data Value box, and then click OK.
On the Edit menu, point to New, and then click DWORD Value.
With New Value #2 selected, type OSAShortcut and then press ENTER.
Double-click OSAShortcut, type 1 in the Data Value box, and then click OK.
On the Registry menu, click Exit.

How do I add an adm policy template to Windows 2000 Server? 

To add or remove an Administrative Template (.adm file)

Open the Group Policy object you want to edit, and then right-click Administrative Templates.

Computer Configuration (or User Configuration)
Administrative Templates

Click Add/Remove Templates, and then in the Add/Remove Templates dialog box,
click Add.
If you want to remove a template, click it, and then click Remove.
If you want to add a template, click Add. Click the template you want to add
in the Add/Remove Templates dialog box and then click Open.

In the Add/Remove Templates dialog box, click Close.

Because the role of Administrative Templates has changed from Windows NT 4.0
to Windows 2000, it is not recommended to use Windows NT 4.0-style .adm files
on Windows 2000 clients.
If you do use the older .adm files to create namespaces in the Group Policy console,
you can control whether the Windows NT 4.0 System Policy settings are visible in
the details pane as follows: in the console tree click the Administrative
Templates node, on the console menu bar click View, and then click Show Policies
Only to select or clear that menu item. You can also use the Group Policy setting
Enforce Show Policies Only to do this:
User Configuration
Administrative Templates
Group Policy

It is also recommended that you use the Disable System Policy
(use Group Policy only) setting, which prevents System Policy settings
from ever applying to Windows 2000 clients.
If a Windows NT 4.0 client computer managed by a Windows 2000 server is upgraded
to Windows 2000, then afterward the computer receives only Computer Configuration
Group Policy, and not Windows NT 4.0 machine System Policy. The policy received by
the user who logs on will be User Configuration Group Policy if the user account
is in Active Directory. If the user account is managed by a Windows NT 4.0 domain
controller, then the user gets Windows NT 4.0 user System Policy.

Policies included with Windows 2000 only set registry keys and values in one of
these four reserved trees:

The first two are preferred. All four trees are secure, and cannot be modified
by a user who is not an administrator.

When Group Policy changes for any reason, these trees are wiped clean and
the new policies are then rewritten.

Windows NT 4.0 policies do not respect these special trees, and can write
to any part of the registry. After such a policy is applied, it persists
until the value is intentionally reversed, either by a counteracting Windows
NT 4.0-style policy, or by editing the registry.

It is possible for an Administrative Template (.adm file) to be added to Group Policy
that sets registry values outside of the approved Windows 2000 Group Policy trees,
although Windows 2000 does not include any such .adm file. The administrator
who chooses to install Windows NT 4.0-style .adm files should be aware that this
can lead to undesirably persistent registry settings.

After installing Internet Explorer 5.5 SP2 or Internet Explorer 6 the Citrix Active X client stops working and my Citrix nFuse apps stop working. How can I fix this? 

Service Pack 2 for Internet Explorer 5.5 Prevents NFuse Applications from Launching

Service Pack 2 for Microsoft Internet Explorer 5.5 (IE 5.5 SP2) renders the browser
incapable of launching published applications from a web page.
This includes NFuse icons or any static ICA file launched by the web browser.

After IE 5.5 SP2 has been installed, users are unable to launch published applications
using NFuse or any web-hosted ICA file. No error message is returned.
The installation of the Citrix ICA client on Windows machines copies a file named
NPICAN.DLL to the \Program Files\Internet Explorer\Plugins directory.
After client installation, as soon as Internet Explorer is launched,
the following registry key is created by IE:
HKEY_LOCAL_MACHINE\Software\Microsoft\Internet Explorer\Plugins\Extension\.ica

IF IE 5.5 SP2 is installed, the presence of this registry key creates an
incompatibility that renders IE incapable of launching published applications using
NFuse or any web-hosted ICA file. The registry key may be deleted, but as long as
the NPICAN.DLL file remains in the Plugins folder, the registry key is recreated
each time Internet Explorer is restarted and one attempts to launch a published

To resolve the issue, clients must follow these steps:
1. Delete the Program Files\Internet Explorer\Plugins\npican.dll file.

2. Delete the registry key and all of the subkeys under
HKEY_LOCAL_MACHINE\Software\Microsoft\Internet Explorer\Plugins\Extension\.ica 

3.Restart Internet Explorer.

Automating the solution
The file and registry setting may be deleted with a script file if the client machine
has access to regini.exe. Regini.exe is included by default on Microsoft Windows NT
and 2000 operating systems, but not Windows 95, 98 or Millennium Edition.
Regini.exe is also available in all versions of the Windows NT Resource Kit.
Create two text files, one called icafix.reg and one called icafix.bat, with the
following contents:

Contents of ICAFIX.REG:

Explorer\Plugins\Extension\.ica [DELETE]

Contents of ICAFIX.BAT:

del "%PROGRAMFILES%\Internet Explorer\Plugins\npican.dll"
regini icafix.reg

Executing icafix.bat on the client machine would delete the file and the registry entry,
assuming that %PROGRAMFILES% is a valid environment variable pointing to the Program
Files directory and that the client has access to a copy of regini.exe. On Windows 9x
systems, replace %PROGRAMFILES% with the actual path, e.g. C:\Program Files.
The script also assumes that the user has permission to modify this portion of the
registry. This content could be added to a domain login script if desired.

Once the file and registry key have been deleted, Internet Explorer 5.5 SP2 will be able
to launch applications using NFuse or static ICA files as soon as the browser is restarted.

I get a file not found error when trying to open an attachment from Microsoft Outlook 2000 within a Terminal Server session. How can I fix this? 

Outlook stores the attachments in the temporary internet files folder.
If you use roaming profiles and specify the temporary internet files folder not
to roam with it in a policy you may experience this problem.

You can try the following to see if it resolves your problem.

To get around this, you can add a line to the top of the usrlogon.cmd file
that creates the folder within the profile if it does not exist.

The usrlogon.cmd file can be found in %systemroot%\winnt\system32.
This file runs for each user at logon.

Adding the below lines will check to see if the folders exists and if not, creates them
and this should resolve your problem:

if not exist "%USERPROFILE%\Temporary Internet Files" md "%USERPROFILE%\Temporary Internet Files"

if not exist "%USERPROFILE%\Local Settings\Temporary Internet Files" md "%USERPROFILE%\Local Settings\Temporary Internet Files"
If you have more than one Terminal server based at the same location (a server farm), can the Notes application and work files be hosted on a file server so the Terminal servers can be set up as a pooled resource? 

Yes, this can be done. There are special configuration issues that need to be met so the user does not encounter share violations of his work files. In addition, there are access issues for the Notes application files that could slow down the MultiWin server as it accesses the file server systems as well as the network that ties them together. (For more information, refer to "Storing User Data Files on File Server with Citrix WinFrame, MetaFrame or Microsoft Terminal Server" [#174957 ]).
See http://support.lotus.com/sims2.nsf/852561c1006719a98525614100588964/0f158ac2570521798525680100619b23?OpenDocument
If the file server encounters a problem, the currently active user`s work files as well as any open Domino databases could become corrupt; therefore, great care must be taken to ensure the systems and network connection can support the user load and can be durable enough.
The user`s CACHE.DSK file must be held on the MultiWin server by using the following NOTES.INI setting:


Therefore, each user`s cache file is isolated form the other concurrent users.
You may require a session cleanup script on the MultiWin servers for when a MultiWin user session does not cleanly exit or if the user fails to exit out of their Notes client session before exiting the MultiWin session. This allows you to avoid the MultiWin server and file server resources being locked or to prevent creating a share violation of the user`s work files when the same user reconnects again.
The network between the MultiWin servers and file server(s) must be isolated so no other traffic is present. You may need to isolate the Notes-client-to-Domino-server traffic to an isolated network as well. (Review multi-homing Domino server technotes in this knowledgebase.)
The file server or file servers performance must be able to handle the heavy I/O that hosting the Notes client on the MultiWin servers requires. You may need to isolate these file servers for the exclusive use of the MultiWin servers.

Can the Lotus Notes application be installed as a shared resource on a Terminal server so the users can access the application files? 

Yes, treat the MultiWin server system as a file server to host the Notes application files for the MultiWin users. During the Notes install, you need to select the shared install checkbox and select the local MultiWin server`s hard drive as the destination volume. You must be careful that the directory and file access rights are correct (read only) so the files are not damaged by the MultiWin users. Each user still needs an independent data directory on the MultiWin server to hold their work files.

Can the Lotus Notes desktop be configured to be the same for all the Termial Server users so they all have the same baseline configuration? 

Yes, this can be done by duplicating a master user`s configuration so each Notes user has his or her own independent copy of the same copy of the DESKTOP.DSK file.

Can a Terminal server host a Lotus Domino server? 

No, the base OS (a modified version of NT) is not able to handle both functions concurrently as the OS resources are allocated differently, which can deprive the Domino server of its resource needs. In the case of Windows 2000, the OS toggles between the two modes of running depending on what options you have enabled. When running the Domino server process, you should not enable the terminal server service.

What is the correct method for installing SmartSuite millennium edition when running Windows 2000 Terminal Server? 

This issue was reported to Lotus Quality Engineering. SmartSuite 9.x must be installed using the multi-user switch for use with Windows 2000 Terminal Server. In addition, Windows Terminal Server requires the same patch as a Windows 2000 multi-user install. See Related Documents for Multi-User Patch. Use the steps below to complete a successful installation of SmartSuite 9.x.

Supporting Information:


1. On the Windows 2000 Terminal Server, you must be logged in as the Administrator account.

2. On the Windows TaskBar, choose Start, Programs, Accessories, Command Prompt.

3. Type "Change User /Install" (without quotes).

4. Install SmartSuite using the multi-user switch (type "Install /m" on the command prompt).

5. When Install finishes, reboot, if needed.

6. After you reboot, repeat Steps 2 and 3.

7. Change to the directory where the MuPatch.EXE file is.

8. Type "MuPatch.exe" to run it. You see the file`s name, and a progress bar.

When the patch completes, do the following:

1. On the Windows TaskBar, choose Start, Programs, Accessories, Command Prompt.

2. Type "Change User /Execute."

SmartSuite is now successfully installed for use with Windows 2000 Terminal Server.

NOTE: This behavior is different from that of Windows NT4 Terminal Server. Under Windows NT4 Terminal Server, the mult-user Install was not required. Microsoft handled all Registry issues for applications. Changes in Terminal Server surfaced these new issues.

Can more than one Terminal Server user access the same Notes client ID and user setup on the server concurrently? 

No, user account and work files cannot be shared. But, you can offer the same functionality by duplicating these files to independent directories and setting up a group of IDs that have the same ACLs that could be pooled via a network login script

1 2 3 4 5 6 7 8 9 10 11 12 13 14 [15] 16 17 18 19 20 21 22 23 24 25 26

Featured Links