This week I spend a whole week troubleshooting at a customer site why my CM12 secondary sites or remote sender capable DP’s would not have any clients that would be able to PXE boot and we didn’t see any issues in the monitoring pane or SMSPXE.log. On my secondary sites I have a Management Point Installed .
Looking a little deeper in the MPcontrol log file on the secondary site sever , it fails with the following comments in the logs:
… Further down in the log file :
In the eventlog you will find a lot of shannel errors too…
My SQL Database server is a two-node SQL Cluster, with SC-SCCM-CLUSTER as the name. In addition to the primary site DB, SC-SCCM-CLUSTER also hosts the WSUS database (WSUS is set up on the primary site server as it will have a SUP). The SQL cluster is Windows 2008 R2 SP1, and the SQL Cluster is a 2-node SQL Cluster 2008 R2 SP1 with CU4.
Things I’ve tried so far to solve my issue :
– Ensuring the SPN for the service account the SQL cluster is running on is correct.
– Look that my custom ports where listening correctly a Kent Agerlund described in his blog post here (http://blog.coretech.dk/kea/installing-a-secondary-site-with-non-standard-sql-port/) .
Digging further in to it , I have found the solution . Apparently there is an issue with the SQL 2008 R2 Native Client .
What is the version of SQL Native Client on the Secondary site? Right SQL 2008 R2 .
We have seen some issues with a SQL 2008 R2 Native Client talking to a cluster on the SQL technet forums. If you are using the R2 SNAC, remove from the Secondary site and install the SQL 2008 SNAC ( the link to the download : http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=16177 ) and the issue will go away!
Stop your Configmgr 2012 services and go to control panel and uninstall SQL 2008 R2 native client as shown below
Install the SQL 2008 Native Client and reboot as shown below :
Reboot your server and go into the MPcontrol.log . You will see the server talking correctly :
Now PXE boot works , but also your Management Point .
Hopefully Microsoft sorts this out pretty quickly …
Hope it Helps ,