Jump to content

Recommended Posts

Posted (edited)

Yeah, two machines yesterday, one today, we've just restored the PC's to a day earlier to fix it well for the minute, can't wait for people screaming and shout today about it, our SIMS is hosted and uses RDP, so that's SIMS out the window, brilliant.

 

This affecting all Windows 7 machines or just the odd few?

Edited by keyboards
Posted
Any that have patched with this months update. Al servers need to be patched to avoid the error. You can get the standalone update online
Posted
Not sure I want to registry deploy Group Policy fixes rather they just release an update ASAP that sorts it

 

I believe there is. It doesn’t help with those that connect using their own computers otherswise

Posted
Yeah changing the reg key locally did it for me. Worked a charm!

 

It does work but doesn’t help with all your remote users :)

Posted (edited)
It does work but doesn’t help with all your remote users :)

 

Package up a .reg file, host it on your site and direct users to it.

 

- - - Updated - - -

 

 

Just got into work after not been able to connect - applied to my work machine and it can now connect.

 

Reg key is here for clients:

 

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\CredSSP\Parameters] "AllowEncryptionOracle"=dword:00000002

Edited by timbo343
Posted
this is what i did to get my clients up and running but the link above had the standalone patches to install as remote users still had the issue
Posted
Just to up date this too.. It took out our papercut server too on Server2016. Adding in the reg entry means i am able to browse papercut via the browser.
Posted
This is why you have a pilot/test/guinea pig groups of PCs.

 

In a perfect world yes but I'm sure we've already all got tons to do, if we had more staff then yeah definitely would have a test environment etc

  • Thanks 1
Posted
I it hasn’t hit my internal clients just remote users that I have no control over. I’m just patching servers now and it’s sorted it
Posted
I must admit that the article leaves me a tad confused. Is that saying that KB4103725 (Windows 8/10) KB4103727 (Server 2016/2012) KB4103718 (Windows 7) are actually okay now then?

I felt the same. What do I need to do to get RDP working again for remote users who connect through our RD Gateway?

  • Thanks 1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...