Microsoft announced the release of the March 2014 Lync App update.
This update brings some cool new features, but I had to force the update through the Windows Store. Eventually, it showed up:
Once installed, the first thing you can see is the change in the log-in screen. Guest log-in is now below the user log-in:
Once logged in, Lync will tell you it was updated:
The first change you see is the big “Meet Now” button on the left:
As soon as you touch it – it launches a new meeting. Unfortunately, you can’t see the meeting entry info like you do with the Desktop client, but you now have the option to invite people using the people menu:
Control over participants is easier and useful:
One more nice thing is that now you have all the controls at the bottom of the screen:
Had a couple of requests this past week to set holidays for Response Groups.
I used Jamie Schwinn‘s great Lync RGS Holiday Set Editor for the first and second customer, but it started getting a little frustrating when I thought I’m going to have to do this for more customers as time goes by.
So for all of you Irish lads using Lync, here’s a script to add all the 2014 Irish holidays to Lync, with a single click.
Import this tool to your Lync server and run it using Lync management shell:
The script will ask you for your RGS’ DB server’s FQDN. Enter the name and hit Enter.
The script will complete in a second, creating all holidays for the year 2014:
You can run Get-CsRgsHolidaySet to verify the settings or use Jamie’s tool to have a better look at it:
That’s it, you even have 2015 New Year’s Day as a bonus, so you can worry about running the 2015 script around February…
* Note – This script is designed to work on EN-US Locale, as this is the default Lync Management shell locale. If you’re working with the EN-IE locale, you’ll have to switch to EN-US for this script to run ok.
Got a colleague ringing me the other day with a strange issue:
He has Lync 2013 on premises with their voicemail hosted on Office 365 Exchange online, all configured and working wonderful.
However, for some users, the “HostedVoiceMail” attribute changes from “$true” to null. If he runs the “Set-csuser –identity Domain\Username –HostedVoiceMail $true” command again it will set it, but that will disappear as soon as DirSync runs again.
Did some investigation, and apparently – If it’s a shared mailbox, DirSync will switch it back from “$true” to “null”.
There is a workaround to fix this!
Go to your DirSync server, and at the following path: “%Program Files%\Microsoft Online Directory Sync\SYNCBUS\Synchronization Service\UIShell”, or ““%Program Files%\Windows Azure Active Directory Sync\SYNCBUS\Synchronization Service\UIShell” if you’re using Azure, you will find “miisclient.exe”:
Open “miisclient.exe” and click the “Management Agents” tab:
Right-click “Source AD” and choose “Properties”:
In the new window, choose “Configure Attribute Flow”, and expand “Object Type: user”:
Under “Object Type: user” click “msExchUCVoiceMailSettings” once. At the Build Attribute Flow window below, uncheck the “Allow Nulls” box:
Click OK, and close the MIIS client.
Re-enable the user for hosted voicemail, then resync. The user’s HostedVoiceMail setting will remain unchanged.