locked
New install Skype for Business 2015 - Standard - on premise RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I have installed Skype for Business 2015 on a Windows Server 2012 R2 server. I used Topology builder and published a topology.

    The following services aren't running:

    Skype for Business Server Front-End

    Skype for Business Server Call Park

    Skype for Business Sever IM Conferencing

    Skype for Business Web Conferencing

    Skype for Business Sever Audio/Video Conferencing

    Skype for Business Sever Application Sharing.

    The 1st one, Skype for Business Server Front-End is the one that sill not start and gives an error. the others start an dthen immediately stop with the 'some services stop automatically is they are not in use.'

    The front end gets "...refer to service specific error code -1008125701'. 

    Looking at the 'Lync event viewer', I see several errors.

    "A serious problem related to certificates is preventing Skype for Business Server from functioning.

    Skype for Business Server machine FQDN cannot be located in the default certificate.
    Machine FQDN: 'LYNC.xxx.local'.
    Make sure the default certificate matches the machine FQDN.

    Cause: The Skype for Business Server failed to initialize with the configured certificate.
    Resolution:
    Review and correct the certificate configuration, then start the service again."

    So... We have a certificate issued by Comodo and it doesn't have our .local extension in it because it's not real, it's just our Domain. What is the way around this?

    Thanks!

    Tuesday, April 19, 2016 1:52 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    You have a problem with certificates.

    Check the certificates again.........

    https://technet.microsoft.com/en-us/library/gg398616.aspx

    “Vote As Helpful” and/or “Mark As Answered” - Thiago Mendes da Silva - MCSE Communication - http://www.ucsteps.com/

    • Marked as answer by Paul L Fisher Wednesday, April 20, 2016 1:40 PM
    Tuesday, April 19, 2016 8:44 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    You have a problem with certificates.

    Check the certificates again.........

    https://technet.microsoft.com/en-us/library/gg398616.aspx

    “Vote As Helpful” and/or “Mark As Answered” - Thiago Mendes da Silva - MCSE Communication - http://www.ucsteps.com/

    • Marked as answer by Paul L Fisher Wednesday, April 20, 2016 1:40 PM
    Tuesday, April 19, 2016 8:44 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Since you are with a STD server , pool name , servername is all going to be the same , make sure you have a certificate installed on this server with the Subject name as the Server FQDN and its assigned using the Deployment wizard 

    Linus

    Wednesday, April 20, 2016 3:59 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I got it to work by issuing an internal certificate.
    • Proposed as answer by P L Fisher Monday, March 20, 2017 2:36 PM
    Wednesday, April 20, 2016 1:41 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Paul,

    I am not stuck at the same error. Please let me know how you got this fixed.

    Regards,

    Gowrishankar

    Saturday, March 18, 2017 7:42 AM