[iamwiz82]

From what I have gathered here, these are the steps I need to take in a knife-edge

You want to perform a knife edge cutover (at least that is what you've explained)

If you're going to rename the new server so it has the same hostname along with the same BES Server Name (which has to remain the same), then you simply stop the services on the original server, backup the database, turn off the original server, reset the computer account of the original server in active directory, rename the new server to the name of the old server (ip address can be different), install BES on new server (do not start services), restore database to new server, start services.

I have a question regarding it, though.

After installing and rebooting, the new server will go through it's configuration, and during that time it prompts for database information, Client Access License, and SRP. Do I input the same values as is on the old server? Or do I cancel out of the install at that point and restore the database, then start the services?

[DarthBBerry]

Originally Posted by iamwiz82

After installing and rebooting, the new server will go through it's configuration, and during that time it prompts for database information, Client Access License, and SRP. Do I input the same values as is on the old server? Or do I cancel out of the install at that point and restore the database, then start the services?

If you restore the *.mdf and *.ldf into place before you install, you can point the installation to the database at that point. If you choose not to restore the files until after the installation is complete, you need to name the database the exact same thing as it is presently called. (Prolly BESMgmt)
Use your regular SRP and CAL to get the server running.

When you drop in the database, everybody and everything should appear as normal.

[iamwiz82]

Originally Posted by DarthBBerry

If you restore the *.mdf and *.ldf into place before you install, you can point the installation to the database at that point. If you choose not to restore the files until after the installation is complete, you need to name the database the exact same thing as it is presently called. (Prolly BESMgmt)
Use your regular SRP and CAL to get the server running.

When you drop in the database, everybody and everything should appear as normal.

Does this include the rest of BES CALs? What if I put the wrong CAL license in when first installing the server? Any issues with that?

[hdawg]

Yes, all the CALs are in the DB. As long as you put in a valid CAL it'll proceed

[DarthBBerry]

Originally Posted by iamwiz82

Does this include the rest of BES CALs? What if I put the wrong CAL license in when first installing the server? Any issues with that?

What if you put in a wrong CAL? Then the installation tell you, WRONG!!in not a so polite manner.
Once you drop the DB into place, all the CALs entered in the past will auto populate.

[iamwiz82]

Originally Posted by DarthBBerry

What if you put in a wrong CAL? Then the installation tell you, WRONG!!in not a so polite manner.
Once you drop the DB into place, all the CALs entered in the past will auto populate.

I should have been clearer about my usage of 'wrong'. When I say wrong, I mean a valid BES CAL, but not the same original CAL I had added when I first installed the server. I have a bunch of individual licenses, which is why I ask.

[DarthBBerry]

Originally Posted by iamwiz82

I should have been clearer about my usage of 'wrong'. When I say wrong, I mean a valid BES CAL, but not the same original CAL I had added when I first installed the server. I have a bunch of individual licenses, which is why I ask.

As long as it's a valid CAL, BES doesn't care which one you use. It could be the first one you ever entered, the last one or one purchased somewhere in betweeen. It just needs to validate against the BlackBerry Farm and you're golden.

[iamwiz82]

Well I just ran through everything as listed and I have failed. I have restored everything, services are up, SRP is correct, all users are in, I see policies re-pushed, but the contact time is not updating and no email is syncing.

Any ideas?

[iamwiz82]

I think I found out what is happening, but not why. The network message for a reactivation are not being pulled out of the inboxes.

[hdawg]

Originally Posted by iamwiz82

I think I found out what is happening, but not why. The network message for a reactivation are not being pulled out of the inboxes.

Check your permissions.

[iamwiz82]

It was a "smack your head" error. I forgot to apply the correct SP on Exchange Admin. Doh! All is well. It would have been a 45 minute migration had I noticed that.