I've searched for the answer for this for ages and it's driving me mad.
I've looked after the GPO's here for the last 7 years but we've recently upgraded to 2008 R2 from 2003 R2. Domain Level is still 2003.
This happens with all GPO's but for example I'll use a clean GPO.
For example. If I create a new GPO and set "Verbose vs normal status messages" in the Computer ADMX Templates to Enabled. The Settings tab report shows Enabled.
Later down the road I decide I no longer want that and I set it back to Not Configured. Previously this would remove the entry for this Setting from the Settings report, however now it shows it as Not Configured.
For example...(not the same setting, I know, but you get the point)
It's not actually applying anything, the machine defaults back to the Local Policy setting. It's more a visual quirk, but a irritating one!
In 2003 R2 once I set something back to Not Configured it no longer appeared in the Settings report (because there isn't anything set anymore).
The Settings report used to only show Enabled or Disabled items.
It's a little messy because we do all our development in test OU's, not on live clients. So if we enable something to "try it out" then decide we don't want to use it, that GPO will be left with the traces of that test.
If we wanted to clean the GPO up we'd have to recreate the GPO again when we want to put that GPO into production.
Is this new to 2008? It's annoying!
Why do I need to know about Not Configured settings?
I've looked after the GPO's here for the last 7 years but we've recently upgraded to 2008 R2 from 2003 R2. Domain Level is still 2003.
This happens with all GPO's but for example I'll use a clean GPO.
For example. If I create a new GPO and set "Verbose vs normal status messages" in the Computer ADMX Templates to Enabled. The Settings tab report shows Enabled.
Later down the road I decide I no longer want that and I set it back to Not Configured. Previously this would remove the entry for this Setting from the Settings report, however now it shows it as Not Configured.
For example...(not the same setting, I know, but you get the point)
It's not actually applying anything, the machine defaults back to the Local Policy setting. It's more a visual quirk, but a irritating one!
In 2003 R2 once I set something back to Not Configured it no longer appeared in the Settings report (because there isn't anything set anymore).
The Settings report used to only show Enabled or Disabled items.
It's a little messy because we do all our development in test OU's, not on live clients. So if we enable something to "try it out" then decide we don't want to use it, that GPO will be left with the traces of that test.
If we wanted to clean the GPO up we'd have to recreate the GPO again when we want to put that GPO into production.
Is this new to 2008? It's annoying!
Why do I need to know about Not Configured settings?
