Linked by Thom Holwerda on Sun 1st Jun 2008 21:46 UTC
Thread beginning with comment 316723
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
That's one solution. Another solution is to look at how your employees work and try to tailor your IT solution to accommodate them. If people like to save stuff on their desktops, why not make sure that their desktop folder is stored on a central server and backed up.
AFAIK if you do this, people's desktops will not start at all if there is a problem with the server.
If you have a server down, it is possible to set up clients so that they can start up, and people can perhaps generate new text (to be pasted into working documents later, when the server is up).
There is some possibility, albeit small, that productive work can proceed even when the server or network is down.




Member since:
2005-07-06
That's one solution. Another solution is to look at how your employees work and try to tailor your IT solution to accommodate them. If people like to save stuff on their desktops, why not make sure that their desktop folder is stored on a central server and backed up. It's not like its impossible to implement. Perhaps make a more flexible rule like "you can store personal working copies on your desktop if you want, but make sure project files that everybody needs to access are stored in the correct project directory".
I've been on both sides of the fence on this. And while I know from experience who much easier the IT departments life is if they get to dictate (seemingly) arbitrary rules and force people to follow them, I've also seen how much happier employees are if IT shows some flexibility to fit their infrastructure around who people actually like to work. Most work most people do does not need to be instantly accessed by their co-workers.