Powershell

Enable-TeamsDRUsers GUI At the time of writing it’s not possible to enable Teams Direct Routing users via Teams Admin Center, only via PowerShell commands. This PowerShell script launches a WinForms GUI that can be used by anyone. This is useful for enabling or making changes to a couple of Teams DR users. Requirements - Microsoft Teams PowerShell module 2.0 or above - Teams Administrative Rights (Teams Service/Communications Administrator + Skype for Business Administrator) - Users must have a Phone System license ...

The Public Preview and Beta modules are useful for testing new features, i.e. managing Private Channel users (Get-TeamChannelUser, Add-TeamChannelUser etc) Installing Beta Module Microsoft documentation used to point you to the poshtestgallery.com to get the module. This has now been replaced by the Preview Module however some MS documentation (i.e. Get-TeamChannelUser) still references Posh Test Gallery. Get-TeamChannelUser advises to use PoshTestGallery. PoshTestGallery.com If you try to install a module from Posh Test Gallery you will get the following error: ...

You may notice that your Skype for Business Front End server consumes a lot of disk space and the culprit will either be: C:\ProgramData\Windows Fabric\Log (SfB 2015) or C:\ProgramData\Microsoft\SF\Log (SfB 2019) This is caused by Windows Fabric log growth and can be rectified by either: Increase disk space Limit how long Fabric Logs are kept (default 3 days) This post shows how to do option 2 manually in SfB 2015: https://myhybridsetup.org/skype-for-business-2015-limit-fabric-tracing-logs-growth/ ...

When connecting to Microsoft Teams or Skype Online ( https://docs.microsoft.com/en-us/office365/enterprise/powershell/manage-skype-for-business-online-with-office-365-powershell) you may experience the following error: Unable to discover PowerShell endpoint URI At C:\Program Files\Common Files\Skype for Business Online\Modules\SkypeOnlineConnector\SkypeOnlineConnectorStartup.psm1:114 char:9 + throw $resources.DiscoveringEndpointFail + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : OperationStopped: (Unable to disco...ll endpoint URI:String) [], RuntimeException + FullyQualifiedErrorId : Unable to discover PowerShell endpoint URI This occurs when your Office 365 Admin Account is not an onmicrosoft.com account. To resolve you need to specify the -OverrideAdminDomain switch on New-CsOnlineSession and specify your default O365 onmicrosoft domain. E.g: ...

Note this script is provided as an example only - By default a user can set their own Client Pin via the Dial-In Conferencing page (usually dialin.domain.com). You may have a requirement to bulk set a Client Pin if you’re rolling out a large number of VOIP phones. The script example below sets a 6 digit client PIN consisting of a two digit prefix followed by the last 4 digits of the users LineUri: ...

Every Lync/Skype admin has the same nightmare with Response Group Holiday sets, something that has to manually be programmed each year for Public Holidays in your country. What if you could script populating Holiday Sets automatically using PowerShell and an API? I live in England and most of my customers are UK based so I needed a service that would give me Public Holidays for the UK. Our government website lists all Public Holidays here: https://www.gov.uk/bank-holidays. They are also conveniently provided in JSON format here: https://www.gov.uk/bank-holidays.json ...

During a side-by-side Lync 2013 to Skype for Business migration I encountered an error moving Response Groups using Move-CsRgsConfiguration. Move-CsRgsConfiguration -Source lyncfepool.domain.local -Destination skypefepool.domain.local This resulted in the error “Move-CsRgsConfiguration : Object reference not set to an instance of an object.”. To resolve I ran Move-CsRgsConfiguration again with the -verbose switch: Move-CsRgsConfiguration -Source lyncfepool.domain.local -Destination skypefepool.domain.local -verbose Verbose output below: VERBOSE: Performing the operation "Move-CsRgsConfiguration" on target "service:ApplicationServer:skypefepool.domain.local/531286fe-e965-4c1c-9949-26eca4d8d3db". VERBOSE: Handle audio files... VERBOSE: Update associations with holiday sets... VERBOSE: Update associations with managers... Move-CsRgsConfiguration : Object reference not set to an instance of an object. At line:1 char:1 + Move-CsRgsConfiguration -Source lyncfepool.domain.local -Destination skyp ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : WriteError: (Microsoft.Rtc.R...lRgsDataContext:TransactionalRgsDataContext) [Move-CsRgsC onfiguration], NullReferenceException + FullyQualifiedErrorId : Microsoft.Rtc.Rgs.Management.MoveCsRgsConfigurationCmdlet VERBOSE: Rollback transaction. ...

I recently had a customer that required 90 Common Area Phones creating in Skype for Business. This is quite a tedious task so the easiest way is to populate a CSV and use a PowerShell script to do the import. When creating a Common Area Phone in Lync/SfB it can take a few seconds before you’re able to assign Policies and Pin numbers to the objects. This slows the script down significantly if waiting 20 seconds between creating the object, then assigning Policies. So, I’ve actually made three ForEach loops, the first one creates the Common Area Phone objects, then it waits 20 seconds before assigning policies to every object, then it waits another 20 seconds before assigning the pins (I found that assigning Pins would fail if I didn’t wait longer). ...

I was recently installing the latest Skype4B CU and came across a strange issue where one of the updates would not install. The error message I received was: “Skype for Business Server 2015 Update Installer: There were errors during the installation process. For details, see the log file atC:\Users\chris\AppData\Local\Temp\Skype_patchinstallerlog-FE01-[2016-08-01][15-28-31].txt” Checking the log files indicated an error 1603. A bit of googling led me to various blog posts advising to ensure all MMCs were closed, checking there was enough disk space on the Front End and also running the Deployment Wizard again. None of these solutions worked for me, I tried running the installer from an elevated prompt and also tried installing server.msp manually. ...

Back in 2012 I wrote a post on how to hide Response Groups from the Address Book in Lync 2010 using ADSI Edit. The same process also applied to Lync 2013. Original Article: /2012/10/16/hiding-response-groups-from-address-book-lync-server-2010/ The original article involved finding the Response Group AD Object manually using ADSI Edit and changing the msExchHideFromAddressLists (Exchange property) to TRUE. You could then run Update-CSAddressbook and Lync clients would pickup the change within due course. ...