Skip to main content

Posts

Showing posts from August, 2016

Looking at Cloud Licensing - Microsoft, IBM and Google

We live in interesting times and while I haven't changed jobs in years, I now do IT for several companies.  What makes this even more interesting is that some are on the IBM infrastructure, some are on Google and some are on Microsoft...   ...and of course, there's a bit of change from one to the other. I tend to get a lot of licensing-based invoices across my desk nowadays.  Recently, we shifted our IBM licensing to the new IBM Mail Dual Entitlement plan. It's basically a combined Notes and Connections licence. Since I've been doing a lot of Microsoft work for another company, I thought I might do a comparison... especially since numbers are so hard to find on the web. Note that these figures are in Australian dollars and they're probably not entirely "apples to apples" (or entirely perfect -- I've rounded) but they still make for interesting comparisons.  They're not intended to be proper comparisons.... more for interest sake. IBM $1

IBM's Cloud takes the Pain out of Updates

I’ll admit that I'm generally not very kind to IBM on this blog. It's not that they're doing a worse job than their competitors, I'm still very impressed with some of the things they're doing.  It's just that after using Notes/Domino for over 20 years, I hold them, sometimes impossibly, to very high standards…. and, of course, any goofs on their part affect my systems a little too directly. The Quiet Migration to 24x7 One of our biggest frustrations in recent years has been the understated migration of our systems from a business hours model to a 24x7 one. It's not so much that our business became so critical that it needed to go 24 hour but more that changes in mobility and connectivity mean that people now expect to be able to connect to our systems at any time, anywhere. Almost imperceptibly, we quietly moved to a "zero tolerance for downtime" model. IT changed to suit the business needs in this regard but the change itself and the i

What's Wrong with the IBM Connections.Cloud Welcome Message (and what IBM Needs to do to fix it)

One of the interesting things about being in IT is that you're responsible for hundreds of "automated" messages each day but... as an IT person, who was already set up on the system from day one, you never actually get to see them - at least, not until someone complains. One of the things we do at work is provide an area on IBM Connections.Cloud for parties external to our own organisation to collaborate. The collaboration in this space is with some pretty important people.  Recently we had our "communications" staff member express unhappiness about the IBM Connections welcome message which went to the CEO of a large institution. I've been sitting on it for a while wondering how to explain this to IBM but today I read a great article on welcome messages .  I figured that blogging might be the best way to explain the problem. The Message So, without further ado, here is the message (which apart from 5 words) is entirely created by IBM. See if you

Good Resources for Support with IBM Connections and Verse 2: Official Channel Web Sites

A couple of posts ago, I provided a list of LinkedIn Groups which I've found to be good sources of IBM Connections Information.  In this post, I aim to provide some "Official" web sites.  Needless to say, the majority of these will be IBM resources.  Of course, there are lots of great personal blogs out there too but I'll cover them in a different post. The Three Big Questions for "Developing Products & Services" IBM Connections (and specifically Connections.cloud) is a "developing product/service". As such there are always new holes, new fixes and new ideas.  There's always just that little bit of functionality which either doesn't work as expected or doesn't go as far as it could.  That's not to say that IBM Connections is a bad product, simply that like all "developing products/services" (indeed, like all Modern Products & Services) the ground is constantly moving and sometimes you need to stop an