Answered Lync CU3 SQL update questions

  • Tuesday, August 23, 2011 4:18 PM
     
     

    In the production environment where I work, there are pretty strict ACL rules in place. So strict, in fact, that attempts to run the SQL update from Lync FEs fail because ports 445 and 139 are blocked. 

     

    First question: is there “danger”  to an environmental state where CU3 is applied but the DB component is not? This appears to not be the case, but I'd like to be sure. 

     

    Second question: if the situation IS a suspect state, can the SQL update be run from the enterprise monitoring server? The monitoring server function is not co-located with the SQL back-end. At http://support.microsoft.com/?kbid=2493736, it's noted that the update should be run from an FE, but I’m wondering if that is an absolute requirement.

     

    Third question: is it correct to say that, long term, ports 445 and 139 should be open between FEs and BEs to enable this functionality?  


    Deskpoet

Answers

All Replies

  • Wednesday, August 24, 2011 3:51 PM
     
     Answered

    Hi,

    1. Installing DB update is mandatory, it can result in various issue on the Lync server like none of the services will start

    2. Yes, its an absolute requirement to run the update from the EE front end server as mentioned in http://support.microsoft.com/?kbid=2493736

    3. Please refer the below articles for SQL port requirements 

     http://technet.microsoft.com/en-us/library/gg425818.aspx

    http://support.microsoft.com/?kbid=841251


    Navin Microsoft Unified Communications
    • Marked As Answer by dadarrah Wednesday, August 24, 2011 5:31 PM
    •  
  • Thursday, September 15, 2011 4:46 PM
     
     

    Hi,

    Is it ok to run apply the CU3 updates along with the DB upgrade on 1 enterprise pool but not the others belonging to the same domain? We have one of the production pools in our environment for testing only. We plan to apply the CU3 patches on this pool first for testing. The updates will be applied to all other pools eventually, after about 2-3 weeks.

    Each pool is under a separate "site" in the Lync topology and has a separate SQL instance.

    I just want to ensure that the version mismatch between the pools and their respective DBs will not make the environment unstable. 

    Thank you.

    Divya