Best bet is to export whatever you can and import it into the 9.1 system then build what you need to back up, upgrading configs over large version differences is sketchy at times anyway and 9.1 is one of the worst ever (not quite as bad as 4.0... but almost)
We do these all the time. It's becoming a real pain in the ass as things that used to export and import into say, 9, don't work right in 9.1, and you end up with missing passwords, broken groups, buttons missing, etc.
Typically wipe out all of the groups, shortcodes, users, user rights on the new config, export those things from the old config (if applicable), then build everything else from scratch.
-Austin
I used to be an ACE. Now I'm just an Arse.
If you don't want to configure from scratch the only way that could make sense is to upgrade the V1 to 9.0 (check for the necessary steps in between). Then initialize the V2 with 9.1 and make the first call to brand it to 9.1. Recreate card with 9.0, start IPO import old config and upgrade to 9.1 again.
We replaced our V1 with a V2 within R9 without configure from scratch and it worked.
If you reconfigure from scratch go directly to 9.1 if the hardware is PCS15 or newer. You have to request a license swap from your old dongle (smart card) to the new one (SD card) and ensure to be able to ship the old card to AVAYA quick enough.
Don't forget to have a new essential edition license available because a virtual essential edition license created by the upgrade process is bound to the chassis and will be lost.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.