Step-by-Step Guide: Configure Skype for Business Cloud Connector Edition

Overview:This guides covers steps involved in downloading and installing Skype for Business Cloud Connector Edition 2.0.1.Microsoft TechNet link https://technet.microsoft.com/en-us/library/mt605228.aspx was used as reference throughout the deployment.To perform a successful dep

 
 
 
 
 
4.8 Star
(4)
5,360 times
Add to favorites
Lync
9/8/2017
E-mail Twitter del.icio.us Digg Facebook
  • After running Convert-CcIsoToVhdx ...
    3 Posts | Last post May 30, 2018
    • The process always stacks on :
      Creating base virtual machine...
      Starting base virtual machine...
      Operating system started in 253 seconds.
      Got virtual machine IP: 169.254.235.16
      Enabling credential delegation for NTLM on host machine.
      
      Could you please advise?
    • Maybe, this issue is affected by the following issue.
      
      https://support.microsoft.com/en-us/help/4093492/credssp-updates-for-cve-2018-0886-march-13-2018
      
      Try to add registry by this command for host machine.
      
      REG ADD HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\System\CredSSP\Parameters /v AllowEncryptionOracle /t REG_DWORD /d 2
    • Hi
      Do we need to tag VLANs when creating virtual switches? 
      
  • What would cause this following error?
    1 Posts | Last post May 06, 2018
    • ms-diagnostics-public: 23;reason="Call failed to establish due to a media connectivity failure when one endpoint is internal and the other is remote";component="MediationServer";Exception="Proxy side ICE connectivity check failed."
  • How to establish a SIP trunk between CCE
    1 Posts | Last post April 12, 2018
    • Hi I just want to know do you have a step by step in establishing the SIP trunk between CCE like asterisk
  • Hi Shankar
    3 Posts | Last post March 29, 2018
    • I am trying to install and deploy CCE 2.1.0 since a month ago. 
      this error occurred at the end of the deployment, how can I solve it and to run script from this step!!:  
      
      Deployment process spent 3852 seconds.
      Enabling credential delegation for NTLM on host machine.
      Creating key on host machine: hklm:\SOFTWARE\Policies\Microsoft\Windows\CredentialsDelegation\AllowFreshCredentialsWhenNTLMOnly
      Disabling credential delegation for NTLM on host machine.
      Removing key on host machine: hklm:\SOFTWARE\Policies\Microsoft\Windows\CredentialsDelegation\AllowFreshCredentialsWhenNTLMOnly.
      The configuration for virtual machine cleanup is generated in memory.
      Successfully removed the virtual switch 343cf841-6ffa-49a6-9fed-7d2455a17712 from the host server.
      Successfully removed the virtual switch c95db915-4e50-489d-9369-88391213a04c from the host server.
      Task:InstallInstance ends at 2018-01-22T10:41:47.0053637-05:00
      The SwitchVersion log is in C:\Users\Administrator\CloudConnector\ApplianceRoot\Log\cce_SwitchVersion_05_00_2018_01_22_10_41_49.log.
      Task:SwitchVersion starts at 2018-01-22T10:41:49.6772332-05:00
      The current scripts version is 2.1.0.
      There are no instances currently running.
      Switching Skype for Business Cloud Connector Edition version starts.
      Restarting 2.1.0 - Broadconnect - AD.
      Wait-MtMachineOn : Can't connect to machine 172.19.40.161 after waiting 617 seconds.
      At C:\Program Files\WindowsPowerShell\Modules\CloudConnector\Internal\MtVm.ps1:473 char:5
      +     Wait-MtMachineOn -MachineIP $MachineIP -Credential $Credential -W ...
      +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
          + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
          + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Wait-MtMachineOn
       Trying to exit current manual maintenance mode.
      Successfully exit manual maintenance mode.
      Wait-MtMachineOn : Can't connect to machine 172.19.40.161 after waiting 617 sec
    • Looks to me the script cannot login to AD, can you try regenerating all Cloud Connector passwords by following these steps:
      
      Restart the host server.
      
      Delete the following file: “%SystemDrive%\Programdata\Cloudconnector\credentials.<CurrentUser>.xml” .
      
      Launch a PowerShell console as administrator, and then run “Register-CcAppliance -Local” to re-enter the passwords following the description.
    • please make sure the virtual switches defined are assigned correctly to VM. SFB Corpnet, SFB Internal/management,SFB Internet. if these switches are not assigned properly you may stop the VM and change the virtual switches which will fix this error for sure.
  • Cloud connector
    5 Posts | Last post March 29, 2018
    • We are getting this error see below.
      
      PS C:\Windows\system32> Set-CcExternalCertificateFilePath -Target EdgeServer -Path C:\Certs\Newedge.pfx -Import
      The SetExternalCertificateFilePath log is in C:\cce\Log\WIN_TIVEAH1K86H_SetExternalCer
      tificateFilePath_08_00_2018_02_14_07_45_59.log.
      Task:SetExternalCertificateFilePath starts at 2018-02-14T07:45:59.3040525-08:00
      The current scripts version is 2.1.0.
      There are no instances currently running.
      Update ExternalCertificateFilePath with value C:\Certs\Newedge.pfx in configuration.
      Get-Ini : C:\cce\CloudConnector.ini doesn't exist.
      At C:\Program 
      Files\WindowsPowerShell\Modules\CloudConnector\Internal\MtCommon.ps1:734 char:16
      +         $ini = Get-Ini
      +                ~~~~~~~
          + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
          + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Get- 
         Ini
       
      Get-Ini : C:\cce\CloudConnector.ini doesn't exist.
      At C:\Program 
      Files\WindowsPowerShell\Modules\CloudConnector\Internal\MtCommon.ps1:734 char:16
      +         $ini = Get-Ini
      +                ~~~~~~~
          + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
          + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Get- 
         Ini
    • Here is the ini file and it is in the host CCE folder
      ; Build number 6.0.9319.419 - Keep this comment for diagnostic purpose 
      ;;;;;;;;;;;;;; Common (topology-wide) parameters. ;;;;;;;;;;;;;
      [Common]
      
      ;Domain(s) of SIP URIs used by company users.
      ;Domain(s) registered on O365.
      ;Support multiple domains separated by space. First domain is the default used.
      ;for phone URI.
      SIPDomains=ucglobe.com
      
      ;Domain DNS suffix for the Skype for Business Cloud Connector Edition itself.
      ;Virtual machines CMS, Mediation server join this domain.
      ;Can be local (e.g. does not need to be in public DNS)
      ;MUST be different with domain(s) registered on O365
      VirtualMachineDomain=ucglobe.com
      
      ;AD Server Name
      ;Server name which will be used to generate Server fqdn. It can NOT contain .<VirtualMachineDomain>. 15 Character LIMIT.
      ServerName=AD.ucglobe.com
      
      ;AD Server IP address
      IP=192.168.3.2
      
      ;O365 Online service FQDNs
      ;No need to change for world-wide O365 instance. For other instances, go to domain settings page in O365 portal to get the right Fqdns.  
      OnlineSipFederationFqdn=sipfed.online.lync.com
      
      ;Must update SiteName before deployment. Register-CcAppliance cmdlet uses SiteName to register current appliance to an existing or new site.
      ;If you want to register the appliance to an new site, SiteName must be unique and different from any other existing site in your Office 365 tenant configuration.
      ;If you want to register the appliance to an existing site, SiteName must match the site name defined in your Office 365 tenant configuration.
      ;If you are copying configuration file from one site to another, make sure you update the SiteName for each site correctly.
      SiteName=Site1
      
      ;Optional site parameters
      CountryCode=US
      City=TX
      State=Forth Worth
      
      ;The IP address of the VM that prepares base VM image
      ;This setting is only necessary for Convert-CcIsoToVhdx
      ;Leave this blank if DHCP is supported
      BaseVMIP=
      
      ;The address of Windows Server Update Service - an intranet server to host updates from Microso
    • whole ini file does not come any way to send to you.
    • Hi there, does the file "CloudConnector.ini" exist with the correct name?
    • please check this path for your error and make sure ini file is present. C:\cce\CloudConnector.ini doesn't exist.
  • Dial Plan
    2 Posts | Last post March 29, 2018
    • When sending out a outbound pstn call we want to remove the + for example if i call +18175551212 I just want to send 18175551212.  
    • this is very much possible. please set manipulation rule in IP to Tel section.
      under action tab, set "remove from left 1". 
  • Not able to make pstn call
    2 Posts | Last post February 20, 2018
    • We are not able to make pstn call, the call does not even connect to sbc.
      
      Also the on the skype for business admin.  in the voice/on premise pstn  it does not show ONLINE.  We are working with the support for office 365 and they are clueless.  Need to attach logs.
    • The parameter "VirtualMachineDomain" cannot be same as "SIPDomains".
      ;Domain DNS suffix for the Skype for Business Cloud Connector Edition itself.
      ;Virtual machines CMS, Mediation server join this domain.
      ;Can be local (e.g. does not need to be in public DNS)
      ;MUST be different with domain(s) registered on O365
      VirtualMachineDomain=sfb-ccedomain.local
  • HA for CCE within same site
    2 Posts | Last post November 30, 2017
    • HI, i am planning to deploy the CCE with HA in my primary site, i guess i can use the same guide you published for installation. 
      
      my Second question is regarding the HA, how i can deploy the HA, i dont see the configuration or sequence for the deployment. can share your experience here. Thanks.
    • Hi Amjad Khan,
      Most of the step are the same as this guide for CCE HA deployment.
      Differences are as per follow:
      
      Add an appliance to an existing site
      
      You can extend an existing Cloud Connector site to support HA by adding additional appliances to the site. 
      Follow the steps to prepare your Cloud Connector appliance as described in Prepare your Cloud Connector appliance. Note that some steps are required only for the first appliance in your deployment. Confirm that the site directory exists and is correctly configured for HA support.
      Run the following cmdlet only on the newly added host server to update topology information in your Office 365 tenant configuration. If you want to add multiple appliances at the same time, run the cmdlet on each newly added host server one by one:
      
      Register-CcAppliance
      Update the topology on existing appliances by running the following cmdlet on each host server. Only run the cmdlet on the existing appliances.
      
      Publish-CcAppliance
      Run the following cmdlet only on newly added host servers. Do not run this cmdlet on the existing appliance. If you want to add multiple appliances at the same time, run the cmdlet on each newly added host server one by one.
      
      Install-CcAppliance
      
      You may also need to check the table the differences between single site with HA support and a multiple site deployment for configure "CloudConnector.ini".
      https://technet.microsoft.com/en-us/library/mt740650.aspx
      
      Ref: https://technet.microsoft.com/en-us/library/mt740654.aspx
      
  • Install-ccapplicance fails
    2 Posts | Last post October 20, 2017
    • I encounter an error when installing the Cloud Connector (Install-CcAppliance) Version 2.0.1:
      
      WARNING: Set-CsCertificate failed.
      
      Command execution failed: "83A0DF9CAADA542E4B78745683FFBEA8C3045DF1" not found in MY certificate store or not trusted
      
      I've even installed the certificate manually with the CA chain in Trusted root CA
    • Hi there, is the cert signed by public CA, and does it include the Root and Chain as well, in PFX format.
      When you mention you installed the Root Cert manually, i assume you are installing in Edge, and not on the Host machine ?
  • Calls failing when testing
    3 Posts | Last post September 29, 2017
    • Now that I've gotten CCE to deploy, I'm trying to do some test calls.  IN our environment we only care about outbound calls as anything inbound goes through an auto-attendant.
      
      When I try and place a call from my SKype client, it immediately goes fast busy.  WOndering what I'm missing in call routing?   I checked to make sure out gateway IP and TCP Port match what was put in the CloudConnector.ini file and they do match.
      
      Any suggestions on next steps?
    • Use Snooper and check client logs located at,
      C:\Users\<username>\AppData\Local\Microsoft\Office\16.0\Lync\Tracing\Lync-UccApi-0
    • I've been updating this on the TechNet forum instead of filling it in both places as an FYI..
1 - 10 of 15 Items