pbastiaans
Enthusiast
Enthusiast

Thank you.

Can you provide the ADMX-based settings config file you're testing with and the ADMX/ADML files it's based on so we can take a look? And do DEM's ADMX-based computer settings act differently than "normal" GPO?

The templates can be found here:  ftp://ftp.adobe.com/pub/adobe/acrobat/win/AcrobatDC/misc/

The behavior expected is that when setting "Disable Updates" to "Enable" bUpdater key gets set to 0 as I have seen on physical machines. UPDATE: This may be due to 'ghost' admx configs are still in play.

When computer environment settings are processed, disabled config files are ignored. Settings that were applied at boot will be reverted at shutdown, and the same happens during a refresh (i.e. "old" settings are reverted before "new" ones are applied.)

How are you testing this, and what do you see in the log?

To your first statement, agreed, the expectation is that disabled is ignored. I understand the default behavior is to revert on shutdown, there is a reg key to control this, however, the default should be revert.

I create the CE Admx, log in. In the case of fail, I see in the logs the that the old config file name is there. UPDATE: I am wondering if this is due to DEM shares being in a DFS cluster, replication issue.

Reply
0 Kudos