Click here to Skip to main content
15,886,362 members
Articles / Programming Languages / C++

Taking Advantage of the Winlogon Notification Package

Rate me:
Please Sign up or sign in to vote.
5.00/5 (18 votes)
6 Jan 2001CPOL 341.3K   78   105
Taking advantage of the Winlogon Notification Package
<!-- Add the rest of your HTML here -->

Introduction

The Winlogon Notification Package is a DLL which exports functions that handle Winlogon.exe events. These event messages includes lock, unlock, logoff, logon, startup, shutdown, startscreensaver, stopscreensaver, and startshell. 

This article demonstrates how to use the Winlogon Notification Package as an alternative to NT Services. The main benefits for doing this is better handling of user activities. In addition, the Winlogon Notification Package will be very lightweight and requires much less code then its NT service equivalent. 

The Steps

Creating a Winlogon Notification package is very simple. Just create a DLL with specific functions to run during the Winlogon event messages. To let Winlogon.exe know about your DLL, simply add a few entries into the registry where appropriate. This method can be quite robust and versatile when combined with your services and applications.

Sample

This sample starts a WIN32 application before the user logon. Because the process is started by Winlogon, it is owned by the system account. Users may not end the process through 'End Task'. This is the exact way NT services behave. In this sample, the logoff notification will terminate the process. If the process needed to stay active, the EndProcessAtWinlogoff function should be removed. If we wanted the process to be owned by the user, we could use CreateProcessAsUser during a startup notification instead of a logon notification. 

Step 1.) - the dll

//sample.cpp

#include <windows.h>
#include <Winwlx.h>

PROCESS_INFORMATION g_pi;
TCHAR g_szPath[] = _T("c:\somepath\execut.exe \"arguments\"");

//This function safely terminates a process, allowing
//it to do cleanup (ie. DLL detach)
//It can be found at the Windows Developer's Journal
SafeTerminateProcess(HANDLE hProcess, UINT uExitCode);   

//Entrance function for the DLL
BOOL WINAPI LibMain(HINSTANCE hInstance, DWORD dwReason, LPVOID lpReserved)
{
    switch (dwReason)
    {
        case DLL_PROCESS_ATTACH:
        {
	    DisableThreadLibraryCalls (hInstance);	
        }
        break;
    }
    return TRUE;
}

//Event handler for the Winlogon Logon event
VOID APIENTRY StartProcessAtWinLogon (PWLX_NOTIFICATION_INFO pInfo)
{
    STARTUPINFO si;
    si.cb = sizeof(STARTUPINFO); 
    si.lpReserved = NULL; 
    si.lpTitle = NULL; 
    si.lpDesktop = "WinSta0\\Default"; 
    si.dwX = si.dwY = si.dwXSize = si.dwYSize = 0L; 
    si.dwFlags = 0;; 
    si.wShowWindow = SW_SHOW; 
    si.lpReserved2 = NULL; 
    si.cbReserved2 = 0; 
				
    CreateProcess(NULL, g_szPath, NULL, NULL, FALSE, CREATE_NEW_CONSOLE,
                  NULL, NULL, &si, &g_pi);
}

//Event handler for the Winlogon Logoff event.
VOID APIENTRY StopProcessAtWinLogoff (PWLX_NOTIFICATION_INFO pInfo)
{
    //terminates the process
    SafeTerminateProcess(g_pi.hProcess, 0xDEADBEEF);  
}

//other event handlers
VOID APIENTRY YOUR_EVENT_HANDLERS (PWLX_NOTIFICATION_INFO pInfo)
{
    //code
}

...

Step 2.) - the exports

The program hasn't exported any functions yet. We need to create a .def file.

sample.def

EXPORTS
StartProcessAtWinLogon
StopProcessAtWinLogoff

 

Now add the following to your linkage options in VC6 and build.

/def: "sample.def"

If everything went well, the files sample.dll and sample.exp will be in your output folder. Move these to \%NTROOT%\system32

Step 3.) - the registry

Add the following values and keys to the registry. These values communicate to Winlogon.exe and let it know which procedures to run during an event notification. Add as few or as many notification events as needed.

HKEY_LOCAL_MACHINE
    \Software
        \Microsoft
            \Windows NT
                \CurrentVersion
                    \Winlogon
                        \Notify
                            \NameOfProject
                                \Asynchronous  REG_DWORD  0
                                \Dllname       REG_SZ     NameOfDll.dll
                                \Impersonate   REG_DWORD  0
                                \Logon         REG_SZ     StartProcessAtWinLogon
                                \Logoff        REG_SZ     StopProcessAtWinLogoff
                                \...           REG_SZ     NameOfFunction

That's it! Now restart and Winlogon.exe will launch your app.

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)


Written By
Architect Frontline Direct Inc., Adconion
United States United States
Tony Truong graduated from UCLA in Spring of 2001 and starting worked at Symantec Corporation as a Software Engineer. After a few years of developing various features for Norton SystemWorks, Tony moved to San Diego. He is currently writing database applications using ASP.NET and C# with the .NET Framework. Tony specializes in tara-byte databases with emphasis on high availability, optimization, and complex entity modeling.

Comments and Discussions

 
GeneralNeed help. atl service not getting registerwindow message Pin
Chak19-Dec-03 16:05
Chak19-Dec-03 16:05 
GeneralRe: Need help. atl service not getting registerwindow message Pin
Blake Miller25-Mar-05 11:54
Blake Miller25-Mar-05 11:54 
GeneralQuestion... Pin
mikasa31-Oct-03 3:08
mikasa31-Oct-03 3:08 
GeneralAction in WinLogon Pin
Member 384856629-Aug-03 8:23
Member 384856629-Aug-03 8:23 
GeneralRe: Action in WinLogon Pin
Anonymous6-Oct-04 4:53
Anonymous6-Oct-04 4:53 
GeneralRe: Action in WinLogon Pin
Anonymous6-Oct-04 5:42
Anonymous6-Oct-04 5:42 
GeneralRe: Action in WinLogon Pin
Anonymous17-Nov-04 4:22
Anonymous17-Nov-04 4:22 
GeneralMFC application as service creating problem on logon Pin
Rohit Dhamija1-Aug-03 19:19
Rohit Dhamija1-Aug-03 19:19 
GeneralRe: MFC application as service creating problem on logon Pin
Blake Miller2-Mar-04 15:10
Blake Miller2-Mar-04 15:10 
GeneralServices vs. Winlogon HELP!!! Pin
miloX19-Apr-03 5:19
miloX19-Apr-03 5:19 
GeneralRe: Services vs. Winlogon HELP!!! Pin
Anonymous27-Apr-04 2:33
Anonymous27-Apr-04 2:33 
GeneralRe: Services vs. Winlogon HELP!!! Pin
ThatsAlok3-Jul-04 0:06
ThatsAlok3-Jul-04 0:06 
GeneralProblem with Terminal-Server notification Pin
mathias.gilhuber@t-online.de14-Mar-03 3:15
sussmathias.gilhuber@t-online.de14-Mar-03 3:15 
GeneralRe: Problem with Terminal-Server notification Pin
Tony Truong25-Mar-03 12:41
Tony Truong25-Mar-03 12:41 
Generaluser can still kill process Pin
geniedren5-Feb-03 0:18
geniedren5-Feb-03 0:18 
GeneralRe: user can still kill process Pin
Hugo Hallman24-Mar-03 0:04
Hugo Hallman24-Mar-03 0:04 
GeneralNot Working in windows NT Pin
Sukanta Kumar Dash29-Jan-03 1:17
Sukanta Kumar Dash29-Jan-03 1:17 
GeneralMSDN topic on Winlogon Event handling Pin
Anonymous4-Sep-02 10:07
Anonymous4-Sep-02 10:07 
QuestionHow do you use the Toekin given to you in the Package Pin
CEF22-Aug-02 9:40
CEF22-Aug-02 9:40 
AnswerRe: How do you use the Toekin given to you in the Package Pin
MSdispenser11-Feb-03 2:51
MSdispenser11-Feb-03 2:51 
Generalproblem with the package. Pin
proman14-Aug-02 4:24
proman14-Aug-02 4:24 
GeneralRe: problem with the package. Pin
Tony Truong3-Feb-03 9:09
Tony Truong3-Feb-03 9:09 
GeneralTaking Advantage of the Winlogon Notification Package Pin
proman13-Aug-02 17:36
proman13-Aug-02 17:36 
GeneralRe: Taking Advantage of the Winlogon Notification Package Pin
MSdispenser11-Feb-03 1:46
MSdispenser11-Feb-03 1:46 
GeneralWindows NT Pin
smelov16-Jul-02 3:30
smelov16-Jul-02 3:30 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.