SBC Service Delayed Start

Discussion in 'Ideas' started by 3cxsbx, Dec 5, 2015.

  1. 3cxsbx

    Joined:
    Nov 18, 2015
    Messages:
    28
    Likes Received:
    0
    * There is no limitation regarding installing an sbc on a domain controller
    * Once the DC goes down for whatever reason (patching, etc.) and comes up again SBC will start faster then the DNS service
    * Once the initial DNS request fails sbc will be offline for a long time (wondering why it does not really check again in a reasonable timeframe)

    * The issue can be solved if the service is installed with the Service Startup Option Delayed -> SBC service will always start after dns service > change installer to do this.
     
  2. bardissi

    bardissi Member

    Joined:
    Jan 31, 2012
    Messages:
    318
    Likes Received:
    0
    You should definitely NOT install SBC on the domain controller.
     
  3. 3cxsbx

    Joined:
    Nov 18, 2015
    Messages:
    28
    Likes Received:
    0
    Thanks for your reply. If so I would like to understand the limitations of this. Could you please elaborate on that?

    Further more: if that is the case: 3CX should update their requirements to mention this is not supported.
     
  4. bardissi

    bardissi Member

    Joined:
    Jan 31, 2012
    Messages:
    318
    Likes Received:
    0
    It's the same reason that you shouldn't install a regular 3cx server install on a domain controller ....too much happening on one machine ...you will start to see "ghost" issues that are hard or impossible to troubleshoot as well as performance related issues ....3CX server and/or 3CX SBC needs to be on individual machines ....consider it best practice