Writing a small package for our Site Support folks to quickly modify some folder permissions on remote PCs (we're a Windows XP/Office 2003 environment). And so via this forum I found my way to SetACL. I can get it to work by running it locally, but not remotely. At this point all I'm doing is using the SetACL examples (http://setacl.sourceforge.net/html/examples.html).

If I copy SetACL.exe to my target PC and then run this from the command line, I get the expected change, which is that the Users group gets Modify permissions added to their existing permissions for the Fonts folder:
setacl.exe -on "C:\Windows\Fonts" -ot file -actn ace -ace "n:Users;p:change"

[font="times new roman"]But what I really want to do is run SetACL on a remote PC. And when I try this code, SetACL returns the error message "The object was not set":
setacl.exe -on \\[testpcname]\c$\windows\fonts" -ot file -actn ace -ace "n:Users;p:change"
[font="times new roman"]
[font="times new roman"]I have no idea what I'm doing wrong or what else I can try. Any help?
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


Figured it out. The remote command as I wrote it is correct. Too bad I wasn't USING that command. [:)]
Somehow I had an extra backslash at the end of my path, which wouldn't work.
So this was bad: "\\[testPCname]\c$\windows\fonts\"
[font="times new roman"]But this was good: "\\[testPCname]\c$\windows\fonts"
[font="times new roman"]
Answered 11/14/2008 by: RonW
Green Belt

Please log in to comment
For software which is so capable in every other area, this 'feature' of SetACL is the one which irritates me the most. How hard is it to test for a trailing backslash?
Answered 11/17/2008 by: VBScab
Red Belt

Please log in to comment