I recently started with a new fabrication company and am the only designer. They had just been privately acquired. When the company was part of an umbrella corporation, they used the vault server/client set up but now there's no more Vault server..
so would it be safe to uninstall the Vault client, and would this solve the problem of dealing with checked out files from previous designers?
what happened to all the files on the Vault Server? All the latest versions will have been on there, unless they were all checked out to your machine first. In which case you wouldn't have the problem of them being checked out by other users.
I think you need to provide some more detail before we can offer a more detailed response.
Also do you have prior experience with Vault before arriving at your new job?
Uninstalling of Vault Client will NOT auto check-in/revert the files.
As Scott highlighted, you may wish to give us more details...
My issue is similar. In my company I am the only one who is using vault, and now we have decided to stop using vault. I am using Vault 2011 with inventor 2011. Vault server is separate and vault client is installed on my computer. Can you please suggest how can I stop using vault.
I tried by checking out files and then checking back in with keeping a copy on my machine. Then I copied all files to new project which is out of vault. I am able to open files even when I am in different project ( and not vault), but I am not able to make any change in files as all files are read only. Please suggest what to do
Sorry to learn that you are discontinueing with vault. Would you please share with us the main concerns/decision of making this decision?
Meanwhile, should you want to work on those files (outside of Vault context), you may simply change the files read/write property, steps follow:
i. Via Window Exporer, navigate to the file
ii. RMB (right click) the file > Property > General Tab >
iii. UNCHECKED the 'read-only' checkbox.
Alternatively, you may do that for the entire folder, and apply the changes to all the files/subfolders underneath.
Cautious: Seeing that you're toggling the read/write state of these files, you might face synchronise/merging issue when checking in those files back to vault. I'm assuming that you will NOT need to work on those files back in vault again.
Hope it helps.