Kb2481109 for windows server 2003

Security Update for Windows Server 2003 x64 Edition (KB2481109)

A security issue has been identified that could allow an unauthenticated remote attacker to compromise your system and gain control over it.

A security issue has been identified that could allow an unauthenticated remote attacker to compromise your system and gain control over it. You can help protect your system by installing this update from Microsoft. After you install this update, you may have to restart your system.

Knowledge Base Articles:	KB2481109
Security Bulletins:	MS11-017

System Requirements

Operating Systems: Windows Server 2003 Service Pack 2 x64 Edition

Installation Instructions

1. To start the download, click the Download button and then do one of the following, or select another language from Change Language and then click Change.

Related Resources

Microsoft Security Bulletin

Источник

Remove From My Forums

Question
в наличии Windows Server 2003 R2 x64 и windows Server 2008 R2. оба сервера являются терминальными.

при подключении с 2003го по протоколу RDP к серверу 2008 возникает ошибка в протоколе лицензирования («удаленный компьютер отключил сеанс, из-за ошибки в протоколе лицензирования.. «)

с Windows Server 2003R2 x32 подключение происходит нормально и без ошибок.

все системы обновлены, но на 2003R2 x64 версия файла mstsc.exe — 5.2.3790.3959, на WS2003R2 x32 версия mstsc.exe — 6.0.6001.18564

как обновить RDP?

Answers

Посмотрите
тут

СПАСИБО! все работает!

Сделал следующее

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nls\Language\Default — 0409

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nls\Language\InstallLanguage — 0409

перезагрузился, поставил обновление (WindowsServer2003.WindowsXP-KB925876-v2-x64-ENU.exe)

потом поменял значения обратно на 0419

перезагрузился… все работает.
- Marked as answer by
  
  Wednesday, May 8, 2013 6:52 PM

Источник

Remote Desktop Connection (RDC) 6.1 for Windows Server 2003

Posted on 26/05/2011 Updated on 22/04/2012

I read and hear a lot of questions about why Remote Desktop Connection 6.1 or later doesn’t exist for Windows Server 2003. Well, if you’re wondering, I have good news for you: RDC 6.1 does exist for Windows Server 2003!

First of all, Remote Desktop Connection (RDC) is the Microsoft RDP client, previously called Terminal Services Client (TSC). It’s by far the most common tool to connect to a Remote Desktop Protocol (RDP) server, which is actually every somewhat modern Windows system. The RDP server component of Windows systems (clients and servers) is called Remote Desktop Services (RDS), formerly known as Terminal Services (TS). Some of those Windows systems can be put in a special mode to allow more remote connections/sessions, making the system a so-called Remote Desktop Session Host (RDSH) or Terminal Server (TS) (the former name).

The last version of RDS, RDP and RDC is 7.1, introduced with SP1 of Windows 7 and Windows Server 2008 R2. This version doesn’t exist for Windows Server 2003 though. Hell no, the latest version of RDC supported for Windows Server 2003 was 6.0. Till recently… Microsoft has published an update for RDC 6.0 and 6.1, upgrading those versions to the latest build of 6.1. This update is also valid for Windows Server 2003, meaning you can upgrade your RDC 6.0 on WS03 to the latest build of 6.1!

Well, it’s still not the same as 7.0 or 7.1, which implies you still can’t get things like multimedia redirection (WMP redirection), true multimonitor support, audio recording (and thus getting a form of bidirectional audio redirection), the so-called “enhanced graphics”, RemoteFX, etc. on a WS03 machine in the client role (also note that starting from RDC 7.0 you can’t connect to Windows 2000 systems anymore!). But you do get RDP signing, Easy Print, a new bulk compressor (RDP6.1-BC) and the ability to explicitly connect to administrative sessions (with the /admin switch instead of the /console switch). And Network Level Authentication (NLA)?

Well, yes and no. For the RDC client itself, yes. But the thing is it only works when the Security Service Provider (SSP) CredSSP is available and that’s not the case in WS03. For Windows XP it is available, but it’s disabled by default; you can enable it, but it doesn’t make sense to do the same for WS03, because it’s just not there. So at the end this means no NLA from a WS03 machine, even with RDC 6.1!

IMHO this is a pity… First of all WS03 is still very widely used and it’s difficult to understand all of at least many of the newest features aren’t supported at RDP client level! Secondly, NLA is perhaps even the most important feature missing! The reason is simple: if a company implements RDS farms with high security requirements, NLA should be enabled. NLA requires the client to provide all the credentials before the actual RDP connection to the target is made. So forget about making a connection and then entering your password into the Winlogon desktop (that’s how it’s called, as it is actually a desktop too, although not the application desktop we typically refer to). Does this sound stupid to you? Well, it isn’t! With NLA authentication happens before the actual RDP connection is made, i.e. during the Kerberos/SSL/NTLM setup, meaning server authentication is required too. This is a good thing security-wise and performance-wise, because bad attempts are blocked earlier and take less resources. I could tell you more about how and why exactly, but I guess it’s best not to go outside the scope of this article, otherwise I end with my opinions about the political situation in Lagos, Nigeria or something similar 🙂
The thing is you can’t connect from your old WS03 working environment to your new highly secured working environment, so if you’re moving from a WS03 to a WS08(R2) RDS farm, it’s not a nice thing. The only thing you can do is to connect to another system and connect to your new WS08(R2) farm from there. Or reduce your security, at least for a while… If your old working environment is XP though, there is no problem at all, because there NLA is possible (after enabling it though).

Anyway, it seems most people are not aware of the fact RDC 6.1 can be run on WS03 for the moment. That is the message I’m trying to spread! For completeness, the latest build for 6.1 is 6.0.6001.18564 and is also supported on XP (you need at least SP2), Vista and WS08; for WS03 you need at least SP1. More information can be found in KB2481109 at http://support.microsoft.com/kb/2481109. This update is available through Microsoft Update (MU). If you really want to know: before this update the last version of RDC for WS03 was 6.0.6000.16459 (a build of version 6.0), available through KB925876 for WS03 SP2. Well, AFAIK, that is.

Greetz,
Pedro

PS: don’t be confused by the version numbering. 6.0.6000.x builds belong to the main version 6.0, while 6.0.6001.x builds belong to the main version 6.1.

Источник

File corruption, missing, or deleted WINDOWSSERVER2003-KB2481109-X86-RUS.EXE files can result in EXE executable errors, most commonly seen during the startup phase of March 2011 Security Release ISO Image. Although annoying, these issues can usually be easily remedied through replacing the problem EXE file. After the problem file is replaced, running a registry scan can help clean up any invalid WINDOWSSERVER2003-KB2481109-X86-RUS.EXE, file extension, or other file path references which could have been affected from a previous malware infection.

An Windows Executable File format that carries the EXE file extension are classified as Executable Files. In the list below, you can download the most recent file versions for nearly all Windows versions, including some for %%os%%. Not all versions of WINDOWSSERVER2003-KB2481109-X86-RUS.EXE may be available for download, but you can request a file by clicking the «Request» button below. We also recommend contacting Microsoft directly if you cannot find your need version below.

Once the file is successfully placed in the right location on you hard drive, these WINDOWSSERVER2003-KB2481109-X86-RUS.EXE issues should disappear. Running a quick verification test is highly recommend. Confirm that the error is resolved by attempting to open March 2011 Security Release ISO Image and / or conducting the operation that triggers the issue.

WINDOWSSERVER2003-KB2481109-X86-RUS.EXE File Summary
Extension:	EXE
Application Type:	Security,Update
Application:	March 2011 Security Release ISO Image
Software Version:	913086
Created by:	Microsoft


Name:	WINDOWSSERVER2003-KB2481109-X86-RUS.EXE
Size:	1655168
SHA-1:	aa7330cd6421e63af518b9d3c5d33107628e0bdd
MD5:	84d213682449cae262b4e6e83500db73
CRC32:	226ed026

Product by Solvusoft

Download Now
WinThruster 2023 — Scan your PC for WINDOWSSERVER2003-KB2481109-X86-RUS.EXE registry errors

Windows
11/10/8/7/Vista/XP

Optional Offer for WinThruster by Solvusoft | EULA | Privacy Policy | Terms | Uninstall

EXE
WINDOWSSERVER2003-KB2481109-X86-RUS.EXE

Article ID: 739276

WINDOWSSERVER2003-KB2481109-X86-RUS.EXE

File Name

Bytes

Download

+ WINDOWSSERVER2003-KB2481109-X86-RUS.EXE