ProcessGroupPolicy callback function
The ProcessGroupPolicy function is an application-defined callback function used when applying policy. The PFNPROCESSGROUPPOLICY type defines a pointer to this callback function. ProcessGroupPolicy is a placeholder for the application-defined function name.
This callback function is not useful for Resultant Set of Policy (RSoP) processing; use the ProcessGroupPolicyEx callback function instead.
DWORD CALLBACK ProcessGroupPolicy( _In_ DWORD dwFlags, _In_ HANDLE hToken, _In_ HKEY hKeyRoot, _In_ PGROUP_POLICY_OBJECT pDeletedGPOList, _In_ PGROUP_POLICY_OBJECT pChangedGPOList, _In_ ASYNCCOMPLETIONHANDLE pHandle, _In_ BOOL *pbAbort, _In_ PFNSTATUSMESSAGECALLBACK pStatusCallback );
- dwFlags [in]
This parameter can be one or more of the following flags.
Apply computer policy rather than user policy.
Perform a background refresh of the policy.
Perform an asynchronous foreground refresh of policy. For more information about foreground policy application, see Initial Processing of Group Policy.
The policy is being applied across a slow link.
Write verbose output to the event log.
No changes to the GPO were detected.
A change in the link speed was detected between policy applications.
A change in RSoP logging was detected between the application of the previous policy and the application of the current policy.
A forced policy refresh is being applied.
Safe mode flag.
- hToken [in]
Token for the user or computer, returned from the LogonUser, CreateRestrictedToken, DuplicateToken, OpenProcessToken, or OpenThreadToken function. This token must have TOKEN_IMPERSONATE and TOKEN_QUERY access. For more information, see Access Rights for Access-Token Objects and Client Impersonation.
- hKeyRoot [in]
Handle to the HKEY_LOCAL_MACHINE or HKEY_CURRENT_USER registry key.
- pDeletedGPOList [in]
Pointer that receives the list of deleted GPO structures. For more information, see GROUP_POLICY_OBJECT.
- pChangedGPOList [in]
Pointer that receives the list of changed GPO structures. For more information, see GROUP_POLICY_OBJECT.
- pHandle [in]
Asynchronous completion handle. If the callback function does not support asynchronous processing, this handle is zero.
- pbAbort [in]
Specifies whether to continue processing GPOs. If this parameter is TRUE, GPO processing will cease. If this parameter is FALSE, GPO processing will continue.
- pStatusCallback [in]
Pointer to a StatusMessageCallback callback function that displays status messages. This parameter can be NULL in certain cases. For example, if the system is applying policy in the background, the status user interface is not present and the application cannot send status messages to be displayed. For more information, see the following Remarks section.
If policy was applied successfully, return ERROR_SUCCESS. If there are no changes to the GPO list, and the extension is to be called again, return ERROR_OVERRIDE_NOCHANGES. Returning ERROR_OVERRIDE_NOCHANGES ensures that the extension is called again, even if the NoGPOListChanges registry value is set. (For more information about this registry value, see Remarks.) Otherwise, return a system error code.
For more information, see Implementing a Group Policy Client-side Extension.
The system calls this function in the context of the LocalSystem account, which has extensive privileges on the local computer. To use network resources, you must impersonate the user or computer by using the token provided in the hToken parameter.
To register this callback function, create a subkey under the following registry key:
The subkey should be a GUID, so that it is unique. It should contain the following values.
A REG_EXPAND_SZ value that specifies the path to the DLL that contains the callback function.
If this value is 1, the callback function will complete its processing asynchronously.
When the callback function is finished, it should call the ProcessGroupPolicyCompleted function.
A REG_MULTI_SZ value that specifies the (event source name, event log name) for client-side extensions.
A REG_SZ value that specifies the name of the GenerateGroupPolicy callback function that generates RSoP data.
Specifies the maximum number of minutes to skip the extension when policy has not changed. If the system is refreshing policy and this limit has been exceeded, the system calls the extension without specifying GPO_INFO_FLAG_NOCHANGES.
If this value is 1, do not call the callback function when policy is applied in the background.
If this value is 1, it indicates that it is not necessary to call the callback function when there has been no change in the GPO list.
If this value is 1, do not call the callback function when computer policy is processed.
If this value is 1, do not call the callback function over a slow link.
If this value is 1, call the callback function to notify the extension when a change in link speed is detected between policy applications.
If this value is 1, do not call the callback function when user policy is processed.
If this value is 1, user policy settings must be cached on a per-user and per-computer basis.
A REG_SZ value that specifies the name of the application-defined ProcessGroupPolicy callback function.
Note that this value has been superseded by the ProcessGroupPolicyEx value.
A REG_SZ value that specifies the name of the application-defined ProcessGroupPolicyEx callback function.
If this value is 1, the callback function should be called only if the registry extension was successfully processed on the client.
You should update the status message only if you are applying policy synchronously. This allows you to provide feedback and diagnostics during a lengthy policy application. To use the status message callback function, you must verify that pStatusCallback is not NULL. Then load your message string resource. When you call the status function, you must indicate whether the string is verbose. If the string is verbose, the callback function will verify that the computer is in verbose mode and display the message. For more information, see StatusMessageCallback.
Warning Do not call the pStatusCallback function from a background thread because you may overwrite another thread's status message.
Minimum supported client
|Windows Vista [desktop apps only]|
Minimum supported server
|Windows Server 2003 [desktop apps only]|
- Group Policy Overview
- Group Policy Functions