Thought I would post a couple of PowerShell scripts that I’ve recently written. Both of these scripts were written specifically for terminal servers but they can be modified as needed. The first one finds what terminal servers a user is logged into. It retrieves a list of terminal server names from the specified OU. I started out by using the Get-TSServers cmdlet for the list of servers, but that cmdlet takes a while and you have more control by just using the Get-ADComputer cmdlet since your terminal servers are more than likely in their own OU anyway.
This blog article will guide you through the steps of setting up Remote Desktop Licensing or Terminal Services Licensing as it’s known in previous versions of Windows Server. You’ve decided to move from Windows 2003 R2 to 2008 R2 domain controllers and you want to run your terminal services licensing on the new domain controllers. You can run the licensing for all your terminal servers operating with Windows 2000 Server and newer Windows Server versions on Windows Server 2008 R2.
Recently while assisting one of my customers who was transitioning from Windows 2003 to Windows 2008 terminal servers we experienced a problem with start menu redirection where there was nothing at all on a user’s start menu. The start menu was (empty) or blank. This problem ended up being due to applying the same group policy to the 2008 terminal servers that was previously applied to the 2003 terminal servers. To resolve this issue the “Remove user’s folders from the Start Menu” setting that was previously enabled in the group policy object (GPO) and worked without issue on Windows Server 2003 needs to be disabled on the new Windows Server 2008 terminal servers.
You’re using group policy to enforce the “Run only approved Windows applications” for a specific group of computers such as terminal servers. After updating Adobe Reader from version 9.0 to 9.2, users receive the message: “This operation has been cancelled due to restrictions in effect on this computer. Please contact your system administrator.” My first thought was “The name of the executable must have changed”. A quick check disproved that. It is the same name with both versions: “AcroRd32.
Wyse Winterms are a cost effective solution for non-power users in your enterprise environment. They are great for users who use office, email, the Internet, etc, and they will handle most of the main stream applications that I have seen in the educational, financial, healthcare, and manufacturing industries. Models like the retired 1200LE and its replacement, the S10 are good choices. They are low cost, easy to maintain, are more eco-friendly than computers since they use a lot less power (average power usage for the S10 is 6.