Anthony, You can grab the trial license by creating an account on vmware.com and requesting the ESXi license. This is still how I get standalone ESXi instances running here at Cisco in my lab.
Login with your account, go to the below link, request a key. https://my.vmware.com/group/vmware/evalcenter?p=free-esxi5&lp=default +Chris TME - MediaSense and Unity Connection From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Anthony Holloway Sent: Wednesday, November 12, 2014 5:15 PM To: Ryan Ratliff (rratliff); Boon Cc: cisco-voip voyp list Subject: Re: [cisco-voip] Prime Collaboration Deployment Tool Ryan, Can you be more specific on where you get the trial license? I heard this same thing mentioned at Cisco Live, and when I approached VMWare about it, they pushed me to Cisco, and Cisco pushed me to VMWare. An alternative option, which I'm not endorsing, is to apply the key seen here in this Cisco Field Trainers video, temporarily of course, and then revert the key once done with PCD. https://www.youtube.com/watch?v=YWsgXrlD4Ew#t=570 On Wed Nov 12 2014 at 3:57:42 PM Ryan Ratliff (rratliff) <rratl...@cisco.com<mailto:rratl...@cisco.com>> wrote: One small thing to add to Dennis' great post. The trial ESXi license will work for a PCD migration if you are moving to a BE with the hypervisor license. This will probably only work for new installs where you are still in the 60 day trial. It's very easy to switch between the hypervisor and trial license. -Ryan On Nov 11, 2014, at 5:43 PM, Boon <ciscovoipu...@gmail.com<mailto:ciscovoipu...@gmail.com>> wrote: Some great advice there thanks all On Tue, Nov 11, 2014 at 4:12 PM, Jason Aarons (AM) <jason.aar...@dimensiondata.com<mailto:jason.aar...@dimensiondata.com>> wrote: I agree, device loads should be hard coded on devices and upgraded outside of CallManager upgrades. From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net<mailto:cisco-voip-boun...@puck.nether.net>] On Behalf Of Josh Warcop Sent: Tuesday, November 11, 2014 9:13 AM To: cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net> Subject: Re: [cisco-voip] Prime Collaboration Deployment Tool Side note - I've started advocating assigning firmware loads to devices via BAT. I no longer want all phones to upgrade or downgrade immediately following a CUCM version switch. Sent from my Windows Phone ________________________________ From: Heim, Dennis<mailto:dennis.h...@wwt.com> Sent: 11/11/2014 8:46 AM To: Boon<mailto:ciscovoipu...@gmail.com>; cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net> Subject: Re: [cisco-voip] Prime Collaboration Deployment Tool PCD is a tool, it is not a complete upgrade and patching solution (sales/marketing). It has specific versions and specific tasks that it can do. Many things it cannot (verify with cco). It does work with all the caveats. You will need to upload all cop files and iso files to the PCD server. All files will be pushed from the PCD server as part of the upgrade task. If you have nodes at remote locations, this will be 4-5gb across your network (allocate necessary time). It will upgrade one node at a time, streamlining and parallel ops is not really in PCD’s deck of cards at this time. For example, it will do each cucm subscriber in serial, instead of all at the same time, or upgrading IM&P while it doing cucm. With proper time, it will complete. Normally in a significant upgrade as 6.x to 10.x is, you are obviously getting new hardware. Without PCD, this would all be staged in an offline environment, so cut night is turning off the existing servers and turning on the new ones. VM migration and all that has to be planned for, etc. However, with PCD, everything happens the night of cut. PCD migrates the data out of the existing cluster, then it shuts those down and bring up the new VM’s. Please also note that you need appropriate VMWare licensing to support the storage API’s .. you need foundation or standard the default that is offered as part of BE7K will not permit the use of PCD. In your migration you will also need to plan for endpoint firmware upgrades, depending on what you are running for some endpoints this may be a multi-step upgrade. Some have also noted there is a bug with the default 10.5 firmware as it relates to headset and transfer functionality, so following your upgrading to 10.X you will want to upgrade past the default firmware. The trick with PCD is to figure out what you want your upgrade process to look like then determine where PCD can help. PCD is great for pushing cop files and firmware upgrades across medium to large size clusters (big time savings). When it comes to full upgrades, it does get the job done, but it does take longer. Hope this helps, Dennis Heim | Collaboration Solutions Architect World Wide Technology, Inc. | +1 314-212-1814<tel:%2B1%20314-212-1814> <image001.png><https://twitter.com/CollabSensei> <image002.png><image003.png><tel:+13142121814><image004.png> From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Boon Sent: Tuesday, November 11, 2014 3:49 AM To: cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net> Subject: [cisco-voip] Prime Collaboration Deployment Tool I'm planning on upgrading a customer's CUCM 6.1(5) to 10.5 in the next few weeks by using the new PCD tool. I've tried it out in the lab and it seems ok. Has anyone used this tool to perform upgrades on production systems? If so what was your experience please, good or bad? Are there any gotchas that I need to be aware of? Thanks itevomcid _______________________________________________ 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<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
