locked
error encountered at end of Skype for Business 2015 Deployment RRS feed

  • General discussion

  • Environmental Variables: Windows 2016 server Datacenter version, SQL server 2012, Skype for Business server 2015

    Issue: I am following the Microsoft Deployment guide (https://technet.microsoft.com/en-us/library/dn951362.aspx) and got to step 7 which is to install system components on each server.

    I got all the way to the end where I have to run the following three PowerShell cmdlets from the Skype management shell in order --

    Enable-CsTopology

    Enable-CsComputer

    Start-CsPool

    First one went through with a warning which was resolved by grabbing ownership of the deleted items in AD.

    Can't run the last one cause the second cmdlet will not run clean.

    While running Start-CsSimpleUrlConfiuration.Activate I get warnings.

    PowerShell shows as follows:

    PS C:\Users\sysadmin.PWOLFINC> Enable-CsComputer
    WARNING: No patterns found. Skipping rewrite rules creation for Web Scheduler
    WARNING: No patterns found. Skipping rewrite rules creation for Web Scheduler
    WARNING: "Enable-CsComputer" processing has completed with warnings. "2" warnings were recorded during this run.
    WARNING: Detailed results can be found at
    "C:\Users\sysadmin.PWOLFINC\AppData\Local\Temp\Enable-CsComputer-4872604a-84ac-4f65-a1b7-c2e7ec44ea80.html".
    PS C:\Users\sysadmin.PWOLFINC>

    I did look at the log and can provide a copy of same upon request.

    I found only the following article which provides a cmdlet for use that either never existed or was deprecated and the corresponding TechNet article was removed: https://social.technet.microsoft.com/Forums/windowsserver/en-US/e3661ff7-8b85-44fa-bf4a-cc9077dbec7f/warning-no-patterns-found-skipping-rewrite-rules-creation-for-meet-simple-urls?forum=lyncdeploy

    The offeneding cmdlets are Set-CsProvisionServiceConfiguration and Get-CSProvisionServiceConfiguration.

    Any help getting past this point would be greatly appreciated and  hope this is not being caused by my using a cert from Godaddy.

    Monday, August 21, 2017 5:04 AM

All replies

  • Hi Mr. Ganz,

    Godaddy is no problem, runs fine on a lot of my deployments.

     Problem with deleted objects can also be ignore, but errors with enable-cscomputer cannot be ignored.

    Be sure that you have enough permission to run enable-cstopology and that the requires RTC security groups are created on the FE computer object on AD.

    Please check also, that the local certificate store have only root certificates in the root store and sub-ca on the other store and not mixed.

    Be also sure, that you only use fqdn on the topology builder and have not mistypes.


    regards Holger Technical Specialist UC

    Monday, August 21, 2017 5:12 PM
  • Thanks for the quick reply.

    I am able to run Enable-CsTopology without issue, warnings or errors which indicates I have the appropriate permissions.

    I will have to check the computer object in AD as well as my cert stores.

    UPDATE: FE Computer object is a member of the appropriate groups (they were created) and Cert store looks fine (one cert, one domain).

    Issue still persists so any additional help is greatly appreciated.



    • Edited by Mr. Ganz Friday, September 1, 2017 8:02 AM typo
    Sunday, August 27, 2017 12:50 AM