For Windows Server 2003 and Windows XP, you can restrict what software users can run on the server. See Using Software Restriction Policies to Protect Against Unauthorized Software and Locking Down Windows Server 2003 Terminal Server Sessions.

First the terminal server checks for license servers listed in the registry (see Q279561 How to Override the License Server Discovery Process in Windows Server 2003). If one of these license servers can be contacted, discovery ends. Otherwise, for a Windows 2000 or Windows Server 2003 domain the terminal server will check with Active Directory for any licensing servers in Enterprise mode, found in the same site. If one is found, and can be contacted, discovery ends.

Yes, Telnet Magic runs on Windows Terminal Server (Windows NT Server 5.0 Terminal Server Edition and Windows 2000 Terminal Services) and on Citrix MetaFame. Telnet Magic configuration is handled in the same manner as when installing Telnet Magic on a network server used by multiple users. See the License Agreement for licensing requirements and review "Using Telnet Magic on an Intranet (Network)" in the "How to..

No differently - pdfMachine is not licensed per user. You can have as many users as you like. pdfMachine is licensed per machine it is used on. e.g. If you have 4 Terminal Server Clients running on different machines using pdfMachine and one Terminal Server where pdfMachine is installed, there are 5 machines involved, therefore 5 licenses are required.

Office 2000: Requires a "transform" file to set up. There's more information in the Microsoft Knowledge Base article How to Install Office 2000 on Windows 2000 Terminal Server (Q224313). Office 97: Requires special instructions from the Microsoft Knowledge Base, including the use of application-compatibility scripts.

Terminal Server lets you deliver Windows-based applications or the Windows desktop itself to virtually any computing device — including those that cannot run Windows. For example, a user can access a virtual Windows XP Professional desktop along with x86-based Windows applications from hardware that cannot run the software locally.

No. It is not possible to run Terminal Services in Application Server mode on Windows Small Business Server 2003. This is a change from Small Business Server 2000. Running Terminal Services in Application Server mode on a domain controller may present a security risk to your network.

EasyBus was conceived out of necessity to efficiently manage the maintenance, driver, and field trip records for a school district in upstate New York. When the broad appeal of a suite of software products designed solely for the bus transportation industry became apparent, we built the business of EasyBus, Inc. Our business philosophy is that specialized software solutions applied with friendly support and service will produce a win-win scenario for every client we support.

For Windows 2000 Server, first read our Windows 2000 Terminal Services Capacity and Scaling white paper. Next, build out a server that you approximate to be correct, and refer to Terminal Server Capacity Planning Tools for capacity planning, and then Terminal Services Scaling Scripts and Utilities to validate your results.

In the Windows 2000 and Windows Server 2003 operating systems, you can choose one of two security modes: Relaxed Security mode gives users the level of access to system components that was allowed in Windows NT 4.0. This includes the ability to modify the SYSTEM32 directory where key operating system files are stored, and read/write access to system registry settings.

This message can appear because a user trying to log on is not in the Remote Desktop Users group, or because an account has no password. Starting with Windows XP, accessing network resources such as Remote Desktop and file shares requires that you have a password associated with an account. Yes. Terminal Server is working now for you because it is in the grace period.

If you enable auditing of security events, you will see all logon and logoff events in the Security tab of the EventLog on the TS. You can filter and export these events once a month to a tab-delimited textfile for further processing. Or you could make your own, very simple daily logon report by adding a line to your TS-specific login script: echo %username% %clientname% %date% %time% >> %date%_logon.log

There are many ways to retrieve this type of information, all giving slightly different results. If you only need this information on an ad hoc basis, the easiest is probably to type one of the following commands in a command window: query session /counter or query user | find "rdp-tcp#" | find /c " Active " If you are running Windows 2003 on your TS, you can also use the following script (save it as TSSessionCount.

Yes. To access the serial console for a PC you will need to log in to ops.schooner.wail.wisc.edu and use an appropriate telnet command: telnet tserver pcname

certain times, you may notice that the CSDE terminal servers slow down considerably. This is because of high resource utilization -- for example, a couple of users are running extremely CPU-intensive jobs, and the server's responsiveness is decreased for everyone else. One easy way to combat this problem is by assigning a lower priority to your long-running jobs.

Please refer to the following documents for information on Terminal Server Accounts: http://www.math.uwaterloo.ca/mfcf/services/mfcf-ppp.html.

Then use the installed OpenOffice.org setup.exe program to set up Workstation installations for each individual user. This can be a long process. It is possible to create a response file so that the installation is done automatically through a logon profile next time your users log into the system.

Microsoft does not recommend this practice, as it compromises security on the domain controller. However, you can find information in Domain Controllers Require the "Log on Locally" Group Policy Object for Terminal Services Client Connections (Q247989) in the Microsoft Knowledge Base.

This typically occurs if there is a device between the client and the server that is receiving packets but not passing them on. One way around this problem is to change the MTU size for the network adapter that is being used as a terminal server connection to clients. Ethernet uses a maximum MTU size of 1500. You can start with 500 and then slowly move up until you notice the problem to find the correct value to set

If you are a Windows XP user, the Remote Connection Client is already built-in. Select Start>Programs>Accessories>Communications>Remote Desktop Connection and use ‘ts.mspshosting.com’ in the computer column to connect to our Terminal Server. If you are not a Windows XP use, you need to download and install the Remote Desktop Connection program. To download, click: http://www.microsoft.com/windowsxp/pro/downloads/rdclientdl.asp.

Yes, You will need to install WorkCenter on your terminal or citrix server. Each user accessing the server will need to have a licensed copy of WorkCenter.

Yes. An Electronic Network License is required to run on Windows 2003 Server, Citrix, or another Terminal Server.

Logging off closes your current terminal server session. Disconnecting only closes your Remote Desktop window, and allows you to connect to that session again later. To log off the terminal server, click the Start button and choose Log off username or Shut Down --> Log off username. This logs you off the terminal server completely. If you have jobs running or files open, they will be closed.

Ans. Yes. You have full root access for Linux servers and RDP Administrator access for windows servers.

While Faximum ought to work with any terminal server that provides a reliable (and transparent) reverse telnet service, we specifically recommend the Easy Server 2 terminal server made by Stallion Technologies. Faximum’s engineers have worked closely with Stallion’s to make the combination of Faximum’s fax software and Stallion’s terminal server work better than any other fax server/terminal server pairing. Contact Faximum Software for the latest information on this project.

Middleware is needed, but it runs on the server. Windows® XP and the Remote Desktop Application transport the smart card session to the server, so to the middleware it looks as if the smart card reader is attached to the server itself.

A terminal condition is an irreversible illness that will result in death in the near future or a state of permanent unconsciousness from which recovery is unlikely. In most states, a terminal illness is one in which the patient will die "shortly" regardless of whether medical treatment is continued. However, state definitions vary. Examples of conditions include advanced cancers, head injuries, multiple organ failures, or massive heart attacks and strokes.

Operating System: Windows NT 4.0 Terminal Server, Windows 2000 Advanced Server, or Windows 2003 Server.

A rate lock is a contractual agreement between the lender and buyer. There are four components to a rate lock: loan program, interest rate, points, and the length of the lock."