File permissions are retained so my guess is registry permissions will also be retained. Just for the record, which key are you setting these permissions to and are you sure these keys are not excluded from the appstack?
You can edit permissions by using the command line utility: regini.exe
Put whatever command you will use to change permission in one of the bat files that runs as system if the user doesn't have permissions
if you use UEM, you could always do a privileges escalation on that program so it has rights.
1 person found this helpful
On registry permissions and app stack, during the process of creating/updating app stack it will capture only HKLM hive and out-side of user profile [i.e it will not capture inside c:\users]
If you are using UEM 9.2.x version you can user Admin Privileged for particular application
Please provide us your feedback/update regarding this request
Has this ever been resolved? I'm trying to modify permissions in appstack while provisining. THe key I need to add users permissions to modify is Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment
Once I modify permissions it just disappears like it's not sticking at all?
1 person found this helpful
Could be that this specific location is being excluded. Just check the snapvol.cfg file on the appstack that you are changing the permissions on. If you can find that specific location with an exclude it is not retained within the appstack.
Seems that with version 4.0 this specific location is not being excluded,.
So it is not beeing exlcuded but I also don't see it being included. Meaning that there is no virtualize_registry= command for that path either. Would this be the case?
Also, I was able to kind of resolve my problem by simply changing the Registry permission for that key on my packaging machine and then provisioning appstack on that .
I am having exactly the same issue, but for another registry key. Could you be more specific how you have resolved it, please?
"by simply changing the Registry permission for that key on my packaging machine" = do you mean changing the permission for that key on the packaging machine, before starting the packaging?
By the way, I cannot find snapvol.cfg in my appstacks since Appvolumes v4. Do you see this file in your appstacks?
Thanks a lot!
So we have 2 packaging machines that are clones of Master images minus almost all apps and horizon agent. I powered it on, consoled in and changed the desired key permissions. Then powered it off and took a snapshot. Next, created new appstack, powered on that packaging machine and started provisioning on it. Once app was installed rebooted and completed provisioning process. Then assigned the appstack and had no more issues with modifying that key by script.
Great glad it worked out for you