I have used your recommendation below before.
The other solution is to create user folders on some hidden server and have some script run on a schedule and copy the checked out files to the server once or twice a day thus minimizing potential data loss.
I try to manage the bulk, force the outliers into the bulk or make them someone else's problem.
Also, when the majority of users are doing something non-approved, I do NOT fight them. Find a way to leverage their behavior to better the business. Otherwise, you die on hills where it doesn't count.
Good luck bud.
Hope it helps.
This free tool from MS might be of use (SyncToy). Its easy and only copies changed files once everything is backed up. This might work nicely with user folders on hidden servers... SycnToy can be set to run at scheduled times using the task scheduler in Windows.
Oooh, that's nice Pete!
Your welcome. I've used it at home and like it. Never used it work for what Jason mentions, but it should work pretty well for that. I think I'll keep it in mind for our migration to EPDM here.
This has always been a concern for the IT minded people. This is a conundrum that we deal with routinely.
What to do?
Local Drive Cache:
1. Cached files are locally stored and this help performance. (debatable to some)
2. Cached files that are checked out are not backed up.
3. Local Drive failure means lost work, this also wreaks havoc on checked out files that have to be dealt with by the Admin.
4. Local drive creates some I.P. issues, tracking user actions is a little more difficult.
The alternative is to use a Network User Share.
1. Cached files are on the Network share, (may cause a performance decrease.)
2. Cached files that are checked out can be backed up with no issues.
3. User Local View should be "For them Only" not "For All Users"
4. Mobile users would need VPN or network access when not at the office.
I know of companies that do this, and they are very happy with it.
You could have a mixed environment, but be careful that the Drive letters for things like Toolbox need to be consistent if they are not managed by EPDM.
Your second option is how we typically work with PDMWorks WorkGroup. In the migration to EPDM I was considering your first option, but it's good to know that folks work in the 2nd option with EPDM and like it.