Status of checked out files when upgrading

[Bluesky2010]

Could anyone advise what occurs to files that are checked out by people under vault, and then said versions of Vault + the client side server are upgraded to 5.X? We have just purchased some new licenses for Vault 5.0, and are eligible for a free upgrade from our previous version. However there are some issues we are having at one of locations, with staff who use Vault Eclipse saying they will take several days to check in all the items they have checked out. (the majority of the company use PC's, but a couple of people use MAC's)

If I update the server with the latest vault version, and update vault on everyones computer when they still have files checked out-do the files correctly remain showing as being checked out or not? And is there any way with vault Eclipse to mass check in all files?

[lbauer]

The checkout status is stored in the database so upgrading should not affect files that are checked out.
If you have concerns about upgrading while files are checked out, uses could backup their working directories just in case.

If you don't want files checked out, users can checkin files or undo the checkouts, leaving any modified versions intact.

Also, the Admin can undo the checkouts in the Vault Admin Web Client. This setting is in the Admin Web Client under Source Control Repositories->(Repository name)->Undo Checkout.