Archive for July, 2015

Skype for Business Server – Assign User policies to AD groups

A good AD tool to change Lync/SFB user policies based on group memberships. The script is written by Yoav Barzilay and Guy Bachar. Please look at their blogs at and
Ett mycket bra AD verktyg för att ändra Lync användares policies som styr olika delar av Lyncs funktioner.
Scriptet är gjort av Yoav Barzilay och Guy Bachar. se på deras bloggar på and

y0av. With a zero.

This is an update to a previous version of this tool written by myself and Guy Bachar.
The updated version can now run (and was tested!) on both Lync server 2010 and 2013, and Skype for Business Server.

Run this tool from Lync Management Shell or Skype for Business Management Shell.

Note you will need to run this tool with Local Admin permissions (You will be prompted for elevation automatically if not) and you must have ADDS RSAT installed so you can use the Active Directory PowerShell Module.
You will be asked to provide an Active Directory Group name. Type the Display Name of the group, the tool will reply with the CN of the group, confirming you chose the right group:

Choose Group

Then choose the type of policy (or dial plan) you want to assign this group, there are 14 options:
1     Voice Policy
2     Client Policy
3     External Access Policy

View original post 121 more words

Categories: Uncategorized

What did the July 2015 update for Lync 2013 and Skype for Business fix?

y0av. With a zero.

  • CPU usage is reduced when emoticon animations are active in multiple conversations in Skype for Business or Lync 2013:
    Occurs when you send or receive emoticon animations. The emoticons keep animating, and that overuses CPU resources.
  • Add the click-to-call feature for RCC-enabled users from the contact card in Skype for Business or Lync 2013:
    If you enabled remote call control (RCC) for an account in Microsoft Lync 2013 or in Microsoft Outlook 2013,  the phone number hyperlink of the contact is not clickable.
  • Active Directory contact’s name is changed to the phone number in the contact list of Skype for Business or Lync 2013:
    Occurs when a contact has no email or SIP address and only has a display name and a phone number in Active Directory.
  • Typed characters take a long time to display in the message input box in Skype for Business or Lync 2013:

View original post 92 more words

Categories: Uncategorized

Server 2012 or 2012R2 Blue Screen when installing Skype for Business or Lync Servers

y0av. With a zero.

Published earlier by Microsoft, a Stop error D1 when will occur when you start front-end services on Skype for Business Server 2015-based servers. This will also affect Microsoft Lync Server 2013 Enterprise Edition pools that have at least two front-end servers in Windows Server 2012. This will mostly impact organizations that will perform an in-place upgrade to Skype for Business Server 2015.

This is due to a bug on in Windows Server 2012 and Windows Server 2012 R2. The trigger is a TDI filter driver on the machine that may be used by some antivirus and VPN software.

To resolve this issue for Windows Server 2012 you will need to install the hotfix described in KB2957927 on all Lync 2013 Servers that are installed on Windows Server 2012.

Do determine if you have such a driver installed on your system, look for event 16001 on your system log.
A faster way of finding…

View original post 24 more words

Categories: Uncategorized

Managing Private Numbers in Skype for Business Server 2015

y0av. With a zero.

Private numbers are a great thing. They can be used as various scenarios where a person needs a direct private line that’s not published in the contact card and isn’t displayed when you dial out. This is not to be mistaken for Response Groups Agent Anonymity, where agents can call on behalf of themselves or on behalf of the Response Group’s number.

Incoming Private Call notification

What’s the difference?
Well, first, you can only manage Private Lines via PowerShell. Use the Set-CsUser -PrivateLine cmdlet to assign a user with a private line. When you’ll run the Get-CsUser cmdlet against that user you’ll get everything… Except for the user’s private number. We must use the explicit Get-CsUser | fl -PrivateLine cmdlet to get the user’s private number:

PS C:Windowssystem32> get-csuser yoav.barzilay@y0av.local | fl

Identity : CN=Yoav Barzilay,OU=Users,DC=y0av,DC=local
VoicePolicy : Non Restricted
VoiceRoutingPolicy :
ConferencingPolicy : Allowed
PresencePolicy :
DialPlan :
LocationPolicy :

View original post 450 more words

Categories: Uncategorized
%d bloggers like this: