Remote Desktop Protocol version 6.1 changed the way RDP sessions are handled (making session 0, which previously meant "console session", into a non-interactive session). I need to be able to figure out from within my program how to determine just what version of the RD protocol is being used on the current RDP session. Nothing I can find in the Windows Terminal Services API, however, seems to give me the protocol version.
the WTSClientBuildNumber attribute in the WTS_INFO_CLASS contains the client build number which appears to be the version of the client's RDP.
The WTS_INFO_CLASS enumeration type contains values that indicate the type of session information to retrieve in a call to the WTSQuerySessionInformation function.
here is the msdn terminal services api article.
Related
When launching an InnoSetup .exe, is it possible to retrieve the current email address logged into Outlook.exe (provided that Outlook is started up and running)? How can one retrieve this value as a string var? Thank you.
Use Application.Session.CurrentUser.Address. In case of an Exchange account, use Application.Session.CurrentUser.AddressEntry.GetExchangeUser().PrimarySmtpAddress
It is not a good idea to connect to a running app from a setup process. I am not sure about InnoSetup, but Windows installer is running as a service, and you won't be able to connect to an out-of-proc COM object (such as Outlook.Application) if the security contexts do not match (even if the local user is the same).
When trying to use RDP shadowing, one of the necessary parameters is the session ID that you want to actually shadow:
mstsc shadow:$sessionID /v:$computerName
Every article I've read online suggests using qwinsta or query to obtain the currently active session IDs from the client you want to connect to using RDP. However, these utilities are only available on Windows Server edition, not Windows 10 Home. Attempting to use them on Windows 10 Home simply returns a "command not recognized as internal or external command" error.
Is there any way to obtain the session ID of a client from the server you want to connect with on Windows 10 Home? I've tried just brute forcing the ID, and this has worked for me at points--but it seems to constantly change.
Thanks!
I'm writing a code for customized management of remote desktop sessions, similar to RD service manager from Windows Server. I'm using functions from wtsapi32.dll and winsta.dll to enumerate sessions, get session information, disconnect/logoff users and send messages to them.
I use WTSSendMessage to send message to user, and this is enough to emulate RD service manager functionality. I'd like to customize resulting message box with info/exclamation/error icon by specifying corresponding value in Style parameter. However, it works for previous generation of OS (Windows 7, Windows Server 2008R2) and client version of current generation (Windows 8)
but not for current generation of server (2012R2)
Is it possible to reinstate desired behavior in WinServer 2012R2, or use different API function? Or this API functionality was deprecated in 2012R2 (or simply lost in transition to Metro UI)?
As I understand, when we start windows it starts Session 0 which does not connect to any GUI, etc. and runs all windows services. So my task is, after windows was started, emulate windows input for selecting user and login to is session. I know that for sending input from service I should run desktop app and through it send input, show GUI, so on, but how can I do it before any user session was start? (for example I see that TeamViewer can do it)
WTSGetActiveConsoleSessionId() will tell you which session is attached to the physical console.
You can then duplicate your security token with DuplicateTokenEx(), change the new token's session with SetTokenInformation() and the TokenSessionId option, and launch a process with CreateProcessAsUser().
The new process should then be running in the right session, but it may also need to attach itself to the right desktop before it can interact with the logon interface. You can use EnumDesktops() to list the available desktops, and trial and error to determine which one the logon interface runs in. (Note that this may be different in different versions of Windows.)
Here's what I want to do:
a program that listens in the network for a message, and when that message is received, if the user is not logged in (for example the computer just powered on and windows displays the classic login screen), it automatically logs in a certain user accordingly to the message. the username and password are known and stored safely inside the computer in a configuration for the program i'm talking about.
What I had in mind was a windows service that starts with the computer and also listens to those messages, and if one is received, then it does it's job
but I have no idea of where to start
(basically i'm trying to login a user without having to type the password, which I said is stored and known - need something mostly like the fingerprint software windows 7 comes with, and the ones that you had to install in vista/xp so that fingerprint login would work (fingerprint was only an example) )
There's two methods to pursue depending upon which operating system you're looking to run under.
For Windows XP, Windows 2000, and Windows Server 2003 you need to create a GINA.DLL. This is a replacement DLL which must follow specific rules which handles the authentication process. In your case your replacement DLL would be known by the service which was listening for your start signal, and it would make a call into the DLL with the username and password as appropriate.
MSDN Magazine article on customizing GINA.DLL
MSDN entry on GINA
For Windows Vista/7 and above you'll need to look into the Credential Provider API.
MSDN Magazine article on Credential Provider API in Vista.
MSDN entry on Credential Provider API
You can use windows auto logon feature to do this.
Create a service which waits for the required data on a network socket. Make sure this service is started after the network service (Tcpip). Modify winlogon service properties (manually) so that it depends on your service. By depends, I mean that winlogon service is started after your service.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\AutoAdminLogon to 1
Once you receive the data on your network socket, set the following registry keys:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\DefaultUserName
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\DefaultPassword
Once the registry settings are in place, then the winlogon service can read those values and proceed with the login process.
For more details on setting the registry values refer: http://support.microsoft.com/kb/315231
I want clarify a little the suggestion of Vikram.exe.
Of cause the usage of AutoAdminLogon seems native for the problem, but saving of the password in registry as a clear text under HKLM\...\Winlogon\DefaultPassword is not good. Since Windows 2000 it is supported the usage of the secrets DefaultPassword which makes the same effect as the DefaultPassword registry value (see Protecting the Automatic Logon Password for the code example).
Another way to force user login or to do any other actions on the login screen is switching to the Winlogon desktop (full name WinSta0\Winlogon). You can use SwitchDesktop and SetProcessWindowStation to do this (see Window Stations and Desktops). If the service run under System account you will have all rights to do this. Depend on the configuration of your service it could be also needed to use SetTokenInformation with TokenSessionId to change the current session id. After the service process will run on the WinSta0\Winlogon desktop you can use functions like FindWindow and other GUI API to place any information in controls of the window (user name, password and so on) of other process. So you can implement more complex scenarios.
Firstly let me just say im not 100% sure how to fully complete such a application but I have a few tips.
you will need to create a Windows Service that starts during the Pre-Login, you can create a service in C#, An example of creating a C# Service is linked below:
http://msdn.microsoft.com/en-us/library/zt39148a(VS.80).aspx
Within your application you would set the property Startup Type to Automatic, This will automatically start your service on boot.
You should know that windows services run under a secure context by account so you will have to get your service to run with privs do do this.
In your Service Properties you can Click Log On and you can
To specify that the service uses the Local Service account, click This account, and then type the following NT AUTHORITY\LocalService.
To specify that the service uses the Network Service account, click This account, and then type the following NT AUTHORITY\NetworkService.
As your trying to do this remotly you will have to look at WMI (Windows Management Instrumentation) and you will be able to start/stop and send commands to your service.
Your service then would send a command to the Login Management (Not Sure of the name).
you may also wish to check this WOL class which will switch the computer on remotely as long as it supports Wake On LAN, If this is for a corporate environment then I advise you to check your network cards to make sure they are supported
http://www.codeproject.com/KB/IP/wolclass.aspx
I know of some education software that I use for schools that's called CC4 ( http://www.rm.com/shops/rmshop/story.aspx?cref=PS1026195 ) and we can do exactly what you need within this system, I'm not fully sure of how it works fully but i believe it takes the same principles described above.