Logo
programming4us
programming4us
programming4us
programming4us
Home
programming4us
XP
programming4us
Windows Vista
programming4us
Windows 7
programming4us
Windows Azure
programming4us
Windows Server
programming4us
Windows Phone
 
Windows Server

Windows Server 2008 Server Core : Working with Terminal Server (part 1)

- Free product key for windows 10
- Free Product Key for Microsoft office 365
- Malwarebytes Premium 3.7.1 Serial Keys (LifeTime) 2019
8/4/2011 3:48:58 PM
Microsoft originally released Terminal Server with Windows NT 4.0, and it's been around in various forms ever since. Terminal Server provides Windows functionality by using a mainframe model. The client acts as a terminal for the server that has all of the applications the client needs to run. Using this model, the client can run Windows even if it doesn't provide the functionality required to do so. You can find Terminal Server resources at http://technet.microsoft.com/en-us/windowsserver/terminal-services/default.aspx.

Make sure you check out the new Query utility if you're using Vista. This new utility helps you discover details about Terminal Server and its associated users, processes, and sessions.

You may find that you need to change the Server Core IP address to allow access to other machines on the network. For example, the IP address for the Local Area Connection may default to 169.254.54.55. Discover the current address by typing NetSH Interface IP Show Config and pressing Enter. Once you determine that the connection IP address is incorrect for your network, use the NetSH utility again to set the address correctly. For example, if you want to set the Local Area Connection IP address to 192.168.0.1, then you'd type NetSH Interface IP Set Address "Local Area Connection" Static 92.168.0.1 255.255.255.0 and press Enter (where the first number is the IP address and the second number is the subnet mask). Adding a third IP entry allows you to define a default gateway when necessary. After you make the required change, you must shut down the system and restart it for the change to take effect.


This article doesn't teach you how to use Terminal Server. However, it does show you how to use a number of utilities to access, query, and manage this important resource. The following sections describe the command line utilities that you'll use when working with Terminal Server.

When you display help for many of the utilities described in this section, you'll see the Terminal Server command that the utility executes. For example, the QAppSrv utility executes the QUERY TERMSERVER command. The utilities don't provide access to all of the Terminal Server commands because you don't need to use all of them from the command line. However, you can find an easy-to-use list of these commands on the Web site at http://www.robvanderwoude.com/termserv.html.


1. Locating Terminal Servers with the QAppSrv Utility

The QAppSrv utility displays a list of all of the application terminal servers on a network. If you use this utility without any arguments, it searches the network for a terminal server and displays its name. Running this utility is the same as using the QUERY TERMSERVER command from within Terminal Server. This utility uses the following syntax:

QAppSrv [servername] [/DOMAIN:domain] [/ADDRESS] [/CONTINUE]

The following list describes each of the command line arguments.


servername

Specifies the Terminal Server to query.


/DOMAIN:
domain

Displays information for the specified domain. The default setting displays information for the current domain.


/ADDRESS

Displays the network and node addresses for the Terminal Servers on the network.


/CONTINUE

Forces the utility to display all of the servers without pausing after each screen of information.

2. Obtaining Processes with the QProcess Utility

The QProcess utility displays information about Terminal Server processes. It's the same as running the QUERY PROCESS command from within Terminal Server. The output of this utility includes the username, session name, session identifier, process identifier, and user. This utility uses the following syntax:

QProcess [* | processid | username | sessionname | /ID:nn |
programname] [/SERVER:servername] [/SYSTEM]

Notice that you may only specify one of the process identifiers. For example, if you include a session name, you can't include the program name. The following list describes each of the command line arguments.

* Displays all of the visible processes.


processed

Displays the specified process.


username

Displays all processes that belong to a particular user.


sessionname

Displays all of the processes running within a particular session name.


/ID:
nn

Displays all of the processes running within a particular session identifier.


programname

Displays all of the processes associated with a particular application.


/SERVER:
servername

Specifies the terminal server to query. The default is the current server.


/SYSTEM

Displays process information for system purposes.

3. Getting Session Information with the QWinSta Utility

Use this utility to obtain information about the various sessions running on a system. It's the same as running the QUERY SESSION command from within Terminal Services. The utility outputs the session name, username, session identifier, session state, session type, and the device used to create the session. The device information is blank for the local session. This utility uses the following syntax:

QWinSta [sessionname | username | sessionid] [/SERVER:servername]
[/MODE] [/FLOW] [/CONNECT] [/COUNTER]

Notice that you may only specify one of the session identifiers. If you provide a session name, then you can't provide a username as well. The following list describes each of the command line arguments.


sessionname

Specifies the name of the session to query.


username

Specifies the name of the user to query.


sessionid

Specifies the numeric identifier of the session to query.


/SERVER:
servername

Specifies the terminal server to query. The default is the current server.


/MODE

Displays the current line settings. In this case, the output changes to show the session name, session state, device used to access the system, session type, device baud rate, device parity, device data bits, and device stop bits.


/FLOW

Displays the current flow control settings. In this case, the output changes to show the session name, session state, device used to access the system, session type, and the flow control settings.


/CONNECT

Displays the current connect settings. In this case, the output changes to show the session name, session state, device used to access the system, session type, and the connection settings.


/COUNTER

Displays the current Terminal Services counters information. In addition to the standard information, the output includes the total sessions created, total sessions disconnected, and total sessions reconnected.

Other -----------------
- Active Directory Domain Services 2008 : Manage Active Directory Domain Services Data - Delete a Group Object
- Active Directory Domain Services 2008 : Create a Group Object
- Windows Server 2008 R2 : Understand Group Policy (part 2) - Learn Group Policy Processing
- Windows Server 2008 R2 : Understand Group Policy (part 1) - Understand the Scope of Group Policy Management & Understand and Control the Order of Precedence
- Windows Server 2008 R2 : Work with Windows Server Update Services
- SQL Server 2005 : Testing Database Routines - Guidelines for Implementing Database Testing Processes and Procedures
- SQL Server 2005 : Testing Database Routines - Introduction to Black Box and White Box Testing
- Microsoft SQL Server 2008 Analysis Services : Designing simple dimensions (part 2) - Using the Dimension Editor
- Microsoft SQL Server 2008 Analysis Services : Designing simple dimensions (part 1) - Using the 'New Dimension' wizard
- SharePoint 2010 Search : Tuning Search (part 4) - Search Keywords and Best Bets
 
 
Top 10
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 2) - Wireframes,Legends
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 1) - Swimlanes
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Formatting and sizing lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Adding shapes to lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Sizing containers
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 3) - The Other Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 2) - The Data Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 1) - The Format Properties of a Control
- Microsoft Access 2010 : Form Properties and Why Should You Use Them - Working with the Properties Window
- Microsoft Visio 2013 : Using the Organization Chart Wizard with new data
 
programming4us
Windows Vista
programming4us
Windows 7
programming4us
Windows Azure
programming4us
Windows Server