Migrate Skype for Business standard to Enterprise Pool

%3CLINGO-SUB%20id%3D%22lingo-sub-46791%22%20slang%3D%22en-US%22%3EMigrate%20Skype%20for%20Business%20standard%20to%20Enterprise%20Pool%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-46791%22%20slang%3D%22en-US%22%3E%3CP%3EDear%20Community%2C%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMy%20Client%20Current%20existing%20skype%20for%20business%20standard%20pool%20is%20planing%20for%20deploy%20enterprise%20pool.%20I%20would%20like%20to%20ask%20if%20you%20have%20document%20related%20to%20integrate%20Skype%20for%20biz%20front%20end%20standard%20with%20enterprise%20pool%20and%20migrate%20user%20from%20standard%20to%20enterprise.%20Welcome%20all%20ideas.%20than%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-46791%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESkype%20for%20Business%20Adoption%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-91240%22%20slang%3D%22en-US%22%3ERe%3A%20Migrate%20Skype%20for%20Business%20standard%20to%20Enterprise%20Pool%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-91240%22%20slang%3D%22en-US%22%3E%3CP%3EAnas%20is%20certainly%20right%2C%20there%20isnt%20a%20way%20to%20just%20change%20from%20a%20Standard%20Edition%20to%20Enterprise%20Edition%2C%20like%20Windows%20Anytime%20Upgrade.%20The%20Enterprise%20Edition%20Pool%20will%20have%20to%20be%20deployed%20from%20scratch.%20I%20would%20recommend%20that%20you%20perform%20the%20following%20in-order%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3EInstall%20Enterprise%20Edition%3C%2FLI%3E%0A%3CLI%3ESet-up%20a%20Pool-Pairing%20relationship%20between%20the%20Standard%20Edition%20and%20Enterprise%20Edition%20Pool%3C%2FLI%3E%0A%3CLI%3EVerify%20Backup%20Status%2C%20for%20all%203%20modalities%20(%20Users%20%2F%20Conferences%20%2F%20CMS)%3C%2FLI%3E%0A%3CLI%3EUpdate%20DNS%20records%20for%20SRV%20records%2C%20LyncDiscover*%2C%20DHCP%20setting%20for%20LPE%20to%20the%20new%20pool%3C%2FLI%3E%0A%3CLI%3EMove%20Users%3C%2FLI%3E%0A%3CLI%3E%26nbsp%3BMove%20CMS%3C%2FLI%3E%0A%3CLI%3EMove%20Dial-in%20conferencing%20Numbers%20(%20move-csApplicationEndpoint)%3C%2FLI%3E%0A%3CLI%3EMove%20RGS%20components%3C%2FLI%3E%0A%3CLI%3EUpdate%20Trusted%20Application%20Pool%20Config%3C%2FLI%3E%0A%3CLI%3EBreak%20Pool-Pairing%3C%2FLI%3E%0A%3CLI%3ERemove%20Standard%20Edition%20Server%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-91147%22%20slang%3D%22en-US%22%3ERe%3A%20Migrate%20Skype%20for%20Business%20standard%20to%20Enterprise%20Pool%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-91147%22%20slang%3D%22en-US%22%3E%3CP%3EFor%20SQL%20make%20sure%20you%20have%20required%20port%20opened%20(1433)%20and%20have%20rights%20to%20write%20in%20to%20SQL%20database.%20Question%3A%20Where%20you%20publishing%20it%20from%3F%20from%20your%20current%20FE%20Std%20server%20or%20from%20new%20server%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-47052%22%20slang%3D%22en-US%22%3ERe%3A%20Migrate%20Skype%20for%20Business%20standard%20to%20Enterprise%20Pool%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-47052%22%20slang%3D%22en-US%22%3EHello%2C%20I%20have%20not%20done%20this%20myself%20in%20the%20past%2C%20might%20be%20great%20to%20see%20if%20we%20get%20any%20responses%20from%20others%20in%20the%20field%20who%20may%20have%20done%20this.%20The%20only%20thing%20i%20can%20think%20of%20is%20that%20since%20you%20CMS%20is%20currently%20still%20on%20the%20std%20Edi%20FE%20it%20is%20likely%20the%20publish%20topology%20after%20adding%20the%20ent%20pool%20will%20still%20reach%20out%20to%20the%20std%20edition%20FE.%20have%20u%20tried%20to%20publish%20topology%20from%20the%20STD%20edi%20FE%20itself%20after%20adding%20the%20ent%20pool%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-46898%22%20slang%3D%22en-US%22%3ERe%3A%20Migrate%20Skype%20for%20Business%20standard%20to%20Enterprise%20Pool%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-46898%22%20slang%3D%22en-US%22%3E%3CP%3EDear%20Sir%2C%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20for%20your%20sharing%20idea%20for%20migrate%20flow.%20Right%20now%2C%20i%20am%20on%20testing%20environment%20as%20below%3A%3C%2FP%3E%3CP%3E-%20Prepare%20new%20SQL%20for%20Backend%20database%3C%2FP%3E%3CP%3E-%20Prepare%20new%20Front%20End%26nbsp%3B%3C%2FP%3E%3CP%3E-%20Install%20SQL%20server%202014%20enterprise%3C%2FP%3E%3CP%3E-%20Start%20install%20new%20front%20end%20and%20its%20tool%26nbsp%3B%3C%2FP%3E%3CP%3Ebut%20facing%20some%20issue%20during%20create%20and%20publish%20topologies.%20new%20front%20end%20alway%20point%20to%20Database%20at%20front%20end%20standard%20and%20i%20stuck%20with%20publish%20topologies.%20appreicate%20if%20you%20have%20similar%20expericene%20and%20document%20how%20to.%20i%20will%20try%20to%20do%20it.%26nbsp%3B%3C%2FP%3E%3CP%3Ethank%20with%20regards%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-46846%22%20slang%3D%22en-US%22%3ERe%3A%20Migrate%20Skype%20for%20Business%20standard%20to%20Enterprise%20Pool%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-46846%22%20slang%3D%22en-US%22%3EHi%20Sokneang%20Sam%20There%20is%20no%20direct%20upgrade%20path%20from%20Std%20edition%20to%20Enterprise%2C%20What%20you%20can%20do%20is%20create%20a%20new%20enterprise%20pool%20in%20the%20same%20topology%20and%20you%20maybe%20able%20to%20move%20users%20from%20Std%20to%20enterprise%20pool.%20when%20you%20move%20them%20the%20external%20webservices%20URL%20will%20however%20change%20for%20these%20users%20and%20will%20now%20be%20the%20external%20webservices%20URL%20of%20the%20enterprise%20pool.%20Best%20option%20in%20my%20opinion%20would%20be%20to%20set%20up%20an%20enterprise%20pool%20and%20create%20a%20new%20test%20user%20in%20this%20pool%2C%20make%20sure%20everything%20works%20for%20him%20and%20if%20it%20does%20then%20you%20should%20just%20be%20able%20to%20move%20users%20from%20STD%20edition%20pool%20to%20Enterprise.%20Might%20be%20good%20to%20wait%20and%20see%20if%20anyone%20else%20has%20any%20better%20ideas.%3C%2FLINGO-BODY%3E
New Contributor

Dear Community, 

 

My Client Current existing skype for business standard pool is planing for deploy enterprise pool. I would like to ask if you have document related to integrate Skype for biz front end standard with enterprise pool and migrate user from standard to enterprise. Welcome all ideas. than

5 Replies
Hi Sokneang Sam There is no direct upgrade path from Std edition to Enterprise, What you can do is create a new enterprise pool in the same topology and you maybe able to move users from Std to enterprise pool. when you move them the external webservices URL will however change for these users and will now be the external webservices URL of the enterprise pool. Best option in my opinion would be to set up an enterprise pool and create a new test user in this pool, make sure everything works for him and if it does then you should just be able to move users from STD edition pool to Enterprise. Might be good to wait and see if anyone else has any better ideas.

Dear Sir, 

Thank for your sharing idea for migrate flow. Right now, i am on testing environment as below:

- Prepare new SQL for Backend database

- Prepare new Front End 

- Install SQL server 2014 enterprise

- Start install new front end and its tool 

but facing some issue during create and publish topologies. new front end alway point to Database at front end standard and i stuck with publish topologies. appreicate if you have similar expericene and document how to. i will try to do it. 

thank with regards,

 

Hello, I have not done this myself in the past, might be great to see if we get any responses from others in the field who may have done this. The only thing i can think of is that since you CMS is currently still on the std Edi FE it is likely the publish topology after adding the ent pool will still reach out to the std edition FE. have u tried to publish topology from the STD edi FE itself after adding the ent pool?

For SQL make sure you have required port opened (1433) and have rights to write in to SQL database. Question: Where you publishing it from? from your current FE Std server or from new server?

Anas is certainly right, there isnt a way to just change from a Standard Edition to Enterprise Edition, like Windows Anytime Upgrade. The Enterprise Edition Pool will have to be deployed from scratch. I would recommend that you perform the following in-order

  1. Install Enterprise Edition
  2. Set-up a Pool-Pairing relationship between the Standard Edition and Enterprise Edition Pool
  3. Verify Backup Status, for all 3 modalities ( Users / Conferences / CMS)
  4. Update DNS records for SRV records, LyncDiscover*, DHCP setting for LPE to the new pool
  5. Move Users
  6.  Move CMS
  7. Move Dial-in conferencing Numbers ( move-csApplicationEndpoint)
  8. Move RGS components
  9. Update Trusted Application Pool Config
  10. Break Pool-Pairing
  11. Remove Standard Edition Server