http://www.sqlmag.com/authors/author/author/5777468/rsscomment/5777468en-USFri, 25 May 2012 08:40:08 GMTFri, 25 May 2012 08:40:08 GMThttp://www.sqlmag.com/article/hardware/putting-terminal-server-to-work#commentsAnchorMon, 09 Aug 1999 10:40:50 GMT
I read Richard Harrison’s “Putting Terminal Server to Work” (April). The article is a great way to motivate systems ad- ministrators who haven’t yet explored the possibilities of Windows NT Server 4.0, Terminal Server Edition to do so. I’ve been working with Terminal Server since the early beta version, and I think the author hit the nail on the head by looking at ways companies can use this product to expand NT’s functionality. I have a couple of comments about the “Food for Thought” sidebar. In the section about using Terminal Server as a remote email server, the author mentions that you need to have your mail-client software and mail store on the Terminal Server system. If you’re already using a mail server such as Microsoft Exchange Server, this setup isn’t necessary. Although the client software must be on the Terminal Server system, you can pull data from any server on the local network that’s running Exchange Server. Every class about Terminal Server that I’ve attended has strongly recommended against installing Exchange Server directly on a Terminal Server system. My understanding is that Microsoft designed the Terminal Server kernel to give priority to the processes that maintain the terminal sessions, so a system-intensive application such as Exchange Server won’t run as efficiently on a Terminal Server system as it will elsewhere. Similarly, if you’re running a database server such as Microsoft SQL Server on the local network, you don’t need to move it to the Terminal Server system so that users can have access.
--Joshua Leewarner

You’re absolutely correct about not installing Exchange Server and SQL Server on the same system as Terminal Server. In both cases, you need to install the client components (not the server-based services) on the Terminal Server system. When I refer to the mail client in the article, I’m referring to the software that users need to access the mail server (e.g., Microsoft Outlook). Although the mail store can stay on an Exchange Server system, not all mail systems (especially POP3-based mail systems) allow this setup. Regarding database clients, if you’re running SQL Server 7.0, some problems exist with installing the Microsoft Data Access Components (MDAC) drivers. For more information, read the Microsoft article “How to Install ODBC or MDAC on Terminal Server” (http://support.microsoft .com/support/kb/articles/q216/1/49.asp). I recommend that you thoroughly test your plans for Terminal Server.
--Richard Harrison]]>Joshua Leewarner Mon, 09 Aug 1999 10:40:50 GMThttp://www.sqlmag.com/article/hardware/putting-terminal-server-to-work#commentsAnchor