managing NTFS permissions - cacls or wmi?

cacls or wmi for managing ntfs permissions?

I was going to go with cacls but having an issue using 'echo y | cacls...'
command? my cacls command is good, it works until I try to echo y into it so
it can go without user interaction. Anyone know whats up with that?

how is wmi for this? haven't looked yet, just looking for others opinions
based on their experiences using either of these

thanks

I was putting a space after y in: echo y | cacls...

echo y| cacls... without the space works, of course

regardless, still interested in hearing about others experience using this
and/or wmi for scripting ntfs permission managment tasks. I have not looked
into the wmi route but do recall an example somewhere that looked overly
complicated for the goal at hand... I'm thinking cacls is much simpler, with
the only negative being I need to shell out from wsh.

thanks

"James" <> wrote in message
news:Or$...
> cacls or wmi for managing ntfs permissions?
>
> I was going to go with cacls but having an issue using 'echo y | cacls...'
> command? my cacls command is good, it works until I try to echo y into it
> so it can go without user interaction. Anyone know whats up with that?
>
> how is wmi for this? haven't looked yet, just looking for others opinions
> based on their experiences using either of these
>
> thanks
>

James - stick to cacls (try xcacls or icacls if you are running Vista).
While managing permissions via scripting (with or without WMI) is certainly
possible, such approach is considerably more complex and time consuming.
Check http://technet.microsoft.com/en-us/m.../cc160995.aspx to get a
taste of it...

hth
Marcin

"James" <> wrote in message
news:%...
>I was putting a space after y in: echo y | cacls...
>
> echo y| cacls... without the space works, of course
>
> regardless, still interested in hearing about others experience using this
> and/or wmi for scripting ntfs permission managment tasks. I have not
> looked into the wmi route but do recall an example somewhere that looked
> overly complicated for the goal at hand... I'm thinking cacls is much
> simpler, with the only negative being I need to shell out from wsh.
>
> thanks
>
> "James" <> wrote in message
> news:Or$...
>> cacls or wmi for managing ntfs permissions?
>>
>> I was going to go with cacls but having an issue using 'echo y |
>> cacls...' command? my cacls command is good, it works until I try to echo
>> y into it so it can go without user interaction. Anyone know whats up
>> with that?
>>
>> how is wmi for this? haven't looked yet, just looking for others opinions
>> based on their experiences using either of these
>>
>> thanks
>>
>
>

"James" <> wrote in message
news:%...
>I was putting a space after y in: echo y | cacls...
>
> echo y| cacls... without the space works, of course
>
> regardless, still interested in hearing about others experience using this
> and/or wmi for scripting ntfs permission managment tasks. I have not
> looked into the wmi route but do recall an example somewhere that looked
> overly complicated for the goal at hand... I'm thinking cacls is much
> simpler, with the only negative being I need to shell out from wsh.

I frequently use cacls from both command line and script. I use it
exclusively with the /E switch, which does not present a confirmation
prompt. In my case, I am just wanting to grant (or revoke) a specific user
from the directory or file. I am not concerned with altering other
permissions on the directory.

I also looked at the WMI method sometime back & came to the same
conclusion as you. It is indeed a lot of learning and work to accomplish
what shelling out to cacls could accomplish easily.

James wrote:
> I was putting a space after y in: echo y | cacls...
>
> echo y| cacls... without the space works, of course

Just so you know: cacls also takes a /f (“force”) parameter to skip
confirmation.

--
David Trimboli
Windows Systems Analyst
Cold Spring Harbor Laboratory

thanks all for the great input. I appreciate it.

"James" <> wrote in message
news:%...
>I was putting a space after y in: echo y | cacls...
>
> echo y| cacls... without the space works, of course
>
> regardless, still interested in hearing about others experience using this
> and/or wmi for scripting ntfs permission managment tasks. I have not
> looked into the wmi route but do recall an example somewhere that looked
> overly complicated for the goal at hand... I'm thinking cacls is much
> simpler, with the only negative being I need to shell out from wsh.
>
> thanks
>
> "James" <> wrote in message
> news:Or$...
>> cacls or wmi for managing ntfs permissions?
>>
>> I was going to go with cacls but having an issue using 'echo y |
>> cacls...' command? my cacls command is good, it works until I try to echo
>> y into it so it can go without user interaction. Anyone know whats up
>> with that?
>>
>> how is wmi for this? haven't looked yet, just looking for others opinions
>> based on their experiences using either of these
>>
>> thanks
>>
>
>

we use the following in a bacth file during our initial image building to
set it up.

xcacls.vbs c:\temp /t /e /g BUILTIN\USERS:F /E /I ENABLE
xcacls.vbs c:\temp /t /e /g "domain\DOMAIN USERS":F /E /I ENABLE

"James" <> wrote in message
news:%...
>I was putting a space after y in: echo y | cacls...
>
> echo y| cacls... without the space works, of course
>
> regardless, still interested in hearing about others experience using this
> and/or wmi for scripting ntfs permission managment tasks. I have not
> looked into the wmi route but do recall an example somewhere that looked
> overly complicated for the goal at hand... I'm thinking cacls is much
> simpler, with the only negative being I need to shell out from wsh.
>
> thanks
>
> "James" <> wrote in message
> news:Or$...
>> cacls or wmi for managing ntfs permissions?
>>
>> I was going to go with cacls but having an issue using 'echo y |
>> cacls...' command? my cacls command is good, it works until I try to echo
>> y into it so it can go without user interaction. Anyone know whats up
>> with that?
>>
>> how is wmi for this? haven't looked yet, just looking for others opinions
>> based on their experiences using either of these
>>
>> thanks
>>
>
>