Consider the following scenario. You have a domain that includes Windows Server
2003-based computers and Windows Server 2008-based computers. You set Terminal Services session limit values in a user object by using Windows Server
2008 tools, such as the Active Directory Users and Computers MMC snap-in. In this scenario, the
values that are stored in the user object will be interpreted incorrectly by
Windows Server 2003 terminal servers. Similarly, if the value is set on a
Windows Server 2003-based computer, Windows Server 2008-based terminal
servers will interpret the time-outs incorrectly.
For example, when
you set a time-out to 1 Day by using a Windows Server 2008-based
server, the parameter is displayed as 58 Minutes on a Windows
Server 2003-based computer. However, Windows Server 2003-based terminal servers
treat this as 20 seconds.
A
supported hotfix is available from Microsoft. However, this hotfix is intended
to correct only the problem that is described in this article. Apply this
hotfix only to systems that are experiencing the problem described in this
article. This hotfix might receive additional testing. Therefore, if you are
not severely affected by this problem, we recommend that you wait for the next
software update that contains this hotfix.
If the hotfix is available
for download, there is a "Hotfix download available" section at the top of this
Knowledge Base article. If this section does not appear, contact Microsoft
Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required,
you might have to create a separate service request. The usual support costs
will apply to additional support questions and issues that do not qualify for
this specific hotfix. For a complete list of Microsoft Customer Service and
Support telephone numbers or to create a separate service request, visit the
following Microsoft Web site:
Note The "Hotfix download available" form displays the languages for
which the hotfix is available. If you do not see your language, it is because a
hotfix is not available for that language.
Prerequisites
To apply this hotfix, you must have Windows Vista, Vista SP1, or Windows Server 2008 SP1 installed on the computer. The hotfix must be applied to all computers that will be accessed by using Terminal Services and to all computers that will be used to edit Active Directory User configurations. If you subsequently upgrade to Windows Vista SP2 or a later version, you must also install the hotfix on those remaining computers or upgrade them to Windows Vista SP2 (or a later version). If only some computers contain this hotfix or Vista SP2 (or a later version), you will experience variations of the symptoms that are described. For example, you will experience premature or overly long session timeouts, which corrupt the time-out value in the user objects.
Restart requirement
You must restart
the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released
hotfix.
Registry information
To use this hotfix, you do not have to make any changes to the
registry.
File information
The English version of this hotfix has the file
attributes (or later file attributes) that are listed in the following table.
The dates and times for these files are listed in Coordinated Universal Time
(UTC). When you view the file information, it is converted to local time. To
find the difference between UTC and local time, use the Time
Zone tab in the Date and Time item in Control
Panel.
Windows Server 2008 note
The MANIFEST (.manifest) files and the MUM (.mum) files that are
installed for each environment are listed separately. MUM and MANIFEST files, and
the associated security catalog (.cat) files, are important to maintaining the
state of the updated component. The security catalog files, whose attributes
are not listed, are signed by using a Microsoft digital signature.
For all supported x86-based versions of Window Vista, Windows Vista SP1, and Windows Server 2008
Collapse this tableExpand this table
File name
File version
File
size
Date
Time
Platform
Regapi.dll
6.0.6000.20947
66,560
28-Oct-2008
04:24
x86
Regapi.dll
6.0.6001.22296
67,584
28-Oct-2008
04:33
x86
Tsuserex.dll
6.0.6001.22296
77,824
28-Oct-2008
04:33
x86
For all supported x64-based versions of Window Vista, Windows Vista SP1, and Windows Server 2008
Collapse this tableExpand this table
File name
File version
File
size
Date
Time
Platform
Regapi.dll
6.0.6000.20947
91,136
28-Oct-2008
04:30
x64
Regapi.dll
6.0.6001.22296
89,088
28-Oct-2008
04:50
x64
Tsuserex.dll
6.0.6001.22296
93,696
28-Oct-2008
04:50
x64
For all supported Itanium-based versions of Windows Server 2008
To
work around this problem, make sure that the terminal service parameters for a user
are set at a computer that is running the same operating system as the terminal servers that they will use:
If a user uses a Windows Server 2003–based terminal server,
set the data for this user from a Windows Server 2003-based computer.
If a user uses a Windows Server 2008-based terminal server,
set the data for this user from a Windows Server 2008-based
computer.
Back to the top
