Connect 2014: Domino Onboarding Manager

February 13, 2014

A feature in an imminent release of Domino was kinda/sorta announced at the Opening General Session. It was at the “What’s New in Domino” session where more information was shared. However, slides are not available for that session on the Connect site. Pity.

Not to worry, dear readers. You download have a rather small PDF of Domino Onboarding Manager right here (see below).

What is Domino OnBoarding Manager?

A tool which can migrate users/groups from Active Directory to Domino and emails/calendars/contacts from Exchange/Outlook to Domino/Notes.

FINALLY . . . we have a tool that will assist in the migration of Exchange/Outlook users to Notes/Domino. Perfect for those organizations that need to migrate recent acquisitions into their Domino environment. Perfect for anyone else that needs to perform a migration. Perfect for allaying the naysayers concerning the future of Notes and Domino.

Enjoy. DominoOnboardingManager presentation


Connect 2014: My Thoughts

February 12, 2014

Connect2014Banner

 

Unlike previous years, it has taken me longer to process what I saw and heard at Connect in order to have an opinion of the conference. Until now, when asked, “How was the conference?” I answered “good.” It was all I had.

Now, I have a better answer.

“Transitional.”

I believe that you have to be in denial to not get the overall direction IBM is taking with this conference and their products. Last year, it was, for the most part, the same as in previous years. It was if IBM was gently placing their toes in the seas of change.

Not so this year.

This year, unless you were “all in” with Connections, WebSphere, and Sametime, there was very little problem scheduling sessions to meet your needs. Oh, there were Notes/Domino/XPages sessions, but the first two were in, IMHO, in short supply. Development (that’s XPages )? Yeah, those were there, but hold no interest for an Administrator like myself. Except in AdminBlast where I learn how to turn off that feature. 🙂

I am very fortunate.

First, I was able to attend Connect with friend and colleague Barb Skedel. Together, we were able to split appropriate sessions, eliminating the whole “which session should I attend at this time” conundrum. Talk about stress relief.

Second, and most importantly, I accepted a full-time position with a company that is installing and implementing Connections, WebSphere, and Sametime. Unlike past years, where I was totally focused on Notes and Domino, this year I transitioned to every appropriate session for those areas. And, if it wasn’t for Barb, I would have been very upset at missing several key sessions. This was for me, a conference exactly like the ones in the past. Full of technical content on software that I use on a daily basis; Connections, Sametime, WebSphere, and Docs. Even as an administrator, you would find me in every “Customizing Connections” session that was available. And I understood exactly what the speakers were presenting and demoing. Isn’t that scary?

That should give you all you need to know about my present and future.

Notes and Domino? Of course, they are my foundation and in my future. However, this conference, in those areas, is no longer the “must attend” event if you’re an administrator. [Author disclaimer: I am not disparaging those attendees or presenters who came to Orlando and spent their time and money on those sessions. Honestly, take a look at the sessions again and tell me that Connect is for you]. Take another look at MailNext. While IBM keeps telling us that it runs on Domino, most, if not all, of the features coming in that product will require a Connections environment in order to take full advantage of those features. And if they don’t with the first iteration, they most certainly will with subsequent releases.

From my standpoint, that is a good thing. I want mail to integrate with Connections. Myself and my teammates have spent a lot of time getting Connections up and running and I want to leverage that investment as much as I can. Because if it integrates with Connections, then everyone will be using Connections, whether they know it or not.

Win-win.

I was not at all disappointed in this conference; Connect hits everything that I am now and will be. If I were a Domino administrator, I don’t think that this conference would be for me. In fact, I would never return. There isn’t enough content to make the conference worth the time or money (seeing my friends, that is another matter entirely. I would still “attend,” I would fly down on Thursday or Friday, stay the weekend, and fly home on Sunday night). Domino development? I really don’t know enough about Domino development to make a judgement.

You can sling all the “IBM says” and “IBM is committed to” statements you want about Notes and Domino. I firmly believe that Notes and Domino are a cash cow for IBM, and is treated as such:

Since the business unit can maintain profits with little maintenance or investment, a cash cow can also be used to describe a profitable but complacent company or business unit.

The place where IBM wants you to go, is exactly where I am going. And I feel fine.

One of the side benefits to attending Connections/Sametime/WebSphere/Doc sessions is that everyone was a new speaker to me. One of the side benefits of not attending Notes and Domino sessions was that I did not have to see the same speakers I’ve seen at more Lotuspheres/Connects that I care to admit. Oh, there is no doubt that they are very good, excellent, in fact, however I’d like to see some new people present. No, I’ll go even further; I’d like to see all new speakers in every Domino session (administrator and developer). Don’t you think that seeing the same people present at the same conference year in and year out is getting tiresome? Want to not have my thought come as a shock to the system? Try this: co-present with the person that will replace you. Then, the following year, take a seat in the audience while your protégé runs the show.

While I wait for that, I’ll just continue to support the regional User Group conferences to see new speakers and topics.

I’ve transitioned from a Notes/Domino Administrator to a Connections/WebSphere/Sametime/Docs Administrator and quasi-developer (you need to customize Connections, after all). Lotusphere transitioned from Notes and Domino to Connect and Connections, Sametime, WebSphere, and Docs. Connect 2014 was exactly what I expected and wanted from IBM.  Even in the labs, with the exception of the MailNext in theDesign Lab, I spent all of my other time with the Connections, Sametime, and Docs people. I didn’t even stop by the Notes/Domino pedestals. Even in the Product Showcase, most of my time was with vendors who are investing in and developing applications for Connections and Sametime.

Like I said, “transitional.”


How is winmail.dat my problem?

December 10, 2012

Misconfigured Outlook clients used to be the bane of my existance. And, occasionally can still be, in 2012. Which is pretty astounding, when you think about it.

The background is pretty simple, really. Outlook clients send e-mail using a Microsoft proprietary format, which certainly isn’t MIME. That is pretty amazing that someone thought that everyone, everywhere, would use Outlook to send mail to other Outlook users.

Try explaining to a customer that those files aren’t a Notes/Domino problem Sure, they understand,  but they want them to go away. So, it becomes my problem.

Thankfully, there are two notes.ini settings that you can apply to your SMTP server. Or server’s. Whatever the case may be.

Open the Domino Administrator. Go to the Servers tab, click on Server Console.

Enter “set config TNEFEnableConversion=1” then click either Send or hit enter.

Enter “set config TNEFKeepAttachments=1” then click either Send or hit enter.

To enable the setting to take effect immediately, enter “tell router update config” then click either Send or hit enter.

There, now someone else’s problem has been resolved on your servers. You’re welcome.

Here is a handy TechNote that explains the cause and resolution in a little more detail.

This behavior is due to messages being sent from Exchange without MIME encoding turned on. Winmail.dat is attached to the message in uuencoded format. Information on how to prevent winmail data being sent to Internet users from MS Exchange is documented and publicly available from the Microsoft Support Web page, in the Microsoft Knowledge Base, article number Q138053