🚀 go-pugleaf

Dima,

You may be correct about the 7.0.9 upgrade specifically not being he culprit. It may very well be any version installed by a domain user who is also an administrator on their own workstation. I just am not sure.

Here is the sequence of events in our environment:
1) The last version of the reader that we installed with SMS was V 7.0.5.
2) Any higher version would have been installed by a person who is an administrator on their own workstation, probably using Adobe Updates.
3) It just happens that the only versions I have found that have been installed by a user who is also an administrator on their own workstations is V 7.0.9.
4) Attempting to upgrade to the reader V 8 on workstations that have been upgraded by a domain user who is also an administrator on their workstation fails with the errors sited earlier.
5) Upgrading to V 8 on machines where the last version upgrade was enterprise wide and installed using SMS (V 7.0.5) is successful, as the local administrators group still has write access to the keys in question.

It appears that a domain user who is also an administrator on their own workstation and has installed a reader upgrade, now becomes the creator owner, knocking out the local administrators group as the creator owner. Local Administrators group must have full control in order write to the keys sited earlier in this thread.

At the risk of repeating what actually worked, once the local adminstrators group is given creator ownership in the parent key, I was able to give the local adminitrators group full contol to the child key, giving write access to the formerly access denied keys.

Hope that makes our situation a little clearer.

Thanks, Dima,
Sandy