"verukins" <verukins@hotmail.com> wrote in message
news:1192016315.276768.242920@v3g2000hsg.googlegro ups.com...
> This isnt quite scripting, but scripting people will get what i mean..
>
> I am using the good old "for /f" along with xcacls.vbs to set home
> drive and profile permisisons, but have always used it setting all the
> way down the tree (ie /s /t) .... as you can imagine this takes a very
> long time for large migrations, as it sets permissions on every file
> instead of using inhertiance (which is obviously quicker and cleaner)
>
> In the Windows Explorer GUI, i can simply set the permissions at the
> top level, and inhertiance will take care of the rest of the tree.
>
> However, if i set the permissions at just the top level using
> xcacls.vbs, the permissions dont flow through to the rest of the
> structure, even though inhertiance is enabled. (so using the
> "inhertitance enabled" fature of xcacls is of no use, as its already
> on!)
>
> Im clearly missing something here, there must be a way to set it once
> at the top with xcacls and have it flow through cvorrectly - can
> anyone assist?

I cannot be sure, but I think I have done something similar with cacls.EXE
(the latest version as found in XP and 2k3). I think, however, that it may
depend on whether or not the folder structure already is setup with "dynamic
inheritence" of permissions.

Anyway, I'd suggest you try setting the permission on one folder using
cacls.exe, and see if the change is inherited.

If it isn't, try it on another folder after having used the GUI to replicate
permissions to see if that results in permission inheritance.

/Al