The official blog of the Microsoft System Center Configuration Manager Product Group
Updated 7/15/2013 - We have released a hotfix that resolves this issue. It is available for download here: http://support.microsoft.com/kb/2867422/en-us. Please follow the instructions in the KB article to install the hotfix.
Updated 7/5/2013 - see manual cleanup procedure
Updated 7/3/2013 - see workaround #1
We have confirmed an issue with Cumulative Update 2 (CU2) for System Center 2012 Configuration Manager Service Pack 1 that affects new secondary site installations.
This issue does not affect upgrades of existing secondary sites, or any other aspects of the Configuration Manager hierarchy.
The ConfigMgrSetup.log file will contain errors similar to the following after an installation attempt:
INFO: SQL Server Script: Creating object spupdatemessageactivity~
INFO: Configuring database replication tables..
*** [Microsoft][SQL Server Native Client 11.0][SQL Server]Object 'PullDPResponse' does not exist : spConfigureReplication
ERROR: Failed to execute dbo.spConfigureReplication.
ERROR: Failed to configure SQL Server replication tables.
You can use either of the following workarounds to install a secondary site.
You should be able to deploy the secondary site on a clean machine now.
If the secondary site installation has failed, you will need to manually clean up the following before you attempt to reinstall. To do this:
Note: you still need to apply the Cumulative Update 2 on your secondary site after the installation.
We will update this blog entry with additional details when available. Thank you for your patience.
--Configuration Manager Sustained Engineering
This posting is provided "AS IS" with no warranties and confers no rights.
Thank you for response!
I will try secondary workaround :)
Thank you very much
Can you confirm this is working?
Yes! Fully working now. (5+ secondary sites are installed in our hierarchy)
There's a different issue after applying CU2 that affects those that have multicast enabled on DP before applying. CU2 fixes the multicast issue where OSD multicast wasn't working if it started when in Windows OS. PXE / boot media it worked fine. CU2 fixes this. However there's an issue that wasn't covered on the CU2 install steps. If you have multicast enabled on DP, apply CU2 you will find that multicast now doesn't work in PXE / boot media or Win OS either. This is because applying CU2 breaks the connection of the multicast account and SQL server. If you go to DP and Multicast settings then check the account used for Multicast then "test connection" you will find the connection to the SQL server and multicast account is broken. You must re-add the multicast account password and then "validate" and "test connection" to SQL server on the DP. Then OSD multicast will work as expected after CU2 in PXE / Boot media and Win OS. I have confirmed this both in my isolated test lab and our production environment. It would have been good to know this up front as it took some time to figure why multicast was not working in any form after CU2. It was because a re-validation of the multicast account to SQL server on the DP setting was required. I hope this helps someone
@Leo Bounds. Thanks for the report. The issue is actually not specific to CU2. It unfortunately happens every time the MCS.msi gets updated. A KB would be good until we can resolve it.
I have attempted the above proceedures with NO luck looking for additional assistance.
@Leo Bounds, we have just published a post for the multicast issue here: blogs.technet.com/.../known-issue-update-to-mcs-msi-fails-to-upgrade-the-multicast-configuration.aspx
Thank You, Terima Kasih!