Ivan,
The risk is that, on ConfigMgr 2012 RTM (no Service Pack), that upgrading to Windows Management Framework Core 3.0 would cause ccmeval.exe to break WMI and the ConfigMgr client. There are some workarounds for this, but I would just hold off on deploying WMF 3.0 until after you've performed the SP1 upgrade on all of your clients. http://trevorsullivan.net/2012/11/21/configmgr-2012-ccmeval-exe-causing-clie nt-corruption/ Cheers, Trevor Sullivan From: [email protected] [mailto:[email protected]] On Behalf Of Lindenfeld, Ivan Sent: Monday, January 6, 2014 5:55 PM To: [email protected] Subject: [mssms] DBAs say no to WMF 3.0 upgrade on clustered SQL, upgrading SCCM to SP1 What is the consequence of not upgrading to WMF 3.0 on my clustered SQL Server 2008 R2 before upgrading SCCM 2012 to SP1? Thanks. Ivan Lindenfeld Sr. Systems Engineer Enterprise Deployment / SCCM Fidelity National Financial | Jacksonville, Florida [email protected] <mailto:[email protected]> | 904 854 8178 Team email: [email protected] <mailto:[email protected]> Teamsite: Enterprise Deployment / SCCM <https://teamsites.fnf.com/sites/technology/apps/sccm/Pages/default.aspx>
