I was just curious if anyone knew if the bug identified in this kb VMware KB: After making a change or restarting Single Sign On server system, vCenter Server 5.1.x fails to start has a clever work around for it. I have noticed migrating virtual center across a couple different platforms causes this scenario. I was thinking about writing a script to execute when it moves, but that seems like a temp solution. Does anyone know if the threshold being exceeded per the document can be set manually?
This is a rather annoying bug for the systems we field.