Question: Using a stand alone Windows Server 2012 Standard edition (no Active Directory),

I succeded to add a new rule to allow sql server connection, by entering the .exe file

When I edited the rule property to specify the port number, text zones for ports are greyed and no way to write in them.

Is there a new feature in Windows Server 2012 that by default disables port numbers editing ?

Any advices please ?

Answer: 
setfacl on linux has the `-d` and `-k` options for manipulating default permissions which are probably what you are looking for (see man for more info).
It is easy to recursively set simple UNIX permissions at upon demand of an appropriately authorized user, the permissions of directories and files. It is not possible to automatically impose this.

You could tell users to use the set the umask of 0002, and that helps to make new files at 0775 (depending on the application). But it is not enforcable.

My understanding is that ACLs are not inherited on UNIX/Linux systems. They are set upon demand.

As for file/directory ownership, you are pretty much out of luck here.

As for file/directory group ownership, by setting the directory set-gid bit (i.e. g+s on DIRECTORIES), this does cause the group ownership to be inherited.

What I have done in such situations is to execute a periodic root cron script which resets non-conforming permissions/ownerships to the standard in such directories. 

Another (NOT RECOMMENDED) process is to have the same user-id be used when working on these files. This could be accomplished by the user logging into the system under his own UID, and then using sudo or su to run as the id. This still is not 100% especially concerning ACLs and permission bits.