3.0.1

Updates Key / Value parsing code to clean up malformed paths (with multiple consecutive backslashes, or leading backslashes)

2.0

Error reporting code has been improved a bit, so the errors you see from this module's commands should behave more like what you'd get from a Cmdlet. (There will be FullyQualifiedErrorId values specific to the PolicyFileEditor module, InnerException and TargetObject values where appropriate, etc.) This should be more useful to users of the module than some of the original code, which just used { throw "Some String Message" }, and makes it easier to modify the module later to support localization, if desired.

Because this change in error output could be a breaking change, version has been bumped to 2.0.

1.4.2

No functional changes in this release. However, the build process has been updated.

The PolFileEditor.dll file is now signed in source control, and that signature is no longer overwritten every time build.psake.ps1 is run to create the distribution. This way, deployment scripts can just check the hash of the DLL and not bother trying to overwrite it if it hasn't changed. This should help to address "file in use" type errors when deploying updates to the module, when the LCM (or any other PowerShell session) happens to have the assembly loaded.

1.4

Added a new DSC resource, cAccountAdministrativeTemplateSetting. This works just like cAdministrativeTemplateSetting, except instead of having a PolicyType property, it has an Account property. This can be passed either a SID string or an NT Account-style string (BUILTIN\Users , COMPUTERNAME\SomeUser , etc.) Non-SID account names that do not already contain a Domain portion are automatically prefixed with the local computer name. (-Account Administrator becomes -Account $env:COMPUTERNAME\Administrator , for example.)

1.3

There were some bugs when the commands were passed a single-element array for the -Data parameter, even if that element contained an appropriate value for the data type (DWord, String, etc.) This caused the DSC resource to fail in many cases. This has been fixed, and the tests updated to make sure it works properly in a live environment.

The module will now create a default GPT.ini file if it doesn't already exist, when the -NoGptIniUpdate switch isn't being used. Use that switch if you want to modify pol files that aren't part of a live GPO, to avoid having GPT.ini files created in weird spots on your file system.

1.1

Added SupportsShouldProcess to the destructive commands, and support for standard preference variables if the PreferenceVariables module is available.

1.0

Initial release.

Module contains PowerShell commands that are more user-friendly wrappers around the TJX.PolFileEditor C# classes (including code to increment Version counters in gpt.ini files, as needed.) These are compatible with PowerShell 2.0 and later.

Module also contains a DSC resource for modifying local GPOs using these PowerShell commands, which can be used in PowerShell 4.0 and later. Windows 2008 R2 systems are also supported in this scenario; the module has no dependency on Cim cmdlets.