Re: Been there, avoided that.
Something that got lost in the story (or perhaps readers simply missed it)...
This outage affected CLIENT-SIDE installed software -- not online services. Just like Microsoft's products, Sage 50 Financials requires a serial number during install. The client software then sends that serial number along with a hardware signature to Sage's activation servers. Because those servers went offline, all new installs and upgrades failed.
I am the IT consultant mentioned in the story. My client purchased 5 additional user licenses. When I added the new serial number to their terminal server, activation failed and the entire package went tits up. The truly painful part is that Sage North America sold my client the license AFTER their registration servers were already down. Had they warned us -- or better yet delayed shipping the serial number -- we could have avoided this outage entirely.