Dorico disappearing on campus network when installed via MECM

We use Dorico on our campus, we install it via Microsoft Endpoint Configuration Manager, we have done this for some time without issue ( other than people opening it before the licensing has completed ) - since the 4.3 update that we did over the summer, we have had a REALLY annoying problem where Dorico just disappears from the system, MECM still says its installed, because, well, it was installed. We then refresh MECM and reinstall it and it installs in seconds ( our network is reasonable, but there is no way its installing 600mb+ in that amount of time ) which leads me to believe that it isn’t in fact uninstalled ( even though it does disappear from the add remove programs and start menu etc ). We have potentially hundreds of bits of software across our estate and none of them have this issue, even CuBase which is installed at the same time remains as expected. We are really struggling to figure this out, has anyone else had this?

As an aside, is the response times for tickets for Dorico/CuBase usually in the ‘months’ kind of timeframe?

Welcome to the forum, @cgreig. I’m very sorry to hear about this problem. I will ask one of my colleagues, who knows much more about these kinds of deployment issues than I do, to get in touch to help you.

Hi, we managed to find out what the problem was - the GUID for the two verisons we had was the same, thats the ‘Globally UNIQUE Identifier’ so MECM was ensuring compliance in that if it found the old verison it would remove it and then installing the current version… only, being as it was using the GUID, every time it ran a cycle, it would either install or remove the software and being as it runs on a 90min check in, this could lead to a three hour loop so trouble shooting it was difficult.

We removed the ‘remove old version’ step from our compliance check and the problem was resolved, but the real issue is that the GUID is the same for two bits of software and not, unique as it should be.


Just thought I would update for anyone else who has this issue.

As I expect my colleagues explained to you, it’s actually important that within a given major version of the software (e.g. 4.x or 5.x) that the overall GUID for the package remains the same, so that the installer can correctly uninstall e.g. version 4.2 when you install version 4.3.

In any case, I’m glad we were able to help you resolve your issue!