Configuring license servers for Windows 2016 RDP

If you setup your RDP deployment from a central broker server, this shouldn't be neccesary. If you have installed The RDS role manually though, it may not pick up your licensing servers. 

To set this, open the local group policy editor and browse to the following:

Computer Configuration -> Admin Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Licensing

In the Use the specified Remote Desktop license servers key, enter the name of your licensing server or servers separated by commas. Also make sure this is set to enabled.

Also check the Set the Remote Desktop licensing mode key is set correctly. Per User if you have User CAL's, Per Device is you have Device CAL's

Updating Redhat 6 and later using Redhat Subscription Manager

To begin, buy a subscription through redhat.com.
You will need to allow access out to internet from your server, in particular to https://cdn.redhat.com, https://subscription.rhn.redhat.com and https://subscription.rhsm.redhat.com

1. on the server, run subscription-manager register
enter your redhat username and password when prompted
you will now see this server in your subscribed systems with a red square as its not yet assigned to a subscription
2.run subscription-manager attach
the red square should now have turned green
3.you should now be able to update your system by running yum update

if you need to chop and change systems to apply updates on(if you don't haven't bought multiple channels), run the command subscription-manager remove --all then follow steps 1-3 on your next server

Active Directory Account Lockout Troubleshooting

If someone’s Active Directory account is getting locked out, you can check the event logs on the domain controllers to see what is doing it. This is useful if people log into multiple devices as a common cause of this is that they have left themselves logged in somewhere and it is trying to authenticate with an old password

 

·         Open remote desktop and go to your domain controller NOTE – if you don’t find anything here, follow the same steps on other domain controllers

·         Open Event Viewer and navigate to Windows Logs > Security

·         Sort by Date and Time and select a log entry close to the time after the suspected account lockout

·         On the right hand side click ‘Find…’ and search for the users login name 

·         You are looking for a message with Event ID 4740 and the heading ’A user account was locked out’ like the one below: