Welcome to Sign in | Join | Help
in
Home Blog Forums

Browse by Tags

All Tags » Terminal Services   (RSS)
  • Re: Mandatory Profiles / 2003 /

    Hey Andy, What you need to do is install Outlook using a transform file and in that file specify %username% for the Outlook profile settings.  There is a tool in the Office Resource kit that will walk you through creating a MST file. Rod
    Posted to Windows Server (Forum) by rodney.buike on April 17, 2007
  • Mandatory Profiles / 2003 /

    Hi, I have a need to setup a TS for remote access and have applied GPO to the accounts that logon so they are restricted them where possible.  I have mandatory profiles for these users and they can logon without problems.   My issue is I want to setup outlook on a per user basis for all of these users.  I have the applications ...
    Posted to Windows Server (Forum) by AndyJG247 on April 17, 2007
  • Configure RDP over SSL with SelfSSL

    Windows 2003 Service Pack 1 included a new feature, RDP over SSL. This feature will allow you to use TLS authentication and encryption with your RDP connections using SelfSSL to create the SSL certificate. It still uses RDP and TCP port 3389 so your firewall rules should not need to be modified. Before we get started there are a few ...
    Posted to The Lazy Admin (Weblog) by rodney.buike on January 26, 2007
  • Automate Client RDP Connections

    Servers get updated every so often and upgrading a terminal server leaves you with one nagging issue, how to update all the client PC RDP connections? TLA reader Phillip Ward wrote this little tip on how to automate this! Recently a senior network administrator asked me to configure remote desktop on nearly all of the machines to point to a ...
    Posted to The Lazy Admin (Weblog) by rodney.buike on September 12, 2006
  • Why 64-Bit is Good for Terminal Services

    A while back I wrote an article for MSExchange.org on why 64-bit is good for Exchange 2007. 64-bit is good for more than just Exchange 2007 and SQL 2005, and this series will cover other scenarios that can benefit from 64-bit. Let's look at terminal services first. Probably the biggest limiting factor to terminal servers today is the virtual ...
    Posted to The Lazy Admin (Weblog) by rodney.buike on July 12, 2006
  • Enable Remote Desktop Remotely

    Well I goofed the otherday :( I installed a new 2003 server into my network and went home, figuring I could login from home and finish up the last bit of configuration after a good meal. What I didn't do was enable remote desktop, making things a bit more difficult, but not impossible. After logging on to a different machine on the network, I ...
    Posted to The Lazy Admin (Weblog) by rodney.buike on January 19, 2006
  • Terminal Services Licensing Primer

    Probably one of the most confusing things ever created by mankind is Microsoft Licensing. In regards to Windows Server 2003, terminal services licensing has undergone some changes. Most notably is it no longer contains any built-in license like Windows 2000 Server did for 2000/XP clients. Terminal Services licensing is comprised of three ...
    Posted to The Lazy Admin (Weblog) by rodney.buike on December 22, 2005
  • Quick Tip: Editing a Terminal Server Users Registry

    When working in a fat client environment and you need to make a change to a users local machine registry key you can connect to the remote registry and make your changes. In a thin client environment, all users share the HKey_LocalMachine key and each users HKey_Users key is listed individually by SID. To determine which user the SID belongs to ...
    Posted to The Lazy Admin (Weblog) by rodney.buike on August 25, 2005
  • Quick Tip: Change Terminal Server Port

    Windows 2000 Server, XP Pro and Windows Server 2003 all listen on TCP port 3389 for connections. There are times when you need to change this. Let's say you have only one static IP but you have three servers/workstations you need to connect to. What do you do? Simple, change the listening port on the server or workstation to listen on a different ...
    Posted to The Lazy Admin (Weblog) by rodney.buike on July 13, 2005
  • Quick Tip: 2003 Terminal Server Console Session

    One of the cool new features of Windows Server 2003 is the ability to get a console session on the terminal server. Unlike Windows XP Pro which gives you the console when you connect via RDP, Windows Server 2003 starts a new session when you connect via RDP. There is a way to get the console session, here is how! From a command prompt type ...
    Posted to The Lazy Admin (Weblog) by rodney.buike on July 12, 2005
  • Terminal Server Performance Tweaks

    I find myself responding to users about slow terminal server performance on a weekly, if not daily basis. Most of the time it can be attributed to user expectations and impatience, but there are some things that can be done to enhance the user experience and cut down on end user complaints. OK well that will never happen but you should apply these ...
    Posted to The Lazy Admin (Weblog) by rodney.buike on July 11, 2005
  • Terminal Services Command Line Administration

    Managing your Windows 2003 Terminal Server can be done faster and easier with a few simple command line tools. There are a lot of them so hang on! Change User - When installing applications on a terminal server you must be in Install Mode. To toggle the system between Install and Execute Modes, you can use the Change User commands. To switch to ...
    Posted to The Lazy Admin (Weblog) by rodney.buike on June 24, 2005
  • Terminal Server Fallback Printer Driver

    Windows Server 2003 SP1 introduces a new feature called Terminal Server Fallback Printer Drivers. Terminal Server Fallback Printer Driver allows you to default to a PCL or PS (or both) capable printer driver to use if the driver required by the client is not available. On a 2003 SP1 Server, open the group policy editor and go to Computer ...
    Posted to The Lazy Admin (Weblog) by rodney.buike on April 5, 2005
  • Using RDP over SSL

    Windows Server 2003 SP1 introduces a new feature to the mix, RDP over SSL. This feature will allow you to use TLS authentication and encryption with your RDP connections. It still uses RDP and TCP port 3389 so your firewall rules should not need to be modified. Before we get started there are a few pre-requisites on both the server side and client ...
    Posted to The Lazy Admin (Weblog) by rodney.buike on March 9, 2005


All postings are provided "AS IS" with no warranties, and confer no rights.
Microsoft product screen shot(s) reprinted with permission from Microsoft Corporation.