The case of the missing mouse on windows 2012 via rdp

Issue: No mouse pointer after you RDP to some windows 2012 servers, seems to be more common from linux systems. Also in my research it seems this fix works for slow mouse pointers too in RDP

Workaround:

  1. launch control panel
  2. click on mouse options
  3. click on the pointers tab
  4. uncheck “enable pointer shadow”

If you need keyboard shortcuts:

  1. windows key +R for run command
  2. then “control main.cpl”
  3. uncheck “enable pointer shadow” *use tab if needed to select option.

References:

https://support.microsoft.com/en-us/kb/192806

https://support.microsoft.com/en-us/kb/126449

bonus https://social.technet.microsoft.com/Forums/windows/en-US/3dcd8f57-3efc-46e9-b2e1-34e61f3ddb3d/remote-desktop-connection-mouse-slow-with-windows-2012?forum=winserver8gen

 

Advertisements

RDP error Local Security Authority cannot be contacted

The error:

Remote Desktop Connection: An authentication error has occurred.
The Local Security Authority cannot be contacted
Remote Computer: hostname or ip

The issue:

Seems to happen more on 2012 server but if you have Network Level Authentication enabled it will not prompt you for a GUI change password option if you have change password at next logon selected. This error could happen for other reasons as well

One of the possible fixes:

  1. uncheck change password at next logon if its selected
  2. use a different tool to change your password at first logon

Additional info can be found at https://blog.mnewton.com/articles/Solution-RDP-The-Local-Security-Authority-cannot-be-contacted/

Cluster Administrator access is denied

Warning: following the below steps could harm your system if you don’t know what you’re doing, please have a up-to-date backup.

Problem: Domain account and local admin both in local administrators group, get an error when trying to access cluster with cluster administrator. An error occurred attempting to open cluster node ‘name’. access is denied. Error ID: 5 (00000005)

The possible Fix: check registry setting HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa and key LMCompatibilityLevel if that is set to 1 you might have this problem. Other things could effect cluster admin and give this error, this is one of them.

  1. backup registry
  2. run regedit
  3. navagate to HKLM\System\CurrentControlSet\Control\Lsa
  4. LMCompatibilityLevel
  5. if set to 1 change to 2 (other options could work in your environment, also no reboot should be needed)
  6. Cluster administrator should now work