Client Install Errors

Question

I'm testing deploying SCCM 2012 to SCCM 2007 clients.  The install works in the end, however both clients I've tested have both generated this same error:
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile: C:\Windows\CCM\SCToastNotification.exe . Error code = 0x8007000b 
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile: C:\Windows\CCM\SCToastNotification.exe.config . Error code = 0x8007000b 
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile: C:\Windows\CCM\SCClient.exe.config . Error code = 0x8007000b 
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile: C:\Windows\CCM\SCToastNotification.exe . Error code = 0x8007000b 

Answer 1

It
doesn't seem to happen on 2012 servers.  My guess is it's because the 2008 R2 boxes only have .NET 3.5 / 2.0.  I've seen some people mention that SCCM 2012 client requires .NET 4.0, but that doesn't seem correct based on documentation I've read
and the fact that despite those errors the client installs successfully and appears to work.
ConfigMgr 2012 clients *DO* require .NET FW 4.0, which is automatically installed by ccmsetup (if not detected)
http://technet.microsoft.com/en-us/library/gg682042.aspx
A similar issue as yours, is described here:
http://sccmfaq.wordpress.com/2014/02/12/sccm-2012-sp1-cu4-client-update-fails-on-windows-server-2003/
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)
In that case, do I need to worry about pushing out .NET 4.0 prior to deploying the client?  I'm assuming I can not worry about it and it will just install whatever it needs automatically.
Also, if I'm reading that correctly it only installs .NET 4.0 if you don't have a .NET 2.0 or 3.5 profile.  Servers with the errors I provided already had .NET 2.0/3.5 profiles.