Vmware syslog Collector Disabled(Error)

Ah, the dreaded IP address change to critical server services...  What should be a relatively simple process that inevitably results in something important breaking. 

Now, you could uninstall the service and try to re-install hoping that the new settings will replace any existing settings; but sometimes that doesn't work and there's little satisfaction in fixing any issue in this way.

If you need to review the installation options, here's the link: VMware's installation reference 

The first place to change the IP is in the vmconfig-syslog.xml configuration file.  On Windows 2008 R2, the .xml config file it is stored at c:\programdata\vmware\vmware syslog collector\

Once open, change the IP highlighted in yellow to the one you need.
Note: The items in orange allow you to set log size and rotation

Now this is only half the story, the rest of the plugin configuration is stored in the vCenter SQL Database.
Find the VPX_EXT_SERVER table - this contains the syslog plugin config

Open the table in edit mode, edit the row highlighted in yellow with the IP address you entered in the vmconfig-syslog.xml file earlier.

It should look similar to this...

Save your changes and open the services MMC, find the 'VMware VirtualCenter Server' service and restart it.

Now open the vSphere client and log back in, the home workspace should now display the 'Network Syslog Collector' plugin.

Click the plugin to check the settings

Remember to update the syslog.Global.logHost settings on each host to the new IP address.
Now open the file browser to the log file location and make sure your Hosts are checking in.

Now the syslog collector should be back in business!