Review us!
I'm aware of the issue whereby if you run your apps as published applications that you require the MFiles mfstatus process to be running and am not worried about that as we will be publishing desktops at this stage.
The queries I have though are in relation to the cache settings in the client.
- What do people assign as the local cache (do you simply make it 0 as it will never be offline from the server
- What happens if you have 0 cache? How does it work with larger documents?
- Do you automatically check in documents on close without prompt?
- What do you do in instances whereby a user logs onto different Citrix servers each day and making sure that the file they are editing is checked in and not from cache?
- If a session crashes and you need to re-login to a different server (the document checked out on a different Citrix server) (or I suppose traditionally workstation) can the user undo the checkout and continue working etc.
Has anyone tried symlinking the M-Files cache location to a central area to resolve issues with users logging onto different servers on different days (time of day)?
