C++ – Getting the number of logged on users in Windows

cmfcvisual c++windows

Let's say I have 3 logged on users. I have a test application which I use to enumerate the WTS sessions on the local computer, using WTSEnumerateSessions. After that, I display the information contained in each of the returned WTS_SESSION_INFO structure.

On Windows XP, there are 3 structures displayed: Session 0, 1, and 3 (for each logged on user), with the name "Console" corresponding to the active user under which I run the test application, and an empty string as the name for the other sessions. For example, if I run the application under the first user, I get Session 0 (Console), Session 1 (), Session 2 ().

On Windows Vista, there are 5 structures displayed: Session 0 (Services), Session 1 (Console), Session 2 (), Session 3 (), Session 65536 (RDP-Tcp). On another computer with Windows Vista, I get only the first four sessions (without 65536, RDP-Tcp).

I would like to know if there is a way (better way) of finding out how many logged on users are on the local machine.

Thanks in advance!

Best Answer

http://www.codeproject.com/KB/system/logonsessions.aspx

Same information available on Getting user name/password of the logged in user in Windows

Try going through this articles:- ( this is for using ASP ...)

http://support.microsoft.com/default...b;EN-US;308157

http://www.c-sharpcorner.com/Code/20...cationWithAD.asp

Related Solutions

C++ – the difference between #include and #include “filename”

In practice, the difference is in the location where the preprocessor searches for the included file.

For #include <filename> the preprocessor searches in an implementation dependent manner, normally in search directories pre-designated by the compiler/IDE. This method is normally used to include standard library header files.

For #include "filename" the preprocessor searches first in the same directory as the file containing the directive, and then follows the search path used for the #include <filename> form. This method is normally used to include programmer-defined header files.

A more complete description is available in the GCC documentation on search paths.

Windows – How to you find out which process is listening on a TCP or UDP port on Windows

New answer, powershell

TCP

Get-Process -Id (Get-NetTCPConnection -LocalPort YourPortNumberHere).OwningProcess

UDP

Get-Process -Id (Get-NetUDPEndpoint -LocalPort YourPortNumberHere).OwningProcess

Old answer, cmd

 C:\> netstat -a -b

(Add -n to stop it trying to resolve hostnames, which will make it a lot faster.)

Note Dane's recommendation for TCPView. It looks very useful!

-a Displays all connections and listening ports.

-b Displays the executable involved in creating each connection or listening port. In some cases well-known executables host multiple independent components, and in these cases the sequence of components involved in creating the connection or listening port is displayed. In this case the executable name is in [] at the bottom, on top is the component it called, and so forth until TCP/IP was reached. Note that this option can be time-consuming and will fail unless you have sufficient permissions.

-n Displays addresses and port numbers in numerical form.

-o Displays the owning process ID associated with each connection.

Related Topic