Just a heads up, in Service Manager 2012 SP1, we made certain changes to custom actions in setup which renders fresh installs of the secondary management server incapable of connecting to the Management Group. This issue was first surfaced in a blog post at http://shaunlaughton.wordpress.com/2013/03/07/service-manager-2012-sp1-secondary-management-servercannot-set-availability-on-a-health-service-that-doesnt-exist/. Please read this blog post for a detailed explanation of the problem.
Once again, this issue ONLY impacts SCSM 2012 SP1 new installs. It does not impact those customers who are either upgrading from Service Manager 2012 RTM, or are installing only the primary management server. The recommended workaround to address this issue yourself is to install System Center Service Manager 2012 RTM and then upgrade to SP1. If for any reason you are unable to do this, please reach out to support so that they can provide assistance.
Update: A hotfix for this issue has been released. If you are blocked by this issue please call support and they should be able to get you unblocked.