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
How do I transfer a Windows 2000 Terminal Services CAL to another computer? 

NOTE: Windows 2000 clients come with a built in TS CAL and hence do not recieve a CAL from the TS server.
The TS CAL is a per-seat license that allows for a one-time transfer to another client.

To transfer the licenses:

1. Run the Terminal Services Licensing program on your Windows 2000 server.
2. Press Properties on the View menu.
3. On the Connection Method tab, press Telephone and your country.
4. Press OK.
5. Use the Action menu to press Install Licenses. This starts the Licensing Wizard and returns a phone number.
6. Call the CSC and describe your need to reissue licenses. The CSR will direct you how to continue.

If you wish to remove the TS CAL from the original client device, use Regedt32 to navigate to:
HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing\Store\LICENSE00x
and delete the LICENSE000 or LICENSE00x key.

NNOTE: Windows 2000 clients come with a built in TS CAL and hence do not
recieve a CAL from the TS server.
The TS CAL is a per-seat license that allows for a one-time transfer to
another client.

To transfer the licenses:

1. Run the Terminal Services Licensing program on your Windows 2000 server.

2. Press Properties on the View menu.

3. On the Connection Method tab, press Telephone and your country.

4. Press OK.

5. Use the Action menu to press Install Licenses. This starts the Licensing Wizard
and returns a phone number.

6. Call the CSC and describe your need to reissue licenses. The CSR will direct
you how to continue.

If you wish to remove the TS CAL from the original client device, use Regedt32
to navigate to:

HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing\Store\LICENSE00x

and delete the LICENSE000 or LICENSE00x key.

NOTE: There may be two keys, one for the Windows 2000 or Windows NT computer and one for the TS CAL.OTE: There may be two keys, one for the Windows 2000 or Windows NT computer and one for the TS CAL.

How do I map a network printer on Terminal Service? 

This tip comes from Jsiinc.com at <"a href="http://www.jsiinc.com">http://www.jsiinc.com

Terminal Services on Windows 2000 and Windows NT 4.0 can NOT automatically map a network printer.
A Printer that is locally attached to a LPT, COM, or USB port can be automatically mapped.
You can map a network printer by using the Windows Scripting Host (WSH) to run a Visual Basic
script:

Set WshNetwork = CreateObject("WScript.Network")
PrinterPath = "\\YourServer\YourPrinterShare"
PrinterDriver = "YourPrinterDriver"
WshNetwork.AddWindowsPrinterConnection PrinterPath, PrinterDriver
WshNetwork.SetDefaultPrinter \\YourServer\YourPrinterShare

NOTE: YourPrinterDriver must exactly match the driver name in the Ntprint.inf file.

If you wish to add a different printer for each user who logs on to Terminal Services:

Set WshNetwork = CreateObject("WScript.Network")

Select Case WshNetWork.UserName

    Case "Username1"

        PrinterPath = "\\YourServer\YourPrinterShare1"
        PrinterDriver = "YourPrinterDriver1"
        WshNetwork.AddWindowsPrinterConnection PrinterPath, PrinterDriver
        WshNetwork.SetDefaultPrinter "\\YourServer\YourPrinterShare1"
   
    Case "Username2"

        PrinterPath = "\\YourServer\YourPrinterShare2"
        PrinterDriver = "YourPrinterDriver2"
        WshNetwork.AddWindowsPrinterConnection PrinterPath, PrinterDriver
        WshNetwork.SetDefaultPrinter "\\YourServer\YourPrinterShare2"
   
End Select

Using a logon script or Group Policy, run the script each
time a user logs on to Terminal Services.

Do you have any information on Windows 2000 Terminal Services?  

The best source of information on this one is direct from Microsoft. Here is the Windows 2000 Terminal Services Reviewers Guide copyright Microsoft Corporation.

Operating System

September 1999

Abstract

The purpose of this guide is to provide reviewers of Microsoft® Windows® 2000 Terminal Services with information regarding usage scenarios, key features and customer benefits of Terminal Services. In addition, the document details information the reviewer will require regarding installing, configuring and operating a Windows 2000-based server running Terminal Services, as well as a list of answers to the most frequently asked questions regarding Terminal Services.

Overview of Terminal Services

What Is Windows 2000 Terminal Services?

In 1998 Microsoft Corp. released the Windows NT® Server operating system 4.0 Terminal Server Edition, entering the server-based computing arena. Microsoft® Windows NT Server 4.0, Terminal Server Edition extended the Windows NT Server product line, delivering the Windows® operating system experience to diverse desktop hardware through terminal emulation. Terminal Server Edition offered the low-cost, centrally managed environment of the traditional mainframe, but added the familiar GUI-based environment, ease of use and breadth of application support the Windows platform provides.

With the release of Windows 2000, all versions of the Windows 2000 Server family integrate the Terminal Services functionality directly into the operating system kernel. This provides several benefits including better integration with the other Windows 2000 services, reduced administration overhead because only a single service pack is required to update the operating system and Terminal Services, and reduced product cost because there is no need to purchase a separate packaged product to acquire the Terminal Services functionality.

Running software on a Terminal Server enables all application execution and data processing to occur on the server. Applications are displayed on a user’s device with terminal emulator software, which can run on a variety of client hardware devices: a personal computer, a Windows-based terminal or even a Windows CE-based handheld PC device.

With Terminal Services, the terminal emulation client application sends keystrokes and mouse movements to the server using the Microsoft Remote Desktop Protocol (RDP). RDP is based on International Telecommunications Union’s (ITU) T.120 protocol, an international, standard, multiple virtual channel conferencing protocol used first in Microsoft NetMeeting® conferencing software. It is a Unicode-compatible, multichannel protocol tuned for high-bandwidth enterprise environments. RDP allows for automatic disconnection and remote configuration, and supports three levels of encryption. It also optimizes for different bandwidth allocations by allowing client-side bitmap caching and optional data stream compression for low-bandwidth support. The Terminal Server does all the data manipulation locally on the server and passes the display back to the client. This approach allows for centralized application management and minimized network bandwidth on high-data applications, and enables remote control of servers.

Users can gain access to Terminal Services over any transmission control protocol/Internet protocol (TCP/IP) connection including Remote Access, Ethernet, the Internet, wireless, wide area network (WAN) or virtual private network (VPN). The user experience is limited only by the characteristics of the weakest link in the connection, and the security of the link is governed by the TCP/IP deployment in the data center.

Terminal Services is the ideal solution for organizations that want to provide remote administration of network resources, a uniform experience to users in branch offices in remote locations, or a graphical interface for line-of-business applications on text-based computers. Some of the benefits of Terminal Services include these:

· Works with low-cost, Windows-based terminal devices

Can deliver the latest Windows-based applications to legacy desktop devices such as Macintosh computers, UNIX workstations, or even older DOS or Windows 16-bit PCs

· Requires minimal disk space, memory and configuration for Terminal Services clients

· Simplifies support for remote computers and branch office environments

· Provides centralized security and management

· Is unobtrusive to applications and the existing network infrastructure

Server Modes

Terminal Services is a built-in feature of Windows 2000 Server, Windows 2000 Advanced Server, and Windows 2000 DataCenter Server. When administrators install Terminal Services, they have the option of selecting one of two Terminal Services modes: Remote Administration or Application Server.

Remote Administration

Remote Administration gives system administrators a powerful GUI-based method for remotely administering any Windows 2000-based server over a TCP/IP connection. They can administer file and print sharing, edit the registry from another computer on the network, or perform most any task accessible from the console. This mode provides the most robust and extensive remote administration functionality available in a Windows 2000 environment.

Remote Administration mode only installs the components of Terminal Services required to provide remote access. It does not install the application-sharing components or affect the process scheduler, as does Application Server mode. This means Remote Administration can be run with very little overhead on mission-critical file, print or BackOffice® application servers. Terminal Services allows a maximum of two concurrent Remote Administration connections. In this mode, only system administrators can enable connections, so the server is protected from inadvertent or malicious access by an end user. No additional licensing is required for the two Remote Administration connections, and a Terminal Services license server is not required.

Application Server

In Application Server mode, applications can be deployed and managed from a central location, saving administrators initial development and deployment time as well as the time and effort required for maintenance and upgrade. Once an application is deployed via Terminal Services, many clients can connect using a Remote Access connection, local area network (LAN) or WAN. These can be Windows-based, Windows CE-based, or even non-Windows-based clients.

Licensing is required when deploying a Terminal Server as an application server. Each client, regardless of the protocol used to connect to Terminal Server, must have the Terminal Services Client Access License (TSCAL) as well as the Windows 2000 Server Client Access License (2000CAL). While each copy of Windows 2000 Professional includes a TSCAL, access from earlier versions of Windows NT, as well as clients using other platforms, must purchase additional TSCALs and 2000CALs. Licensing is covered in more depth later in this guide.

Terminal Services Usage Scenarios

There are four basic scenarios that have been identified in which customers implement Windows 2000 Terminal Services using either the Remote Administration or Application Server modes.

Remote Administration

Remote Administration enables system administrators with the appropriate permissions to remotely administer any Windows 2000 server over TCP/IP connections.

In this scenario, a system administrator may use any of the built-in Windows 2000 management tools such as the Microsoft Management Console (MMC)-based Domain Manager or Directory Services Administration to remotely administer servers within their own directory domain.

If Terminal Services is enabled in Remote Administration mode, server management can be provided to forests and into mixed mode domains where there are both Windows 2000- and Windows NT-based desktop computers. Terminal Services can also be used to administer clustered Windows 2000 servers.

Remote administration can be deployed on every server in an enterprise and allows direct connection and administration if all servers run Windows 2000.

Because enabling Terminal Services has little impact on a server, there is little reason not to enable Terminal Services on all servers in a forest. For mixed environments, or where control should be contained, Remote Administration can be deployed on a limited set of servers, such as the domain controllers. Other servers can be administered across the domain using LAN-based management tools. Administration on a Terminal Services Remote Administration enabled server can be performed from any client that is supported by the Terminal Services client.

Terminal Services has two built-in per-server connections specifically for Remote Administration, which requires no special licensing, as detailed later in this document. Multiple connections are provided to allow for collaboration and recovery. Remote Administration mode is not designed to support multi-user computing or multiple administrators running concurrently with different tasks.

Centralized Applications Deployment

Centralized applications deployment is achieved by desktop applications being loaded onto a Windows 2000 server with Terminal Services enabled in Application Server mode. Each client computer has a single, small application (the Terminal Services client) that enables the emulation of each user’s Windows-based desktop. Applications are actually running entirely on the server.

In this scenario, a global enterprise provides its users with reliable access to production and legacy applications, as well as office productivity tools. With Terminal Services enabled on a Windows 2000-based server, clients can run a controlled, standardized set of applications even when located remotely, or when using legacy client hardware. The Windows NT-based system security provides clients with only the appropriate access rights to both applications and data.

Because the Windows desktop experience is available to all users, developers can create standard Windows-based user interfaces for proprietary applications using tools such as the Microsoft Visual Basic® development system, and the development of separate client software for each legacy desktop device is not required.

Line-of-Business Application

Line-of-business applications are classic examples of server-based applications that send keystrokes and mouse movements to a server, which in turn performs all the data storage and manipulation.

In this scenario, data entry operators access a line-of-business application to enter product information into a database. Because the application is on a Terminal Server, the data entry operators can be working on Windows-based terminal rather than client computers. If a server goes down, work can be distributed to another server. If a terminal goes down, it can be replaced with minimal disruption to the data entry operator. Maintaining the data separately from the Terminal Servers supports this, and using Network Load Balancing across a farm of Terminal Servers provides the ability to distribute the computing across multiple “farmed” Terminal Servers.

Throughout an organization, departments are organized centrally, and security is designed to provide the appropriate access to only the information and network resources that are required by the tasks each user performs. Because Terminal Services is just part of the underlying operating system, it interoperates with and takes full advantage of built-in Windows NT technologies, eliminating security or reliability weaknesses due to the use of legacy operating systems at the client.

Remote Access

Remote Access extends the capabilities of Terminal Services over external TCP/IP connections.

In this scenario, users in a remote office with Terminal Services client software on their computers can access the applications on the Terminal Server back in a central office. Essential corporate data is accessed via a Remote Access connection over a modem. Since primarily keyboard and display information is being exchanged between the client and the server, the bandwidth requirements are low, providing an acceptable experience, even for users over a slow modem link. In fact, applications with high data access and low graphical requirements will run significantly faster over Terminal Services than over direct connect using a dial-up line. Applications can be added to the server without increasing the need for bandwidth, as long as they are not graphically intensive. Many companies use Terminal Services as a way to provide their employees who are working at home or sales people working in the field with access to standardized set of corporate desktop applications. Companies with many small or georgraphically dispersed branch offices may also use a dial-up configuration to lower management costs through centralized administration.

Before remote users can access network resources, they have to present their credentials and be fully authenticated. This is achieved using the integrated Windows 2000 security infrastructure.

Terminal Services Client Options

Terminal Services natively (without requiring the purchase of additional third-party software) support a wide variety of clients including Windows 32-bit (Windows 95, Windows 98, Windows NT 3.51, Windows NT 4.0 and Windows 2000 Professional and Server), Windows CE and Windows 16-bit (Windows for Workgroup 3.11) operating systems. Client support for Mac, Unix and DOS platforms is provided through third parties.

Each of these clients can take advantage of a full Windows 2000 desktop experience and the latest applications available for the platform, and/or remotely administer any Windows 2000-based server. The Terminal Services Client displays the desktop and applications currently running on the server.

Terminal Services Licensing

New in Windows 2000, Terminal Services has a built-in method for licensing clients that log on to Terminal servers which is transparent to the end user. Terminal Services licensing includes the following components: a license server, the Microsoft Clearinghouse, a Terminal Server and client licenses.

Each client computer or terminal that connects to a Windows 2000 server via Terminal Services (Application Server mode only) must have a valid Terminal Services 2000 client access license. After initial configuration, the client access license is stored locally on the client and presented to the Terminal Server each time the client computer or terminal connects to the server. When a client attempts to connect, the Terminal Server validates the client license and then allows the client computer or terminal to connect.

License Server

A license server stores all client licenses that have been acquired from the Microsoft Clearinghouse for a Terminal Server and tracks the licenses that have been issued to client computers or terminals. A Terminal Server must be able to connect to an activated license server before clients can be issued licenses. One license server can serve many Terminal Servers at the same time. The license server is required for Application Server mode only: if all Terminal Servers are in Remote Administration mode, no license server is required.

The Microsoft Clearinghouse is the database Microsoft maintains to activate license servers and to issue client license key packs to any license servers that request them. The Clearinghouse securely stores information about all activated license servers and key packs that have been issued. Users can access the Clearinghouse through the Licensing Wizard in the Terminal Services Licensing tool. The information collected by the Clearinghouse is housed separately and securely from other information a customer may have provided Microsoft. Microsoft will not use this information for marketing-related purposes. More information is available on Microsoft’s Privacy Policy for Terminal Services Licensing in Terminal Services Licensing online help.

Terminal Server

A Terminal Server is the server on which Terminal Services is enabled. When clients log on to a Terminal Server, the server validates the client’s license. If a client does not have a license, the Terminal Server requests one from the license server.

Client Licenses

Both a Windows 2000 Server Client Access license and a Windows 2000 Terminal Services Client Access License are required for each computer or Windows-based terminal connecting to Windows 2000 Server. Client Access licenses permit clients to use the terminal, file, print and other network services provided by Windows 2000 Server. The Terminal Services component of Windows 2000 Server requires per-seat licensing for the Windows 2000 Terminal Services Client Access license, except when the Windows 2000 Terminal Services Internet Connector license is purchased (see below for more on the Internet Connector license). This means every client device must be licensed, and a single Client Access Licenses may not be “shared” concurrently between different client devices. A Windows 2000 Terminal Services Client Access license or Windows 2000 Professional license provides each client computer or Windows-based terminal with the legal right to access Terminal Services on a Windows 2000 Server. For example, this license is required to start a terminal session and run Windows-based applications on the server. The Windows 2000 Professional license permits the legal right to access Terminal Services on a Windows 2000 Server without the purchase of a Windows 2000 Terminal Services Client Access license.

The Terminal Server Client Access license is not required for administrators connecting to a Windows 2000 Server in Remote Adminstration mode.

Optional Terminal Services Licenses

In addition to the required Terminal Services licenses, two optional licenses are available: the Windows 2000 Terminal Service Internet Connector License and the Work at Home Windows 2000 Terminal Services Client Access License.

The Windows 2000 Terminal Services Internet Connector License is used in place of the client access licenses and has unique usage implications. This license is purchased separately as an add-on license to Windows 2000 Server, and allows a maximum of 200 concurrent users to connect anonymously to a Terminal Server over the Internet. This is useful for organizations that want to demonstrate Windows-based software to Internet users without rewriting Windows-based applications as Web-applications. All users who access a Terminal Server with this license must be nonemployees.

When the Internet Connector license is used with a specific Windows 2000 Server, the server only allows client access through the Internet for Terminal Services. The Internet Connector license can not be used in addition to other types of Terminal Services client access licenses on the same Windows 2000 Server.

The Work at Home Windows 2000 Terminal Services Client Access License is available for organizations that want to use Terminal Services to provide their employees with home access to the Windows 2000 desktop and 32-bit Windows-based applications. The Work at Home Terminal Services Client Access license is available through the Microsoft Volume licensing programs. For each Windows 2000 Professional or Terminal Services Client Access License purchased for corporate employee use, an additional Work at Home Windows 2000 Terminal Services Client Access license can be purchased for employee home use.

Key features of Terminal Services

Feature Description

Ease of Use

Automated Local Printer Support *NEW* This feature provides ability to detect, install and access printers attached to Terminal Services clients. Such local printers are automatically made the default for that user, without exposing the printer to other Terminal Server or network users.

Clipboard Redirection *NEW* This feature provides ability to cut and paste between applications running on the local machine and those running on the Terminal Server.

New performance enhancements *NEW* Many improvements to caching, including persistent caching, packet utilization, frame size, and so on have provided significant performance improvements.

"Windows GUI" sent remotely to variety of desktop devices The new Windows 2000 GUI is delivered remotely to users of Windows-based terminals and legacy desktops, including Windows 16 and 32 bit-based, Macintosh and UNIX machines, as well as Win32® application programming interface-based desktops. (Connectivity to MS-DOS®-based, Macintosh and UNIX machines requires the Citrix MetaFrame add-on.)

Roaming disconnect support Users can disconnect from a session without logging off. They can leave a session active, or running, while disconnected and then reconnect to the existing session from another machine or at another time.

Multiple logon support Multiple simultaneous logon sessions from different desktops are supported. This enables users to log on to multiple Windows 2000-based servers or a single Windows 2000 Server multiple times to do multiple tasks or to run multiple unique desktop sessions.

Multilanguage user interface (MUI) *NEW* Localized Terminal Services clients in different languages can connect and properly display applications running on a single Windows 2000 Server.

Automatic session reconnection and session resume A session will remain active and even automatically reconnect on log-in when clients are disconnected from the server for a period of time.

Manageability

Remote control *NEW* Administrators can view, control and interact with other Terminal Services client sessions.

Complete Integration with Windows 2000 Server advanced management and infrastructure features *NEW* Terminal Services supports and extends all the Windows 2000 advanced features, such as the Active Directory™ services, Microsoft Management Console, etc.

Network Load Balancing support *NEW* Terminal Services clients can connect to the least busy member of a pool of Terminal Services servers.

Windows-based terminals running Windows CE (including Handheld Pro) Windows-based terminals for the Microsoft Windows 2000 Server Terminal Services, based on a custom implementation of the Windows CE operating system and the Remote Desktop Protocol, will be available from major terminal partners (such as Wyse Technology Inc., Network Computing Devices Inc., Boundless Technologies Inc., Tektronix Inc. and Neoware Systems Inc.) shortly after the release of Windows 2000 Server. *NEW* This now includes Windows CE for the Handheld Professional devices.

Client Connection Manager *NEW* Administrative client connection tool allows single-icon connections to sessions or applications to be developed through a simple wizard-based tool. The icon connections can be distributed throughout an organization to facilitate connection to the Windows 2000-based server.

Terminal Services License manager *NEW* Administrators can track and manage all the licenses for the Windows 2000 Terminal Services clients connecting to the server(s).

New System Policies components to allow further lockdown of Terminal Services-based desktops *NEW* New components have been added to the desktop and Start menu (Disconnect, Logoff and Windows NT Security) for Terminal Services-based clients. Added capabilities in the System Policy to disable those additional components of the Terminal Services-based client interface can be activated with a simple mouse click.

Centralized applications installation and update Administrators install applications once at the Windows 2000 Server and provide access to the latest applications immediately to all connected Terminal Services clients.

Terminal Services Administration The Terminal Services Administration tool is used to query and manage Terminal Services sessions, users and processes on Windows 2000-based servers. *NEW* This has been rewritten as an MMC snap in for adding future functionality and expandibility. Functions that can be performed include these:· Disconnect a session from a Terminal Services Session· Send a message to a Terminal Services Session/User· Reset a Terminal Services Session· Display Terminal Services Session connection status· Display Terminal Services Session client information· Display user and system processes· Terminate a process· Display Windows 2000 Server Terminal Services information

Terminal Services Connection Configuration Administrators can create, modify, and delete sessions and session sets on a Terminal Server. Functions that can be performed by Terminal Services Connection Configuration include these:· Configure a new connection· Manage permissions for a connection· Add users and groups to permission lists· Control timeout settings and disconnect settings

Integration with Windows 2000 Server User Manager User accounts for Terminal Server users are created in the same way they are for users of Windows NT Server. This allows existing PC users to access their accounts from terminal and terminal emulation desktops.

Integration with Windows 2000 Server Performance Monitor System administrators can easily track Terminal Services system performance. Performance Monitor with Terminal Services allows them to do the following:· Track processor utilization per user session· Track memory allocation per user session

How do I use the Windows 2000 PathPing utility to troubleshoot Network Connections? 

PATHPING is part of the Windows 2000 TCP/IP utility suite and is available in all Windows 2000 operating systems. You use PATHPING on the command line, much like PING and TRACERT. Type PATHPING /? to display command syntax and a list of available commands, shown here:

Usage:
pathping [-n] [-h maximum_hops] [-g host-list] [-p period]
[-q num_queries] [-w timeout] [-t] [-R] [-r] target_name

Options:
-n Do not resolve addresses to hostnames.
-h maximum_hops Maximum number of hops to search for target.
-g host-list Loose source route along host-list.
-p period Wait period milliseconds between pings.
-q num_queries Number of queries per hop.
-w timeout Wait timeout milliseconds for each reply.
-T Test connectivity to each hop with Layer-2 priority tags.
-R Test if each hop is RSVP aware.

When you execute PATHPING with a target host (the target_name parameter), it will first produce a report that shows the list of nodes that make up the path between your source machine and the target host, shown as standard output on the console. At this point, what you get from PATHPING is similar to what you would expect from TRACERT. However, PATHPING will pause standard output while it analyzes its diagnostic data, displaying the message Computing statistics for X seconds. The number appearing here is a best guess, so don`t hold your breath. Once PATHPING has all of the data and has completed its analysis, it displays a list of nodes and links and the percentage of packets lost at each one.

When you interpret PINGPATH`s reports, you should be primarily focused on the third column, This Node/Link Lost/Sent=Pct and Address, and on lines that end with a pipe (|) symbol, as these show statistics for links between routers. Statistics shown for routers on lines ending with an IP address are similar to what you would see if you pinged the router directly.

How do I configure the task bar settings (clock, small icons, autohide) as part of a policy? 

These settings are part of a windows state that doesn`t get written to the registry until logoff. The taskbar properties are stored in:
HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\StuckRects\Settings.

You can`t define binary values as part of a policy. You can however import a registry files
for that specific key using something like reg or kix when the user logs on:

So, to set the values you need to modify the toolbar to the settings you need and log off
and log on again. Then export the registry settings for the previously mentioned key.
Find attached some examples.

If you cut and paste the following you get auto hide with small icons:

REGEDIT4

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\StuckRects]
"Settings"=hex:38,00,00,00,20,03,00,00,58,02,00,00,3e,00,00,00,3e,00,00,00,1e,  00,00,00,04,00,00,00,03,00,00,00,fe,ff,ff,ff,3c,02,00,00,22,03,00,00,5a,02,  00,00,03,00,00,00,0c,00,00,00

This next example give always on top, small icons:

REGEDIT4

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\StuckRects]
"Settings"=hex:38,00,00,00,20,03,00,00,58,02,00,00,3e,00,00,00,3e,00,00,00,1e,  00,00,00,1e,00,00,00,00,00,00,00,fe,ff,ff,ff,3c,02,00,00,22,03,00,00,5a,02,  00,00,03,00,00,00,0e,00,00,00

And always on top, small icons and clock.

REGEDIT4

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\StuckRects]
"Settings"=hex:38,00,00,00,20,03,00,00,58,02,00,00,3e,00,00,00,3e,00,00,00,1e,  00,00,00,1e,00,00,00,00,00,00,00,fe,ff,ff,ff,3c,02,00,00,22,03,00,00,5a,02,  00,00,03,00,00,00,06,00,00,00
How do I change the name of My Computer to display the server name or username? 

Using Regedt32 edit Registry for My Computer. The key is :HKCR\CLSID\{20D04FE0-3AEA-1069-A2D8-08002B30309D}

Delete  the following value in this key and recreate as follows :
Value Name : (No Name)
Data Type : REG_EXPAND_SZ
Data : %USERNAME% %COMPUTERNAME%

(To do this delete the current value and using `Edit` from menu bar select`String`. Do not enter a value name.)

How do I reduce the size of the Server Memory in order to install applications that will not install? 
This comes from Microsoft Q article Q241289 at http://support.microsoft.com/support/kb/articles/Q241/2/89.ASP.

How to Change the Amount of Memory Used During an Installation


The information in this article applies to:
  • Microsoft Windows NT Workstation version 4.0
  • Microsoft Windows NT Server version 4.0
  • Microsoft Windows NT Server version 4.0, Terminal Server Edition
  • Microsoft Windows NT Server, Enterprise Edition version 4.0
  • Microsoft Windows 2000 Professional
  • Microsoft Windows 2000 Server
  • Microsoft Windows 2000 Advanced Server


SUMMARY

You can install Windows NT and Windows 2000 products with limited memory settings if necessary. This method allows the "virtual" removal of RAM. You do not have to physically remove chips and then replace them after the installation is complete.

NOTE: If you use this method for a Windows 2000 installation and your /maxmem setting is set to less than 64 MB, you receive the following error message and Setup does not continue:

This computer does not have enough memory to run Windows 2000.

This version requires 64.00 (MB)of memory (RAM).

Setup cannot continue. To quit Setup, press F3.

MORE INFORMATION

To install Windows NT or Windows 2000 products with limited memory settings:

  1. Edit the Txtsetup.sif file in the source files (this method does not work if you are installing from CD-ROM). The [SetupData] section must read:

    [SetupData]
    OsLoadOptions = "/nodebug /maxmem=32"
    OsLoadOptionsVAR = "/maxmem=32"
  2. Install Windows NT or Windows 2000.
  3. Edit the Boot.ini file to remove the /maxmem switch.
  4. Reboot. Windows then uses the installed physical memory.
What is the RDP client for the Handheld PC Professional included on the Windows 2000 Server and Professional CDs? 
Microsoft is expanding the client options for Windows NT Server Terminal Server Edition and Windows 2000 Terminal Services with the release of a Terminal Services client for the Windows CE Handheld PC Pro. With Windows 2000 Server, Microsoft is releasing client software that will enable devices running Windows CE Handheld PC (H/PC) Pro version 3.0 to seamlessly integrate with the existing Windows NT Server 4.0 Terminal Server Edition-based computers and the Terminal Services capabilities included in Windows 2000 Server. This client will work with both Windows NT Server 4.0 Terminal Server Edition and Windows 2000 Server. However, it offers the RDP 4.0 feature set and does not include the newer RDP 2000 features such as remote control, brush or persistent caching, or local cut and paste. This client is also available for download from the Windows CE site at http://www.microsoft.com/windowsce/products/download/term-serv.asp.
How should I set up NTFS Permissions on Terminal Server? 

Jen Madafer of Republic Steel has contributed this listing  she uses in her
envirounment for your assistance.
To use the below document, you must start at the first line and execute each line
below in the order that it appears (any line that applies to your
environment anyway).  The column labeled "Repl?" means `replicate?` and it
indicates whether you should check the box that says "change permissions on
subfolders?" or not.

It`s likely you run applications that aren`t included in this document.  My
approach to locking down a new application is to install and test it in a
user session.  Then log the user off and set the entire folder (that the app
is installed in) to "Read" only.  Then log in as the user again and test all
functions of the application that you can.  If everything still works, then
great.  Document it!

If something breaks, then I log the user off.  Turn auditing on for that
user and log them back in.  I then get up to the point immediately before
the app bombs and go to the server and clear Event Viewer`s Security log,
then go back to the users session and attempt the function that fails.
Before even clearing the dialog box that tells you it failed, go back to the
server and refresh event viewer to see what shows up in the security log.
Whatever file is referenced is the one the user needs more permissions to.
I typically give Change control to whatever file they need.  And, again,
document it!

NOTE:   in every step listed below the group “Domain Admins” and SYSTEM are given “Full Control”

The group   ‘Everyone’...	From:	       To:	       Repl?
M:\                         Full Control   Read         Yes
M:\temp                         Read        Full Control Yes
M:\wtsrv\system32\spool         Read        Change         Yes
M:\wtsrv\help                 Read        Change         Yes
M:\wtsrv\system32         Read   Spec file & dir: RWX No
M: or N:\execusoft         Full Control Remove “Everyone” Yes
N:\                         Full Control Read            No
N:\123rw\                 Full Control Read          Yes
N:\Acrobat3                 Full Control Read          Yes
n:\cbtlib\cache                          ? Change          Yes
N:\hgw                         Full Control Read          Yes
N:\kix                         Full Control Read          Yes
N:\lotusapp                 Full Control Read          Yes
N:\minisoft                 Full Control Read          Yes
N:\powerway                 Read         Full Control Yes
N:\Program Files         Full Control Read          Yes
N:\Program Files\MS Office
\Office\normal.dot (if exists)       Read Change
N:\Program Files\MS Office\Office\*.md? Read   RWX
N:\Program Files\MS Office\Office\xlstart ? Remove “Everyone” Yes
N:\Program Files\MS Office \Office\Library\Autosave.xla Read Full Control
N:\PTW32                         Full Control Read Yes
N:\QA9000                         Read         Change
N:\SAPPC                         Full Control Read Yes
N:\spc                                 Full Control Read Yes
N:\winzip                         Full Control Read Yes
I have a bunch of error messages in event log that say "Application error occured", most of the messages are coming from Internet Explorer 5.5 what can I do to prevent this? 

You can try the following and see if it helps. Navigate to the file OLEPRO32.DLL in the wtsrv/system32 directory right click on it and choose properties. Choose the security tab and add the everyone group and give them read access to this file. If this does not get rid of it try also adding read access to the following files for the everyone group if they exist:
oleaut32.dll
asycfilt.dll
hticons.dll
sndvol32.exe
stdole2.tlb
MSVBVM60.dll

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