I'll suppose you are running 11.00 or 11.20, since you don't mention any version. If you have moved the QMS (QlikView Managment Service) to another server and has it running properly, you should be able to safely uninstalling the QMS (which contains the QMC) from the first server, using the QlikView Server installer package, like Rajesh mentioned above.
A configuration management tip; the QVPR (which is the QMS database that keeps Publisher tasks amongst other things) is per default resident on the same machine as the QMS is running on. Make sure to backup the content of the QVPR folder (C:\ProgramData\QlikTech\Management Service\QVPR) on a regular basis, for disaster recovery purposes.
Another tip is to make absolutely sure to never have two or more QMS services running at the same time, pointing to the same QDS or QDS Cluster, or sharing the same QVPR database path, since they will "fight" over the workorders.
Sorry - I should have mentioned that it is running 11.00, soon to be upgraded to 11.20.
Good point about not running more than one QMS Service. The recent move of it was to a Virtual Server, such that we now have the inherent resilience of virtualisation on multiple physical hosts without running more that one QMS. It could be argued that QMS is not critical to QlikView End Users, but we store Section Access data using the QMS in Users | Section Access Management | Section Access Tables, and without it any reloads using it would fail.
Another good point from you about backing up the content of the QVPR folder (C:\ProgramData\QlikTech\Management Service\QVPR). The whole sever is regularly backed up & replicated, but a daily scheduled copy of this folder to a backup area on one of our physical QV servers would give us more belts & braces, and following your suggestion I intend to do that.
Well, the QMS scenario in 10.00 is basically the same, so yeah. The only thing that might be an issue with Section Access Management, is when switching the QMS from one machine to another, the URL to the SA mgmt page will change, right? This means that you will have to change the URL in the scripts to point to the new and correct one.