Thanks. I would like to run it as a vbs script to keep it in the backgroup
and run it from group policy. However, I am terrible at vbs scripts and
don't understand the formatting or how to create one on my own.

As for applying to multiple folders, can you show me an example? I don't
quite understand what you mean. The folders needs the same permissions for
domain users and also a file. Can you specifiy a specific file or files
within the script to have the same permissions?

There are 80% XP and 20% Windows 2000 pcs.

"Al Dunbar" wrote:

>
> "rocketz21" <rocketz21@discussions.microsoft.com> wrote in message
> news:4AFD1FB0-90CC-43DA-A074-521A18DEEDF4@microsoft.com...
> > Here is what I have done, but I'm afraid it won't work correctly from
> > group
> > policy:
> >
> > xcacls.vbs c:\fsp\ /g DOMAIN\"domain users":f /f /t /e /q
> >
> > Saved it as a .bat file. When I run the program the command prompt window
> > stays open, anyway to hide it in the background?
>
> run it as a scheduled task, or run it from a vbscript that causes its window
> to be hidden. This seems to me a one-time thing done by an administrator, so
> I'm not sure if the additional work required would be warranted to make it
> more agreeable to run.
>
> > If i want to include multiple folders, do I need to make separate lines
> > for
> > each or what's the correct syntax?
>
> xcacls.vbs/.exe (and cacls.exe too) process one file or folder specification
> (which can be a wildcard, if that s you) and all object processed have
> the same permissions applied them. If you need to apply different
> permissions, or if you cannot specify all the folders you want throug the
> clever use of wildcards, or if you just want to make this simple and
> manageable, you will need separate xcacls or cacls commands.
>
> > What if the pc doesn't have the xcacls installed? Will it not work? I
> > want
> > to deploy this over group policy to ensure all the pcs have the correct
> > permissions for any current and new employees.
>
> Your system(s) is/are not w2k, but what are they? If they are XP or windows
> server 2003, then they should already have installed an executable called
> cacls.exe that is, by definition, compatible with NTFS on the respective
> systems. xcacls.vbs seems to be a vbscript implementation of the resource
> kit utility called xcacls.exe. That, in turn, was originally written to
> address shortcomings of the version of cacls.exe that came with NT. With XP
> and w2k3 we now have a native cacls.exe that is what it should have been all
> along, and, imho, no further need for any of the xcacls variants out there.
>
> /Al
>
>