In your post-provisioning script box, add something like: echo " /Windows/rsc/users
Then you can push the ACL's as part of your post-provisioning job.
Can you actually show the error in context? There are a variety of places you can get a ‘permission denied’ message and the root cause can vary – eg – rsc files are wrong (not mapping to the right user), acls on the server object are wrong, your role doesn’t have permission to run the particular job or job type, etc…
On the refresh All Server ACL job i get
Error Sep 26, 2012 1:51:09 PM Pushing of AgentACL to TS-BL-TEST failed due to 'Permission denied'
Error Sep 26, 2012 1:51:18 PM Encase->Encase failed on server TS-BL-TEST exit code = -5003
Warning Sep 26, 2012 1:51:14 PM Error initializing node
Error buffer: /C/Windows/rsc/secure: Permission denied
I'm guessing it is down to mapping, how does that get added when provisioning servers?
1 of 1 people found this helpful
the provisioning job should echo something into users or users.local to allow the role running the job access.
is the admin user named 'Administrator' ?