I just did one of these last month: 9.1.7 to 11.1. There is an official way - upgrade to 11.0.4.4 then to 11.1.1. My attempt to go to 11.0.4.4 killed my primary server's hard drive. I had a backup so I came out OK but I highly recommend....
- BACK UP YOUR SERVER - either both a snapshot if virtual and a back up of the IPO programming through web management or just the IPO if a physical server.
* I ended up just using a copy of the config of the SE and an export of the mdb from VMpro (with copies of their WAV folder) and told the customer to re-init their mailboxes
- If virtual, power down your SE and spin up a new server edition instance at R11.1.1, otherwise wipe and reinstall at 11.1.1
- restore your backup to the new SE
- push out the upgrade to any nodes (this can take a LOOOOONNNGGGG time)
- convert all your licenses to PLDS and/or re-host them to the WebLM server
- once the push to the nodes are done redirect all of them to the WebLM for licenses
I had to reboot D100 base stations at multiple sites to get them back online. I also had to go in and remove the login code and voicemail code complexity rules. If you use reception soft consoles you'll need to upgrade the clients and if they were logging in without a password that is no longer allowed.
You can push the upgrade out to all 500v2 nodes at the same time. When I did my first I did the local node first to make sure things went fine, then pushed out to the other 12 sites. Surprisingly the ones with bad internet connections in smaller centres finished before the two in the major metro areas with solid and fast connections. Go figure.
It took a couple hours easy. At one point I was texting my wife and calculated it at 3 minutes per percentage point. I don't think it was that slow the entire time but yeah, 3 or 4 hours to push the upgrade to the sites that took the longest (Scarborough and Hamilton). The local 500v2 took about an hour I'd say.
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.