Upgrade Midsize Business Template from 5.2.1 to virtual 6.3

[joeyhump]

Upgrading from CM 5.2.1 and have to put patch 02.1.016.4-20790.tar.gz on the system.
Does anyone know if this is service affecting?
I would also like to leave the patch on for about a week before the upgrade.
Does anyone know if that would cause any problems with the 5.2.1?

I wanted to get the pre-upgrade translations and deploy them on the new system in a test environment for a about a week or so before going live.

Any info greatly appreciated.

 

[kyle555]

Heck, the big boldface red type about these patches say: "Communication Manager pre-upgrade software should only be applied immediately before the upgrade to Communication Manager 6.x. Once the applicable pre-upgrade patch or patches are activated, the only thing that should be done is a backup followed by an immediate upgrade."

Mr. AvayaTier3 might know if you can get away with removing it after and carry on with business as usual. The ideal circumstance would be having a different server you could load 5.2 on outside of production, restore a 5.2 backup to that, apply the pre-upgrade patch, and use that to get something to put on 6.3.

 

[joeyhump]

All I can do is throw it out there to see if anyone has tried to do this. Heck, the big boldface red type was my first clue that it wouldnt work so thats why I came to tek-tips to see if anyone had ever tried.
Unfortunately I dont have a different server to load the 5.2 on and try. My customer is a little worried about not having a backout plan if the 6.3 bombs. Thanks for the help anyway.

 

[dialtonebone]

I've never had an issue myself with putting that patch on a month ahead or so. I never have gone longer than that, but I can't imagine it is harmful.