Also the below command will only work in Windows Server 2016/Windows 10 and higher. It is much preferred to use a 3rd party trusted certificate. Before we get into how to do this, let me emphasize this is not recommended by Microsoft. You can now use PowerShell to create a certificate for as long as you like. So you want to use a self-signed certificate for (RDS) Remote Desktop Services or maybe a custom website, but you want the certificate to be valid for longer than a year. I ran across this little gem this morning and figured I would share. It has been quite some time since I last posted. If you have any corrections or anything to add, please do so in the comments below. If this changes in the future I will update this blog post. In the end we fixed the problem by installing licensing on the Windows 2016 server. It appears that may no longer be the case with 2019 or this may be a bug. For instance, it is possible to install 2012 RDS CALs on a 2016 license server. Normally this should not be a problem as you can install down-level CALs. After emailing Microsoft, I was able to confirm the license code was good.Īfter going back to my customer, I found out that the license server was running Windows 2019. I assumed this was due to a bad license code, as I have seen that a couple of times in the past. At both and in the install license wizard we were receiving the error “Invalid license code” and “The serial number is not valid.” respectively. I had a customer that was having a tough time installing his RDS CALs. I had an interesting issue this morning I figured I would share.
0 kommentar(er)
