It’s time for you and me to take this to the next level!

We are moving on!! And by that I would like to thank all of you who have been following my blog over the year! But its long from done with this, im just moving on!

It’s time to face new challenges and set new goals for myself. It’s not a secret that the future of IT is in the cloud and most of my work the last couple of years have been with Office 365 so I now made the decision to go “all up”!!!

The first of January I  started a new company togheter with some of the best people on this planet when it comes to Exchange, the company will be called Altitude 365.
Together we are two MVP’s, one MCSM and the best guy available for migrations from non-Microsoft platforms. Please feel free to visit our website, our Facebook page, our LinkedIn page and follow us on Twitter to find out more about us!

All content will remain on this blog but new content will be added to our new blog, please add it to you favorites our add it to your RSS reader, I can promise you a lot of great information now when we are more people writing content than just me, so you want to follow us!

Once again a big Thank you! and if you need to reach me its now for both Lync and email.

Moving from a broken Lync On-Prem to Lync Online

When moving from Lync On-prem to Lync Online there are like three or more different approaches, last week I tried one of them where my customer had lost all their Lync servers in a SAN failure.

So the mission was to get them on boarded to Lync online!
Well its just to create a tenant, add the domain, enable dirsync and it should work, right?

Well there is actually one more step to take.
When a user is enabled for Lync some attributes gets tattooed in AD, like the msRTCSIP-UserEnabled & msRTCSIP-PrimaryUserAddress for example and since these attributes has values in the on-prem AD, Lync Online will not provision these users and they will not be able to logon.

You can verify this by going to the users tab in the Lync Admin Center in the Office 365 portal. You should then see all the users that are provisioned for Lync Online there
And IF the user is not listed, make sure that he/she has a license, and if he/she still does not show up (and in the case that there has been an on-premises Lync) make sure that none of the msRTC… attributes has any values on them. They should all be cleared for the Lync Online provisioning to work.

And if you have more than five or so users that needs this clean up, there is a tool called admodify at that is super simple to use that can clean this up for you in minutes.

This tool is also perfect to use for any bulk changes that needs to be done over many different OU´s for example.

Out of band security advisory related to TIFF that could allow remote code execution #Lync #Office

Microsoft today released a out-of-band security advisory on an issue with how Office clients, Lync included handle TIFF files, this exploit could allow remote code execution and I think this is the second time that TIFF is affected in about a year if I am not mistaken.

For more information please see the official advisory from Microsoft

Microsoft Security Advisory (2896666)

There is a workaround published describing how to mitigate this by disabling the TIFF codec.

Disable the TIFF codec

Note See Microsoft Knowledge Base Article 2896666 to use the automated Microsoft Fix it solution to enable or disable this workaround.

You can prevent TIFF files from being displayed by modifying the registry to control the parsing of the TIFF codec. By changing the registry entries, you can control which images are parsed and rendered and which images are rejected in GDI+. For example, you can select to parse and render Joint Photographic Experts Group (JPEG) images, but block Tagged Image File Format (TIFF) images.

Warning: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

Note After you change a registry entry, you must restart the application that uses the codec.

To disable the TIFF codec:

  1. To add a registry entry, create the following registry subkey:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Gdiplus
  2. Create a DWORD value for the TIFF code by creating a registry entry (DWORD value) under the registry subkey you created in step 1:DisableTIFFCodec
  3. To disable the TIFF codec, set value of the DisableTIFFCodec registry entry to 1.

Impact of Workaround. You will not be able to view TIFF files.

How to undo the workaround

To re-enable the TIFF codec, set the value of the DisableTIFFCodec registry entry to 0.

#lync ama on reddit, right now

Ok it all started like 2-3 hours ago, and some 400 comments in right now.

If you are not in to reddit i suggest you check this chat out, Reddit is a site iwe been visiting more and more lately.

Come join the fun! and ask the Lync team your questions!

Hold of your updates for a minute #office365 #Lync #ADFS

Just got off the phone with the Office 365 support, (a great experience again btw)

Anyway, one of my customers had automatic updates on their ADFS servers and the latest batch kills ADFS. Where none of the users could logon this morning.
The guy I talked to had taken a lot of calls already and knew exactly where to look

So if its broken right now or soon… look at those update!


A “how to” on #Lync Mobile logs

I´m currently troubleshooting why Exchange integration wont work in Lync Mobile for Windows Phone 8, so I have spent the afternoon in the log files, and I learned some things listed here…

So lets start with the basics.

On all three of the mobile clients, WP, iOS & Android you can enable logging from the settings menu. Its off by default and needs to be turned on to collect logs.


After you enable logging, restart the application and retry what you are trying to do, then go back in to the settings menu and click on Save logs.wp_ss_20130812_0005

(the image above actually says email it across, where it should say copy )

Depending on what platform you are doing this on, the experience will differ.

On Windows Phone, when you click Save logs it will create a .JPG file. this is because there is no direct access to the “file system” on Windows Phone. But we can access some multimedia files so this is actually pretty smart.

Naturally the next step from here would be to send this jpg file in an email. Well actually NO!!!! Don’t do that, this was only possible before on Windows Phone 7.5. The reason being that the mail app compresses the images and will actually remove the logging information.


See its only 7 KB

Instead plug the USB cable in and copy the file manually and it will be a much larger file, like 3 mb larger


Now rename the extension of that file to a .log file and open it in Notepad (I actually use Notepad++)

There will be a lot of jibberish at the begging, but under that the real Lync Mobile logs are located


The iOS experience is a bit more straight forward. Again just go in to the Options \ Logging and hit the Send log Files button.

The app will then compose a email for you with the log files attached including some basic info


The Android experience is similar to that of iOS but it actually stores the logfiles in a zip file.

A funny thing is that I use Office 365 with vanilla settings and the zip file gets removed every time I try to send it from myself, to myself from an Android device so you might have to look out for that.

Well at this stage you should have received the log files and you are good to go do some trouble shooting

Some good blog posts on #Lync from the last weeks that #SummerReading

Its summer and you all got time to read. So here is a random collection of some of the last weeks great posts that the Lync MVP community has produced.

Tom Arbuthnot’s Lync’d Up Blog

Justin Morris on UC

Ken´s Unified Communications Blog

Thomas@UC (Microsoft LYNC)

And last but not least, some of my latest posts.

Ultimate Communications by Tommy Clarke


I hope u all have a great summer!!!!

Force a Office 365 ProPlus ClickToRun Update #Office365 #Lync

With the July 2013 Cumulative Update for Lync that just got released I wanted to try it out as well. There’s a lot of cool new features in it like:

  • IM Mute
  • Question and Answer capability in meetings
  • Paste photos straight into Lync
  • Meetings Tab (so you can now see your Lync meetings directly in the client)

So I went to download the update like I usually do from the Microsoft Download Center:

Microsoft Lync 2013 (32-bit)

Microsoft Lync Basic 2013 (32-bit)

Microsoft Lync 2013 (64-bit)

Microsoft Lync Basic 2013 (64-bit)

And I ran it and BOOM!!!


That message is in Swedish for some reason, but it says that there is no product installed on this computer for this update

Well, yea I remember, after I installed Windows 8.1 a couple of days ago I installed the amazing click to run version of Office Pro Plus called Office 365 ProPlus

And here’s a little info on how updates works on the Click To Run Office 365 ProPlus

By default, Click-to-Run for Office 365 installations are automatically updated. The automatic update process detects and downloads the new data in the background. The updates are installed in the background as soon as the download is completed. However, the installation may be postponed if a resource to be updated is being used by an Office application that is running. In such cases, the updates are automatically applied the next time that the application is cycled or when the application is started by the user. Administrators can turn automatic updates off.

The updates are kept as small as possible and they download only when changes are required to keep the installation up-to-date. This optimizes network bandwidth use. Updates occur only when the affected Office applications aren’t being used and they don’t require a computer restart.

Administrators can configure updates behavior by using the Configuration.xml file for Click-to-Run. The following Updates element attributes are available:

  • Enabled   If set to TRUE, Click-to-Run will automatically detect, download, and install updates. This is the default. If Enabled is set to FALSE, Office won’t check for updates and will remain at the installed version.
  • UpdatePath   Can be used to specify a network, local, or HTTP path for a Click-to-Run installation source to use for updates. If UpdatePath isn’t set, or is set to special value “default”, the Microsoft Click-to-Run source on the Internet will be used.
  • TargetVersion   Can be set to a Click-to-Run for Office 365 product build number, for example, When the version is set, Click-to-Run for Office 365 attempts to update to the specified version in the next update cycle. If TargetVersion isn’t set or is set to special value “default,” Click-to-Run for Office 365 updates to the latest version advertised at the Click-to-Run source.

For information about Configuration.xml syntax, see Reference for Click-to-Run configuration.xml file.

From <>

But I haven’t got that update so how do I force it?

It turns out t be pretty simple. Just open a Office program (other than Lync)
Then go into the settings bar for it and in Outlook click Office Account.
Once there you will see this


Simply click the Office Updates that also tells me that there actually is updates ready. Once clicked it will open a menu and then just select Update Office

There is also a “About Office updates something button” that leads to: and this page got some great info on the latest updates

When the update starts it will need to close any open Office application

Just hit close and wait 3-4 minutes…

And when its done it restarted my Office apps and I’m back to productivity


And I’m back in to Lync with those new features enabled.