Not Understanding Audit Policy with SCM 8.1 Baseline

Question

We want to configure Audit Policy on all standalone Windows 8.1 computers to log Success and Failure for Logon attempts.
The Beta Baseline for Windows 8.1 contains a setting for this, but it is read only and you cannot change it.  Why?
When that baseline is put into effect on the computer with the LocalGPO tool from the command line, Logon attempts are logged.   However what is bizarre is that both SecPol.msc and GPEdit.msc fail to see this setting for Audit policy.  Why?
Equally bizarre, if you modify the settings for Audit Policy in SecPol.msc and GPEdit.msc, they show as modified, but as soon as you quit and restart those tools, the settings are lost and the items show up as not configured again.
So, I'm not understand the behavior at any level here, which looks quite different than other settings in the Baseline.  For other settings, we are able to edit them in the Baseline, and further the local SecPol and GPEdit tools are able to change them.
Will

Answer 1

Turns out this question is actually fairly complicated to answer.   The historical "audit policy" contains fewer options than what Windows Vista or later can express.  So, for example, instead of just auditing Logon and Logoff with a single setting,
later versions of Windows are able to audit Logon and Logoff through separate settings.
The SCM baseline for 8.1 and the GPEdit both have access to a setting to affect whether Windows uses the historical audit behavior or the newer finer-category "subcategory" settings.  Under local policies | security options there is a setting "Audit:
Force audit policy subcategory settings"   When this is enabled, your attempts to use the historical audit settings will not change behavior on the computer, and when you quit GPEdit and restart your changes to the historical settings will simply have
disappeared.
Will