Welcome to this TechNet Event

We would like to bring your attention to the key elements of theTechNet programme; the central information and communityresource for IT professionals in the UK:

• FREE bi-weekly technical newsletter• FREE regular technical events hosted across the UK• FREE weekly UK & US led technical webcasts• FREE comprehensive technical web site• Monthly CD / DVD subscription with the latest technical tools

& resources • FREE quarterly technical magazine

To subscribe to the newsletter or just to find out more, please visit www.microsoft.com/uk/technet or speak to a Microsoft representativeduring the break

Terminal Services

Server-Centric Computing Now and in the Future

Welcome

• Agenda09:00 – 09:30 Registration

09:30 – 11:30 Supporting Terminal Services

11:30 – 11:45 Coffee

11:45 – 12:45 Terminal Services Roadmap

• FacilitiesPhones off

Toilets in lobby

The PSS View: Supporting Terminal Services

Sasha LoncarevicCritical Problem ResolutionEMEA GTSC Platforms Support

Agenda

• Microsoft GTSC Support Processes• Support Statistics for Terminal Server• Common Issues

– Licensing– Scalability– Profiles– Printing

• Summary• Questions

Support Processes in EMEA GTSC

• Support Specialist– Incident database, KB (external, partner and

draft), Solution Objects (internal)– International/Local Aliases– Collaboration and mentoring– Escalate to CPR/EE

• CPR/EE– In-depth troubleshooting– Source code & Build Environment– Debugging and Instrumentation– Request for Collaboration/Hotfix with WinSE

• WinSE (sustained Engineering)– Part of Product Group– Instrumentation– Close collaboration with developers and PMs– Developers and WinSE are on aliases too

Support Statistics

• Terminal Services calls are categorised in two main areas– Licensing– All others

• Many sub-categories also coded– by engineer when closing the case

• e.g. “\Printer Redirection\Driver Comatibility\Misconfiguration”

• Results are analysed by Volume and Labour Time (Minutes per Incident)– Used to drive product development and

documentation

Support in 2004

• Windows 2000– ~10% of total Windows Server volume– ~5% of total Windows Server labour– Licensing accounts for half of volume,

a third of labour

• Windows 2003– ~15% of total Windows Server volume– ~7% of total Windows Server labour– Licensing accounts for 75% of volume

and labour

• Terminal Services Licensing is in the top 10 by labour

Windows 2000

Volume

Windows 2000

Labour

Windows 2003

Volume

Windows 2003

Labour

TS Other

TS Licensing

Non TS

Support Trends

• Volume increasing for Windows 2003 – Terminal Services improvements in Windows 2003

driving deployment

• Decreasing MPI for Windows 2000 and Windows 2003– Bugs exposed by modern scenarios being ironed out– Building a Hotfix stockpile

• Symptoms matched quickly

– Up to a third of non-Licensing calls resolved with an existing Hotfix

EMEA Virtual Team Experience

• Licensing– Connections denied, or licenses not tracked

• Scaling– Memory limitations– Old 3rd party drivers– Deadlocks and hangs

• Profiles– Incomplete profile upload/download

• Printing– Printers not mapped or jobs not printed

• Application compatibility– Lose profile settings

Licensing - Overview

• No licensing required in grace period– 90 days Windows 2000– 120 days Windows 2003

• Grace ends when Licensing Service is discovered– First contact obtains certificates to check

CALs

The Grace Period

Windows Terminal Services

Server running Licensing ServiceServer running

Licensing Service

Finding the License Service

• Discovery is done– Windows 2003

• In the background every hour until an in-site License Service is found

– Windows 2000• In the background every 15 minutes until a License Service

is discovered thereafter every 2 hours

– Or whenever a License Service is required• Upgrade or issue CAL

• Secure Licensing option in Windows 2003– Configured via Group Policy– Local “Terminal Server Computer” group

Finding the License Service

1. Registry override Multiple servers in Windows 2003

2. Check AD for site licence object Created during install Licensing Service

If Enterprise mode selectedUser modifiable (add servers)

Contact each and cache (EnterpriseMulti)

3. Check each DC (in site for Windows 2003) Contact each and cache (DomainMulti)

4. Broadcast

License Service Discovered

• Each device needs a CAL– Except with Internet Connector (Windows 2000) or Per User

mode (Windows 2003)

• Upon first connect, client offers a unique hardware ID• Terminal Server gets CAL from Licensing Service

– CAL is uniquely identified by client hardware ID and stored in Jet db

• CAL passed back to client and stored in its registry• Client offers CAL at subsequent connections

– Terminal Services validates the CAL

• No CAL and no License Service available = no session• License Server issues temporary CALs until Activated

License Service Not Activated

Windows Terminal ServicesTerminal Services Licensing Service

Activating the License Service

• User Interface for connection to Clearing House (CA)– Web Browser, telephone, fax, Internet

• Activated Windows 2003 License Service issues– Builtin CAL for Windows 2000/Windows XP clients

• Windows 2000 Terminal Services only• No Expiry, Unlimited pool, A02-5.00-EX

– Temporary CALs for Windows 2000 or Windows 2003• 90 days expiry, not renewable, A02-5.00-S or A02-5.02-S

– Full CAL for other clients (if CAL pak installed)• 52-89 day expiry, A02-5.00-S or A02-5.02-S

• Temporary CAL issued at first connect, marked after logon, and upgraded to full CAL on next connect– Prevent Denial of Service, and stealing of CALs

Activated License Service

Windows Terminal ServicesTerminal Services Licensing Service

Additional Considerations

• Lost license is ‘found’ via hardware ID– Some thin clients do not store license– Citrix caches licenses on Terminal Servers

• Metaframe XP replicates to all farm servers

• Deleting entire Licensing store (registry) on client causes new hardware ID generation

• Client renews CAL 7 days before expiry• Expired CALs returned to pool every 24 hours

Problems

• Multiple CALs for one client name

• Cannot connect– Cannot discover License Service– Cannot upgrade temporary CAL

• Backing up, moving License DB

Troubleshooting

• Eventlog (MPS Reports)• Resource Kit

– LSREPORT – LSVIEW– TSCTST

• PSS Tools– LSDIAG– TSTST

• Checked version of LSERVER.EXE• TermSrv tracing & additional instrumentation

Troubleshooting Connection

• Also for Remote Desktop– Ping target– telnet target 3389

• Check firewall if no connect but can ping

• Delete local license & retry

Recommendations

• Implement backup LS (no licenses)– Not ideal for certain cases e.g. Metaframe 1.8– Policy module is complex, some cases result in no

connection• Enterprise LS if possible, manual edit• Verify before deployment

– TSCTST– LSVIEW– LSAdmin

• Review KBs and Whitepapers822134 - The function of Terminal Server CALs in Server 2003823313 - Server 2003 TS licensing issues and requirements

Scalability

• Number of user sessions limited– Poor Performance– Errors during certain operations– New applications or sessions fail– Session or Server Hangs

• How many sessions can a server host?

Scaling – Windows 2000

• Tested in conjunction with NEC• Tests use classes of worker

– Data Entry Dedicated (3Mb), Data Entry (4Mb), Knowledge (9Mb), Structured (10Mb)

– Knowledge worker types a page in Word, responds to an email, creates a small spreadsheet, uses IE

– Data Entry Worker connects to and uses SQL via simple app

http://www.microsoft.com/windows2000/techinfo/administration/terminal/tscaling.asp

Scaling - Windows 2000 (NEC)

1 Kernel was tuned using the procedure described in the section entitled “Error! Reference source not found.”

2 System was kernel address space limited, even after tuning the kernel

3 Scenario not tested with a tuned kernel, as the 2-way configuration was kernel address space limited after the kernel was tuned.

Therefore no additional users would be able to logon if the server had the same amount of RAM as the 2-way.

4 This server was tested in a 2-way configuration with one processor disabled using the /numproc=1 boot.ini switch. Therefore it

was using a multi-processor kernel and HAL, rather than a uni-processor kernel and HAL.

5 Because of a limitation in the testing simulation tools, there was no canary timer script running for the Data Entry Worker

Dedicated (DEWD) scenario. As the standard Data Entry Worker was canary limited, it was assumed that the DEWD would

have also been canary limited running on the same hardware.

Server configuration

Structured

Task

Worker

Knowledge

Worker

Data Entry

Worker

Data Entry

Worker

Dedicated

8 x Pentium III

500 MHz

2 MB L2 Cache

4096 MB

105 Users 160 Users1,2 Not Tested3 Not Tested3

4 x Pentium III

500 MHz

2 MB L2 Cache

4096 MB

90 Users 135 Users Not Tested3 Not Tested3

2 x Pentium III

450 MHz

0.5 MB L2 Cache

1024 MB

40 Users 70 Users 320 Users1,2 350 Users1,2

1 x Pentium III

450 MHz4

0.5 MB L2 Cache

1024 MB

25 Users 35 Users 280 Users1 280 Users1,5

4 x Pentium Pro

0.5 MB L2 Cache

200 MHz

1024 MB

30 Users 50 Users Not Tested Not Tested

1 Kernel was tuned using the procedure described in the section entitled “Error! Reference source not found.”

2 System was kernel address space limited, even after tuning the kernel

3 Scenario not tested with a tuned kernel, as the 2-way configuration was kernel address space limited after the kernel was tuned.

Therefore no additional users would be able to logon if the server had the same amount of RAM as the 2-way.

4 This server was tested in a 2-way configuration with one processor disabled using the /numproc=1 boot.ini switch. Therefore it

was using a multi-processor kernel and HAL, rather than a uni-processor kernel and HAL.

5 Because of a limitation in the testing simulation tools, there was no canary timer script running for the Data Entry Worker

Dedicated (DEWD) scenario. As the standard Data Entry Worker was canary limited, it was assumed that the DEWD would

have also been canary limited running on the same hardware.

Server configuration

Structured

Task

Worker

Knowledge

Worker

Data Entry

Worker

Data Entry

Worker

Dedicated

8 x Pentium III

500 MHz

2 MB L2 Cache

4096 MB

105 Users 160 Users1,2 Not Tested3 Not Tested3

4 x Pentium III

500 MHz

2 MB L2 Cache

4096 MB

90 Users 135 Users Not Tested3 Not Tested3

2 x Pentium III

450 MHz

0.5 MB L2 Cache

1024 MB

40 Users 70 Users 320 Users1,2 350 Users1,2

1 x Pentium III

450 MHz4

0.5 MB L2 Cache

1024 MB

25 Users 35 Users 280 Users1 280 Users1,5

4 x Pentium Pro

0.5 MB L2 Cache

200 MHz

1024 MB

30 Users 50 Users Not Tested Not Tested

• 500MHz procs used – now Xeon 3.2GHz with HT not uncommon– Windows 2003 uses HT

better; Windows 2000 suffers slightly

• Scripted: No indication of ‘usability’

Windows 2000 Scaling (NEC)

0

50

100

150

200

250

300

350

400

1 CPU 2 CPU 4 CPU 8 CPU

Use

rs

Structured Task Worker Knowledge WorkerData Entry Worker Data Entry Worker Dedicated

Scaling - Windows 2003

• From product documentation on Microsoft.com– Users classed as Light (10Mb), Power (21Mb)

and Structured (10-21Mb)– Recommended RAM = 128 + user RAM as

above– CPU & RAM scale linearly…

• Depends on bus technology etc

– No users/CPU recommendation• Test, test, test

Scaling – Windows 2003

• Scalability Whitepaper– Tests use more modern hardware – Two worker classes

• Data Entry Worker (3.5 Mb)• Knowledge Worker (9.5Mb)

http://www.microsoft.com/windowsserver2003/techinfo/overview/tsscaling.mspx

Scaling - Windows 2003

1 Using Physical Address Extension and 6GB RAM 2 System PTE exhaustion 3 Response time degradation due to cache hit ratio drop 4 A dual processor P4 system was used and processors number was reduced to 1 by disabling hyperthreading and using /NUMPROC=1 in boot.ini configuration. The system was running multi-processor binaries. 5 This is a retired model used for legacy testing. For more information, see Appendix C.

Server Configuration Model Number Knowledge Worker Data Entry Worker

4 x Intel Xeon Processors MP 2 GHz

2 MB L2 Cache 4096 MB

DL560 270 Users1,2 520 Users3

2 x Intel Xeon Processors 2.4 GHz

2 MB L2 Cache 4096 MB

DL360G3 200 Users3 440 Users

1 x Intel Xeon Processors 4 2.4 GHz

2 MB L2 Cache 4096 MB

DL360 G3 140 Users 200 Users

2 x Intel Xeon Processors 2.4 GHz

2 MB L2 Cache 4096 MB

DL380G3 200 Users3 440 Users

2 x Intel Xeon Processors 2.4 GHz

2 MB L2 Cache 4096 MB

BL20pG2 200 Users3 440 Users

1 x Intel Ultra Low Voltage Pentium III 900 MHz 1024 MB

BL10e 50 Users 120 Users

4 x Intel Xeon Processors MP 2.0 GHz

2 MB L2 Cache 4096 MB

BL40p 240 Users3 Not Tested

x Pentium III Xeon 550 MHz

2 MB L2 Cache 4096 MB

ProLiant 6400R5 170 Users Not Tested

• When kernel address space limits, Windows 2003 is much better

• Otherwise, Windows 2003 still better– MM/OS design improved

• 64bit exciting– Hardware will limit– Until recent CPU performance

improvements, 64bit did not offer much

Windows 2000 vs Windows 2003

Limiters• Obvious : Hardware

– CPU, Disk, RAM, Network

• Less obvious : Software and Operating System– Address space limitations (2Gb Kernel, 2Gb User)– Redirector and other driver design– Registry size/contention– Applications

• Polling (keyboard or otherwise)• Not multi-user friendly design

– …most of these can be tuned

Common Problems

• Poor performance– Hardware limitations– Registry contention– Old client technology (UI needs accelerator)

• Logon and/or network file access slow (>15secs)– Redirector current commands, Server workitems

• KB232476

• Missing icons, user32.dll errors– Desktop Heap or session pool

• Application or session start failures– memory space limitations

• PagedPool 160Mb-380Mb (Windows 2000 registry hives)• NonPagedPool 128Mb, double in Windows 2003

MemoryMap

Kernel ModeKernel Mode

User ModeUser Mode

0k0k

2Gb2Gb

4Gb4Gb

8000000080000000

ffffffffffffffff

e1000000e1000000Paged Pool (160Mb)Paged Pool (160Mb)

Kernel code + initial Non paged pool

Kernel code + initial Non paged pool

eb000000eb000000

Non-paged poolSystem PTEs

Non-paged poolSystem PTEs

ffbe0000ffbe0000

Win32k space, session space

Win32k space, session space

a0000000a0000000

Xtra PTE/cacheXtra PTE/cache

a4000000a4000000

c0000000c0000000Process page tables etcProcess page tables etc

c1000000c1000000System CacheSystem Cache

Session Pool

16Mb

Session Pool

16Mb

Session View

(desktop heaps)

20Mb

Session View

(desktop heaps)

20Mb

Win32k & GDI drivers

8Mb

Win32k & GDI drivers

8Mb

Troubleshooting with Perfmon

• CPU– >75% usage– Q length>1 sustained

• Process– Identify spinning or leaking process– Private Bytes or Handle Count growing

• Memory – Page Faults/s >10000– Available memory <10Mb– Disk Q Length >1 sustained– Paged Pool, Non-Paged limits

Troubleshooting with Perfmon

• Physical Disk– Q Length > 1

• Thrashing due to paging, fragmentation

• Redirector (on Terminal Server)– current commands>20

• Server Work Queues (on File Server)– Available WorkItems <10– Resources dynamically allocated

• Workitems < MaxWorkItems• Connections created asynchronously

Demo• Performance Monitor• Redirector Current Commands• Server Workitems

Other Troubleshooting

• Network trace analysis– Repeated packets– Large RoundTripTime

• User-mode Debugging• Kernel Debugging (forced dump or live)

– Find deadlocked threads– Examine memory usage

• OEM tools– dheapmon.exe, userdump.exe

Recommendations

• Test scalability– Roboclient in Resource Kit– Performance Monitor– Sweetspot may be 4-way CPU with 2Gb– If task takes 10% longer than on empty server, server

is reaching saturation– Run User Acceptance Tests under desired load

• Scale out not up– Address space limitations, until 64 bit

• RAM and disk are cheap– <=4Gb, no PAE– Pagefile & OS on separate/multiple spindles/controller

Recommendations

• Rethink folder redirection & run apps locally

• Set up and test Memory Dump– Problems are more complex since hardware

allows greater loading

• Collect and store baseline performance data

Profiles – Overview

• User configuration, settings and files• Per machine persistence

– Cached locally in c:\documents and settings\username

• Optionally roaming, mandatory or temporary– PKI implications

• Stored on file server for roaming• Separate profiles available for Terminal Services

(not at console)

Establishing Profile Location• WINLOGON/MSGINA handles logon & obtains normal

profile path from user account– Set via UI, TSPROF, or scriptable Windows 2003 WTSADMIN

• If not at console then check GPO settings– Force local– Override path (append with %username%), not for mandatory

• Otherwise TS profile path retrieved via SAM API– RPC over SMB has firewall implications– Log event & optionally deny logon if SAM calls fail

• If profile path is still blank, use default profile– “\\logonserver\Netlogon\Default User” or– local “\documents and settings\Default User”

Profile Load

• Userenv has 10 threads to copy profile– Each file is copied to a prfxxx.tmp, target is

deleted & temp file renamed to target• ntuser.dat and usrclass.dat (Classes key,

non-roaming) loaded into HKEY_CURRENT_USER

• User policy applied– In foreground i.e. before desktop– background (90+- 30 minutes)– Loopback, if configured

Profile Unload

• Unload ntuser.dat, usrclass.dat– Retry 60 times, once per second

• Copy files (as per load) to roaming store

• Remove cached copy if DeleteRoamingCache enabled

• TermSRV waits 180s for completion of session close

Profile Problems

• Profile load/unload failures– Registry key in HKCU in use (unload)– File copy fails (file in use or other error)

• Usually AntiVirus• Redirector timing

• Profile path is blank or not collected– Password change code defect in Windows 2003

(KB833409)– >=SP4 provides single retry with DC rediscover– SAM 2048 handle limit (Windows 2000 DC)

Profile Problems

• XForestLogon (Windows 2003, Win2k >=SP4)– Prevent roaming profile and policy from

foreign domain

• Profiles shared between NT4, Windows 2000, Windows 2003 and Windows XP– ProtectedStorage one time migration

Troubleshooting Profile Problems

• Eventviewer– Userenv events in Application log

• userenv debug logging– userenvdebuglevel = 0x10002 (HKLM\...\Winlogon)– Make userenv.bak read-only

• UPHCLEAN– Identifies process holding registry key

• SPOOLSV.EXE usually implies printer driver

• Inspect HKEY_USERS– Each HKCU is loaded as user SID

Demo

• UPHCLEAN– Profile unload

Recommendations

• Use UPHCLEAN

• Monitor event log for problems

• Force local profile or use mandatory where possible

• Monitor disk space and cached profiles– DeleteRoamingCache has overhead

• Keep profiles small when using roaming

• Hybrid profile solution – beware PKI

Redirected Printing

• Seamless experience– Default printer on client is default in session– Print on Word in session, job comes out of local

printer

• Enabled by server, per user, or by client• At connect time, client printers are mapped into

user’s Terminal session• Jobs printed in session are spooled/rendered on

Terminal Server• Raw data conveyed to client

Redirected Printing

• Network printers in user profile are unaffected– Default is switched to client default, if the

printer is mapped

• Network printers on client can also be mapped– Process is the same – rendered job conveyed

to client for transfer to network printer– 5.0 client needs FilterQueueType registry

change

Mapping Printers – How it works

• After logon (reconnect), RDPDR requests list of ports and printer driver names from client

• Client returns filtered list (FilterQueueType)• RDPDR maps ports to TSxxx and notifies

Winlogon of printer ports and printer driver• Winlogon creates TSxxx port then calls Spooler

to create a printer on that port– Printer similar to local queue, port is TSxxx not LPTx– Printer name is decorated with session details– Permissions for current user only

Mapping Printers – How it works

• Printers only created if driver in ntprint.inf – or if admin has already installed printer driver– Driver names can be mapped with a wizard –

KB239088

• Client settings not mirrored during first connect– Persisted to client 60 secs after a change in

the session

Problems

• Bad drivers crash spooler– BSoD in NT4.0, still possible in Windows 2000 but mini-driver

model user-mode & more robust• No printers mapped

– No drivers– Process is asynchronous with logon – may be slow

• Wrong page size set (A4, Letter)• Spooler stressed

– Printers slow to appear, and get deleted– Jobs slow

• Overcome now (>=Sp4, Windows 2003)– Misdirected jobs– Printers seen by all users

Demo

• Redirected Printers

• Printer Driver Redirection Wizard

• Print job sizes

Troubleshooting

• System Event log– Data DWORDs helpful for PSS

• DrWatson log or Application Event Log– SpoolSV automatically restarts– Send in user.dmp for analysis

• Usually bad driver

• Performance Monitor– Print mapping thrashes registry, causes performance

data dropout– RegistryLazyFlushInterval tuning– SpoolSV CPU time

• WLNotify debug logging

Recommendations

• Be aware of rendered job sizes– Compressed in Windows 2003 but can still consume bandwidth

• Pre-Install required drivers and lock down installs– Add/Remove drivers user right– TrustedDriverPath (KB239536 still applies)

• Review KB324446 – RegistryLazyFlushInterval may need tweaking

• Monitor size of setupapi.log– Delete regularly

• Install latest versions of relevant files– Usbmon.dll, spoolsv.exe, localspl.dll, winsrv.dll, wlnotify.dll,

rdpdr.sys

Application Compatibility

• Remote Desktop or Remote Administration– Control Panel Add/Remove required in Windows 2000

• Application Server– Requires Control Panel Add/Remove– Check TSOC.LOG if errors occur – Additional overhead to maintain multi-user

compatibility• For applications that are not multi-user aware (very few these

days)

Application Server

• Install or Execute mode– Always logon into Execute mode– Install mode used when installing software

• HKCU changes copied to shadow registry• master INI file copies written in %systemroot%

– Execute mode to ensure multi-user awareness

• INI file changes to user’s copy of INI file• Missing HKCU keys fetched from shadow

Application Server Mode

• At logon– INI files newer in %systemroot% are merged or

copied to user directory– HKCU keys older than shadow keys _deleted_

• Unless overridden by registry (or process image)…– Windows directory mapped to home drive (or profile)

• INI files read from user’s Windows directory

– Missing HKCU keys read from shadow

Problems

• Settings revert to old values e.g. ‘Lose’ Office Config– Usually caused by NOT imaging servers…– KB297379

• Server not in correct mode– require more than two sessions, or non-administrator

• Internet Explorer, Outlook Express icons re-appear after removal– Explorer stubs difficult to remove

Troubleshooting

• 3rd Party Tools– REGMON from SysInternals for registry activity

• userinit deletes old shadows at logon

– FILEMON from SysInternals for INI file activity– use filters to reduce noise– run on console to capture activity in session

• PSS Tools– RDT, SDT

• Show and set reg key times so that shadow keys

Demo

• Shadow key deletion(time permitting)

3rd Party Value Add

• Many 3rd Party solutions are now available• Full Product Suite Add-ons:

– New Moon (Tarantella)– Citrix MetaFrame

• Other Add-ons:– HTTP Gateway/Firewall Traversal : Whale– Universal Printer Driver : TriCerat, ThinPrint,Jetro– Application Publishing : Jetro– Seamless Windows : Jetro– Application Monitoring/Eventing : Lakeside– Non-Windows Clients : HOBsoft– Integrated Load Balancing : Jetro

Summary

• Terminal Services stability and features in Windows 2003 is a driver of Windows 2003 deployment

• Licensing is a big issue – SP1 improvements• Current hardware allows loading up to address

space limits• A few bugs are being exposed under the

additional load allowed by current hardware– Unique challenges for in-depth troubleshooting

• Arsenal of hotfixes driving down time to resolution

Hotfix List – Windows 2000 SP4

324446 - Terminal Server and Connected Terminal Services Clients Pause W…327984 - Your Profile Is Not Unloaded If You Change Printer Settings and…813130 - A Computer May Lose Network Connectivity Under High Stress816134 - Citrix Terminal Server Sessions Are Not Disconnected and Cause …816560 - You Cannot Save Printing Preferences817275 - Office Documents Are Synchronized to an Offline Share Automatic…817446 - Terminal Services Stops Responding818523 - Dr. Watson Error Occurs When You Run a Program That Uses Utildl…818528 - Problems When More Than One User Accesses the Same File820550 - Spooler Service Crashes When You Submit a Print Job and an Even…820604 - Cannot Connect to a Printer or the Connection Is Slow from the …821225 - A Windows 2000 Terminal Server That Is Configured with Citrix M…822834 - Spooler Failure Causes High CPU Usage in the Winlogon.exe and823447 - Add Printer Wizard Does Not Complete the Installation of Your P…823485 - Errors Occur When You Use a .NET Framework 1.0-Based Program823747 - Windows 2000 Terminal Server Stops Responding and a Black Scree…824301 - Error Message Occurs When You Try to Connect to a Server by Usi…824309 - Very Long Logon Time When You Try to Connect to Citrix MetaFram…

Hotfix List – Windows 2000 SP4

825027 - Terminal Services Licensing Denies Your Connection to Your Term…826026 - Documents from Terminal Server Users Who Map LPT1 to Different …827664 - Local Security Policy Values Revert to the Values That Are Stor…827825 - "Windows Cannot Unload Your Registry Class File" Error Message …828326 - Slow logoff with 2 or more Redirected Printers828804 - Stop Error Code 0x1E Occurs If Your Server Has Terminal Server …829395 - The Terminal server does not automatically shut down when the829480 - WMI Query for the Name of a Console User Returns a Null Value830268 - NUM LOCK and CAPS LOCK keys are out of sync when you shadow ano…830515 - Processes in a Terminal Services session quit with access viola…831754 - You receive an error message when you try to print to a shared …832821 - Error 161 occurs when you use the runas command in a Terminal S…833123 - Windows 2000 may take a long time to start up and Terminal Serv…834423 - You cannot use RUNDLL32 to install printer drivers on a remote …834878 - Windows Installer package does not install correctly on a Windo…837321 - You cannot connect to a Windows 2000 Terminal Server if…837585 - Several orphaned Csrss.exe processes cause performance issues o…

Hotfix List – Windows 2003329896 - Because of a Security Error, the Client Could Not Connect to the Termin…813508 - Cannot connect to a Terminal Server from a Windows-Based…816513 - Poor Program Performance Occurs in a Remote Terminal Services Session821467 - Windows Server 2003 Terminal Server Stops Responding821929 - User Cannot Create a Terminal Server Roaming Profile Path If a User wit…822110 - The minimum encryption level set in a Citrix policy for Citrix MetaFram…823874 - Access Does Not Start After You Modify the Terminal Server Registry to …824309 - Long Metaframe Logon Time825027 - Terminal Services Licensing Denies Your Connection to…826821 - Terminal Server Remote Session Unexpectedly Runs in Install Mode828326 - Slow logoff with 2 or more Redirected Printers828662 - Terminal Server stops responding when idle sessions are829109 - Terminal Server Profile Path Is Ignored If the User Who Is Logging On D…829422 - Stop 0x0000008E" Error Message When a Terminal Services Client Prints a…831129 - Folder tree flickers when you view a mapped network drive in Microsoft …831716 - No Terminal Services License Server was found on the…831754 - You receive an error message when you try to print to a shared network …832048 - Terminal Services .ini files do not synchronize as you expect in Window…

Hotfix List – Windows 2003832088 - Windows Server 2003 Terminal Server ignores the idle disconnect setting…832129 - Word is waiting for another application to complete an OLE action" erro…832794 - TSL Wizard generates a PID that does not work832971 - Terminal Services stops responding on your Windows Server 2003 server833308 - "%" character in Terminal Services profile path appears as a numeric st…833409 - The roaming profile is not loaded after the user uses Terminal Services…833746 - You cannot print from a Terminal Server session833781 - "Windows cannot unload your registry class file" error message when you…833890 - Tsadmin.exe quits unexpectedly when you click the server…834651 - Terminal Services Lic mode changes from User to Dev834803 - License Server Security Group setting does not work in Windows Server 2…837211 - Clients cannot obtain permanent Windows 2000 Terminal Services Client A…837321 - You cannot connect to a Windows 2000 Terminal Server…837583 - STOP: 0x00000050 error occurs in Windows Server 2003…840371 - High processor usage from the spooler occurs when a user logs off from …840378 - Roaming profiles are not unloaded on a Windows Server 2003…840721 - Remote user cannot unlock a Terminal Services session…840872 - You may not be able to paste an item in an Office 2003