Quote:
Originally Posted by hdawg
Do you use MDSS / MDS-IS?
Do you know the difference between MDS-CS and MDSS/MDS-IS?
Can you restate your procedure again? It made me dizzy after reading it a few times.
|
Well, I know that the MDS-CS is the connection server for the BES and that changing the machine name of the BES (Windows name) can bring up problems with web broswing. Is the MDS-IS for BPS or BIS?
Sure. Sorry about that
I'm still in planning phases so my process is kinda jumbled right now, so bear with me.
-Currently have one BES (Also the BlackBerry Server Name) with 500 users on it.
-Version is 4.0.5.5
-Current DB is the MSDE Config DB
-Want to move to an actual SQL DB and the SQL DB will housed on a remote SQL 2000 server.
-Have a new hardware that's being prepped for a new BES installation
-Want to have the BES version 4.1 SP5 on the new box
-Since I don't want the users to re-activate using enterprise activation (that would be a disaster), I need to backup the current MSDE config db and restore that onto the soon to be created SQL DB on the remote SQL server.
1. Record the current BES info (SRP ID/KEY, CAL keys, BES admin info)
2. Backup the MSDE DB on the exisiting BES and save it locally
3. Create a new SQL DB on the remote SQL 2000 server and name it BESMgmt (the same default name as the MSDE DB)
4. Install BES 4.0.5.5 on the NEW server, point the DB location to the newly created BESMgmt SQL DB on the remote server. (Here's a question; Should I just skip the manual creation of the DB and just let the BES install create a DB on the remote SQL server?)
5. Install the BES 4.1 SP5 media on the NEW server. (Make sure the BES services are Stopped)
6. Restore the MSDE DB backup from the OLD server to the new BESMgmt SQL DB on the remote SQL server.
7. Stop and disable the BES services on the OLD server.
8. Start the BES services on the NEW server.
9. Move the BES users from the OLD to the NEW server
Again, sorry for my gibberish. Thanks for your help.
Mike