The Administrative tool extensions that apply to policy targets are designated by the Extension list of a GPO. Each Administrative tool extension in the GPO Extension list is represented as a GUID that is associated with an administrative-side extension protocol, sometimes referred to as an administrative plug-in. The plug-in resides on the computer that hosts the Administrative tool. To identify GPOs that the administrative-side extension can query to obtain the stored settings for that extension.
To provide the message sequences for updating the administrative-side extension settings that are stored in the logical part of a GPO. To invoke a file access protocol to retrieve or store extension-related policy settings in the extension policy files on the Group Policy file share. Policy settings for a given class of extension functionality are communicated by a CSE protocol itself and not directly by the core Group Policy engine. The behavior of a given protocol extension is specified in the documentation for that extension.
The extension protocols that are native to Group Policy are specified in section 2. I like the script method because users tend to shut their computers off. I'd like to script it and liked this template because it looks to see if it was already installed on the machine, if so, it skips.
Superflan, that looks simple. I use PDQ Deploy for some some things and was considering using it. I'll give this script a shot. Thank you. To continue this discussion, please ask a new question. Which of the following retains the information it's storing when the system power is turned off? Aimless Ramblings from a Blithering Lunatic. You will need to edit the paths to the installers in the script.
The defined paths can be found on lines 47 — Note that these paths must be UNC paths to work. Leave a Reply Cancel reply Your email address will not be published.
0コメント