Monday, February 6, 2017

Office 365 Wizards

I have recently been looking at the different wizards that Microsoft provide in their Office 365 tenancy, and thought it might help some people to see them all in one place...

If anyone finds any discrepancies or new ones that I haven't added, please let me know.

Tuesday, August 2, 2016

Moving from On-Premises to Skype for Business Online

This is a gotcha which took me two days to figure out. I was moving a customer from a broken Skype for Business on-premises to O365 Skype for Business Online.

Why go through the pain of hybrid, if the users never used the system in the first place. What I found is there is a lack of documentation on what are the steps to move in a big-bang scenario. So here goes....

  1. Remove all users from your on-prem deployment
  2. Make sure the users are not licensed for Skype for Business Online yet (if they are, remove it)
  3. Make sure that "ALL" msRTCSIP-* attributes are null, and have propagated to all your DCs
  4. Do another directory sync to O365 using your ADDConnect server
  5. Assign License on O365
  6. Test User Connectivity
What got me here was step "3" .. All attributes were Null except for msRTCSIP-DeploymentLocator which was set to "SRV:" ... in a normal deployment this would be good because it means automatically detect the server. In O365 world, this means the user is On-Prem and don't enable them for Skype for Busienss.

Powershell Command to remove it..

Get-ADUser -SearchBase "OU=Users,DC=contoso,DC=local" -Filter * |Set-ADUser -Clear "msRTCSIP-DeploymentLocator"

Sunday, July 17, 2016

Phone Number Mismatch

I have been at many sites where the phone numbers on the AD contact is not the same as what is configured on Lync/SfB (Skype for Business).

Since SfB is the single source of truth when it comes to which number the user will ultimately answer on; I have devised a quick script that will match those two numbers up, and make sure that all AD contacts that have a Lync/SfB account have the correct phone number associated with them.

Hope this helps a few people out there...

P.S. This script can be easily modified to make other changes to contacts as required.

v.0.1 - 2016-07-18

Thursday, June 2, 2016

Sonus SBC Call Actions

I haven't found a place that explains the real life use case for this; so I thought I would write one for anyone that may search one day for how to do this.

I usually use this as a first step in the call flow, to manipulate the call before it gets to the routing stage.

As a simple example (don't want to get too complicated here). Let's say you want to mask certain caller IDs based on the "department" field in AD.

First thing, you need to setup the AD integration (lots of details on Google about how to do this), and make sure you synchronise (or otherwise leave it set to online) the AD attributes:

  • msRTCSIP-Line
  • department
Once you have got that working, you should create a manipulation table that will make the required changes to your call based on certain rules. In our case, it should check the "department" field and change the CallingNumber based on that.

Next an "Action" needs to be created to direct the call flow. In our example, we need to call to continue down its path regardless of the outcome.

This action will need to be used in an "Action Set" to modify the call flow. Again, in this case, we will allow the call to continue down the same path regardless. Quick gotcha here, the "Continue" option in the "Action Set" does not mean continue the call; it means continue the processing of the rules, so if you put "Continue" the call will fail...

Finally, you need to apply this "Action Set" to a signalling group for it to take affect. In our case, we will apply it to the "To/From SfB" so that it will be intercepted before the call is made out to the PSTN...

Tuesday, May 24, 2016

Last Login Timestamp

Ok ... here is one that I have used with some of my customers to clean up their user database ...

This script will go through a pool or all the pools in the deployment and check the last login timestamp for all the users that have logged in to each of the member servers (or SBAs).

You can use the -Unique switch to get only the latest login or drop the switch to get all timestamps available in the deployment.

You have also the option of producing the results in a Grid format, or a CSV file. Alternatively, do not specify any output format, and the result will be an array of objects that you can use to pipe into other commands.

If you get an error reading from the SQL database, you might not have access to that server's RTCLocal database; or you may need to open the correct ports (check out the infamous Get-CsConnections.ps1 script by Pat Richard on how to do that).

Hope this helps, and as always your feedback is highly appreciated.

v.0.01 - 2016-05-25 -

Wednesday, January 13, 2016

New Year ... New Holiday Lists

Since its the new year, and everyone is updating their RGS holiday lists, I thought I would contribute with a quick one-liner to help all those who want to quickly view which RGS groups have what holiday lists (you would think Microsoft would make that easier for you).

$Workflows = get-CsRGSWorkflow
$Holidays = @()

foreach($Workflow in $Workflows){

   $List = @($Workflow.HolidaySetIDList)
   $S = ""
   if ($List){
     $S = [string]::Join(", ",($List |%{$Holiday = $_;Get-CsRgsHolidaySet -ShowAll|?{$_.Identity -match $Holiday.InstanceId}}).Name)
   $Workflow |Add-Member "HolidaySet" $S
   $Holidays += $Workflow |Select-Object Name,LineURI,Language,TimeZone,HolidaySet

return $Holidays

Tuesday, September 29, 2015

Changing the primary SIP domain

Recently I came across a situation where it was necessary to change the primary SIP domain for a Lync 2013 customer (although this will work for any Lync or Skype for Business deployment). This is not a very difficult process but there are a few gotchas which I would like to share...

  1. Make sure that you change the SIP address for all your users after making the change to the new SIP domain
  2. Make sure you run the bootstrap after you have made the change on all servers
  3. Make sure you modify all your RGS workflows to use the new SIP domain
  4. Finally, and the hardest one (because its not documented anywhere); you will need to manually edit the application contacts using ADSIEdit.exe to use the new SIP domain

 Changing the Application Contacts

First open ADSIEdit and go to the configuration node, and navigate to the Application Contacts folder:

 Once there, open each entry and modify the msRTCSIP-PrimaryUserAddress and Proxy address to use the new SIP domain:

Don't forget to restart the services that you have changed !!