Sunday, May 24, 2015

May 2015 - New or updated KB articles for Lync and SfB



Saturday, May 23, 2015

Starting and shutting down Lync services using Powershell


The "Disable/Enable all Lync services" ones are especially helpful when the OS will need to be restarted a couple of times, and you don't want to deal with the hassle of waiting for the Pool/Windows Fabric to settle down first.


Get status - Get-Service | ? {$_.displayname –like “*Lync Server*”} | select status,displayname

Start all Lync services - Start-CSWindowsService

Stop all Lync services - Stop-CsWindowsService -Graceful

Disable all Lync services - Get-Service | ? {$_.displayname –like “*Lync Server*”} | Set-Service -StartupType disabled

Enable all Lync services - Get-Service | ? {$_.displayname –like “*Lync Server*”} | Set-Service -StartupType Automatic

Friday, May 1, 2015

SfB uses SQL express 2014

Interesting find: Skype for Business installs SQL Express 2014 on the FE servers.


Hmmm...wonder if that was to support WinFab v3 ...


Lync for Mac 2011 - No Delegate support

Symptom:  Lync for Mac 2011 | Delegates not able to see delegators or manage Lync meetings in Lync for Mac 2011.

Cause:  Delegate functionality is not currently present and supported in Lync for Mac 2011.  Delegator (add delegate) functionality is only delegate/delegator functionality currently supported.


Storage Service had an EWS Autodiscovery failure - ErrorIncorrectExchangeServerVersion

These events can be ignored if you have Exchange 2010.

Log Name:      Lync Server
Source:        LS Storage Service
Event ID:      32054
Task Category: (4006)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      FE03.domain.com
Description:
Storage Service had an EWS Autodiscovery failure.

UnsupportedStoreException: code=ErrorIncorrectExchangeServerVersion, reason=GetUserSettings failed, smtpAddress=User2@domain.com, Autodiscover Uri=https://autodiscover.domain.com/autodiscover/autodiscover.svc, Autodiscover WebProxy=<NULL> ---> Microsoft.Exchange.WebServices.Data.ServiceRequestException: The request failed. The remote server returned an error: (401) Unauthorized. ---> System.Net.WebException: The remote server returned an error: (401) Unauthorized.
   at System.Net.HttpWebRequest.GetResponse()
   at Microsoft.Exchange.WebServices.Data.EwsHttpWebRequest.Microsoft.Exchange.WebServices.Data.IEwsHttpWebRequest.GetResponse()
   at Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverRequest.InternalExecute()
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverRequest.InternalExecute()
   at Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverService.InternalGetUserSettings(List`1 smtpAddresses, List`1 settings, Nullable`1 requestedVersion, Uri& autodiscoverUrl)
   at Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverService.GetSettings[TGetSettingsResponseCollection,TSettingName](List`1 identities, List`1 settings, Nullable`1 requestedVersion, GetSettingsMethod`2 getSettingsMethod, Func`1 getDomainMethod)
   at Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverService.GetUserSettings(List`1 smtpAddresses, List`1 settings)
   at Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverService.InternalGetSoapUserSettings(String smtpAddress, List`1 requestedSettings)
   at Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverService.GetUserSettings(String userSmtpAddress, UserSettingName[] userSettingNames)
   at Microsoft.Rtc.Internal.Storage.Exchange.ExchangeContext.SendGetUserSettingsRequest(StoreContext ctx, String smtpAddress)
   --- End of inner exception stack trace ---
   at Microsoft.Rtc.Internal.Storage.Exchange.ExchangeContext.SendGetUserSettingsRequest(StoreContext ctx, String smtpAddress)
   at Microsoft.Rtc.Internal.Storage.Exchange.ExchangeContext.GetUserEwsSettings(StoreContext ctx, String smtpAddress, CacheMode cacheMode)

Cause: Autodiscovery Uri was not correctly configured or unreachable, that there is a problem with the Proxy, or other errors.
Resolution:
Check event details.  Check autodiscovery Uri is properly configured and reachable. Check that proxy setting is properly configured and reachable.  Validate Skype for Business to Exchange Autodiscovery configuration by following the trouble shooting guide. If problem persists, notify your organization's support team with the event details.