nry

I've only ever followed the guides on here, so we have one group for Win7, one for the Server OS, one for Office, one for SQL Server... Seems to work fine here.

We had that too...after I also then upgraded to SCCM 2012 v1511 it magically fixed itself...

Even on 1511 I am still getting this error...completely baffled! The network itself is file again, clients deploying OK with applications being deployed etc. but the SCCM Server continues with this error...

No just one domain, one SCCM server, it is now installing OK on clients again which is a good start after the 1511 update WSUS sync now seems broken too...the joys Chris

OK, upgraded SCCM to 1511 and still the same error except the client version is reporting the correct newer version, MP in the error is still being reported as the old version above...

The MP reports as the correct version the client is looking for, so why is the client seeing the wrong version?

Did you get this resolved? I'm having a similar issue myself.

Any ideas on my next step anyone? I'm going to try CU3 initially!

Hi all, We've been running in to a few weird issues recently, but I'm not 100% sure where they have come from. We updated SCCM 2012 to SCCM 2012 R2 SP1 about 2 months ago, and according to 'About' for SCCM this worked fine. This week, seemingly randomly as I have not changed anything on the SCCM Server (2008 R2), clients have stopped installing any software. We can still deploy the OS as before through PXE/MDT, Windows 7 Enterprise x64, but no software is hitting these machines or existing ones. The SCCM Client installs but then goes into a loop trying again every few hours. On a handful of machines I took some advice from other websites which seemed to fix it, but now nothing is working - the CCMCACHE folder stays empty, SCCM Console can see the new PC's but they are not listed as having the client. I did a little digging on the server and noticed it was doing the same thing with the SCCM Client trying to upgrade I presume from the SP1 update. It was failing so I did a manual uninstall, then used the Console to push out the Client and monitored the install logs. I see this error: The client version 5.00.8239.1000 does not match the mp version 5.00.7804.1000 The MP seems to be stuck on the pre-SP1 version - I removed this role and re-added it but the same error is showing. Can anyone advise on steps to try and troubleshoot and hopefully resolve this? We have a good number of new computers to roll out and we're rather stuck I debated going to the latest CU patch, but unsure if this is advisable or not and even whether this is the best initial approach? Thanks for any help, Chris

Anyone got an idea on getting Win10 to install to 'C' instead of 'D'? Thanks, Chris

I have the deployment working fine following this, however the OS installs to 'D' as opposed to 'C', any way I can change that? Chris

To confirm it is all back behaving as expected! Win7 x64 deployments working fine, Windows 10 deployment also working but I've not set these up within MDT further yet, just the base no-touch install.

I was barking up the wrong tree..no idea why but my previously working driver package for onboard LAN was not being detected during OSD - I sorted a new driver and voila, all fine

Hi all, I have got SCCM 2012 SP2 installed OK, ADK 10 (the original version) installed and MDT 2013 Update 1 all running, PXE boot is working as expected however with the new boot images, I am unable to insert the network card driver that we used previously. Our laptops need the driver available otherwise they boot and install with no network connection therefore no domain join etc. I am deploying Windows 7 Enterprise x64 SP1. Trying to add the original driver that worked on the previous boot images fails, the error suggests an unsigned driver but it is listed as Microsoft signed - is it perhaps more that the new boot images are Windows 10 PE based and need a different driver, or should I still be able to use the old one? There is no Windows 10 driver but I would presume this is not the right one - or should I still be using the old boot image for this deployment? Thanks for any reply, Chris

I'm not sure it matters...I generally test the upgrade then I don't need to worry about the uninstallation part...maybe I'm lazy

There are lots of comparison check options for installs...MSI is clear enough, if you do a script exe install then it is often about checking file versions or registry Uninstall keys for versions etc. Generally most stuff does upgrade OK...not always...but I personally have a virtual test PC or two and I'll throw the old package on, then send out the update - if it works then I can look at a larger rollout test before comitting to everywhere that needs it. Remove deployments of the old version, deploy the new one and for me that's it. My background with app deployment spans 17 years now...so generally there is a way to get most stuff sorted if you know where to look

Well I think we're all back and running! Refreshed the ADK to the older ADK 10 verison, deleted and re-ran the Windows 10 deployment guide on here and this setup the new boot images etc.... Need to run through the build in full, but my old Win7 deployment kicked off OK and it presented the Windows 10 too... In the end I had to run through this to get PXE back: untick the enable PXE checkbox on the distribution point. Answer yes that you want to remove the Windows Deployment service. remove boot images from your distribution point, then delete %windir%\temp check with server manager. If WDS is done uninstalling there is a reboot pending. Reboot. check if the remoteinstall folder is located on your system. If it fails to delete due to permission issues with the SMSTempBootFiles path, delete all folders except that one and then rename the remoteinstall folder something else. reboot Add the PXE point again by checking the box on the distribution point properties. Check the distrmgr.log and see if the remoteinstall folder reappears.. Replicate the boot image to the DP again. After they land you can try running an F12 and it should roll smoothly. Courtesy of: https://community.spiceworks.com/topic/628123-sccm-2012-r2-pxe-boot-fails-bcd-error-0xc98

And now an error installing the older ADK...SQL Server 2012 Express with an MSI error in C:\Windows\Installer....one step forward, one back

And typically I used the new (incorrect!) version of the Windows 10 ADK...so now installing the correct (older!) version...I hit the: Windows PE initialization failed with error code 0x80220014 Error It wasn't the NIC driver...

Well....typical SCCM fashion...I repeated the remove PXE then re-add PXE...low and behold it booted and gave me my task sequence choices! It failed which I think ids down to a missing NIC driver which I'll try adding in and see if that sorts it...but one step closer now!

I noticed you said you removed the MP and re-added it...will this affect anything else such as packages/applications etc.? Thanks, Chris

My keys are there and I have removed and re-added the PXE from the DP etc. and I still have the same issue...all getting a little frustrating now I have, for the sake of trying, ran through the Windows 10 deployment guide on here, it all went perfectly, no errors etc. but I can't PXE boot from that either, same error as always, 53, missing boot file....and those files are there

Still the same error though I believe the upgrade to the client is now complete according to the logs...it failed on a Silverlight dependency...strange.

Curiously, I checked the MP log and it says this: <02/22/16 14:24:32> Installing pre-req using command line "D:\Program Files\Microsoft Configuration Manager\client\ccmsetup.exe" /UpgradeWithServer:mp<02/22/16 14:24:47> Pre-req installer "D:\Program Files\Microsoft Configuration Manager\client\ccmsetup.exe" /UpgradeWithServer:mp finished with exit code 1 Then: <02/22/16 14:24:47> Failed to Install Pre Req CcmSetup. Return Code is 1 Does the CCM Client on the SCCM server itself need upgraded for the PXE to work again? It seems to be trying this before failing each time I try a PXE boot but I may be misinterpreting things.

OK, the boot images are now importing and distributing OK, I noticed that removing Windows ADK for 8.1 had left some of the folders behind and all I have done is rename them, leaving just the 10 ADK ones... However now, checking the SMSPXE.log I am getting the following, trying to PXE Boot a client results in this error in the client: PXE-E53 not boot filename SMSPEXE.log: Prioritizing local MP http://MYSCCMSERVER. SMSPXE 22/02/2016 11:30:05 10116 (0x2784) RequestMPKeyInformation: Send() failed. SMSPXE 22/02/2016 11:30:05 10116 (0x2784) Failed to get information for MP: http://MYSCCMSERVER. 80004005. SMSPXE 22/02/2016 11:30:05 10116 (0x2784) reply has no message header marker SMSPXE 22/02/2016 11:30:05 10116 (0x2784) Failed to send status message (80004005) SMSPXE 22/02/2016 11:30:05 10116 (0x2784) Failed to send the status message SMSPXE 22/02/2016 11:30:05 10116 (0x2784) PXE::MP_ReportStatus failed; 0x80004005 SMSPXE 22/02/2016 11:30:05 10116 (0x2784) PXE Provider failed to process message. Unspecified error (Error: 80004005; Source: Windows) SMSPXE 22/02/2016 11:30:05 10116 (0x2784) 38:60:77:8F:6C:68, D78C0F00-FE1A-81E0-2F8F-3860778F6C68: Not serviced. SMSPXE 22/02/2016 11:30:05 10116 (0x2784) File C:\RemoteInstall\SMSTemp\2016.02.22.11.08.18.03.{A9385315-B1C7-4B10-BC12-239B7CBDB84D}.boot.bcd deleted. SMSPXE 22/02/2016 11:38:24 11016 (0x2B08) File C:\RemoteInstall\SMSTemp\2016.02.22.11.08.18.03.{A9385315-B1C7-4B10-BC12-239B7CBDB84D}.boot.bcd.log deleted. SMSPXE 22/02/2016 11:38:24 11016 (0x2B08) It was all working nicely before SP2 Chris