I work at a newspaper that uses Macs. We upgraded earlier this year to iMacs, all running 10.6.6. Made a big jump from 10.3.9.
We have a network that everyone has access to. I know this defeats the purpose of the security that's built into Macs, but the reality of how we do business is that everyone, from the top dog in the newsroom down to the lowest peon, theoretically needs to have complete, unfettered read and write access to every single, solitary piece of data on the network. There is much passing around of work, different people working on different projects, people needing access to photos that have been stashed on the network, etc.
This was easy with 10.3.9, was simple to give everyone read/write access to everything. It's been, for lack of a better term, hell in 10.6.6, there does not seem to be a way that someone can give everyone in the newsroom complete and unfettered and unrestricted acccess to every bit of data that's placed on the network, although we are learning to manage. Basically, things have to be copied from the network to individual computers instead of working off the network with elements as in the past, has caused extra steps and work, but we're learning to deal with it.
However, there are an awful lot of folders sitting on our network that, because of issues in trying to deal with permissions, have been converted to "everyone/no access." They are sitting there, taking up space, and nobody can do a blasted thing with them.
We do not have an in house tech person, nearest guy in corporate is two hours away, and he's a PC guy. So we're flying blind in a lot of ways here.
I'd like to know ... can anyone give me a simple, step-by-step method by which we can get this stuff off our server? I've dallied a bit with terminal, am having no success making it work although I could very well be screwing it up. I'm just tired of looking at those red circles on our server and want them to go way.
One thing ... server is still running 10.3.9, could that have something to do with the issues? Is there anything we can do at the server level to get rid of this stuff, or to fix the permissions issues to where access can be granted more liberally?
Again, I realize this defeats the purpose of security, but we're a small newsroom, we do a lot of interactive work, lots of different hands on everything, and again, everybody needs access to everything.
Thanks in advance for any help.
We have a network that everyone has access to. I know this defeats the purpose of the security that's built into Macs, but the reality of how we do business is that everyone, from the top dog in the newsroom down to the lowest peon, theoretically needs to have complete, unfettered read and write access to every single, solitary piece of data on the network. There is much passing around of work, different people working on different projects, people needing access to photos that have been stashed on the network, etc.
This was easy with 10.3.9, was simple to give everyone read/write access to everything. It's been, for lack of a better term, hell in 10.6.6, there does not seem to be a way that someone can give everyone in the newsroom complete and unfettered and unrestricted acccess to every bit of data that's placed on the network, although we are learning to manage. Basically, things have to be copied from the network to individual computers instead of working off the network with elements as in the past, has caused extra steps and work, but we're learning to deal with it.
However, there are an awful lot of folders sitting on our network that, because of issues in trying to deal with permissions, have been converted to "everyone/no access." They are sitting there, taking up space, and nobody can do a blasted thing with them.
We do not have an in house tech person, nearest guy in corporate is two hours away, and he's a PC guy. So we're flying blind in a lot of ways here.
I'd like to know ... can anyone give me a simple, step-by-step method by which we can get this stuff off our server? I've dallied a bit with terminal, am having no success making it work although I could very well be screwing it up. I'm just tired of looking at those red circles on our server and want them to go way.
One thing ... server is still running 10.3.9, could that have something to do with the issues? Is there anything we can do at the server level to get rid of this stuff, or to fix the permissions issues to where access can be granted more liberally?
Again, I realize this defeats the purpose of security, but we're a small newsroom, we do a lot of interactive work, lots of different hands on everything, and again, everybody needs access to everything.
Thanks in advance for any help.