Joohan

Yes, so far that's been the case... However, by limiting the available Resources (CPU), as described above, it works in most cases - that behaviour is binary... 2 CPU == 100 % failure, 1 CPU == 80 % Success....

We run tests on Hyper-V; SCCM single server setup and a few clients on one subnet, nothing fancy. However your question made me think – we use several of these test environments on various hardware with different level of performance (different CPUs, mechanical HDD in some cases, SSD in others). I realized that the high performance environments where more impacted, one in particular. On that system we had 100 % failures. Our test clients typically have 2 CPU an 4 GB RAM; when I changed that giving the client only 1 CPU and also reducing the “Virtual machine limit” to 75 % it all started to work. Obviously something is going to fast when Powershell / DotNet is loading….. Of course this isn’t of much help IRL, the issue is still very much alive…..

Thank you, bootable media working at two locations (I have no delays by the way) is the first consistency I've seen so far... And now we wait!

I just realized that if I create bootable media (iso), as opposite of distributing them over PXE, my images works just fine. Can anybody else suffering from the issue confirm this? Next question is of course why, but it will narrow the possible causes down a bit….

I have the same problem and I followed Brandons advice to the letter...

"any applications deployed to the All Systems collection and with the Allow this application to be installed from the Install Application task sequence action instead of deploying it manually setting set in the applications properties will appear in the list." - deploying to All Systems means the applications will show up in the Software Center on each and every computer, right? Instead I created a new collection, named it "MDT Applications", set it as Application Catalogue, and deployed my "cool apps" to that - this seems to work fine, but I'm curious whether it is a recommended solution??

No big deal, but perhaps it can save somebody else some time? Everything worked according to instructions - except that the language pack (sv-se) wasn't installed... Turned out I used an old lp.cab file from pre-SP1 days, once it was replaced with the correct one - Voila, right on! And, of course, a big thank you to you Niall!!

Perhaps somebody can help me to figure this out? I have a Task Sequense that suddenly stopped working. It was last used about a week ago, without any issuses. Yesterday evening, after a week on the road, I tried to reinstall my notebook just to learn that it now fails resolving dependencies. (0x8007000E) I have attached the smsts.log file, I have tried googling the error but that didn't help :-( smsts.log

It can’t be said enough: Anyweb for president! I’ve now been playing around with SCCM 2012 RC for a couple of weeks and have a few things to say and ask….. My setup is more or less according to Anyweb’s instructions, except that I use a stand-alone SQL 2008 R2 for both SCCM and WSUS – haven’t had any problems with that I’m happy to say. I have also configured it to run in “Native” mode and published the whole thing to the web using TMG and SSL-bridging; even that works, updates as well as software are applied to an outside notebook. The deployment service is still a constant source of annoyance; every time the server is rebooted I have to revive it according to the “Nooblar-method”, un-checking, re-checking the pxe-box; just found out that omitting password protection might help thou – will try that? I have now stumbled in to a “build and capture” problem; my goal is to install Office 2010 and IE 9 during the process and can’t for my life get the TS to install any updates after the packages have been applied. If I run a B&C straight up according to instructions in this lab everything works fine. It seems, however, that whatever software installation I put in will cause every attempt to install updates to fail, any tip on that would be highly appreciated?? Again thanks for this source of facts and inspiration!

Actually having a folder named "boot" tells me you installed the wds service from the server manager, if installed by checking "PXE" on the DP you don't (at least I don't) get such a directory at all? Instead you get a similar set of folders all starting with "sms", i.e. "smsboot" etc... Furthermore these folders don't get populated until you successfully distribute yout boot-images to the DP. I think, as stated in an earlier post, that the trick to get pxe running after a server-reboot is to toggle the pxe-checkbox (2x apply) and then manually start the wds-service; problem is that until you redistribute you boot-images the reminst-folders will be empty :( Very annoying I also had some trouble having an too up-to-date-image with DotNet 4 already in it - took care of that running c:\.....\aspnet_regiis -i -enable