Thursday, November 10, 2016

O365 Click to Run versions

Month
Current Release
First Release Deferred
Deferred
Jan-16
1511 (Build 6366.2062)
1509 (Build 6001.1054)
-
Feb-16
1601 (Build 6568.2025)
1509 (Build 6001.1061)
1509 (Build 6001.1061)
Mar-16
1602 (Build 6741.2021)
1602 (Build 6741.2021)
1509 (Build 6001.1068)
Apr-16
1603 (Build 6769.2040)
1602 (Build 6741.2026)
1509 (Build 6001.1073)
May-16
1604 (Build 6868.2067)
1602 (Build 6741.2042)
1509 (Build 6001.1078)
Jun-16
1605 (Build 6965.2063)
1605 (Build 6965.2063)
1602 (Build 6741.2048)
Jul-16
1606 (Build 7070.2033)
1605 (Build 6965.2069)
1602 (Build 6741.2056)
Aug-16
1607 (Build 7167.2047)
1605 (Build 6965.2076)
1602 (Build 6741.2063)
Sep-16
1608 (Build 7341.2035)
1605 (Build 6965.2084)
1602 (Build 6741.2071)
Oct-16
1609 (Build 7369.2038)
1609 (Build 7369.2038)
1605 (Build 6965.2092)
Nov-16
1609 (Build 7369.2055)
1609 (Build 7369.2055)
1605 (Build 6965.2105)
Dec-16
1611 (Build 7571.2075)
1609 (Build 7369.2095)
1605 (Build 6965.2115)
Jan-17

1609 (Build xxx)
1605 (Build xxx)
Feb-17

161x (Build xxx)
1609 (Build xxx)
Mar-17

161x (Build xxx) 
1609 (Build xxx)
Apr-17

 161x (Build xxx)
1609 (Build xxx)
May-17

 161x (Build xxx)
1609 (Build xxx)


Office 365 client update channel releases - https://technet.microsoft.com/en-
us/office/mt465751

Friday, October 14, 2016

Issues with GlobalSign public certs

What a mess!!!

If you use public certs from Globalsign, be aware of the issue that started yesterday with their CRLs.

We had to go in and update ALL our external-facing servers with the new Intermediate Cert they provided.

More details here - http://downloads.globalsign.com/acton/fs/blocks/showLandingPage/a/2674/p/p-008f/t/page/fm/0


Tips:

We use public certs on our SfB FEs too, and the same cert is also used for OAuth. We ended up removing and reapply the cert (from the SfB Wizard) so that it replicates out to the other servers and pools.

You need to remove the old Intermediate cert from the store. Search the Computer as well as the User stores and make sure you get rid of the old Intermediate one, else it will stay latched to the chain.


Can get the Intermediate cert from here -  https://support.globalsign.com/customer/portal/articles/2599710-ocsp-revocation-errors---troubleshooting-guide

Thursday, July 28, 2016

Unable to assign phone numbers to certain users on Skype for Business Online


Assigning numbers fails with "Sorry, but we couldn't save your changes. Please try again later."



Verify that:
  • Correct licenses are assigned. Need "Cloud PBX" from E5 as well as a "Calling Plan" license. If the license is correct the the users should show up in the "Voice users" view.
  • Check the Location assigned to the user. It has to match up with the “Emergency Location” when assigning the telephone number. You can find the Location in the main Admin portal where you assign licenses to users.


 
Skype for Business Admin Portal > Voice Users > Assign Number


In main O365 Admin portal > Users > Product Licenses

Wednesday, June 8, 2016

Move users to and from Lync Online


Move users to Skype for Business Online

Move-CsUser -Identity username@contoso.com -Target sipfed.online.lync.com -Credential $creds -HostedMigrationOverrideUrl <URL>

(https://technet.microsoft.com/en-us/library/jj204969.aspx)



Move users back to on-premises

Move-CsUser -Identity username@contoso.com -Target localpool.contoso.com -Credential $cred -HostedMigrationOverrideUrl <URL> -DomainController <DC>

(https://technet.microsoft.com/en-us/library/jj204967.aspx)

I found that if the "-DomainController" switch is not used then the move fails with the error - Move-CsUser : Cannot find user in Active Directory with the following SIP URI:<>










Wednesday, May 4, 2016

Skype Meeting Broadcast - You don't have permission to create meetings


Started seeing this message when creating new Broadcast meetings just out of the the blue. 



I'm not sure since when it's broken, but it did work as expected about a month ago, when I configured our hybrid setup as per this technote.

Same issue for other users in my tenant too.. so had to be something at the configuration level. There are policies that can be assigned to users, but the default global policy already makes it available for all. Hmmmm..

Long story short, I disabled and re-enabled "Set-CsBroadcastMeetingConfiguration –EnableBroadcastMeeting", and after a few hours it was working again... 



More to add to this story... turns out that sometime in Q1 this year, it was changed so that your account needs to also have a "Skype for Business" license applied to the Organizer of the Broadcast meeting. With mostly on-prem users, this was something new for us.


Bottom-line: On-prem SfB users need to have a SfB license assigned in your tenant, else they will not be able to schedule meetings. MS Technote.






Wednesday, April 13, 2016

Wednesday, February 10, 2016

Mac users not able to sign in to the Dial-in Conferencing page


After the recent in-place upgrade of the primary server pool to SfB version (the one that hosts all the simple URLs), we started getting calls from our sizable Mac user-base about not being able to login to the https://dialin.domain.com page any more.

Just the Mac clients were seeing this issue. Tested on Safari and Chrome and Firefox, and all behaved the same exact way, but the issue could not be duplicated on a Windows PC.

Can't login to the dialin page means the user can't set or update their PINs, or reset their conference IDs.

Either there was no "sign-in" link on the page, or it was replaced with a cryptic message "Cannot sign in because your Web Browser does not support the authentication method used by the server. Contact your system administrator for assistance"



Now, if the same Mac client accesses the "external" dialin page, all's well and normal. Issue only happens when the Internal dialin page is accessed (which is the default for users on the internal domain).

Called in a case with our favorite support team, and it turns out that this is a know issue ever since SfB was RTM'ed (April 2015 I believe) :-(. Something about the javascript code on the page hiding the sign-in URL if the browser does not support integrated windows authentication.

So till the product group can fix this issue the only workarounds available seem to be:

  1. Switch out the Mac's with Windows PCs (just kidding).
  2. Have Mac users login to the dialin page thru a Windows PC/ Citrix.
  3. In Safari, switch the user-agent to IE before accessing the page (need to enable Developer mode to see this option).
  4. The Internal dialin page could temporarily be redirected to reverse proxy so it can be proxied to 4443 instead.
  5. Use Powershell to set user's PINs with "Set-CsClientPin -Identity userA -Pin 1234"

 Take your pick..

Lync 2013/ Skype for Business Versions - Mac Clients


I've moved this list to a page to make it easier to maintain -> Mac Clients


Lync 2013/ Skype for Business Versions - Windows Clients


I've moved this list to a page to make it easier to maintain -> Windows clients