pluecking Posted October 31, 2013 Report post Posted October 31, 2013 Same problem here. Nothing works. Uninstall Forefront ist not an option or a solution. Quote Share this post Link to post Share on other sites More sharing options...
Clientmgmt.de Posted October 31, 2013 Report post Posted October 31, 2013 Same problem here. Nothing works. Uninstall Forefront ist not an option or a solution. Do you have a virus scanner enabled on the site server? If I were you, I would try it out. Quote Share this post Link to post Share on other sites More sharing options...
Patrik_B Posted October 31, 2013 Report post Posted October 31, 2013 I had the same WDS crash but installing wimgapi.msi from the Installfolder\Microsoft Configuration Manager\wim\ (NOT from the install media for R2 which didn't work) solved it for me. One reboot later and it's all on and working again. Running it on Server 2012. Quote Share this post Link to post Share on other sites More sharing options...
KrisO Posted October 31, 2013 Report post Posted October 31, 2013 yeah I tried C:\Program Files\Microsoft Configuration Manager\wim\wimgapi.msi and that didn't work for me. I also tried uninstalling System Center Endpoint Protection and that did work... I'm getting " Configuration Manager is looking for Policy" then it "PXE Boot Aborted. Booting to Next Device..." Which is alot better which means it's responding and I can work. My with this solution is that Endpoint will probably install it self again and PXE will stop working. But I'll follow up on how it goes. Quote Share this post Link to post Share on other sites More sharing options...
D3w4yne Posted October 31, 2013 Report post Posted October 31, 2013 Removing SCEP had no affect for me. Quote Share this post Link to post Share on other sites More sharing options...
KrisO Posted October 31, 2013 Report post Posted October 31, 2013 OK, so SC Endpoint Protection re installed itself automatically and it broke PXE again. While it was working I was able to image a computer. I've created a Case with Microsoft already. So I'll keep you informed. Quote Share this post Link to post Share on other sites More sharing options...
linkztream Posted November 4, 2013 Report post Posted November 4, 2013 I got WDS to not go belly up when I changed the WSUS application pool to use .Net 4 instead of 2.0 Quote Share this post Link to post Share on other sites More sharing options...
D3w4yne Posted November 5, 2013 Report post Posted November 5, 2013 Mine was already set to .Net 4.... Glad you found a fix though. Quote Share this post Link to post Share on other sites More sharing options...
D3w4yne Posted November 5, 2013 Report post Posted November 5, 2013 Uninstalling the console worked for me.... It was mentioned in another thread on this forum. Apparently MS is suggesting running a PXE enabled DP on another system as a temporary work around. 1 Quote Share this post Link to post Share on other sites More sharing options...
sccduck Posted November 6, 2013 Report post Posted November 6, 2013 Uninstalling the console worked for me.... It was mentioned in another thread on this forum. Apparently MS is suggesting running a PXE enabled DP on another system as a temporary work around. After trying all of the other suggestions in this and other threads this worked for me. Uninstalled the management console and rebooted - Removed PXE and WDS and rebooted - installed WDS and rebooted - Initialised WDS and set the reminst path - Enable PXE on the DP. I also removed a customised boot image from some of the task sequences and used the default x64 one. Thanks D3w4yne. Quote Share this post Link to post Share on other sites More sharing options...
