00thatcher00 Posted January 10, 2013 Report post Posted January 10, 2013 HI Guys, Wondering if you can help? We have just upgraded SCCM 2012 to SP1 and its broken our OSD deployment. After looking though the logs etc. i noticed its failing at the installation of the SCCM client. I can confirm the client package is the SP1 version. Once OSD task sequence has failed and the computer restarts, i can login to windows and it’s just a blank image with no SCCM client. If i try to install the client manually in windows it fails. During the manual install it installs Silverlight but fails on .net. Has anyone come across this or got any ideas? Many thanks Jamie Quote Share this post Link to post Share on other sites More sharing options...
Peter33 Posted January 10, 2013 Report post Posted January 10, 2013 Did you create a new package from definition for the client package after updating to SP1? Quote Share this post Link to post Share on other sites More sharing options...
00thatcher00 Posted January 10, 2013 Report post Posted January 10, 2013 Did you create a new package from definition for the client package after updating to SP1? It was already created after the upgrade but i also tried re-creating from the definition Quote Share this post Link to post Share on other sites More sharing options...
Peter33 Posted January 10, 2013 Report post Posted January 10, 2013 So i guess your base image has not .net4 installed. I would recommend to add it though. This also saves a lot of time during imaging. You can try install the client with /skipprereq:dotnetfx40_client_x86_x64.exe as a workaround. Quote Share this post Link to post Share on other sites More sharing options...
00thatcher00 Posted January 10, 2013 Report post Posted January 10, 2013 That is correct. is .net 4 not ment to be installed as part of the client? Quote Share this post Link to post Share on other sites More sharing options...
Peter33 Posted January 10, 2013 Report post Posted January 10, 2013 The client requires at least .net 3 as prerequisite. Check out the prereqs here. Quote Share this post Link to post Share on other sites More sharing options...
00thatcher00 Posted January 11, 2013 Report post Posted January 11, 2013 The client requires at least .net 3 as prerequisite. Check out the prereqs here. This is the line that got me on that page: 'If these dependencies are required to complete the installation of the client, they are automatically installed with the client software' but i think i found the issue: http://sccmfaq.wordpress.com/category/sccm-2012-sp1/ Looks like were gona have to wait to deploy any computers till M$ sort it out..... Quote Share this post Link to post Share on other sites More sharing options...
Peter33 Posted January 11, 2013 Report post Posted January 11, 2013 What a mess, jeez. I was reading about this problem today on here already. Lots of people had suddenly problems to deploy the client. Thanks lord i have not upgraded our production environment to SP1 yet. Quote Share this post Link to post Share on other sites More sharing options...
Rocket Man Posted January 12, 2013 Report post Posted January 12, 2013 Hey just seen this post.... I have just created a fully blown SCCM 2012 SP1RTM production infrastructure over the past 3 days. This was not an upgrade from non-SP1 it was a brand new install. I am having no issues with OSD and client installations. It works both via OSD and client push method. The clients are reporting back as normal as I can do all the normal stuff as usual like hardware inventories, RMC etc. Is this an issue that only occurs from upgrading an NON-Sp1 infrastructure to SP1 can anyone verify? I would be keen to know as I have 5 other non-Sp1 sites that I am considering upgrading. Thanks Quote Share this post Link to post Share on other sites More sharing options...
00thatcher00 Posted January 14, 2013 Report post Posted January 14, 2013 Hotfix has been released http://support.microsoft.com/kb/2801987 haven't tried it yet but hopefully it'll work. Enjoy! Quote Share this post Link to post Share on other sites More sharing options...
