Hi All,

I did something silly and need some assistance to resolve, hopefully it is straight forward.

I decided to convert one of our Windows Server 2012 R2 Servers (Server A) from Full GUI mode to Server Core using the following command:

Uninstall-WindowsFeature Server-Gui-Shell Restart

The server a virtual machine within our vSphere 5.1 environment, so I took a snapshot before doing this.

The server is an application server, and is a member of our domain.

That seemed to work fine, so I converted the server back to Full Windows GUI using the following command:

dism /online /enable-feature /featurename:ServerCore-FullServer /featurename:Server-Gui-Shell /featurename:Server-Gui-Mgmt

The Server is operational again.

However when we log into the server, it now displays the following warning message which I'm not sure how to resolve:

I reverted the server back to it's snapshot thinking that would resolve it, however this message still comes up whenever anyone logs in. So now I need to resolve this message asap!

Now, we have another Windows Server 2012 R2 application Server (Server B) in the domain, and this server looks to me like an RD Licensing server, because I can see the following on this server:

Therefore, my initial plan is to use Server Manager Manage > Add Roles and Features > Remote Desktop Services Installation to install the Remote Desktop Services on Server A, choose 'per device' licensing mode and point it to use Server B as its RD Licensing server.  Does this sound correct?

I would be grateful for any help.

Many thanks

Koncise

Hi Koncise,

You are right. Server A should be Remote Desktop Session Host server and Server B should be Remote Desktop License server. Please follow the steps mentioned in this link to configure license server (skip the part of activating the license server and installing CALs since you have already done those).

Hope this helps!

Thank you, this resolved the issue and the message no longer appears.

Thanks

Koncise

Hi Koncise,

Glad to hear that the issue is solved!

Please feel free to let us know if there are any further requirements in the future.

Here is a related blog below for you:

Licensing How To: When do I need a Client Access License (CAL)?

http://blogs.technet.com/b/volume-licensing/archive/2014/03/10/licensing-how-to-when-do-i-need-a-client-access-license-cal.aspx

Best Regards,