Home > Remote Desktop > Remote Desktop Broken After Latest Windows Update
Remote Desktop Broken After Latest Windows Update
Generated Wed, 11 Jan 2017 17:43:23 GMT by s_wx1077 (squid/3.5.23) TechNet Products IT Resources Downloads Training Support Products Windows Windows Server System Center Browser Office Office 365 Exchange Server Hope this helps you... Systems that do not have RDP enabled are not at risk,” Microsoft says. This was my original setting prior to the 3/11 patches. http://openfeedback.org/remote-desktop/windows-remote-desktop.php
Have a look at the server and client logs as well.-- Al Thursday, March 12, 2015 10:08 PM Reply | Quote 0 Sign in to vote I'm curious here... Certainly, having the machine rebooted several times is not what you’d expect when installing an update released by Microsoft, but you should actually accept it because, after all, it could be This worked quite smoothly until this morning, after the updates of last evening. (3/11/2015) When users tried to log into the Remote Desktop this morning their credentials were rejected, as if Microsoft Registry Fix User Tej Shah shared a technet forum entry that shows a registry workaround. http://news.softpedia.com/news/botched-microsoft-update-kb3126446-now-causing-issues-on-windows-7-500511.shtml
Windows Update Breaks Remote Desktop
Double click that file and let it do it's thing. If so, could you please have them log in with credentials: domain.local\username (I suspect they may be currently using domain\username) To answer your question, yes, rebooting the server does put Marked as answer by Justin GuMicrosoft contingent staff, Moderator Thursday, April 02, 2015 3:00 AM Monday, March 16, 2015 5:44 PM Reply | Quote Moderator 0 Sign in to vote Absolutely. Hope this helps you...
sometimes an update to NIC drivers (through wonderful windows updates) can cause a firewall to mistake a VM's IP address as a spoofed address, which I've seen affect DRP even while I dance. Comments Trey says July 2, 2012 at 8:32 am This guy suggested a solution other than those listed here. Windows Update Remote Desktop However, several users are now unable to connect via the same method.
You are putting yourself/customers at risk. Dustin Thursday, March 12, 2015 11:04 PM Reply | Quote 0 Sign in to vote Hi Dustin, I have the same issue as you with a Windows Server 2003 R2 environment. Then click on View Installed Updates and search for your Windows Updates. The particular machine I had an issue with was rebuilt and it didn't come back the second time around but if the above doesn't cut the muster for you give it
The SBS is set up as a RDS. Windows 10 1607 Rdp Not Working Tried all sorts of tricks including adjusting NTLM authentication levels as suggested by other forums - no go at all. Creating your account only takes a few minutes. passwords in just a few movesHideMe VPN: A lightweight and easy to use software solution that can help you browse the web securely and access websites that are restricted in your
- TECHNOLOGY IN THIS DISCUSSION LiteManager 21 Followers Follow Techinline 1018 Followers Follow Remote Desktop Read these next... © Copyright 2006-2017 Spiceworks Inc.
- The users unable to connect are receiving the following error:I've read about this error possibly having to do with the update from RDP 7.1 to 8.0/8.1 but I'm not sure.
- If the server is rebooted, does it put the RDS users back into a "credentials failed" situation?
- Softpedia and the Softpedia logo are registered trademarks of SoftNews NET SRL.
- After removing KB3046049 and KB3002657 and rebooting the affected Servers TWICE the issue has been resolved.
- It couldn't have been the Windows Updates because both machines received the same updates and one worked and the other didn't.
Windows Update Breaks Rdp 2016
Server 2003 Domain may be the contributing factor as the RD server is 2008 R2 but the DC is 2003. https://www.tenforums.com/network-sharing/58427-rdp-files-wont-open-remote-desktop-after-win10-anniversary-update.html I've tried performing a system restore to before the updates and even uninstalling/hiding the updates but no luck. Windows Update Breaks Remote Desktop One of the updates shipped by the software giant as part of February 2016 Patch Tuesday seems to be pushing Windows 7 computers into a longer reboot loop. Kb2984972 Breaks Rdp If the server is rebooted, does it put the RDS users back into a "credentials failed" situation?
After removing KB3046049 and KB3002657 and rebooting the affected Servers TWICE the issue has been resolved. Windows 10 Anniversary Update Rdp Not Working I'm going with the secure it at the firewall workaround but if you have the time (and his solution works) this could be better. I can also normally logon to the server using the Remote Desktop functionality.
It was KB3002657 V2 that did the trick.
We have all learnt a VERY valuable lesson: NEVER install updates unless absolutely necessary and pick the ones you need and fully charge the customer for the time involved. You are correct that we've been using domain\username. It is a VM, but as far as I can see the nic driver haven’t been updated (driver date 21.06.2006), and the roll back driver button is greyed out. Windows 10 Rdp Not Working Wednesday, March 18, 2015 7:13 AM Reply | Quote 0 Sign in to vote all good stuff just applied v2KB3002657 over the top of the original as suggested on all my
The trick of logging on to the 2012 RDS Server as each user from the SBS 2003 Server via RDP corrects the problem (but reverts back the following morning again). Thank you very much for your help, Dustin Thursday, March 12, 2015 5:49 PM Reply | Quote Answers 1 Sign in to vote Exact same problem here with MANY of our Users connect to their internal work computers externally using the gateway we established on a random port we've allowed through our Sonicwall firewall. navigate here After all of that RDP connections are working to the previously unavailable 2008 R2 RDP server.
To remove the patch go to Control PanelProgramsPrograms and Features. The relevant status code was 0xd0000001. SysLog & IDS Server After a regulatory & security audit, it was made apparent the company needs a server to collect system logs for central management. Text Quote Post |Replace Attachment Add link Text to display: Where should this link go?
The RDS has the Remote Desktop Services role installed, up, and running. Creating your account only takes a few minutes. Edited by mikehein Monday, March 16, 2015 10:48 AM Proposed as answer by mikehein Monday, March 16, 2015 10:51 AM Marked as answer by Justin GuMicrosoft contingent staff, Moderator Thursday, April Do local users credentials work for you?
Edited by mikehein Monday, March 16, 2015 10:48 AM Proposed as answer by mikehein Monday, March 16, 2015 10:51 AM Marked as answer by Justin GuMicrosoft contingent staff, Moderator Thursday, April anyone got an idea? Reply Subscribe RELATED TOPICS: Remote Desktop Broken Due to Windows Updates Cannot Connect to server using Remote Desktop restart remote desktop service on server 2008R2 remotely? Or is the jury still out on whether it works? https://technet.microsoft.com/library/security/MS15-030 Remove KB30399762.
Monday, March 16, 2015 5:38 PM Reply | Quote 0 Sign in to vote Would someone be willing to do two things? 1. Tried all sorts of tricks including adjusting NTLM authentication levels as suggested by other forums - no go at all.