I will send the TS developers in Redmond an email today. -----Original Message----- From: Brian Madden [mailto:brian@xxxxxxxxxxxxxxx]=20 Sent: March 10, 2004 6:42 PM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Cursor blink rate in Windows 2003... Ron, Claudio, and I will all be attending the MVP Conference in Redmond in about three weeks. We'll be sure to ask the developers then. Hopefully that's not too long of a wait! Brian Brian Madden brian@xxxxxxxxxxxxxxx +1.202.302.3657 Visit www.brianmadden.com for in-depth Citrix, Terminal Server, and server-based computing news and analysis, white papers, downloadable videos, and product reviews. -----Original Message----- From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Jeff Durbin Sent: Wednesday, March 10, 2004 6:36 PM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Cursor blink rate in Windows 2003... Man, that's lame. Thanks Microsoft!=20 > -----Original Message----- > From: thin-bounce@xxxxxxxxxxxxx=20 > [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Sjolund, Dag > Sent: Wednesday, 10 March 2004 4:57 p.m. > To: thin@xxxxxxxxxxxxx > Subject: [THIN] Cursor blink rate in Windows 2003... >=20 >=20 > List Subscribers, >=20 > In preparing for an upgrade of a Windows 2000 Server-based=20 > terminal services farm to Windows 2003 Server, I have run=20 > into an issue with the cursor blink functionality on the=20 > Windows 2003 Server platform. After talking with Microsoft=20 > Support, cursor blinking functionality is programmatically=20 > disabled by design on the Windows 2003 Server platform for=20 > RDP sessions. This was not the case on Windows 2000 and NT=20 > 4.0 based platforms. Microsoft's reasoning for this design=20 > is likely anchored in the historically well known issue of=20 > bandwidth implications relating to a blinking cursor, coupled=20 > with the desire to make RDP protocol as "thin" as possible by=20 > default. Even though the cursor blink issue only had=20 > bandwidth implications in certain environments, the global=20 > disabling of this "feature" has ramifications in environments=20 > where available bandwidth is a non-issue. Does anyone have=20 > any connections with the right people at Microsoft to get=20 > something like this addressed? I have an active case with MS=20 > Support on this issue, though it is currently in a "We=20 > can't/won't change this functionality" > stage. The support rep is trying to address the issue=20 > through proper MS Support channels, but I figured I would try=20 > to assist him with some help from this distinguished forum. =20 > The cursor blink rate issue is a big one as it relates to=20 > window/field navigation, especially for visually impaired=20 > users, and though a minor detail configuration wise, is a=20 > show stopper for the overall solution. Someone with the=20 > right connections please respond.....please.... Did I say=20 > please? I'll attach an e-mail that I sent to MS Support for=20 > those who are really interested. For those who are not,=20 > sorry for temporarily taking up ~25K in your inbox. >=20 > Dag Sjolund, MCSE, CCNA, CCA, CISSP > Senior Systems Engineer > Best Western International, Inc. >=20 > ______________________________________________________________ > __________ > _ >=20 > [MS Support Rep], >=20 > The issue that we are experiencing with the CursorBlinkRate=20 > feature on Windows 2003 Server may have adverse implications=20 > on proceeding further with Windows 2003 Server-based Terminal=20 > Services implementations in our environment. Best Western=20 > International, Inc., THE WORLD'S LARGEST HOTEL CHAIN(r),=20 > currently utilize a multi-server, multi-farm Windows 2000=20 > Advanced Server Terminal Services solution to provide call=20 > center functionality for all Central Reservation Centers worldwide. > =3D20 > Though potentially viewed as a minor detail in the overall=20 > solution, one of the vital requirements of this solution is=20 > for the call center agents to at all times be able to=20 > identify where in their call center applications they have=20 > navigated. This is especially true for agents that are=20 > visually impaired and/or have other physical challenges=20 > relating to mouse movements and keyboard operation. With the=20 > Windows 2000 Server platform this was a non-issue, as the=20 > cursor blink rate was a functional and adjustable setting,=20 > that could be tailored to the target Terminal Services environment. > =3D20 > This brings us to the issue at hand: In Windows 2003, the=20 > cursor blink functionality has been globally disabled for the=20 > purpose of optimizing bandwidth usage of the RDP protocol and=20 > Terminal Services. As one can surmise, this means that even=20 > in scenarios were available bandwidth is not an issue, this=20 > feature cannot be enabled. In Best Western International's=20 > Terminal Services environment, cursor blinking has by design=20 > been enabled since the release of Windows NT 4.0 Terminal=20 > Server Edition, and is currently enabled in the Windows 2000=20 > Server-based implementation. The Terminal Services=20 > environment spans multiple LAN/WAN architectures, including=20 > Dial-up modem connectivity, DSL/ADSL, Frame Relay circuits,=20 > T1/T3, and 100/1000Mb LAN segments. The individual servers=20 > routinely handle 250+ concurrent Terminal Services sessions=20 > without performance issues. At no point have we experienced=20 > issues relating to bandwidth usage as a result of the cursor=20 > blink feature. > =3D20 > In summary, and judging from the numerous responses received=20 > from posts on newsgroups and other support forums on this=20 > topic, this issue is one that impacts decisions regarding the=20 > feasibility of Windows 2003 as a Terminal Services solution. =20 > The suggested behavior for the cursor blink feature would=20 > mirror the functionality on the Windows 2000 Server platform,=20 > but with one small adjustment: The cursor blink feature is=20 > enabled and adjustable, but the default behavior should be=20 > set to "no blinking" (-1). > =3D20 > Please investigate if would be possible to submit this case=20 > as a justification for a patch or revision of the associated=20 > code. Below are details of the issue experienced. Let me=20 > know if you have any questions or concerns. > =3D20 > Thanks, > =3D20 > Dag Sjolund, MCSE, CCNA, CCA, CISSP > Senior Systems Engineer > Best Western International, Inc. - THE WORLD'S LARGEST HOTEL=20 > CHAIN(r) =3D20 >=20 > -------------------------------------------------------------- > ---------- > -------- >=20 > =3D20 > Summary of issue at hand: >=20 > Platform: Windows 2003 Server Enterprise Edition with all=20 > updates, upgraded in place from Windows 2000 Advanced Server=20 > SP3. Running native Terminal Services (RDP 5.2). >=20 > Symptoms: User profiles retained the pre-upgrade=20 > CursorBlinkRate settings, but cursor is not blinking at all. =20 > The users are able to change the Cursor blink rate setting=20 > Control Panel's Keyboard applet properties, but it has no=20 > actual effect on the blink rate. Cursor blinking and the=20 > functional adjustment of this value seems to be globally=20 > disabled. There are no "override" string values in the=20 > HKLM\System\CurrentControlSet\Control\Terminal > Server\WinStations\RDP-Tcp\UserOverride\Control Panel\Desktop key. > Adding a "CursorBlinkRate" string value with a desired=20 > millisecond value in this key has no effect. >=20 > =3D20 >=20 > ******************************************************** > This weeks sponsor triCerat Inc. > triCerat makes your job easier by offering essential=20 > applications to eliminate your printing, policy and profile,=20 > and your application management problems. > http://www.triCerat.com > ********************************************************** > Useful Thin Client Computing Links are available at: > http://thin.net/links.cfm > *********************************************************** > For Archives, to Unsubscribe, Subscribe or set Digest or=20 > Vacation mode use the below link: > http://thin.net/citrixlist.cfm >=20 ******************************************************** This weeks sponsor Emergent Online. Emergent OnLine is the leading server-based computing consulting integration firm in the nation. Emergent OnLine delivers expert=20 consulting services you can depend on. http://www.go-eol.com ********************************************************** Useful Thin Client Computing Links are available at: http://thin.net/links.cfm *********************************************************** For Archives, to Unsubscribe, Subscribe or=20 set Digest or Vacation mode use the below link: http://thin.net/citrixlist.cfm ******************************************************** This weeks sponsor Emergent Online. Emergent OnLine is the leading server-based computing consulting integration firm in the nation. Emergent OnLine delivers expert=20 consulting services you can depend on. http://www.go-eol.com ********************************************************** Useful Thin Client Computing Links are available at: http://thin.net/links.cfm *********************************************************** For Archives, to Unsubscribe, Subscribe or=20 set Digest or Vacation mode use the below link: http://thin.net/citrixlist.cfm ******************************************************** This weeks sponsor Emergent Online. Emergent OnLine is the leading server-based computing consulting integration firm in the nation. Emergent OnLine delivers expert consulting services you can depend on. http://www.go-eol.com ********************************************************** Useful Thin Client Computing Links are available at: http://thin.net/links.cfm *********************************************************** For Archives, to Unsubscribe, Subscribe or set Digest or Vacation mode use the below link: http://thin.net/citrixlist.cfm