Removing Old Broker Server from SQL Server
Article ID: 431193
Updated On:
Products
Issue/Introduction
After migrating Harvest to our new server, and once we are satisfied with the new Broker Server, how do we disconnect the Old Broker Server from the SQL Database? At this time, I can still connect with both broker servers to the SQL Database Server. I can stop all the services, etc., but if the old server gets rebooted a user can log on. It usually takes a month or so to decommission an old server.
Environment
Harvest Software Change Manager all versions
Windows Server OS
Resolution
There are 2 things you can do.
The quick and easy one is, on the old broker machine, open the Windows Administrative Tools -> Services window and go to the properties for the "CA Harvest SCM Broker" service. Change the "Startup type" to "Disabled". That way, if the server reboots, the broker service won't automatically restart. If you have a "CA Harvest SCM Agent" service, do the same with that one.
The other option is to go to Control Panel -> Programs and Features and uninstall all "CA Harvest Software Change Manager" components. With the software removed, it cannot then be used by others trying to login to the wrong broker machine.
Additional Information
Note: The Harvest broker hostname is not found in any table in the Harvest database, so no need to update the database to remove the old broker server.
Feedback
