Microsoft Office 2011 and the Me contact
If you deploy Microsoft Office 2011 from a central repository and have your macbooks/mini’s/imac enrolled in Active Directory, you may find some puzzling results when your users send you emails.
When a new user signs into the macbook with his Active Directory credentials, his account is created on the fly (assuming you’ve deployed your topology to do so). At the same time your Outlook 2011 profile will set itself up with your email address, and providing your Exchange DNS records are configured correctly, all server addressing will be configured on the fly.
So, here’s the scenario, new (to the macbook) user signs into Outlook, all appears well, his mail is there, contacts etc. He or she sends an email to colleagues who receive an emails where the From: field appears fine, as in it shows their name.
However when you reply, you notice that the To: field derives a ‘Microsoft Office User’ preface to the full email address.
You get a result that looks like this:
From: Luke Darby <Luke@lukedarby.co.uk>
Date: Fri, 13 Jan 2012 16:24:11 +0000
To: Microsoft Office User <lukedarby@lukedarby.co.uk>
Subject: RE: I have a name you know!
Initially this was a huge issue for us as it seemed to be linked to the “This product is licenced to” field. In short, it’s not directly related, but indirect.
Outlook 2011 creates a contact for you when you first create a profile, called ‘Me’ If it doesn’t have all information available, it uses your email address and the licences to field. In Essence you get a ‘Me’ contact which has ‘Microsoft Office User’ as the contact First and Last Name and your Work E-mail completed with your primary SMTP alias.
Me contact
You find this contact by clicking on Contacts -> Organize -> Me
Outlook Me contact
Once in there, you can manually complete the details you want, OR….
Scroll down and you should see your AD Directory contact detail. A handy ‘Update Contact’ button is provided for convenience to fill all the fields for you.
Once done, restart Outlook for good measure and you won’t see the issue again. It’s annoying, but simple to solve, and the user can do it themselves.
If you gave the bulk distribution licences to name as something else, then you’ll need to change THAT name in your Me contact.
Communicator 2011 13.1.2 Release – Lion patch at last
As many of you who have upgraded to Lion in either beta, GM (Gold Master seed) or the release version will know, if you were/are running Communicator 2011 and patched it under Snow Leopard to anything other than 13.0.0 (release version) then you’ll know it crashes as soon as you message someone (or they message you) once you were running Lion.
The ‘solution’ to this was to roll back to 13.0.0 which is pretty messy to be honest, and with Lion having been around for a while most of us expected the patch to have followed the release VERY closely.
Anyway, all that said, Microsoft have released the patch, download it here.
However take note of the kb, pre reqs:Before you install the Communicator 2011 13.1.2 Update, make sure that the computer is running Mac OS X v10.5.8 or a later version of the Mac OS X operating system.
In other words, if you’re running the pre-release, GM or the full release, AND have regressed your Communicator 2011 install to 13.0.0 then the upgrade won’t work. A neat guideline is that if Microsoft Autoupdate doesn’t ‘find’ it, then you’ll get an install error like this
Thanks for the image Nick!
This is pre-release btw. To resolve this error make sure you install the ‘broken’ 13.1.x version update first, THEN the patch will install.
This is made clear in the KB : Additionally, you must install Microsoft Communicator for Mac 13.1.0 Update or a later update before you install the Communicator for Mac 13.1.2 Update.
Successful install of Communicator2011-13.1.2
So to recap, the patch will install on pretty much any version of Lion or Snow Leopard(tested), but you must have patched Communicator to 13.1.0 minimum for it to install. If you regressed your install to 13.0.0, then patch it again, THEN install 13.1.2. Easy way to do this is let AutoUpdate work for you.
Anyway good news for a lot of folk who have put their money into Communicator/Lync etc, justifying the spend on these products is tough enough without having to explain to CEO’s that you’re waiting for a patch and have to roll them back to an inferior version (no screen share, EDGE etc)
Oh and connecting via EDGE … If you’re running Snow Leopard it still works with 13.1.2… Currently testing it on Lion, I’ve had 2 successes and 1 fail, so far I’m going with it still works! good news.
I know it’s life on the leading edge, but still, come on Microsoft, keep up!
Latest Jetstress Field Guide
I’ve always relied on JetStress to gain confidence in any new Exchange infrastructure I build. It gives you good loading feedback and is great for benchmarking disk I/O and IOPS.
http://gallery.technet.microsoft.com/Jetstress-Field-Guide-1602d64c
According to the Exchange Team, the highlights are:
Updated for version 14.01.225.017 of Jetstress
Added Exchange Server 2003 instructions
Added more troubleshooting information
Added guidance for running Jetstress on a production Exchange Server
Included guidance for testing Raid Arrays
Included information and guidance on Background Database Maintenance
General corrections and clarity improvements
If you’re building or are about to build an Exchange setup, it’ worth a good read. Use it.
Office for Mac 2011 14.1 Update
SP1 for Office 2011 was released on the 12th April(12/04/2011), today was my first moment to give it a look over.
The main thing I was after was the addition of Exchange server side rule manipulation. I’ve had a few questions about this from fellow members of staff, they adopted Outlook for Mac to replace Entourage or Mail.App etc and have had to keep a Windows Outlook session on hand to manipulate rules.
I went straight to the rules section, and got this:
Looks like I’ll jhave to press on with that Exchange 2010 upgrade! 1 step forward, 2 back.
Another addition is the ability to resend a mail, so far it was a faff, having to either forward/reply your mail and edit the content and subject line accordingly to make it look like a fresh mail. The ‘Resend’ option is now available on the Message menu and the right-click context menu.
For more detail on what fixes are in the service pack, look here. To download the file, it’s here
I’ve not paid too much attention to what is updated in Word, Powerpoint and Excel, I’m a pretty basic user of them all, so long as spell check and SUM work, I’m pretty covered 
.
Cisco UC Product Tour
I had an interesting trip to see our friends at Cisco HQ (UK) today. It was a multi-purposed session to discuss a multitude of UC subjects.
We’re busy embarking on a Cisco Unity Connection install, to replace our old Unity 4.X installation. We’ve made a few test builds, but that’s largely been to get comfortable with the install process. We wanted to see some of the technology in action, hear some of the marketing and also get an informed demonstration.
Unity Connection: Features like Visual Voicemail and its ability to store voicemail ‘offbox’ in Exchange are what have attracted us. It’s an interesting way to achieve Unified Messaging without incurring the expensive Microsoft licencing costs. I like that unlike Unity, Unity Connection is now a linux appliance, it’s AD integration isn’t some masked Exchange 2003 installation. The only aspect I am currently not impressed by is the personal contacts feature, it’s a manual upload of contacts, with limited fields. It’s not dynamic at all, not linked to Exchange, it’s a one time import via a web portal.
Jabber: Cisco have started to combine open standards based XMPP technology obtained through the Jabber acquisition. This is being integrated into the WebEx and CUPS and CUPC products. There are ‘Cisco Jabber’ applications available for the Android and Apple platforms, and lots of work in progress to bring in more features towards the end of the year. Blackberry solutions require MVS which is essentially some glue to get it to work under the RIM framework. It creates a SIP trunk into CM, to enable you to use your mobile to make calls via CM trunks.
Cisco Quad: A very interesting product, I’m sure there are many ways to describe it and frame what it is, but it’s essentially a fully fledged ‘corporate-facebook-intranet-in-a-box’ That somewhat undersells it, a recent piece of work has seen our company develop its own intranet with social collaboration in mind, this has met with mediocre success. The Quad product would have pretty much full-filled all the technical needs for us in a turn-key solution. I’m not saying it’s all things to all men, but I was suitable impressed. As a social collaboration suite, it tops my interested list. There are Android, iPad and iPhone applications available for Quad.
Cisco CUPS: I’ve known about CUPS for ages, but it’s always been this monstrously huge product, that was a sledge hammer to crack a nut. It always felt expensive and cumbersome. I’ve no doubt it’s still quite a challenging install, but it’s mediation/federation offering to lash together CUCM and OCS/Lync that mean I will definitely be looking it over again now. The CUPC client is also much improved and is very polished. It has become a very polished and attractive product. The product was re-written with the Jabber technology and is now open standards based. Federation will be achieved using XMPP. Version 8.5.
Show and Share: I’d describe it as corporate YouTube. It enables users to share and collaborate with video/media rich content, tagging and making video content searchable. You can record a piece via a video enabled device and with 1 click publish it as online content. Also known as Cisco Digital Media Manager.
Video Conferencing (Telepresence): Cisco has done a lot of work integrating the Tandberg end points into their product range. I was impressed with the speed that this integration seems to have happened.
Luke Darby
Technology Infrastructure | Media | Communication | Broadcasting
United Kingdom
