Summary:
Time has a way of confounding a systems administrator when it comes to the shared-folder environment in his network. There are some ways to stop all the confusion, however.

Details or Sample:
Have you ever taken the time to analyze the current shared-folder environment in your network? If you have, the chances are good that you were quickly dumbfounded by how unclear and complex your share and permissions structure has become. Time has a way of confounding even the best laid plans of systems administrators and men and network shares are a notoriously difficult can of worms to keep simple. There are some ways to get around this, however. Provided, of course, you are prepared to roll up your sleeves and redo your shared-folders from the ground level up.

Keep it simple and keep it flat. Huh? What does he meant with that? I"ll tell you what I mean with that.

First of all, it is important that you will be willing to work with a standard group of basic, "first-level" permissions which will be applied on all shared folders throughout your network. It is understood that System and Administrators will have full control. But having said this, a global Deny Group should also be assigned to every share, as well. Should a user ever need to be denied permissions immediately, for instance, entering this person to such a group is much faster than identifying and removing this user from all the other groups he or she may belong to. The "flow down" of permissions can also take considerable time in this second scenario.

You"ve heard of the KISS principle, right? Keep it simple stupid, oops, I mean sweetheart. Well, that principle certainly applies to network shares. A simple permissions structure is, quite simply, simpler to manage than a complex one. Why start out using 30 security groups to assign permissions to a share when you can use 3 instead?

Purchase this content for your website...

Pricing:
Usage:	$7.5	[Add to Cart]

Downloads: 1
Written by: clarsonimus
Available File Types:Text
Words: 800