I have an issue that I haven't been able to find an answer for. I have a handful of Mac designers here that started using a program called Articulate to generate flash objects to embed on our website. Articulate will create a folder, and in that folder is an html file, some javascript files and the swf file.
The designers have a single PC that they use the Articulate software on, and then they'll move the generated files to their department Share (running on a Windows Server 2008 box). Then they'll get on their macs, connect to the Windows file server via SMB and pull the file to their local computer.
The issue that is coming up is that when they pull the files from the Share to their Mac, OS X is making the permissions 700. When the users try and change the permissions using Finder > Get Info, they get a message that says it can't complete the operation, error code -50. If I use chmod from the terminal, it fixes it just fine. This is an issue because the CMS system we use depends on the files having the GROUP set to read. So with these files being copied down as 700, it's breaking the CMS.
If I create a new file or folder from the GUI or from the terminal, it applies the umask as expected and gives me 755 and 644, but through SMB it's doing 700. How can I change what default permissions are being set when they pull a file from a SMB share?
Additional Information:
On the Windows share, the folder has the Designers group with all permissions except for "change permissions" and "take ownership". The Designer will then get on their iMac and connect to the Windows fileserver using their Active Directory user, which is a member of the Designer group. Once they've pulled the share up in Finder, they find the folder they want and they drag and drop it to their local desktop. Upon inspecting the permissions of this new folder on their local machine, they have
drwxr-xr-x 63 ryan staff 2142 May 23 09:31 .
drwxr-xr-x 337 ryan staff 11458 May 22 16:25 ..
drwx------ 5 ryan staff 170 May 22 11:54 Folder1
I bet the file permissions could be retained if you used something like RSYNC or something similar that has file-permissions features during a copy...