| re: Removing Everyone Account Stops PERL Sync Script
We are trying to get the functionality to work as it does for inhouse servers, in which the image repository folder on the server uses simple directory security.
This folder is under the default IIS Home Directory location... C:\InetPub\wwwroot\FolderX structure, in which FolderX is the image repository folder.
For inhouse source servers- the inherited permissions were removed for this folder using Windows Explorer\Folder Properties\Security Tab\Uncheck "Allow inheritable permissions...". The Administrator account was added with full control, then each user account was added with the following permissions: Read & Execute, List Folder Contents, & Read.
This works fine for the inhouse servers. But... for the big pipe external servers in which the PERL Sync Script is required to PULL imagery from the inhouse source servers, & write them to the equivalent remote folder, this setup does not work.
With inherited permissions enabled on the target folder on the external server, the PERL Sync Script works fine. Once you remove inherited permissions, then add in the administrator accounts, then add in all the user accounts, the PERL Sync Script stops working.
I've tried adding the Local System account, & all other accounts to see if the PERL Sync Script would start working. It is not until you add the Everyone account back in that the PERL Sync Script starts working again.
How can I change the PERL or IIS functionality/permissions/or whatever else it might be so that the PERL Sync Script does not use the Everyone account to work?
I'm not sure if I can make this any clearer. The PERL Sync Script needs to operate on the target folder on the remote server in the absence of the Everyone account, using simple directory security. The remote server is a 1.5 hour drive away from here. Remote Desktop is used to access it.
Any help much appreciated - KD
|