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]
Why aren`t my apps working in Terminal Server? Application Compatibility Scripts may be the answer. 

A lot of this is gleened from Citrix Documentation and from the Book Windows NT Terminal Server and Citrix Metaframe by Ted Harwood which I am going to highly reccomend especially for Integrators.
Do you know why your apps aren`t working in Terminal Server?
If you haven`t installed the proper application compatibility script that is probably the reason.
What are they?
Application Compatibility Scripts (ACS)are programs you must run after installing an application that take care of compatibility problems with Terminal Servers Multiuser Environment. They adapt the application to run properly under this environment. The application compatibility scripts can be found in C:\WTSRV\Application Compatibility Scripts Directory. The main directory contains several utilities written by M$ that are used in the scripts as well as some general purpose scripts. There are also three subdirectories. Logon, Install and Uninstall.
The logon directory contains scripts for application that should be run in the WTS logon script and they usually make changes to the users registry.
The uninstall directory contains uninstall scripts for the ACS. (Yes if you uninstall an application you also have to uninstall its corresponding ACS)
The install directory has the install scripts for certain apps. These are intended to be run AFTER the application is installed.

There is a suggested particular order of installing the ACS.
1. Set up the users home directories using the chkroot.cmd file
2. Install the application in the change user /install mode
3. Run the proper application compatibility script from the wtsrv/Application Compatibility Scripts/install directory

1. Home Directories
To set up the users home directory go to user manager and click on the users name and then click profile. Fill in the home directory path on this screen. You can use either the home directory path or if you want the users home directory to be on another server or share on the network use the connect to path. Run the chkroot.cmd file from the c:\wtsrc\application compatibility scripts directory. This will create a file called ROOTDRV2.CMD that you have to edit with notepad and add your drive letter you want as the root drive letter after the = sign on the line that says Set RootDrive= . Make certain this drive letter is not used by anything else on your system. The Rootdrv2.cmd file is a very important piece in the compatibility scripts and they all use it to map the users home directory.

2. Install the Application
Always install the applications using User Global Install Mode(change user /install) Install the application from the control panel add/remove programs applet or from the run in the start menu(only after you have issued the change user /install command). If you install through add/remove programs it puts you in the install mode.

3. Install Scripts
In the install directory there are many scripts for common applications. Corel Office 7,8 (coffice7.cmd & coffice8.cmd), Diskeeper 2.0 (diskpr20.cmd),Dr. Watson(drwatson.cmd) M$ Excel and Word 97 (excel97.cmd & word97.cmd), MS Internet Explorer 3.x and 4(msie30.cmd and msie40.cmd), MS Project 95 & 98(msproj95.cmd and msproj98.cmd), MS SNA Server(mssna30.cmd), Netscape Communicatory 4.0 and Navigator 3.0(netcom40.cmd and netnav30.cmd) ODBC drivers(odbc.cmd) MS SNA Server 4.0 and Client(sna40srv.cmd and sna40cli.cmd) Lotus Smart Suite 97(ssuite97.cmd)and Windows Messaging (winmsg.cmd) Also most vendors are starting to include ACS with their distribution disks. You may have to write your own acs to get your app working correctly. These scripts should be run right after you install your application for the first time. If you changed the directory from the default install directory when you installed your application you will have to open up the ACS with an editor and change it. It is a good idea to take a look at it before you run it anyways to see what it is doing. To run the ACS all you need to do is click on it to execute it. If the application needs a special logon script it will be created in the c:\wtsrv\application compatibility scripts\logon directory. There are two files here usrlogn1.cmd and usrlogn2.cmd. These files are run from the usrlogon.cmd file that every user gets when they log on. The install script will usually write to one of these two files.

There is nothing I can stress more than to read the readme files and documentation for Terminal Server and for your applications BEFORE you start doing anything. Terminal Server looks like NT, but it is a different beast when it comes to installing apps and getting them to work properly. I suggest you also check the Citrix and MS sites and your programs vendor first to see it there are ACS for your programs or updates before new installations.

In response to this document Brian Cambier, Certified Citrix Instructor of Asynch Technical Institute adds the following suggestions....

To all using Application Compatibility Scripts -

Do not just blindly run these application compatibility scripts (A.C.S.), print them out and see what they do to your system. Many (if not all) set security permissions or loosen security permissions on many files in \system32. I have had a couple of instances where the Office97 A.C.S., actually cripples other software. Yes, it does take time to review what each ACS does, but - do your due diligence before taking anyone`s (Microsoft or Citrix`s) word as gospel.

Also, if you need to uninstall an app, use the Add/Remove Programs applet in Control Panel and then check to see if an UNINSTALL ACS is available in \wtsrv\application compatibility scripts\uninstall. Not all apps that have an Install ACS have a Logon ACS or an Uninstall ACS. Either way, you may have to manually cleanup "call" statements in USRLOGN2.CMD after removing the software.

Just want to add this to the excellent post by Jim-
Brian Cambier MCT/CCI
ASYNC Technical Institute, Inc.
http://www.atii.com

Here is a document from Microsoft on how to write your own Application Compatibility Scripts.

Why am I having problems with my Hewlett Packard Printer not working or blue screening my Terminal Server? 

This is an issue that is annoying TS administrators across the land. Since MS and HP can`t ever seem to get along it is no wonder why we have to deal with such frustrations. I am still amazed at this phenomenom that HP continues to get away with distributing drivers that have so many bugs or just plain do not work. MS continually blames HP`s third party drivers for its woes. Unfortunately....HP has one of the most popular and "workhorse" type of printers out there, more unfortunate is the current drivers offered with Terminal Server for HP Printers literally CRASH the server spooler causing a blue screen.
After a month of messing around with this issue I have determined what currently as of (9/3/99> are the best possible settings and setup for the use of just about any HP printer.
For your perusal below there are three articles from the MS KB documenting the woes of owning an HP printer and trying to run it on Terminal Server. The one key suggestion is to use the printer drivers from the HP Laserjet 4 that are supplied on the Windows Terminal Server disk. MS indicates that HP is currently writing drivers for TS but it will most likely be a year and a day before it ever happens.
So my reccomendation is no matter what HP printer you have, you should install the driver for the HP laserjet 4 from the TS distribution disk for it ON THE TERMINAL SERVER. (let the client keep their driver information in other words) Next you have to set up a file on Terminal server that tells TS to use the hp4 driver for the clients connected printer. The name of this file is WTSUPRN.INF and you must create it from WTSUPRN.TXT as described in the below KB article. If you are using winterminals/dumb terminals you will have to set up the printer on the TS as an HPLJ4 despite what you have connected to it. You will also have to make sure that these printers have the correct security settings (ie the everyone group is removed)and to set them up to spool and begin printing immediately under scheduling
The next step is to set the HP printers to all think they are Laserjet 4`s. (At least until we have some stable CORRECT drivers from HP for Terminal Server). Again you do this through the WTSUPRN.INF file which resides in the WTSRV\System32 folder.
The important thing to remember when you are editing this file is that you have to have the EXACT name of the printer driver you installed on the WS and also the exact name of what you called your HP Laserjet 4 printer when you set it up. You may have to look at your local WS printer.inf file to find this.
The line to type in the WTSUPRN.INF file is fairly simple. For example if I had a Laserjet 5L on my workstation and I wanted TS to use the 4 driver for it I would type:

"HP LaserJet 5L" = "HP LaserJet 4"

This is usually the way that the printer name comes up but I have also seen it come up using Hewlett Packard in the name instead of the abbreviation HP. DO NOT JUST PUT RANDOM NAMES IN THIS FILE! Only put names of printers you KNOW that you have or TS will crash looking for a driver that is not installed.
I hope this piece of information helps you solve some of your headaches!

FROM: http://support.microsoft.com/support/kb/articles/Q191/6/66.ASP
Terminal Server responds with the following blue screen STOP error:
STOP 0x00000050 Page_Fault_in_Non-Paged_Area
when you print numerous print jobs to a Hewlett Packard LaserJet 5 P/MP, 6P/MP, or 2000C printer using a Hewlett Packard driver.
CAUSE
There are compatibility issues with the current printer driver and Terminal Server.
Windows Terminal Server with Metaframe ICA Client Cannot Autocreate Some Printers
FROM: http://support.microsoft.com/support/kb/articles/Q214/5/93.ASP

The information in this article applies to:
  • Microsoft Windows NT Server version 4.0, Terminal Server Edition


SYMPTOMS

After you connect a locally attached printer and load the printer drivers to the local workstation that has a Citrix Metaframe ICA client, you log on to the Terminal Server computer. The printer is supposed to be autocreated and available to you in the Printers folder of your Terminal Server session. The printer does not appear in the Printers folder.


CAUSE

If the printer driver name on the local workstation does not match the printer driver name on the Windows NT Terminal Server computer exactly, the printer will not autocreate. This occurs with Windows 95, Windows 98 and any other operating system or platform where the printer driver name on the client station does not match the printer driver name on the Terminal Server computer. If you are adding a new printer that is not native to Terminal Server, and the client and server print driver names are different, this problem will also occur.


RESOLUTION

There is a file on the Terminal Server computer that can be modified to make the disparate printer driver names appear to be the same and the autocreate function will work.

To make this modification, follow these steps:

  1. On the client workstation in local mode, not a Terminal Server session, click Start, click settings, and then click printers. Select the printer that did not autocreate and right-click it. Click Properties and then click the Details tab.
  2. Write down the name that appears in the Print Using the Following Driver box. This box contains the print driver name. For example, HP DeskJet 1600C ColorSmart.
  3. On the Terminal Server computer, click Start, click Settings, and then click Printers.
  4. Double-click Add Printer, click to select the My Computer radio button, and then click Next. In the Available Ports box, click to select the LPT1 check box, and then click Next.
  5. In the left pane, select the manufacturer of the printer you have installed on your workstation. In the right hand pane, scroll to the model of the printer you have installed on the workstation. For example, HP DeskJet 1600C. This is the server printer driver name for that printer. Write this name down.

    As you can probably see, the workstation printer driver name and the printer driver name on the Terminal Server computer are different. The server driver does not have "ColorSmart" added to it.
  6. In the %systemroot%\system32 folder, open the Wtsuprn.txt file. The file is as follows:
     ==========================================================================
     ; WTSUPRN.TXT 
     ;
     ; this is a template for wtsuprn.inf -- rename this file to wtsuprn.inf
     ;
     ; this file provides a mapping for client printers which have a name
     ; different from the server printer.  this file is necessary since many
     ; printers for Win95 are different from their WinNT equivalent.
     ;
     ; Note: the driver for the server printer must be installed.  See the
     ; WinFrame Concepts and Planning Guide.
     ;
     [Identification]
             OptionType = PRINTER
     [ClientPrinters]
     ;
     ;     Client Name                                  Server Name
     ;          |                                            |
     ;          |                                            |
     ;         \|/                                          \|/ 
     ;"HP LaserJet 4/4M"                          = "HP LaserJet 4"
     ;"HP LaserJet 4P/4MP"                        = "HP LaserJet 4P"
     ;"HP LaserJet 4 Plus/4M Plus"                = "HP LaserJet 4 Plus"
     ;"HP LaserJet 4Si/4Si MX"                    = "HP LaserJet 4Si"
     ;"HP LaserJet 4V/4MV"                        = "HP LaserJet 4V"
     ;"HP LaserJet 5/5M - Enhanced"               = "HP LaserJet 5"
     ;"HP LaserJet 5/5M - Standard"               = "HP LaserJet 5"
     ;"HP LaserJet 5/5M PostScript"               = "HP LaserJet 5"
     ;"HP LaserJet 5L (PCL)"                      = "HP LaserJet 5L"
     ;"HP LaserJet 5P/5MP (HP)"                   = "HP LaserJet 5P"
     ========================================================================== 
  7. Using this exact format, enter the previous information that you gathered from the workstation and the server.

    NOTE: Leave out the semicolon; this is used to remark the line out.

    Make sure you type the right driver under the proper colum. Client name would be the workstation; server name is the Terminal Server computer.

    For example:
     "HP DeskJet 1600C ColorSmart"                = "HP DeskJet 1600C" 
  8. After making the change, save this file with a .inf extension and then close the Wtsuprn.txt file.

    NOTE: From now on, if you have to add any other printers, add them to the Wtsuprn.inf file.
  9. Log off of the Terminal Server computer and log back on. Log your client workstation on to a Terminal Server session and you should now see your printer autocreated in the Terminal Server session printers folder, and you will be able to print to your local printer.


MORE INFORMATION

Installing a New, Non-Native Print Driver

http://support.microsoft.com/support/kb/articles/Q195/8/55.ASP
When you need to install a new print driver to your workstation, you will also have to install a print driver to the Terminal Server computer. Install the printer on the server as a local printer. Upon completion of the printer installation, delete the printer icon from the printer folder. The printer driver will be installed on the server and, when you connect the workstation to the Terminal Server computer, the new printer will be autocreated. If the print driver names are different between the workstation (client) and the server, follow the same procedure as above to make them the same. Application Exception in Spoolss When Printing
SYMPTOMS
When you use the Citrix ICA client and are connected to a server configured using the Metaframe add-on to Microsoft Terminal Server, you may receive a Dr. Watson error in Spoolss if using the HP LaserJet 4000 printer.
Application exception occurred:
App: exe\spoolss.dbg (pid=74)
When: 9/14/1998 @ 14:28:14.841
Exception number: c0000005 (access violation)
CAUSE
This issue may be caused because you may have a mismatched version of the Hpdcmon.dll file, or the Hpdcmon.dll file may be corrupted, or it may be unnecessary for proper operation.
RESOLUTION
Remove the dynamic link library file named Hpdcmon.dll from %SystemRoot%\System32 folder. If it is not found in this folder, perform a search of your %SystemRoot% folder including subfolders, and remove it from any folder in which it is found.
MORE INFORMATION
Hpdcmon.dll is a port status monitor that queries the parallel port for incoming information. Not all versions of Hewlett Packard`s printer drivers require this library file. Check with Hewlett Packard for more information on using this file with the printer driver being used.
The third-party products discussed here are manufactured by vendors independent of Microsoft; we make no warranty, implied or otherwise, regarding these products` performance or reliability.

Can I use Office 2000 on Windows 2000 Terminal Services? 
Yes. Using Terminal Services to deploy Office 2000 via a centralized server can be a cost-effective deployment option. In order to install Office 2000 on Windows 2000 Server running Terminal Services, you must install the Terminal Services tools in the Office 2000 Resource Kit. The Office 2000 Resource Kit and instructions on how to install Office 2000 on a terminal server are available on the Office 2000 Web site. Keep in mind that a valid Office 2000 license must be obtained for each device connected to Windows 2000 Server while running Office 2000 via Terminal Services.
What are all those jet*.tmp files in my WTSRV directory for. Can I delete them? 
These files are scratch files from the terminal server licensing and the license logging service . It always opens 4 *.tmp files. If it finds a pre-existing copy of the files on startup (and since it never cleans up the old ones this always happens) it creates 4 new ones whose names are numerically icremented = up by 0x4 hex each time. If you never had to reboot your system, you`d only ever have 4 jet*.tmp files ;-). The solution? Turn off the services, or just have a little script that deletes extraneous jet*.tmp files on startup..
Is RDP Performance improved in Windows 2000 Terminal Services? 

RDP performance is improved in Terminal Services for Windows 2000. Specific performance numbers will be released closer to the Windows 2000 launch. In addition, Microsoft, NEC Corp. and Groupe Bull are working together to determine capacity planning specifications for Terminal Services in Windows 2000 Server. These performance numbers will be released when Windows 2000 Server ships.

How do I set up profiles or policies using Windows Terminal Server? 

How do I Create User Profiles and Policies for MetaFrame Servers?

Synopsis:
Because MetaFrame is an addon to Microsoft Windows NT 4.0, Terminal Server Edition (TSE), user profiles and policies are a functionality of the TSE base operating system. MetaFrame administrators will find the following Microsoft Knowledgebase article extremely helpful in understanding and implementing user profiles and policies in TSE/MetaFrame environments.

Details:

For complete information on how to configure user profiles and policies in a TSE/MetaFrame environment see the Microsoft Technet article "Guide to Windows NT 4.0 Profiles and Policies," PSS ID Number Q161334.

This article is the first in a series of articles that provides information and procedures for implementing Microsoft Windows NT 4.0 profiles and policies on client workstations and servers.

A whitepaper is available that contains all of this information and additional flowcharts, diagrams, and examples and can be downloaded from the following web page:

http://www.microsoft.com/NTServer/Basics/TechPapers/default.asp

For the other sections of this guide, please see the following article(s) in the Microsoft Knowledge Base:

The beginning of these articles can be found by clicking here.
ARTICLE ID: Q185587
TITLE: Guide to Windows NT 4.0 Profiles & Policies Part 2 of 6

ARTICLE ID: Q185588
TITLE: Guide to Windows NT 4.0 Profiles & Policies Part 3 of 6

ARTICLE ID: Q185589
TITLE: Guide to Windows NT 4.0 Profiles & Policies Part 4 of 6

ARTICLE ID: Q185590
TITLE: Guide to Windows NT 4.0 Profiles & Policies Part 5 of 6

ARTICLE ID: Q185591
TITLE: Guide to Windows NT 4.0 Profiles & Policies Part 6 of 6

How do I install Internet Explorer 5 on Windows Terminal Server and Citrix Metaframe? 

As always be sure and do a backup and and rdisk /s before attempting the install of any new software on Terminal Server.

I have made the policy .adm files for IE 5 available for download at http://thethin.net/ieadm.zip Also remember to disable the system sounds that are created by IE5 by using the tip at http://thethin.net/soundoff.cfm

There is a good document on how to use the IEAK at http://technet.microsoft.com/cdonline/default-f.asp?target=http://technet.microsoft.com/cdonline/content/complete/Internet/Client/IE/technote/deploy5/intro.htm

Be certain that the you have a decent size paging file on the root drive or IE5 will not install..the error message you will get is application is already installed. further after you run IE5 and a reboot is done you MUST log back on with an account that has admin priviledges so that the installation can complete. You MUST also change to install mode by typing change user install and run the connection wizard as an admin so that it will not run for all users.

This tip comes to us with many thanks to:
Ed Evans
Sr. NT Windows Terminal Server Specialist
Purdue University Computing Center
edevans@purdue.edu
Note: I have edited and added comments where necessary. -Jim

--------------------------------------------------------------------------------

Internet Explorer 5.0 Installation Instructions Provided by the Windows Terminal Server Core Group

This installation should be performed at the console. This installation requires the server to be rebooted. It is recommended to logout all users and disable logons prior to beginning.

There are 3 components that will be needed to complete this installation: the Internet Explorer 5.0 installation program (ie5setup.exe), inetset.adm from the Internet Explorer Administration Kit (IEAK) for configuring policies, and the Internet Explorer 5.0 Patch for "Malformed Favorites Icon" Vulnerability. All of these products are freeware from Microsoft and can be downloaded from the following locations.

Internet Explorer 5.0: http://www.microsoft.com/windows/ie/default.htm
Internet Explorer 5.0 Patch: http://www.microsoft.com/windows/ie/security/favorites.asp
IEAK 5.0: http://www.microsoft.com/windows/ieak/en/download/default.asp.


Jim`s Note: You will also want to download apply the Java Virtual machine Security hole fix from:http://download.microsoft.com/download/javasdk/install/3186/w9xnt4/en-us/msjavx86.exe

-------------------------------------------------------------------------------
Internet Explorer 5.0 Installation:

1. Warn any connected users that the upgrade is taking place and the server will be rebooted. This can be done by sending a message with the Citrix Server Administration application.

2. Disable new logons on the server by right clicking on the server name in Citrix Server Administration and selecting Disable New Logons.

3. Open the Add/Remove Programs control panel and click the Install… button on the Install/Uninstall tab. Click Next.

4. When the Command line for installation program dialog box appears, browse to the location where ie5setup.exe was saved and click Next.

5. Select All users begin with common application settings and click Next.

6. The Windows Update: Internet Explorer and Internet Tools screen will appear. Select I accept the agreement and then click Next.

7. The next screen prompts you to select the appropriate installation type for Internet Explorer. Select Install Minimal, or customize your browser. Click Next.

8. The installer will now provide you the opportunity to customize the installation. (Jim`s Note:You can use the default setting for the directory but if you are installing on a load balanced farm it is best to be certain all servers have the same directory. If the server previously had IE4 on it, it will default to the Program Files Plus directory, if not it will be put in program files, internet explorer folder...be certain these things match up across servers. If you do not choose customize you are not given a choice where to install IE5.) Select Minimal for the installation type and make the following changes: · Select Microsoft virtual machine under Internet Explorer 5 · Unselect Windows Media Player under Multimedia Components This makes a total of 4 items that will be selected: · Internet Explorer 5 Web Browser · Internet Explorer Help · Microsoft virtual machine · Visual Basic Scripting Support Note: If this is an upgrade from Internet Explorer 4.01, you may not be able to unselect the Offline Browsing Pack, in that case there would be 5 items marked for installation. Click Next.(Jim`s note:You should also add outlook express if you expect to be mailing web pages)

9. Click Yes if prompted to create the installation folder

10. Select a download site and click Next.

11. Click Finish to restart the computer

12. Once WTS restarts, logon as an administrator to let installation finish.

--------------------------------------------------------------------------------

Internet Explorer 5.0 Patch for "Malformed Favorites Icon" Vulnerability

1. Logons are automatically enabled when the server is rebooted. Launch Citrix Server Administration and disable new logons again.

2. Download the Internet Explorer 5.0 Patch for "Malformed Favorites Icon" Vulnerability from the above location. Note: More information on this vulnerability can be found in Microsoft Security Bulletin MS99-018 at http://www.microsoft.com/security/bulletins/ms99-018.asp.

3. Open the Add/Remove Programs control panel and click the Install… button on the Install/Uninstall tab. Click Next.

4. When the Command line for installation program dialog box appears, browse to the location where q231452.exe was saved and click Next.

5. Select All users begin with common application settings and click Next.

6. Click Yes when prompted to install the update.

7. You should receive a message saying This update has been installed. Click OK.

8. Select the Next button on the After Installation dialog box followed by the Finish button on the Finish Admin Install dialog box to complete the installation. (Jim`s Note: It is at this point that you should also install the Java Virtual Machine Security fix. This fix requires a reboot and that you re log on as administrator after the reboot for it to finish. Be sure and install this fix in user install mode.)

--------------------------------------------------------------------------------

Configuring Internet Explorer 5.0:

1. Download ie5policy.zip from the above location. Extract inetset.adm and save it in c:\wtsrv\inf. Note: If Internet Explorer 4.01 was installed on the WTS server, you will be prompted to overwrite an older version of inetset.adm. Select Yes to replace the older file with the newer one.

2. Launch the System Policy Editor (under Start, Programs, Administrator Tools).

3. Add the inetset.adm template to the System Policy Editor as follows: · Click Options, Policy Template… · Click Add… and enter c:\wtsrv\inf\inetset.adm for File name: · Click Open. · Click OK on the Policy Template Options window. Note: This step is not necessary if c:\wtsrv\inf\inetset.adm is already listed in the Policy Template Options window.

4. Open the WTS policy by clicking File, Open Policy. For File name: enter c:\wtsrv\NTConfig.pol and click Open.

5. Double click on Default User and make the following changes under Advanced settings: · Click on Browsing until a check mark appears in the toggle box. Under Settings for Browsing, make certain only the following items are enabled (i.e. have a check mark in their toggle boxes): · Disable script debugging · Use smooth scrolling · Enable page transitions · Browse in a new process · Enable page hit counting · Underline links Always · Show Go button in the Address bar · Show friendly http error messages · Click on Security until a check mark appears in the toggle box. Under Settings for Security, make certain only the following items are enabled (i.e. have a check mark in their toggle boxes): · Enable Profile Assistant · Delete Save pages when browser closed · Warn if forms submit is being redirected · Warn if changing between secure and not secure mode

6. Click OK to close the Default User Properties window.

7. Double click on Default Computer and make the following changes under Component Updates: · Disable Periodic check for updates to Internet Explorer and Internet Tools (the toggle box should be clear, not gray) · Disable Help Menu>About Internet Explorer (the toggle box should be clear, not gray)

8. Click OK to close the Default Computer Properties window.

9. Save the file and exit the System Policy Editor.

10. Open My Computer and look for a new folder called Scheduled Tasks. This is a update to the Schedule service that sometimes installs with Internet Explorer 4.0. If Scheduled tasks does not exist, skip to step 17 .
11. Browse to c:\wtsrv. Right click on the tasks folder and select Properties.

12. Select the Security tab and click Permissions. In the Name: window, select Everyone and click the Remove button.

13. Select Replace permissions on Subdirectories. Click OK.

14. Locate mstask.dll in c:\wtsrv\system32. Right click on the mstask.dll and select Properties.

15. Select the Security tab and click Permissions. In the Name: window, select Everyone and click the Remove button. Click OK.

16. Launch regedt32 and delete the following registry key to get rid of Dial Up Networking(Note the line is wrapped for readability): · LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\ MyComputer\NameSpace\{D6277990-4C6A-11CF-8D87-00AA0060F5BF}

17. Reboot the WTS server. Logons will automatically be enabled after the reboot

How do I install OFFICE 2000 on Windows Terminal Server and Citrix Metaframe? 

Installing Office 2000 in a Windows Terminal Server Environment.

First things first, remember to do an rdisk /s before messing with the registry. The Thin Net or any other parties mentioned on this page will not be responsible for any damage you may do to your system from these hints. Be sure and read the Thin Net Copyright statement so that you fully understand this.

If you dont undertand some of the terms in this document click here to bring up the Office 2000 Glossary.

This is direct from MS and the CITRIX KB
Installing Office 2000 in a Windows Terminal Server Environment

Synopsis:
This document is based on information obtained from the Microsoft Web site. Click the following link for more information: http://www.microsoft.com/office/ork/2000/two/30t3.htm

Details:

Using Office 2000 with Windows Terminal Server

Microsoft Windows NT Server Version 4.0, Terminal Server Edition provides a thin-client solution in which Windows-based programs are executed on the server and remotely displayed on the client. If your users have computers with limited disk space, memory, or processing speed, you can install Microsoft Office 2000 to run in this environment.

IMPORTANT: You must install Microsoft Windows NT 4.0 Terminal Server Service Pack 4 on the Terminal Server computer before installing Office 2000. You can obtain Service Pack 4 from the Microsoft Web site.

With Terminal Server, you install a single copy of Office on the Terminal Server computer. Instead of running Office locally on their hard disks, multiple users can connect to the server and run Office from there.

TOOLBOX: Because of the special requirements for running Office in a Windows Terminal Server environment, you must use the transform provided in the Office Resource Kit to install Office on the Terminal Server computer. Office Setup does not install Office on the Terminal Server computer without this transform. For information about installing TermSrvr.mst, see the Office 2000 Resource Kit Toolbox.

The following is an overview of how you use Office with Terminal Server:

The administrator installs a single copy of Office on the Terminal Server computer. Users install Windows Terminal Client on their computers. Users log on to the Terminal Server computer, start Windows, and run Office from within the Windows session.

The Office applications run on the Terminal Server computer and only the Windows display is transmitted to users` computers.

In the Terminal Server environment, Office 2000 separates application and user data, and uses environmental information supplied by Terminal Server. This arrangement allows multiple Terminal Client users to run from the same Office installation.

To improve performance in the Terminal Server environment, Office optimizes certain functions in the Office applications to reduce the amount of network traffic necessary to update the user`s display. For example, in the Terminal Server environment, Office applications display a text-based splash screen, rather than the standard graphics-based screen - the text-based screen is faster to display.

TIP: You can improve the performance of Office in a Terminal Server environment even more by reducing the amount of incidental display information transmitted over the network. For example, select the Office Logo Office Assistant, which uses the least amount of animation, and set application options that eliminate menu or cursor animations. Alternatively, install the Motionless Office Assistant from the Office Resource Kit.

How to Install Office Disk 1 on a Windows Terminal Server

You install Microsoft Office 2000 from Microsoft Office 2000 Disk 1 on a Microsoft Windows Terminal Server computer in much the same way you install Office on a client computer. With some careful planning and a few modifications, Office performs well in the Windows Terminal Server environment.

To run Office 2000 in this environment, follow these steps:

1. Customize the Terminal Server transform (MST file).

2. Install Office on the Terminal Server computer.

3. Set default Office application settings for Windows Terminal Client users.

4. Configure Microsoft Outlook 2000.

Running Office on individual users` computers is different from running it in a Terminal Server environment. When you install Office on a Terminal Server computer, the users who connect to the server are limited to your Office configuration and cannot install or remove features.

In other words, all users running Office from the Terminal Server computer inherit the features you select during installation. If your users need different sets of Office functionality, you might need several Terminal Server computers - one for each unique Office configuration.

Because of the multiuser nature of the Terminal Server computer and users` restricted access to the server, you cannot select the following installation options for any Office features:

Run from CD or Run from Network
Run all from CD or Run all from Network
Installed on First Use

Instead, you must predetermine which Office features your users need and select one of the following installation options for each feature:

Run from My Computer
Run all from My Computer
Not Available

Customizing the Terminal Server Transform

The Microsoft Office 2000 Resource Kit includes a Windows installer transform that you must use when installing Office on the Terminal Server computer - Setup does not install Office on the Terminal Server computer without the transform. This transform, named TermSrvr.mst, is configured to install all Office features to run from the local computer or not be installed at all.

TOOLBOX: Because of the special requirements for running Office in a Windows Terminal Server environment, you must use the transform provided in the Office Resource Kit to install Office on the Terminal Server computer. Office Setup does not install Office on the Terminal Server computer without this transform. For information about installing TermSrvr.mst, see the Office 2000 Resource Kit Toolbox.

What the TermSrvr.mst File Does

The Windows installer transform included in the Office Resource Kit, TermSrvr.mst, is configured to install Office correctly on the Terminal Server computer. Office Setup does not install Office on the Terminal Server computer without this transform.

The primary function of the TermSrvr.mst file is to modify the feature tree so that all Office features are installed to run from the local computer. There are a few exceptions - those features that are not recommended or that do not perform well in the Terminal Server environment are set to not be installed at all.

In addition, the NOUSERNAME property is set so that Setup does not supply a default user name when you install Office on the Terminal Server computer. This setting ensures that users who log on to the Terminal Server computer are asked to provide a user name when they run an Office application for the first time. This property is set internally in the transform - if you examine the transform with the Custom Installation Wizard, you do not see the NOUSERNAME property listed on the Modify Setup Properties panel.

The TermSrvr.mst file also sets a property to increase the amount of registry space allocated for Office on the Terminal Server computer. This setting allows Office to store necessary information in the registry for each Office user. Again, this property is not listed on the Modify Setup Properties panel.

In the TermSrvr.mst file, all Office features are set to one of the following installation states:

Most features are set to Run from My Computer. These are features that work well in the Terminal Server environment.

A few features are set to Not Available. These are features that do not perform well in the Terminal Server environment, typically because they use additional animation that generates excess data traffic between the Terminal Server computer and the Terminal Client computer. Consider leaving these features set to Not Available so that they are not installed.

A few features are set to both Not Available and Hidden. These features do not work under Terminal Server because they rely on capabilities not available in this environment or they require write access to restricted areas of the Terminal Server computer. Leave these features set to Not Available so that they are not installed on the Terminal Server computer.

Some features are set to Run from My Computer and Hidden. These are features that are normally hidden in the Office Setup feature tree, but they have been exposed in the Custom Installation Wizard so that you can choose whether or not you want to install them.

TOOLBOX: A number of Outlook features, normally hidden in the Office Setup feature tree, are exposed in the Terminal Server transform. This arrangement allows you to choose whether or not to install these features. The Office Resource Kit includes an Excel worksheet named OutlFeat.xls that describes these Outlook features. For information about installing OutlFeat.xls, see the Office 2000 Resource Kit Toolbox.

If you want to accept the default Office configuration, you do not need to modify TermSrvr.mst. However, if there are Office features that are not needed by your users, you can improve overall performance and conserve disk space by customizing TermSrvr.mst so that Office Setup does not install these features on the Terminal Server computer.

Installing non-English Versions of Office

The TermSrvr.mst file was created using the Windows installer package (Data1.msi) for the US English version of Office 2000. Some other language versions of Office have additional features that are not present in the US English version and the TermSrvr.mst file does not change the installation states of those features. If any of these additional features are set to Run from Network or Installed on First Use, they do not function correctly on the Terminal Server computer.

To install a non-English version of Office on a Terminal Server computer, use the Office Custom Installation Wizard to make sure that all features in the transform are set to either Run from My Computer or Not Available.

To Customize the Terminal Server Transform

1. Start the Office Custom Installation Wizard.

2. On the Open the MSI File panel, specify the Office MSI file, Data1.msi.

3. On the Open the MST File panel, select Open an existing MST file and enter the file name and path of the TermSrvr.mst file.

4. On the Select the MST File to Save panel, enter the file name and path of the TermSrvr.mst file.

If you do not want to modify the original MST file, enter a new file name for the wizard to create.

5. On the Set Feature Installation States panel, set unneeded features to Not Available. Make sure that all features you want to install are set to Run from My Computer.

6. If you are installing Outlook, under Microsoft Outlook for Windows\OutlookMessaging, select either OutlookMAPI or OutlookOMI; set one feature to Run from My Computer and the other feature to Not Available.

7. On the Customize Outlook Installation Options panel, select Customize Outlook profile and account information and set Configuration Type to either Corporate or Workgroup Settings or Internet Only Settings.

This choice must match your choice in Step 5. If you select OutlookMAPI, you must select Corporate or Workgroup Settings; if you select OutlookOMI, you must select Internet Only Settings. Because users are restricted in how they can configure the Terminal Server computer after installation, you must make this selection during installation.

8. On the remainder of the panels, make additional customizations to tailor the Office installation on the Terminal Server computer.

For example, to fully customize how Internet Explorer 5 is installed, click Customize on the Customize IE5 Installation Options panel.

TOOLBOX: By default, the Terminal Server transform (TermSrvr.mst) does not install any Office Assistants. However, after running Office Setup you can install the Motionless Office Assistant (Stillogo.acs) included in the Office Resource Kit. This Office Assistant uses no animation, so there is minimal network traffic between the Terminal Server computer and the Terminal Client computer. For information about installing the Motionless Office Assistant, see Terminal Server Tools in the Office 2000 Resource Kit Toolbox.

Installing Office on the Terminal Server Computer

To install Office, run Office Setup on the Terminal Server computer. You can run Setup from a network administrative installation point or from the Office Disk 1. You must specify the Terminal Server transform (TermSrvr.mst) and additional command-line options.

NOTE: Before you install Office on a Terminal Server computer, log on to the server with administrator privileges.

How to Install Office Disk 1 on a Terminal Server Computer

1. In Control Panel, double-click Add/Remove Programs, click Install, and then click Next.

2. Click Browse.

3. In the root folder of the Office Disk 1, select setup.exe and click OK.

Setup.exe is added to the command line for installation program box.

4. On the command line, add the following two commands after setup.exe, separated by spaces:

TRANSFORMS="path\TermSrvr.mst"

This command identifies the Terminal Server transform for Setup to use during installation. Specify the correct path to the MST file.

/l* "%WINDIR%\Office 2000 Setup(0001).txt"

This optional command places the Setup log file in the Windows folder, rather than in the %TEMP% folder so that it is not deleted automatically by Windows.

5. Click Next.

6. In Add/Remove Programs, select All users begin with common application settings, and then click Next to run Office Setup.

IMPORTANT: You must use Add/Remove Programs in Control Panel with the All users begin with common application settings option selected. This setting runs Setup in Install mode, which installs Office for all Terminal Client users who connect to the Terminal Server computer. If you run Setup directly from Office Disk 1, Setup runs in Execute mode, which installs Office only for the user running Setup.

Setting Default Office Application Settings

You can use the Profile Wizard to customize the default Office user settings for all users logging on to the Terminal Server computer. For best performance in this environment, consider setting the following options in Office applications.

Microsoft Access 2000

1. On the Tools menu, click Customize, and then click the Options tab. Set the Menu animations option to None.

2. On the Tools menu, click Customize. Remove the Detect and Repair command from the Help menu.

3. On the Tools menu, click Options, and then click the General tab. Clear the Provide feedback with sound check box.

Microsoft Excel 2000

1. On the Tools menu, click Customize, and then click the Options tab. Set the Menu animations option to None.

2. On the Tools menu, click Customize. Remove the Detect and Repair command from the Help menu.

3. On the Tools menu, click Options, and then click the Edit tab. Clear the Provide feedback with animation check box.

4. On the Tools menu, click Options, and then click the General tab. Clear the Provide feedback with sound check box.

Microsoft FrontPage 2000

On the Tools menu, click Customize, and then click the Options tab. Set the Menu animations option to None.

Microsoft Outlook 2000

1. On the Tools menu, click Customize, and then click the Options tab. Set the Menu animations option to None.

2. On the Tools menu, click Customize, and then click the Commands tab. Remove the Save as Web Page command from the File menu, and remove the Detect and Repair command from the Help menu.

3. On the Tools menu, click Options, and then click the Other tab. Click Advanced Options and clear the Provide feedback with sound check box.

4. On the Tools menu, click Options, and then click the Preferences tab. Click E-mail Options and clear the Display a notification message when new mail arrives check box.

5. On the Tools menu, click Options, and then click the Preferences tab. Click E-mail Options, click Advanced E-mail Options, and clear the Play a sound and Briefly change the mouse cursor check boxes.

6. On the Tools menu, click Options, and then click the Preferences tab. Click Calendar Options and clear the Use Microsoft Schedule+ as my primary calendar check box.

Microsoft PowerPoint 2000

1. On the Tools menu, click Customize and then click the Options tab. Set the Menu animations option to None.

2. On the Tools menu, click Customize. Remove the Detect and Repair command from the Help menu.

3. On the Tools menu, click Options, and then click the General tab. Clear the Provide feedback with sound to screen elements check box.

4. On the Tools menu, click Options, and then click the Spelling and Style tab. Clear the Check spelling as you type check box.

5. On the Tools menu, click Options, and then click the General tab. Click Web Options, click the General tab, and clear the Show slide animation while browsing check box.

Microsoft Word 2000

1. On the Tools menu, click Customize, and then click the Options tab. Set the Menu animations option to None.

2. On the Tools menu, click Customize. Remove the Detect and Repair command from the Help menu.

3. On the Tools menu, click Options, and then click the General tab. Clear the Provide feedback with animation and Provide feedback with sound check boxes.

4. On the Tools menu, click Options, and then click the Spelling and Grammar tab. Clear the Check grammar as you type check box.

5. After you customize all the application settings you want, run the Profile Wizard and save your settings in an OPS file. Store the OPS file in a folder that is accessible to users running Office from the Terminal Server computer.

To point users to your customized settings:

1. On the Start menu, click Run, and type regedit.exe to open the Windows Registry Editor.

2. Create a new subkey named RunOnce in the following subkey:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion
\Terminal Server\Install\Software\Microsoft\Windows\Current Version

3. In the RunOnce subkey, create a new entry with a string value and any value name. Set the value of the new entry to the following: path\Proflwiz.exe /r file /q, where path is the fully qualified path to the Profile Wizard and file is the file name and fully qualified path to the OPS file you created.

When users log on to the Terminal Server computer, Windows runs the Profile Wizard using the command line in the RunOnce subkey and restores the settings you saved in the OPS file. This command runs one time for each user the first time the user logs on to the Terminal Server computer.

Configuring Microsoft Outlook 2000

To complete the installation of Outlook 2000, you need to perform two additional steps after running Office Setup

1. Run Outlook 2000 once.

2. Optionally provide write access to a portion of the Windows registry.

Outlook 2000 performs a number of initialization tasks when it runs for the first time on the Terminal Server computer. These tasks complete the Outlook installation and require write access to system areas on the Terminal Server computer.

To allow Outlook to finish installing:

1. Before any user runs Outlook on the Terminal Server computer, log on to the Terminal Server computer as the administrator.

2. Run Outlook. Outlook completes any remaining installation tasks.

3. Exit Outlook.

By default, users have write access to all portions of the Windows registry on the Terminal Server computer. However, if you have any custom Outlook forms installed on the computer and you have configured the Windows registry on the Terminal Server computer to restrict user access, you need to make sure that users have write access to the HKEY_CLASSES_ROOT\CLSID key in the Windows registry.

Outlook registers custom forms the first time they are opened; this requires that the user have write access to this portion of the registry.

To give users write access to the CLSID key:

1. Log on to the Terminal Server computer as the administrator.

2. On the Start menu, click Run.

3. Type regedt32.exe and click OK.

4. In the HKEY_CLASSES_ROOT window, select CLSID.

5. On the Security menu, click Permissions.

6. In the Registry Key Permissions dialog box, select the Replace Permission on Existing Subkeys check box and then click Add.

7. In the Name box, click Everyone, click Add, and then click OK. If you do not want to give all users this access, you can add specific users or groups of users in the Names box, rather than selecting Everyone.

8. In the Type of Access box, select Special Access and then select the Query Value, Set Value, and Create Subkey check boxes.

9. Click OK and close the Registry Editor.

See Also

Office 2000 Setup contains other options that you may want to take advantage of, such as installing Microsoft Internet Explorer 5 and removing previous versions of Office. For more information about Office 2000 Setup, see Office Setup Program.

By using the Office 2000 Custom Installation Wizard, you can modify TermSrvr.mst to further customize your Terminal Server installation. For more information about the Custom Installation Wizard, see Office Custom Installation Wizard.

For more information about the user settings that the Profile Wizard saves and restores, see Profile Wizard. The following is an overview of how you use Office with Terminal Server:

The administrator installs a single copy of Office on the Terminal Server computer. Users install Windows Terminal Client on their computers. Users log on to the Terminal Server computer, start Windows, and run Office from within the Windows session.

How do I set the start page in Internet Explorer via a policy? 

Put the following in an .adm file and use it as a template:

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
CLASS USER   ;;;;;;;;;;;;;;;;;;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
CATEGORY !!Strings_Pages 
KEYNAME "Software\Microsoft\Internet Explorer\Main"

POLICY !!Start_Page
PART !!Default_Page_URL  EDITTEXT
VALUENAME "Start Page"
END PART
PART !!Search_Page  EDITTEXT
VALUENAME "Search Page"
END PART
END POLICY

END CATEGORY;
[strings]
Strings_Pages="Definition of Home and Search pages"
Start_Page="Change the Start or Search pages?"
Default_Page_URL="Enter the URL for the home page."
Search_Page="Enter the URL for the search page."
Are there any installation issues for installing OFFICE 97 on Terminal Server and Citrix Metaframe? 

Here is some further information from MS Release Notes on installing Office 97 on TSE.
This is from http://www.microsoft.com/ntserver/terminalserver/techdetails/moreinfo/ReleaseNotes.asp

MICROSOFT OFFICE 97 AND OFFICE 97 APPLICATIONS

Description of Issues
Office 97 has various application compatibility issues. They include:
Files that need permissions different from the default.
Files that need to be moved to the user`s home directory.
Removal of the Find Fast option.
How to Solve After installing Office 97, run the %systemroot%\Application Compatibility Scripts\Install\Office97.cmd script. This will correct the issues listed above. The installation script will also add the %systemroot%\Application Compatibility Scripts\Logon\Ofc97Usr.Cmd script to UsrLogon.cmd. This script ensures that the needed per-user directories and files have been configured.
Customization
None.
Limitations
Office 97 Custom Dictionaries. The only per-user custom dictionary is the file Custom.dic created in the \Office97 subdirectory in the user`s home directory. The list of custom dictionaries is not private for each user. Any new custom dictionaries that may be created by users will be seen by other users.
Office 97 Menu Animation. Users should avoid enabling the Menu Animation feature in Office. Enabling this feature can severely affect system performance.
Access 97 Tools and Wizards. Some Microsoft Access wizards and tools do not support concurrent use, including Combo Box Wizard, List Box Wizard, Lookup Wizard, Option Group Wizard, Database Documenter Wizard, Table Analyzer Wizard, Table Wizard, Field Builder, and Switchboard Manager. Database Documenter is not supported on servers using NTFS and running securely. To use the Documenter database, users must have permission to modify the System.mdw file. To use Database Documenter, users must be granted Write permission on the %systemroot%\System32\System.mdw file.
Creating Access 97 Workgroups. If you create a new Access Workgroup using Wrkgadm.exe you will need to change the security permissions on the new Workgroup Information File for the groups Administrator and Everyone to Read in order to make Access available to all users. Only administrators can create Workgroup Information Files.
Adding Users to Access 97 Workgroups. If you want to add users to an Access Workgroup with the Security command on the Tools menu, you must first change permissions on the Workgroup information file to Write (the default Workgroup information file is %systemroot%\System32\System.mdw). Once users have been added, you should change permissions back to Read.
PowerPoint 97 Conference Presentations. The PowerPoint Presentation Conference command on the Tools menu can be used by only one person on a server. It is not possible for several people on a server to conference among themselves.

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