TomHD Posted October 23, 2014 Posted October 23, 2014 Hi All, I have installed Pivot Animator across the CC4 network. When it is opened for the first time the language needs setting, this is written to the .ini. When Pivot is closed it tries to write to the .ini again. The problem I am getting is when I am logged in as any user that is not an administrator, Pivot cannot access the .ini and subsequently tries to write to the error log .txt so I get three errors. I have played support tennis with RM and have added Group Policy via GPMC for All Users to allow access to the Pivot folder in ProgramData and have added a Software Restriction through RMMC to allow files in that path and subsequent files and folders to be run but still am having no luck. If I login as admin and manually set the ProgramData\Pivot Animator path to full control for all users it will work but this is not a viable solution for 100+ workstations! Anyone have Pivot Animator working on their CC4 network? Thanks, TomHD
3s-gtech Posted October 23, 2014 Posted October 23, 2014 You can set directory permissions via Group Policy, so rolling out this change to all applied PCs easily. File System: Security Policy
TomHD Posted October 23, 2014 Author Posted October 23, 2014 Thanks 3s, I have tried that following this advice from RM: 1) Logon to your FRDC as administrator 2) Start-Run-gpmc.msc 3) On the Group Policy Management console 4) Expand Establishment->Right click All Stations policy and click Edit 5) Expand Computer configuration->Policies->Windows Settings->Select File System 6) Right click File System->Add File->Folder section type the path as %systemdrive%ProgramData\Pivot Animator ->Click OK 7) Click Add and add a group as Everyone and give Write permission to the group. 8) Peform a gpupdate /force in the server and reboot a couple of stations. 9) Login as a student user and let me know your findings Doesn't work
3s-gtech Posted October 23, 2014 Posted October 23, 2014 Can you check the directory permissions from the server after testing the policy on a test machine? That GP works well IME - I used it to stop the dreaded utilman exploit by denying permission to the application.
TomHD Posted October 23, 2014 Author Posted October 23, 2014 Can you check the directory permissions from the server after testing the policy on a test machine? Don't want to sound like an idiot but what do you mean by this? Cheers
3s-gtech Posted October 23, 2014 Posted October 23, 2014 Sorry - just access the client through the UNC path \\clientname\c$\ProgramData\... then look at the directory permissions there. Are you 100% sure that the path you're setting is correct?
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now