Win7 Hi, I have a service which implements the SENS interfaces, Eg: http://msdn.microsoft.com/en-us/library/aa376863(v=VS.85).aspx I also have my system setup for AutoAdminLogon http://support.microsoft.com/kb/315231 (I know that's an XP article, but it works on Win7 also) My service does not catch the Logon event if AutoAdminLogon is used. If I logon manually, the event is caught. Does anyone know if this is not supported? Does AutoAdminLogon take a different code path? Thanks

More info... apparently system was just too slow, so autoadmin logged me in before the sens service was ready. Thus. another question. Why would windows provide the sens service and autoadminlogon functionality, and not ensure that logon waited until sens was ready? Ie, why provide the sens callbacks when you're not gonna call them? Seems like an oversight or bad design. Anyone know if this is supposed to work?

Hi, You may kindly refer to the following article: Windows Server 2008 R2 and Windows 7: The subscriber has a maximum of 3 minutes to respond to a notification on the ISensLogon and ISensLogon2 interfaces. After 3 minutes, SENS cancels the call to subscribers and unblocks the notification thread. If a lengthy operation is required to respond to the notification, return from ISensLogon or ISensLogon2 as quickly as possible and open another thread for processing. Notifications (Windows) And it is recommended to discuss this issue in MSDN forum: General Windows Development Issues Forum Hope it helps. Alex ZhaoPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.