Woke up to panicky emails from three customers, who had just received this via Deluxe:
image.png
Firstly, as far as I'm aware, there was never a publicly released 3.5.21: 3.5.20 was followed by 3.21.7. In any case, Dolby have been stating for about the last year that 3.5.20 (not 21) is the earliest safe version for the IMS3000. So this bulletin induced a (metaphorical) heart attack in a customer that I'd left on 3.5.20, because 3.21.7 introduces aggressive and persistent nag banners if non-Dolby approved RAID drives are installed, and this customer had installed 4TB WD Red SSDs for extra space (which have now been running for almost three years without problem or issue). None of the critical issues fixed in 3.21.7 were relevant to this site, which I'd therefore left on 3.5.20. So the guy there saw 3.5.21 as being the earliest version that won't brick his IMS3000, and went straight to DefCon 5.
Secondly, what is "Dolby DSS servers are unaffected as their certificates don't begin expiring in 2031" supposed to mean? The only thing I can think of that it could mean is that this document wasn't properly proof read before being approved for release. I wouldn't be surprised to receive approaches from DSS operators asking if they need to take action now.
It's been tough enough negotiating the confusion and fear that built up within the customer base around this "update or brick" issue, and now we're going to have even more of it to contend with, including fielding inquiries from customers whose equipment is now safe. Grrr....
image.png
Firstly, as far as I'm aware, there was never a publicly released 3.5.21: 3.5.20 was followed by 3.21.7. In any case, Dolby have been stating for about the last year that 3.5.20 (not 21) is the earliest safe version for the IMS3000. So this bulletin induced a (metaphorical) heart attack in a customer that I'd left on 3.5.20, because 3.21.7 introduces aggressive and persistent nag banners if non-Dolby approved RAID drives are installed, and this customer had installed 4TB WD Red SSDs for extra space (which have now been running for almost three years without problem or issue). None of the critical issues fixed in 3.21.7 were relevant to this site, which I'd therefore left on 3.5.20. So the guy there saw 3.5.21 as being the earliest version that won't brick his IMS3000, and went straight to DefCon 5.
Secondly, what is "Dolby DSS servers are unaffected as their certificates don't begin expiring in 2031" supposed to mean? The only thing I can think of that it could mean is that this document wasn't properly proof read before being approved for release. I wouldn't be surprised to receive approaches from DSS operators asking if they need to take action now.
It's been tough enough negotiating the confusion and fear that built up within the customer base around this "update or brick" issue, and now we're going to have even more of it to contend with, including fielding inquiries from customers whose equipment is now safe. Grrr....
Comment