Forum Discussion
Migrate Skype for Business standard to Enterprise Pool
- Sri TodiJul 28, 2017Former Employee
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
- Install Enterprise Edition
- Set-up a Pool-Pairing relationship between the Standard Edition and Enterprise Edition Pool
- Verify Backup Status, for all 3 modalities ( Users / Conferences / CMS)
- Update DNS records for SRV records, LyncDiscover*, DHCP setting for LPE to the new pool
- Move Users
- Move CMS
- Move Dial-in conferencing Numbers ( move-csApplicationEndpoint)
- Move RGS components
- Update Trusted Application Pool Config
- Break Pool-Pairing
- Remove Standard Edition Server
- asang1979Nov 09, 2022Copper Contributor
Hello,
I am worried about step 2. Is it possible to pair a standard edition pool to an enterprise pool? I have read some MS articles and it only mentions that you can only pool pair standard with standard and enterprise with enterprise. Strange i can't find allot of toppics on this matter.
Regards
- Sokneang SamFeb 18, 2017Copper Contributor
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,
- Syed AliJul 28, 2017Copper Contributor
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?
- Mohammed Anas ShaikhFeb 19, 2017
Microsoft
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?