I would also add that, even if you do let PCD run wild, at best it is another server to setup and get working (assuming new PCD install and not re tasking an existing) on top of reading the PCD guides ... etc.
So even if it all goes perfect, you're still down the time it takes to get PCD up and working from a OS/network perspective. Basically, you're adding in a layer to a process that yields no more benefit (IMO) other than to be able to say you used PCD. I'm not trying to be negative to PCD; it's actually a fantastic idea -just not "there" yet from a development perspective. I would love a product that could completely automate the migration process in all circumstances (although, I would miss my ANSI art installation menus); however, I'm not sure Cisco has a ton of emphasis on that right now (IMO) so .... In practice, I would not use PCD because there are enough caveats that it isn't worth it to me. I would have to be able to blindly trust it to get the value out of it that I'd need and in my opinion, PCD is not at a point where it can be trusted in that manner. -Ryan Sent from my iPhone On Oct 6, 2016, at 10:02 AM, Anthony Holloway <avholloway+cisco-v...@gmail.com<mailto:avholloway+cisco-v...@gmail.com>> wrote: I think the most important thing to know is, upgrading your apps via PCD is no different than you upgrading them yourself. That is, unless you plan to be asleep while it's happening, and just wake up in the morning on 11.5. If instead you plan to babysit the PCD process, you really are not gaining anything by using PCD to do the upgrade for you. You still have to plan for the upgrade as if PCD were not involved: read upgrade guides, release notes, read mes, install COP files, clear disk space, plan the phone firmware upgrade, check compatible phones (and yes you're going to lose phone support in 11.5), check gateway compatibility, upgrade Jabber, and the list goes on. PCD is going to save you zero time and effort, and in fact, it will increase your work effort, because on top of everything you are already responsible for in planning and executing the upgrade normally, now you need to read the PCD guides and cross your fingers you don't hit a PCD bug in the process. So, like I said, unless you're going to let PCD run all by itself while you're away, I wouldn't bother with it. But really, who is ready to trust PCD to an unattended upgrade, to include a switch version? That's my opinion on the matter. Let's hear from you, why you are using PCD for this task in the first place, and what benefits you think it brings to your project. On Thu, Oct 6, 2016 at 8:17 AM, Michael Voity <mvo...@uvm.edu<mailto:mvo...@uvm.edu>> wrote: Hello, This weekend I am going to be upgrading our CUCM, CUC and CUPS cluster from 10.5.2 to 11.5.1. I will be using PCD to execute and switch the upgrade. Upgrade will be applied Friday, and Sunday the switch will happen. I have read the doc: http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/upgrade/11_5_1/cucm_b_upgrade-guide-cucm-115.html It seems pretty straight forward. My question to the group is, are there any issues I should be concerned about or is there something the doc missed that I need to do? As always, thanks for reading. -Mike -- Michael T. Voity Network Engineer University of Vermont _______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net> https://puck.nether.net/mailman/listinfo/cisco-voip _______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net> https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
