We have a Unity 3.1.1 on a DELL that is on A/D with Win2K and Ex2K off-box. We need to migrate it to a new compaq server, which is linked to a new A/D domain with Win 2003 and Exchange 2003. Essentially we are facing 3 types of changes. As usual, the options are:
1) Install 3.1.1 in new server. Backup the production server and restore db on new. Upgrade the new server to 4.0.3
2) Upgrade the production to 4.0.3. Install 4.0.3 too on the new. Backup from the old and restore db to the new
1) is preferred as production is unaffected. But I think it is not feasible as 3.1.1 cannot talk to Ex2003.
In case of 2), how does the license procedure work out. Do I need to apply two licenses, one for the old server mac, the other for new server mac ?
Re: Crossroad - Complex migration from 3.1.1 to 4.0.3
I'm thinking of the 3rd option which may have the least downtime on production server. Since this customer has 44 mailboxes and 1 call handler. May I just build the new server from scratch, import A/D user in the new domain and tie the wav of recorded name and greeting captured from the old server and we are done. The only drawback is user has to change the phone password from default again. Is there any hidden trap of doing so ?
These are the paths to get to each CCX logs through CLI. They may be helpful if you are having issues accessing RTMT or downloading logs through it.
If you want to download them you have to prefix "file get " and you can add one of the options (re...