The goal of this page is to assist you in operations required for your Office 365 tenant in order to get the full benefit of Cloud Connector Edition (CCE) on SBC Edge.
Computer configured with Office 365 tenant and Skype for Business Online, Windows PowerShell Module.
Use PowerShell and the Skype for Business administrator account to connect your Office 365 tenant:
For details, refer to https://technet.microsoft.com/en-us/library/dn362831(v=ocs.15).aspx.
Familiarize Yourself With Tenant
Enable federation on your Tenant:
Ensure that your tenant has the proper configuration using the PowerShell command:
The site is created automatically when installing your CCE, and your CCE will be assigned to the new site.
Viewing the Site List
You can see the site list using:
Removing the Site List
If the site is not properly created when installing your CCE, you can remove the site with:
You can assign a default site for your tenant using:
Ensure that your tenant has the proper default site using the PowerShell command:
Configuring the Appliance
The appliance will be created automatically when installing your CCE. An appliance is identified by its Name (Host computer Hostname and Mediation Server FQDN) and its site.
You must remove the Appliance when deploying with a new host (new hostname or new Mediation server name)
Managing User Accounts
Create a User on the Office 365 Portal
- Create an Office 365 user using your portal.
- Assign an E5 or E3 + cloud PBX license to this user
Enable the User for Voice and Cloud Connector Edition
Execute this PowerShell command to ensure that the user has been created:
Assign the proper voice policy and phone number using the PowerShell command:
Ensure that the user has the proper voice policy using the PowerShell command:
Assign a PSTN site to this user. The site must already exist. If you don't specify a site, your user will be assigned to the default site. If you want to assign the user to a specific site, use:
Ensure that the user has the proper configuration by using the PowerShell command:
Cloud Connector Edition Update
Cloud Connector Edition is comprised of:
- Cloud Connector Edition Update: Microsoft refers to this as "BitsUpdate." This update is performed when a new release of Cloud Connector Edition is available from Microsoft.
- Windows Update for Host and VM. Microsoft refers to this as "OSUpdate." This update covers all the Windows Update released by Microsoft that apply on the Host or the VM, and its primary aim is security.
This update covers the script that deploy CCE and the Skype component that handle the call inside CCE.
The configuration for the CCE Update on a PSTN site is made on the Tenant. The configuration is then automatically sent to the CCE on this site. You can use the Powershell module Skype Online to create a time window for when the update should occur, and then assign it to a specific site. To configure it, use the command:
When entering the time window, the tenant will check if Microsoft released a new version of Cloud Connector since the last check.
If that the case, the ASM Host will start downloading the new CCE bits and will start building a new CCE deployment in parallel of the existing VMs. The host will use the content of the ini file and the current External certificate to rebuild a new set of VM. If the deployment is successful, the system will drain the call on the previous VMs and disconnect them from the network in order to attach the new VMs on the network.
For High Availability, once you enter the CCE update time window, one of the CCEs on the site will start updating and will be flagged as in “Maintenance Mode”. This status is reflected through the WebUI for SBC Edge 6.1.2 and later (Tasks > Operational Status). Once the CCE update completes, it will return to Idle state. If it is still in the time window for updating, a second CCE will then start updating and will be flagged as in “Maintenance Mode”. Once the second CCEs update is complete, it will return to Running state. All the CCEs on a site will follow the same rule, until the window of time expires. If a CCE is not updated by the expiration, it will be updated in a the next cycle.
The previous version will remain as a backup soluton until the next Cloud Connector Edition update.
Windows Update for the Host and Virtual MACHINE (VM)
Windows Update can be performed automatically, or manually.
Automatic Windows Update
The trigger for the Cloud Connector Edition update is made from Office 365. You can use the Powershell module Skype Online to specify a time window when does this update should occurs. To configure it, use the command:
When entering the time window, the tenant will check if Microsoft released a new Windows Update that apply for CCE since the last check. If that the case, the update will occurs as follow:
VMs run Windows Update
Drain the call from CCE
- Reboot the VMs if needed
- ASM Host run Windows Update
- Reboot the ASM Host if needed
For High Availability deployment the update will be apply on one CCE at the time.
This is the Appliance initial state on the tenant:
Manual Windows Update
If you do not want to use automatic updates in your environment, follow these steps to manually check for and apply Windows updates. Checking for and installing Windows updates may require a server restart. When a host server is restarting, users will not be able to use Cloud Connector Edition to place or receive calls. You can manually check for and install updates to control when the updates take place, and then restart the machines as needed during times you choose to avoid disruption of services.
You will need to disable the Automatic Windows Update using the Powershell module Skype online command:
To manually check for updates, connect to each host server and open the Control Panel. Select System and Security >Windows Update, and then manage the updates and server restarts as appropriate for your environment.
- If there is only one appliance in the site, connect to each virtual machine and open the Control Panel. Select System and Security >Windows Update, and then configure the updates and server restarts as appropriate.
If there are more than one appliance in the site, the instance being updated and restarted cannot be accessed by users during the updates. Users will connect to other instances in the deployment until all virtual machines and all Skype for Business services start on the virtual machines after the updates are completed. To avoid any potential disruption to service, you can remove the instance from HA while you apply the updates, and then restore it when complete. To do so:
On each host server, open a PowerShell console as administrator.
Remove the instance from HA with the following cmdlet:
Follow the steps for a single instance to manually apply the updates and restart the virtual machine.
Set the instance back to HA with the following cmdlet:
For multi-site deployments, follow the steps for a single site for each site in the deployment, applying updates to one site at a time.