Cloning of Cisco Collaboration devices on a virtual machine changes the Serial Number?
We are currently encountering a problem on our Cisco telepresence Servers, conductor, VCS-C And VCS-E, content server after we cloned the virtual machines to another host as we need to upgrade the host server. As we observed serial numbers were changed and encountered many errors (kindly see attached photos). Also do we need to migrate/transfer all the licenses and option keys to the cloned virtual machines? If yes,How?
Coping Conductor, TelePresence Server, and VCS virtual machines isn't supported, the serial number will change and the licenses will be come invalid. This is expected behavior to prevent duplication, you should use vMotion if you need to migrate the servers to another host. If vMotion isn't possible and you must perform fresh installs, you'll need to contact TAC and submit to rehost the licenses from the old servers.
The Content Server serial number and licenses are stored in the Windows registry (HKLM\SOFTWARE\Wow6432Node\TANDBERG), you should be able to update them to match the existing server. However, if that doesn't work, you'll need to also contact TAC to rehost these licenses as well.
Thank you so much. However, Vmotion is not supported. We will just export the OVF file per application and deploy it to another hose server machine. Is this means that we will just need a Cisco TAC for the re-hosting of licenses right?
vMotion is supported by most virtual collaboration applications, including Conductor, TelePresence Server, and VCS products. No documentation regarding TCS support for vMotion, but as it's a Windows based VM, I'd assume it is.
If you can't vMotion the VMs from one host to another and must perform a copy, contact TAC and perform a rehost of the licenses.
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...