Review M-Files on G2 & get a $25 gift card Arrow right Review us!

Options
  • Locked Locked
  • Replies 7 replies
  • Subscribers 13 subscribers
  • Views 1736 views
  • Users 0 members are here
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Upgrade M-Files Client/Server 21.10 to latest version

dejan

Hi M-Files and community, 

I am slowly starting preparation of our big upgrade to latest M-Files version. I came up with some questions that I would like to ask here:

  • Unfortunately, we are on-premise without internet access, so no automatic update possible. If I just download MSI and execute it on server, will it uninstall and then install new version. We have never done it before so any guidance would useful. Or do we need to uninstall first previous version, backup everything, whole vault? What is generally the best practice?
  • I am aware of upcoming UI launch. If we upgrade now with October version, can we then just upgrade November desktop version without upgrading server? Are there any incompatibilities or breaking changes? So far, I haven't heard of any.
  • If we upgrade now our development vaults (we develop in cloud) and continue developing new features, would it be possible to export those packages (e.g. workflows, metadata cards) and import them to old vaults in on our on-premise environment which is still 21.10? Is the package structure different between versions? Does it mean we would need to first upgrade all environments and then continue with business development?
  • Looking through release list, it often happens that the latest version in unstable or introduces certain side-effects and issues. Can we download somewhere previous releases? What is generally suggestion by community, do you always go to the latest version or go to some stable one based on feature set?
  • I've read and learned in one of trainings that first clients should get rolled out and then server should be updated. Is this the best practice? What would happen if we upgrade server side and someone still has an old client? Are there issues?

Thanks for your support and best practice suggestions.

Best,

Dejan

  • Some resources for you to review:

    You don't need to (and should not) uninstall anything when doing an upgrade, the installer will upgrade the installed components in place. It's a good idea to have fresh backups taken before the upgrade just in case, though.

  • in reply to Joonas Linkola

    Thanks Joonas. Very valuable information as always. 

    I went through the most: it is good to know that update happens automatically even when manually run. I am still not clear about replication packages between versions (it is mentioned that structure changes but examples are always about version 10 and 9, do I miss something there?). 

    Also not quite sure, I understand the requirement that we need to update Compliance Kit too. As written in some other post, I have found an issue in latest Compliance Kit within Advanced Notifications. So I would not like to update Compliance Kit as this would introduce an issue back. Does it mean that older compliance it (20.10) would not work with upgraded M-Files?

    Also the licensing info is somehow misleading: do we need new license from accounting manager for new installation of M-Files or can we re-use our license? The same thing for compliance kit.

    Those are some understanding from my side. Will go through the new dekstop FAQ still.

    Best,

    Dejan

  • in reply to dejan

    Compliance Kit releases have a minimum server requirement, so upgrading to a newer server version shouldn't cause issues and you should be able to continue using the same CK release if you like. Of course upgrading CK at some point is also a good idea so you'll get the latest improvements and fixes, instructions in Upgrading M-Files Compliance Kit.

    Upgrades do not require any license changes, the same license is in use after the upgrade.

  • in reply to Joonas Linkola

    Thanks Joonas. Yes, definitely I would love to upgrade M-Files compliance kit as it has quite a few fixes for us but unfortunately it has an issue with advanced notifications using state transitions. So we needed to rollback. Good to know that we don't need to worry about licenses after upgrade. 

  • in reply to Joonas Linkola

     Thanks again for summary. Is there any info about compatibility between exported Vault packages from new M-Files (e.g. September 2022) with older version (in our case October 2021). Would we be able to import those packages on old M-Files? Based on documentation, Vault database will get updated and could be incompatible. But it is not strictly stated if this causes a problem or not. It would great to know.

  • in reply to dejan

    They may be incompatible and there may be some checks preventing an import to an older server version, I don't recall off the top of my head. If you want to be sure you should test this with the versions you mentioned.

    In any case, I think the recommended path would be

    1. Upgrade development environment to new version
    2. Test that everything is still working as expected in the dev environment
    3. Upgrade production environment to new version
    4. Continue business development after all environments are on the same version
M-Files
M-Files Support


© 2024 M-Files, All Rights Reserved.