<p dir="ltr">I'd recommend to install PCD, discover your esxi hosts and then your old UC cluster(s), then you can go through the various wizards to see if PCD will let you do what you are trying to do.</p>
<p dir="ltr">If I recall with PCD 10.5.2, I could change the hostname but not the domain name. That's my recollection, though it may not be right. But again, if you setup PCD you can walk through the tutorial and checkout the options.</p>
<div class="gmail_quote">On May 4, 2015 11:30 PM, "Anthony Holloway" <<a href="mailto:avholloway%2Bcisco-voip@gmail.com">avholloway+cisco-voip@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">That's a relief to hear you've done it. The documentation isn't very clear if a Network Migration is possible, let alone a Simple Migration. Just take a look at the PCD 10.5(3) doc under supported releases. Thanks for replying. <br><div class="gmail_quote">On Mon, May 4, 2015 at 10:27 PM Justin Steinberg <<a href="mailto:jsteinberg@gmail.com" target="_blank">jsteinberg@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">i've done it and it is mostly straightforward. In my case, I did a network migration to change the hostname of IM/P. However, I used the same IP address as the old server (this was a MCS to UCS 8 to 10 migration).<div><br></div><div>I only did a network migration because I wanted to change the hostname to align with naming conventions. The first go around, I didn't update the DNS with the new hostname A/PTR for the new IMP name. The PCD migration task for the IMP server failed. It needed to have the DNS server updated with the new IM/P 10.x server's A/PTR in DNS and the old MCS v8 CUPS server removed from DNS (since it was using the same IP)..</div><div><br></div><div>Make sure that all the VMs in the new v10 cluster have perfect DNS resolution, A & PTR before the PCD. If there are any issues, this will mess up the migration.</div><div><br></div><div>Also, open the console of the VM in VMware during the PCD tasks to monitor the status of the tasks. PCD doesn't provide alot of progress update, but if you watch the console of the VM in VMware you can follow the familiar CLI install process.</div></div><div class="gmail_extra"><br><div class="gmail_quote"></div></div><div class="gmail_extra"><div class="gmail_quote">On Mon, May 4, 2015 at 10:57 PM, Anthony Holloway <span dir="ltr"><<a href="mailto:avholloway+cisco-voip@gmail.com" target="_blank">avholloway+cisco-voip@gmail.com</a>></span> wrote:<br></div></div><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Has anyone experience with PCD and performing a <b>Network Migration</b> on IM&P? If not, how about performing a <b>Network Migration</b> on CUCM, and then how did you handle IM&P?<div><br></div><div>Thanks.</div></div>
<br></blockquote></div></div><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br></blockquote></div><br></div>
</blockquote></div>
</blockquote></div>