Server 2012 RDS ‘there are no Remote Desktop License Servers available to provide a license.’

Article from: http://ravingroo.com/949/server-2012-rds-no-remote-desktop-license-servers-available/

Assuming your licensing configuration is valid and you have licenses available, if you receive the above error the problem is likely an expired “GracePeriod” registry key. In our case, this “GracePeriod” key found its way into the registry at some point when this template was built. And since it was built many months ago, this grace period has since expired. You’d think RDS would be smart enough to see the license server in the domain and act accordingly, in this case, talk to the license server, confirm there are available licenses and then either ignore the grace period key or remove it. But nope, it just gives you the above error instead.

Lucky for you the fix is easy. You simply delete this key manually.

Open up the registry editor and browse to:

\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM

You should see a key called “GracePeriod”. Right-click this key and then click “Permissions.” Assign yourself (or Administrators, assuming you are part of that group) “Full Control” and then DELETE the key. You won’t be able to delete it unless you give yourself at least read/write permission (Full Control is just expedient). Now reboot the server and everything will be right as rain.

How to Set Network Location to be Public or Private in Windows 8 and 8.1

Article from:
http://www.eightforums.com/tutorials/9837-network-location-set-private-public-windows-8-a.html

How to Set Network Location to be Public or Private in Windows 8 and 8.1

   Information

The first time you connect to a network, you'll be asked if you want to turn on sharing between PCs and connect to network devices such as printers. Your answer automatically sets the appropriate Windows Firewall and security settings for the type of network (private or public) that you connected to. You can turn sharing on or off anytime.

This tutorial will show you how to set your network to be connected to a public or private type of location for if you would like to turn sharing and connect to devices on or off in Windows 8, Windows RT, Windows 8.1, and Windows RT 8.1.

You must be signed in as an administrator to be able to do the steps in this tutorial.

   Note

Private network - Choose Yes, turn on sharing and connect to devices below for home or small office (work) networks, or when you know and trust the people and devices on the network. This setting allows your PC to connect to devices on the network, such as printers. Computers on a private network can belong to a homegroup.

Public network - Choose No, don't turn on sharing or connect to devices below for networks in public places (such as coffee shops or airports), or when you don't know or trust the people and devices on the network. This location is designed to keep your computer from being visible to other computers around you and to help protect your computer from any malicious software from the Internet. HomeGroupis not available on public networks, and network discovery is turned off.

Unidentified network - See: Unidentified Networks - Set as Private or Public - Windows 7 Forums

• Turning on sharing prepares your PC for sharing files and devices on a network.
• The network sharing setting is only available for Wi-Fi, Ethernet, VPN (non-domain), and dial-up (non-domain) connections. It's unavailable for domain networks. On VPN or dial-up connections, you must connect to the network first, then press and hold or right-click the network name to change the network sharing setting.
• Turning on sharing changes your firewall settings to allow some communication, which can be a security risk. If you know you won't need to share files or printers, the safest choice is No, don't share or connect to devices.
• Choosing No, don't turn on sharing or connect to devices blocks the following apps and services from working: PlayTo, file sharing, network discovery, and automatic setup of network devices.

EXAMPLE: Private or Public Network in "Network and Sharing Center"
NOTE: The Network and Sharing Center can let you see if your network is public or private. To open the "Network and Sharing Center", you could open the Control Panel (icons view) and click/tap on theNetwork and Sharing Center icon.

 OPTION ONE 

Set Network to be Private or Public in Windows 8 Networks

1. Do step 2 or 3 below for how you would like to open the Networks flyout.

2. On the desktop, click/tap on the Network system icon in the taskbar notification area, and go tostep 4 below. (see screenshot below)

3. Open the Charms bar, and click/tap on Settings.
NOTE: You could also press the Windows + I keys to open the Settings flyout.

A) In the Settings flyout, click/tap on the Network icon, and go to step 4 below. (see screenshots below)
NOTE: The Network icon will have the name of your network under it. The example below is for either an ethernet or wireless network.

 

4. In the Networks flyout, right click or press and hold on your network connection (ex: "Network 3" or "Brink-Router"), and click/tap on Turn sharing on or off. (see screenshots below)

 

5. Do step 6 or 7 below for what you would like to do. (see screenshots below)

6. To Set Network Location to be Public in Windows 8

A) Click/tap on No, don't turn on sharing or connect to devices, and go to step 8 below. (see screenshots below step 5)

7. To Set Network Location to be Private in Windows 8

A) Click/tap on Yes, turn on sharing and connect to devices, and go to step 8 below. (see screenshots below step 5)

8. If prompted by UAC, then click/tap on Yes.

 OPTION TWO 

Set Network to be Private or Public in Windows 8.1 Networks

NOTE: PCs with an ethernet network connection will be set as a private network by default, and doesn't appear to be able to be changed using this option.

1. Open PC settings, and click/tap on Network on the left side. (see screenshot below)

2. Click/tap on Connections on the left side of "Network", and click/tap on the network (ex: Brink-Router 2) on the right side that you want to set as public or private. (see screenshot below)

3. Under Find devices and content, do step 4 or 5 below for what you would like to do. (see screenshot below)

   Note

The Find devices and content option will not be available for PC with an ethernet network connection.

You will need to have your UAC settings set to the default or lower level to have the Find devices and content option available for other types of network connections. The Find devices and content option will not be available if you have your UAC settings set to the top "Always Notify" level. Close and reopen PC settings afterwards if you needed to change your UAC settings.

4. To Set Network Location to be Public in Windows 8.1

A) Move the slider to the left to turn it off, and go to step 6 below. (see screenshot below step 3)

5. To Set Network Location to be Private in Windows 8.1

A) Move the slider to the right to turn it on, and go to step 6 below. (see screenshot below step 3)

6. When finished, you can close PC settings if you like.

 OPTION THREE 

Set Network to be Private or Public in Windows 8 and 8.1 in Registry

1. Press the  + R keys to open the Run dialog, type regedit, and press Enter.

2. If prompted by UAC, then click/tap on Yes.

3. In Registry Editor, navigate to the location below. (see screenshot below)

Code:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\Profiles

4. Double click/tap on the Profiles key in the left pane to expand it. Click/tap on each long GUID number subkey, and look at it's PofileName string value in the right pane to see if it has the current network name (ex: Network) until found. (see screenshots below)

5. When you find the correct PofileName for your network name, double click/tap on the CategoryDWORD value in the same right pane to modify it. (see screenshot below)

6. Type in a new Data value number for the network location you want, and click/tap on OK. (see screenshot below)

Network Location	Data Value
Public
Private	1
Domain	2

7. When finished, you can now close Registry Editor if you like.

8. Sometimes you may need to sign out and in of your user account to apply the new network location.

 OPTION FOUR 

Set Network to be Private or Public in Local Security Policy

NOTE: This option will override the other options above.

1. Open the Local Security Policy (secpol.msc).

2. In the left pane, click/tap on Network List Manager Policies. (see screenshot below)

3. In the right pane of Network List Manager Policies, double click/tap on your network name (ex: Network). (see screenshot above)

4. Click/tap on the Network Location tab, and do step 5, 6, or 7 below for what you would like to set. (see screenshot below)

5. To Set Network Location to be Public

A) Under Location type, select (dot) Public. (see screenshot below step 4)

B) Under User permissions, select (dot) User cannot change location.

C) Click/tap on OK, and go to step 8 below.

6. To Set Network Location to be Private

A) Under Location type, select (dot) Private. (see screenshot below step 4)

B) Under User permissions, select (dot) User cannot change location.

C) Click/tap on OK, and go to step 8 below.

7. To Allow Network Location to be changed by user
NOTE: This is the default setting, and will allow you to be able to use OPTION ONE, OPTION TWO, or OPTION THREE above.

A) Under Location type, select (dot) Not configured. (see screenshot below step 4)

B) Under User permissions, select (dot) Not configured.

C) Click/tap on OK, and go to step 8 below.

8. When finished, you can close Local Security Policy if you like.

How to Set Up Your Own Terminal Server Using Remote Desktop Services On Server 2008 R2

Article from
http://www.howtogeek.com/100812/setup-terminal-services-remote-desktop-server-2008/

Installing Remote Desktop Services

Open the Server Manager and right-click on roles, select Add Roles from the context menu

Click next on the Before You Being page to bring up a list of Roles that can be installed, select Remote Desktop Services and click next

On the Introduction To Remote Desktop Services page click next, this will bring you to the Role Services page, select the Remote Desktop Session Host as well as the Remote Desktop Licensing Service and then click next.

When you get to the application compatibility page it tells you that you should install the Session Host Role before you install your applications, just click next as we have not yet installed our applications. You are then asked if you want to require NLA, this will only allow Windows clients to connect to the Remote Desktop Session Host Server, in addition they must be running a Remote Desktop Client that support Network Level Authentication. I will go ahead and require NLA and then click next

Now you have to choose a licensing method, most of you guys wont have Remote Desktop Client Access Licenses, so you can leave your option at Configure Later this will give you unlimited access to the Remote Desktop Server for 4 Months (120 Days). However, if you do have licenses here is some information help you make your choice:

Licensing Modes

The licenses you purchased can be used either as Per User or Per Device. It is purely up to you, however if you already have a RDS Licensing Server you will have to choose the same option you chose when importing the licenses originally.

• RDS Per User CAL –  This means that every user that connects to the RDS Server must have a license. The user is assigned the license rather than the devices that he/she connects to the server from. This mode is a good choice if your users want to connect from a lot of different computers or devices (iPad, Home PC, Laptop, Phone etc)
• RDS Per Device CAL – If your users share a common workstation this is the mode for you, the license is given to the device rather than the users, this way many people can connect from a single device. However, if they try to connect from a different device they will not be able to since their user account doesn’t have a license.

I will leave mine at configure later and click next

Now you should specify who can connect to the Remote Desktop Server, I will just add my user account (Windows Geek), then click next

You are now given the option of making the RDS Server look and act more like Windows 7, this is to avoid users getting confused when they see the classic theme. I will enable the all the settings, it requires more bandwidth though, so take your network traffic into account before going click-happy and selecting everything. Once you have made your choice click next

Since we are running Server 2008 R2, we don’t need to specify a Discovery Scope so just click next again

Finally you can click on install.

Once installation is complete, reboot your server, when you log in the configuration will complete. That’s all there is to installing a Remote Desktop Server.

Activation

If you need to install your licenses you can do it through the RD Licensing Manager. You will need to activate the Server first though. I wont go through this, as it is self-explanatory.

Once you have installed you Licenses you will need to specify a license server for the RDS Session Host to use, to do this, open the RDS Session Host Configuration MMC

When the console opens double-click on the Remote Desktop license servers link.

Now you can specify your licensing mode and then hit the add button to specify a licensing server.

As I said before, you can skip this activation section and use Remote Desktop Services for 120 Days before you need to purchase a CAL. Once you have done this you will need to install your applications. However you cant just install them in any fashion you want, there is actually aspecial method for installing applications on a Remote Desktop Server.

How to Check Number of RDP CALs