4 Replies Latest reply on Feb 16, 2007 9:46 PM by John McAfee

    Deleting read-only directories with a BLPackage

      So we're trying to delete some rather large directories on a number of Windows servers. We're using a BLPackage to avoid having to write, test, worry about an NSH script. The problem is a large percentage of the child directories is read-only. When BL tries to delete these directories, it interprets the read-only response from the OS as a file lock and bombs out. We've tried tweaking the objects and permissions in the package, but with no clear documentation of how the Owner, Group and Permissions properties work (or if they even have any bearing), we're not sure where to go from here. Has anyone had any experience with this scenario or have any tips on the aforementioned properties? We'd prefer not to have another script to manage, and clearing the read-only attribute on all these servers isn't really an option.