Hi, Clients running Win 7 SP1 have received an automatic Windows update (KB2592687) which prevents them from using Remote apps on our 2008 r2 Gateway server. The server has been working well previously for over two years. After this update, clients can be authenticated and then view the remote desktop, but then when they try to use an application, authentication fails. Corel draw 8 serial key. Win 7 without SP1 client is OK, XP and Vista clients are OK. Uninstalling KB2592687 brings the RDP Client version of 6.2.9200 back down to 6.1.7601 and allows the client to use the gateway function as normal. Is there anything I can do on the server to fix this besides removing this update on all the clients?

Download rdpbus.sys Microsoft RDP Bus Device driver version 6.2.9200.16384 64bit. About Us; rdpbus.sys. Microsoft Corporation. Microsoft RDP Bus Device driver. Threat Score. Original size. Download size. C a 7 d f 5 e c 9 5 d 8 d e 0 d d 2 4 b e 7. How can I tell if I have Windows 2012 R2 (vs the 'R1' original release')? Operating system Version number Windows 8.1 6.3* Windows Server 2012 R2 6.3* Windows 8 6.2 Windows Server 2012 6.2 Windows 7 6.1 Windows Server 2008 R2 6.1 Windows Server 2008 6.0 Windows Vista 6.0 Windows Server 2003 R2 5.2 Windows Server 2003 5.2 Windows XP 64-Bit.

The server is fully up to date with Windows updates. I note that there's another thread on this issue: which suggests ignoring client certificates will help. In my case, that option was already selected, and so made no difference. There was a message about certificate corruption in event viewer, after the server updates had been applied.

I thought this was the issue, so rebuilt the license database, but that made no difference to the problem. Regards, Steve Steve. Hi, Here you go: 1. I confirm that is the case.

Here are the log lines written during the failed logon attempt. Keygen fm 2014 staffing. Note that 192.168.10.46 is the IP of the RD server, 192.168.10.35 is the IP of our ISA 2006 server. Hi, I checked the ISA logs by monitoring a connection attempt in realtime.

I can see that authentication is working and I am allowed to connect to the gateway server. When I try to open an app from the desktop, nothing more is shown in ISA logging.

I can't open the app and I see 'Logon attempt failed', but nothing in ISA log at all. One of the following may be happening: • The ISA has authenticated me and there's nothing more for it to do. • The process of opening the app fails at the client and doesn't get as far as the ISA. • The process of opening the app fails at the server and has already got past ISA. So with my limited understanding of ISA and this problem I think that it's number 2.

Thanks for your help, but I didn't enable Anonymous authentication at the ISA. There are so many steps along the way (broadband modem, NAT, ISA web listener, ISA firewall rule, authentication at the server. I think you mean remove the authentication at the web listener? Or is it at the firewall rule? Regards, Steve Steve.

Hello Steve, I am wondering if you are using the RemoteApp which published by UAG? If so, the issue would be an expected issued.

Because Windows RDC 8.0 is currently not on the supported list of RDP client through UAG. The RDP access issue is caused since the RDC 8.0 client starts its connection in a different manner, by using a different HTTP request, than in the previous versions, and this is unexpected for UAG in the current version. If this is our issue, I recommend the client to be using RDC 7.0. Hence to resolve the issue we need to remove this update from all the clients that are planning to leverage RDS service through UAG. See more evidence from the following KB article: The following are the limitations for RDS publishing in this release: Remote endpoint access is supported for clients running the Windows 7, Windows Vista with Service Pack 2, Windows Vista with Service Pack 1, and Windows XP with Service Pack 3 operating systems. Endpoints must be running the Remote Desktop Connection (RDC) 7.0 client.