SendSAS function
Simulates a secure attention sequence (SAS).
Syntax
VOID WINAPI SendSAS( _In_ BOOL AsUser );
Parameters
- AsUser [in]
-
TRUE if the caller is running as the current user; otherwise, FALSE.
Return value
This function does not return a value.
Remarks
To successfully call the SendSAS function, an application must either be running as a service or have the uiAccess attribute of the requestedExecutionLevel element set to "true" in its application manifest. If an application is not running as a service, it must be running as either the current user or the LocalSystem account to call SendSAS. In addition, if an application is not running as a service, User Account Control must be turned on to call SendSAS.
- \Program Files\
- \windows\system32\
The local security policy of a computer must be configured to allow services and applications to simulate a SAS. To configure the policy, modify settings in the Group Policy Editor (GPE) Microsoft Management Console (MMC) snap-in. The GPE settings that control delegation are in the following location:
Computer Configuration | Administrative Templates | Windows Components | Windows Logon Options | Disable or enable software Secure Attention Sequence
A service can impersonate the token of another process that calls that service. In this case, a call to the SendSAS function by that service simulates a SAS on the session associated with the impersonated token.
Windows Server 2008 and Windows Vista: Sas.dll is not available natively. You must download the Windows 7 version of the Microsoft Windows Software Development Kit (SDK) to use this function. In addition, an application must refer to Sas.dll to call this function.
Requirements
|
Minimum supported client |
Windows 7 [desktop apps only] |
|---|---|
|
Minimum supported server |
Windows Server 2008 R2 [desktop apps only] |
|
Header |
|
|
Library |
|
|
DLL |
|