If this is a production system, then you would want to follow the proper guidelines for installing Unity Connection 8 in VMWare. From there, you could use COBRAS which is the migration tool to get from Unity to Unity Connection. I've done this many times in my lab environment...I just haven't used CUC 8 as I don't typically go with dot zero releases for many reasons. Read the COBRAS help file at www.ciscounitytools.com and you can reference some of my materials here:
Great Thanks guys for the info! One other question, since im going the VMware route I'm just going to build another VM server and import the data from COBRAS as reccomended however, I would like to keep the old VMware server running until I know that Unity Conenction is 100% ready to go. And if there is an issue switch back if needed.
What is the best way to do this? Should I leave the old IP on the old VMware machine and give Unity Connection a new address? And by doing this method will I run into any issues?
It seems like a simple process however, I'm used to the older versions of Unity where it had the "Manage Intergrations" application where you could easily change the server IP address to Call Manager and and VM ports.
Build CUC as new so you can keep the old IP on the Unity server. You shouldn't run into any issues based on IP address - COBRAS doesn't care. As far as the UTIM ("Manage Integration"), you still have that on even newer versions of Unity. In CUC, you control integration thru Port Group settings.
These are the paths to get to each CCX logs through CLI. They may be helpful if you are having issues accessing RTMT or downloading logs through it.
If you want to download them you have to prefix "file get " and you can add one of the options (re...