none
Migrating Lync 2010 server setup with standard to enterprise

    Question

  • I have Lync 2010 Standard server setup with Edge and R Proxy configured.

    I want to move the present setup to a new server with Lync 2010 Enterprise and phase out the current hardware . I want to retain the same name and use the public certificates.  I have two servers for enterprise pool and SQL 2008 server. How do I start. I am documenting the steps involved but did not find elaborate process to deal with migration scenario. Can someone please suggest.


    Monday, October 01, 2012 12:23 PM

Answers

All replies

  • Hi

    Here is another thread that gives some ideas on what to think about and also some usefull links.

    http://social.technet.microsoft.com/Forums/nl-NL/ocsplanningdeployment/thread/8d942c86-ebf1-42a9-8ab6-5d7ae31fdd1f


    /Tim

    Monday, October 01, 2012 12:32 PM
  • Hi,Shireesh1,

    If you would like to use the same FQDN for your Enterprise Edition server,the best option is you need create a new Enterprise Edition pool with another name,move the users and CMS to the new pool then decommission the old SE server,after that change the External Web Service FQDN for your new pool to the old one which matched the Public certificate then assign the certificate to it.However,during this time the external web service features such as ABS will no work.

    Some references about move CMS to another server for your reference.

    http://ingazat.wordpress.com/2011/01/06/moving-your-lync-server-2010-cms-to-another-server/ 

    Regards,

    Sharon


    Sharon Shen

    TechNet Community Support

    ************************************************************************************************************************

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question.

    Tuesday, October 02, 2012 7:03 AM
    Moderator
  • Thanks Sharon,

    I moved CMS from my standard pool to another server pool. Now in the topology builder property,under Associations I find -

    Note:User store for this pool cannot be moved since this pool also hosts Central Management Server.To move the user store to another SQL instance, Central Management Server must first be assigned to another pool.Please refer to documentation to find out how to do that.

    How to deal with this. The SQL store already has an rtc instance which says "This SQL store cannot be modified because it hosts the Central Management Store"

    Can someone please point to the documentation it refers.

    What new store instance name do we need to provide for restoring the database since rtc already hosts CMS.

    Regards





    • Edited by Shireesh1 Saturday, October 06, 2012 2:10 AM
    Friday, October 05, 2012 8:38 AM
  • Hi,Shireesh1,

    Have you verified that you have moved the CMS successfully?Check the cental management server FQDN listed in topology builder and the event log/Deployment log to see if any errors.

    If you make sure you have done it then restart both the Master Replica Service and File-Transfer Agent service on your Old SE server and NEW FE server,also please make sure you have launch the setup wizard and run the “Install or Update Lync Server System” step for any Front-End server which was part of the old pool, and for any Front-End server which is part of the new pool.

    Another blog post about moving CMS from SE to EE step-by-step for your reference.

    http://demagnum.wordpress.com/2012/06/04/moving-cms-front-end-standard-to-cms-enterprise-lync/

    Regards,

    Sharon


    Sharon Shen

    TechNet Community Support

    ************************************************************************************************************************

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question.

    Wednesday, October 10, 2012 7:03 AM
    Moderator
  • Yes Sharon, the CMS move went well, I restarted both the servers that would take care of service restart.

     I have been using following links -

    http://cmcgreanor.wordpress.com/2012/07/24/move-lync-central-management-store-and-front-end-servers-to-a-new-lync-pool-with-a-new-sql-backend

    http://blogs.technet.com/b/nexthop/archive/2010/12/20/change-a-pool-database-instance-when-the-pool-hosts-the-central-management-server.aspx

    http://www.vatland.no/post/2011/08/03/Move-Lync-database-to-new-sql-server.aspx

    Not sure if I should have used some other instance instead of rtc in while running -

     Install-CSDatabase -CentralManagementDatabase -clean -SqlServerFqdn <mySQLserver> -SqlInstanceName rtc

    I used rtc since the old FE server had both CMS and user store on same SQL instance and thought that would work,but the note in red as I mentioned above is something I'm not sure how to deal with.


    • Edited by Shireesh1 Wednesday, October 10, 2012 12:25 PM
    Wednesday, October 10, 2012 10:44 AM
  • Hi Shireesh,

    When you move the CMS to another sql was it successfull.

    The RED remarks which you have shown above is the normal one, lets say you have one SQL store / Standard edition when ever you deploy CMS these remarks are shown on the topology builder to notify the administrator.

    What is your actual Instance name is it rtc or some thing else

    If it was successfull then as per sharon run the add or remove components wizard to let the servers know and make them aware about their roles.


    If answer is helpful, please hit the green arrow on the left, or mark as answer. Salahuddin | Blogs:http://salahuddinkhatri.wordpress.com | MCITP Microsoft Lync

    Wednesday, October 10, 2012 12:29 PM
  • Thank you so much,

    Yes CMS move was successful. Actual instance name is rtc.

    Ran 'Setup or Remove Lync Server Components" wizard on both the servers, checked replication. When I start moving users from the old pool to the new one it errors out . 

    Another thing, do I need to restore the database on the new FE server that I backed up from the old one ? 

    Wednesday, October 10, 2012 3:42 PM
  • The error has changed to 

    Move-CsUser : Distributed Component Object Model (DCOM) operation SetMoveResourceData failed. For details, see inner exception. 

    after the target pool hostname was able to get resolved from the old FE server.

    Please correct me here ,to fix this error as I explored requires to enable cross database chaining in the sql database properties RTC and  databases which I do not see unless the databases are restored from the backup I'd taken from the old FE server to the new SQL instance. 



    • Edited by Shireesh1 Thursday, October 11, 2012 5:46 AM
    Thursday, October 11, 2012 5:44 AM
  • Move-CsUser succeeded this time when Databases were restored and chaining was enabled.

    Thursday, October 11, 2012 8:11 AM