I'm guessing you meant to say PCD (i.e. Prime Collaboration Deployment), not PCB which isn't an acryonym I'm aware of. The appraoch you mention is certainly the fastest. That said, it's a brand new process so it's a road less traveled. Many of us have done it in the lab but real-life deployments of it are less clear.
The other approach would be to do a jump upgrade as described in 9.1; however, this would represent significantly more time. Here's the decision tree I would make if it helps:
Do you have a whole weekend-sized change window opportunity?
Yes: Use PCD and don't change readdress (i.e. direct replacement). This has the advantage of not needing to deal with the ITL or certificate changes but you need time to thorougly test everything afterward.
No: Are you able to assign new IPv4 addresses and hostnames?
Yes: Use PCD and readdress during the process. This allows you to run both systems concurrently and test features. You need to account for the ITL file (explained in the PCD docs) and update things like DHCP 150 values though.
No: Use the 9.1-era Jump Upgrade process and hop your way toward 10.0 like you would before 10.0 shipped.
Hi Jonathan, Thats a great answer and confirms my understanding. Sorry about the acronym error. I'd probably go for the new names and ip addresses as that would also give me a good fallback route in case there a serious errors and would also give us a platform to do testing and allow us to integrate other systems without interrupting the current production environment.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: email@example.com Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...