I run today into an odd issue, a user was not able to to RDP into their new Terminal Server.



When you check on the RDP connection tab it says NLA is not supported.


The cause seems to be an issue with a DLL file in the Registry.

And here is fix:

Configure Network Level Authentication
1. Click Start, click Run, type regedit, and then press ENTER.
2. In the navigation pane, locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
3. In the details pane, right-click Security Packages, and then click Modify.
4. In the Value data box, type tspkg. Leave any data that is specific to other SSPs, and then click OK.
5. In the navigation pane, locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders
6. In the details pane, right-click SecurityProviders, and then click Modify.
7. In the Value data box, type credssp.dll. Leave any data that is specific to other SSPs, and then click OK.
8. Exit Registry Editor.
9. Restart the computer.


– http://www.powercram.com/2009/07/enabling-network-level-authentication.html#
– https://community.dynamics.com/gp/b/gpdynland/archive/2013/07/26/windows-7-remote-desktop-connection-error-remote-computer-requires-network-level-authentication




I hope you all have at least heard of Spiceworks, a free, simple yet powerful multi-user web application that allows you to inventory, monitor, report on and troubleshoot your network, run a help desk, and access a community of IT pros – all from one easy-to-use interface.

However to me, Spiceworks is more than that. Along with the Spiceworks ‘products’ you also get access to the community, a home, a safe haven, a trading post for knowledge, skills and experience, a sometimes a lot of silliness… :o)

At over 6 million IT pros strong, The Spiceworks Community’s a place where IT pros trade tech tips, show off their awesome projects, share real-world advice from the IT trenches… and have a laugh.

Being around in the Spiceworks community for years, I only recently decided to actively participate in discussions, helping answering questions and testing applications.

I helped to Beta test the Spiceworks Network Monitoring Software and the new (and at this time still work in progress?!) iOS Spiceworks App for iPhone, iPad, and iPad Touch, found bugs and helped to improve things.

If you work in IT, check out my profile and or join us, I promise, you wont regret it! RAWWWR!




There is no default GPO to set the Desktop background. We have a terminal server with a white wallpaper, however the default background is black, thus you can not read the icon’s font. To fix that, you can create an ADM template.

Save that file to your server and name it ‘backgroundcolor.adm’. Open up Group Policy Management and create a new  GPO and link it to the right OU.
Edit the GPO, go to User Configuration -> Administrative Templates, right click Administrative Templates and then Add Template

Browse to the Backgroundcolor.adm and add it in. Under Administrative Templates you will now see a custom category called “Set Background Color”

To change the colour of the desktop, select “Desktop Background Color policy”, then enable it.

Simply then enter the RGB value of the color you want.