Changing SRP keys from one BES server to another(BES4.1 to BES5.0)
I am planning to move my BES 4.1 SRP key to the new BES 5.0 server,
What kind of issues i might be facing, i did consulted a Blackberry tech who told me that it should be fine if i am just transferring the SRP from one server to another both the BES 4.1 and BES 5.0 are on different servers and they use different database and different email systems. I have already installed BES 5.0 trial with gapps and it works fine. BEs 4.1 is on exchange while we are migrating to google apps and i am using BES 5.0 on google apps. Is there anything i should be aware of or transferring the SRP from one BES to another wont cause a massive downtime. I am just trying to avoid any surprises during migration thanks for your help Prab |
Re: Changing SRP keys from one BES server to another(BES4.1 to BES5.0)
BES SRP's are platform aganostic, does not care.
just make sure BES runs for 4 hours when you switch SRP or you will need to do some manual activations. |
Re: Changing SRP keys from one BES server to another(BES4.1 to BES5.0)
are you referring to the new BES server. So need to make sure the new BES runs for 4 hours after SRP transfer.
Is there a specific reason for it? thanks |
Re: Changing SRP keys from one BES server to another(BES4.1 to BES5.0)
so all devices will get the new SRP info
|
Re: Changing SRP keys from one BES server to another(BES4.1 to BES5.0)
knottyrope, transfer of SRP key = new SPR key?
PrabThind? Questions:- 1. Are there users on BES4 still? (Yes/No) 2. If 'Yes', are they supposed to be moved to the BES5? (Yes/No). 3. If 'Yes', then you might want to consider contacting RIM to get a migration kit. 4. Alternatively, get another set of new SRP ID + Auth Key and use the Enterprise Transporter tool for user migration from BES4->BES5. If all above is "No", then you can simply just transfer the SRP key over from BES4->BES5. |
All times are GMT -5. The time now is 05:08 PM. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.