BlackBerry Forums Support Community               

Closed Thread
 
LinkBack Thread Tools
Old 02-21-2005, 09:56 AM   #1 (permalink)
New Member
 
Join Date: Feb 2005
Posts: 7
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default Migrating BES to new server

Please Login to Remove!

Currently have 3.6 SP4 on Exchange 2000 set up on Server A. Need to migrate all BES users to new server B, running same level of BES software. Have been loaned a SRP key for the new server B. Intend to move all users across in planned phases as the move will require a new PIN generation. Once all the users are on the new server the server A SRP key needs to be moved across to server B to replace the SRP loan key. Will this work or is there a need to re-generate PIN again once the loan SRP key has been replaced with the original.

Mark
Offline  
Old 02-21-2005, 10:12 AM   #2 (permalink)
Talking BlackBerry Encyclopedia
 
Talldog's Avatar
 
Join Date: Jan 2005
Location: Connecticut
Model: 8330
Carrier: Verizon
Posts: 213
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

When you change the SRP key, a new encryption key will be required for each user.
__________________
Talldog
Offline  
Old 02-21-2005, 10:18 AM   #3 (permalink)
New Member
 
Join Date: Feb 2005
Posts: 7
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

Talldog

Thanks for the reply. I was hoping to get away with only one PIN regeneration as this works out at around 40 man hours work for all of te Blackberries on Server A. This will now need to be doubled for the extra PIN generation.

Mark
Offline  
Old 02-21-2005, 10:39 AM   #4 (permalink)
BlackBerry God
 
jibi's Avatar
 
Join Date: Oct 2004
Location: Jibi's Secret Place
Model: 8900
OS: 4.6.1.174
Carrier: AT&T
Posts: 11,310
Post Thanks: 0
Thanked 1 Time in 1 Post
Default

i had the same move and experienced issues when the temporary SRP expired. mind you, i had already changed the SRP in the Management Console to our owned SRP. for whatever reason, it did not change the SRP for MDS, thus it expired (after so many days) and our MDS services were not connecting to RIM's network.

to resolve, i had to export users and keys and drop the database and recreate a new one. here's the email information on it.

Quote:
To try and fix this issue I would like you to recreate you database. Before doing this export your BlackBerry server from the management console. Then go to a DOS prompt and enter the following commands:

bcp besmgmt..licensekeys out c:\keys.txt -c -T bcp besmgmt..itpolicy out c:\itpolicy -c -T bcp besmgmt..itpolicy2 out c:\itpolicy2 -c -T bcp besmgmt..itpolicytemplate out c:\itpolicy3 -c -T bcp besmgmt..itpolicytemplate2 out c:\itpolicy4 -c -T

This will export your license keys and any IT policies that you currently have. Stop all BlackBerry service and close the management console and then enter the following commands from a DOS prompt:

OSQL -E
drop database besmgmt
go
exit

Then navigate to the C:\Program Files\Research In Motion\BlackBerry Enterprise Server\Management\Database directory and enter the following commands:

createdb -E
bcp besmgmt..licensekeys in c:\keys.txt -c -T bcp besmgmt..itpolicy in c:\itpolicy -c -T bcp besmgmt..itpolicy2 in c:\itpolicy2 -c -T bcp besmgmt..itpolicytemplate in c:\itpolicy3 -c -T bcp besmgmt..itpolicytemplate2 in c:\itpolicy4 -c -T

The first command will create the database and the other commands will import you license keys and IT policies into the database. Then open your management console and import your BlackBerry server. After importing the server start all BlackBerry services and see if the issue has been resolved.
so, just in case you have issues post-SRP change, do the above.
__________________
In the beginning the Universe was created. This has made a lot of people very angry and is widely regarded as a bad move.
Offline  
Old 02-23-2005, 07:25 AM   #5 (permalink)
New Member
 
Join Date: Feb 2005
Posts: 7
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default BES Server Migration

Thanks for all of the replies to the original question.

I've just been informed that Vodafone have announced the release of BES 4.0 in the UK.

Modifying the original question :

SERVER A BES 3.6 sp 3
SERVER B BES 4.0

Would this migration be easier than the original migration ?
Can the PINs be generated over the air rather than requring a re-cradle ?
Are there any pre-requisttes for the hand held software ?
Current units are RIM 7230 and 7100v. Can these both be managed over the air ?

Regards

Mark
Offline  
Old 02-23-2005, 07:51 AM   #6 (permalink)
Thumbs Must Hurt
 
Join Date: Jan 2005
Location: Palos Hills, IL
Model: None
Carrier: None
Posts: 72
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

1. Most likely no
2. PINs cannot be regenerated over the air in your case
3. Handhelds need to run v4.0 in order to use OTA activation, but there is no pre-req tied to version 4.
4. If they run V4.0 handheld software. Depends if Vodafone has released v4 upgrades (check the upgrades sticky thread in the General section of this forum)

As you will need to cradle all handhelds in order to upgrade them to 4.0, in this case, it makes no sense to do an OTA activation for all your users
Offline  
Old 02-24-2005, 10:42 AM   #7 (permalink)
Knows Where the Search Button Is
 
Join Date: Oct 2004
Location: Las Vegas, NV
Model: 8100
OS: 4.5.0.xx
Carrier: T-Mobile
Posts: 45
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default

There is a utility to do this in BES 4.0 where NO SRP change will be needed, NO RE-DOCK of users needed. Less than an hour downtime depending on users. (i moved close to 300 users in about 30 minutes).

See this post with my details.

http://www.blackberryforums.com/view...ghlight=#22996

Feel free to PM me with any questions.
Offline  
Closed Thread


Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On





Copyright 2004-2014 BlackBerryForums.com.
The names RIM and BlackBerry are registered Trademarks of BlackBerry Inc.