Posts Tagged ‘RDP’

Recently was trying to save credentials logging into a management server and it would ask for a password each time
 
Computer configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Connection Client
 
Do not allow passwords to be saved was set to “Enabled”
 
Computer configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Security
 
Always prompt for password upon connection was set to “Enabled”
 
Removing both of these fixed the issue
VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

https://support.microsoft.com/en-au/help/4093492/credssp-updates-for-cve-2018-0886-march-13-2018

 

I had one user with this issue and on Windows Home Edition – so the machine don’t have GPO or Gpedit.

It didn’t had the Registry key, way to fix was creating the Registry key manually with value=2

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\CredSSP\Parameters]

"AllowEncryptionOracle"=dword:00000002

Group Policy path: Computer Configuration -> Administrative Templates -> System -> Credentials Delegation Setting name: Encryption Oracle Remediation

from Vulnerable to Mitigated on Client computers (Win 10, Win 7)

If the CredSSP patch has not been applied to the server, you will get an error and will not be able to connect. If applying the patch to the server (released March) is not possible the setting can be changed via GPO or local GPEDIT on client machines.

 

Obviously patching the server is the better option!

 

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

MacRDPClient[1]Recently upgraded a 2008 R2 Server to Enterprise from Standard using

 Dism /online /Set-Edition:ServerEnterprise /ProductKey:xxxxx-xxxxx-xxxxx-xxxxx-xxxxx

Wouldn’t work with the customers Volume License Enterprise Key. I used the KMS key which did work and activated using the Volume license key again , however on restart the server could not be remote desktoped in.

I had to run a 

SLMGR /REARM

Restart the server and reactivate it using the proper Volume license key. After this , restarting the Remote Desktop Service enabled RDP to work again

 

You should check in the Computer settings , that the memory is not set to 4GB Usable out of the new memory allowance. If this is the case you will need to do the following

  1. Open the command prompt and change working directory to System32 directory
  2. Type in slmgr.vbs -ckms (this clears and KMS entry you may have)
  3. Type slmgr.vbs -upk (this removes any product key installed)
  4. Type slmgr.vbs -ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx (where the x’s is the new product key you want to use )
  5. Type slmgr.vbs -ato (this activates the server)
  6. Restart Server

 

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)
Remote_desktop_connectionUpon trying to open up a remote application on a 2008 terminal server I am greeted with the following error:unable to open connection file.

This issue seems to be down to the file signing , if you have access to the terminal server , republish the file without signing and redeploy this. You can take out the signing manually by

  • Opening up the .rdp file in question with notepad
  • Find the line starting “signscope:s:” and delete any of the text on that line and after it. ( This removes the signing code )
  • Save the text file and try again
VN:F [1.9.22_1171]
Rating: 7.5/10 (2 votes cast)
VN:F [1.9.22_1171]
Rating: +1 (from 1 vote)