Sage News and Discussion

Isolated. Uh huh...

I wonder if we would have received a notice if half a dozen people hadn't quickly noted on LinkedIn that they too were receiving bad unlock keys....

Sage is starting to sound like communications from my Congressman and Senators, which usually make me wonder ""Are you really that stupid or do you just think we are?

What's starting to be odd is that Sage isn't getting out ahead of these types of issues. They're almost entirely reactive -- as if everyone at Sage is afraid of being the first one to stand up and make a statement.

It definitely seems like the only recognition being passed around there is blame and punishment.

They don't have the funding (or other resources) to be proactive. Let's face it, the resellers (as much as they won't admit it) are the early warning beta testers now.

Getting new keys for v4.50 generated and I told the tech guy I had seen the memo. He just wanted to make sure I was aware of the issue.

Erica mentioned this on Wayne's LinkedIn post about this. Several people after that said it wasn't just since Atlas but has been happening for quite a while. Personally, I am hesitant to use new keys for add-ons, etc...

Lesson learned: Just wishing it were so does not make it so...