Gordon's remark is not on the fact that you cannot do that, his remark is on the fact that the moment you do this, you lose all Cisco support. If this is only for a lab and you want to fool around and change settings, go for it.
If this is a production system, you've just lost all Cisco support on that VM.
We don't support any method for root access other than reaching Cisco TAC, and they asking you to generate the root account for logs or to fix something. Any change under root access not directed by Cisco, will also turn your system into a not supported system. Obviously, creating your own root account, and making changes on your own, has the same outcome.
Since you're on VMware workstation, I assume this is only for lab/testing, as that is also not a supported platform.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...