HEHS_Matt

This board, as it turned out, required a BIOS update to build. Strange, since it built on SCCM RTM just fine, but SP1? No dice. It's a fiddly update as well. They obviously have quite an old BIOS on them already, since I have to upgrade to two intermediate BIOS revisions before I can apply the latest. And then, I have to remove the BIOS jumper and the BIOS battery to apply the last stage. Bit annoying, since I've now got to do that on another 120 workstations! I've found a working Driver for my Broadcom NIC on the other Intel board as well, so for the moment I'm cooking on gas again. Task sequences are running, drivers are installing and whether or not I needed to re-install, I now have a much cleaner and well organised SCCM installation (since I was an early adopter, and the best practice guides have improved somewhat since I first installed). In conclusion, what really did me over was not the SP1 update itself, but the Windows PE update - this is the bit that caused my machines to stop doing what they used to do during builds, and is the bit that has required me to look at BIOS updates and re-assess my driver library to cope with the change. Given more time (and a clearer, stress-free head) I may have figured this out without the need to rebuild completely, but at the time it seemed like the problems were crawling out of everywhere, rather than being focussed on one elements of SCCM. Either way I'm happy. Clean SCCM install, successful Task Sequences. Now back to re-importing all my applications... -M

So I rebuilt my SCCM server - fresh install, same Site Code. All my existing clients are popping back up on the new console so that's great! Unfortunately, I'm still having exactly the same build issues as before so this has been a completely fruitless exercise! Oh well, back to the drawing board... VMs build fine. DH61WW motherboards build, install drivers, but fail to join the domain during the TS. Tried multiple driver versions, same old story. DG41TX motherboards I can't find a working Broadcom driver for at the moment. The fact the VMs build fine suggests there's no underlying SCCM issue. It can only be a combination of network infrastructure/BIOS/drivers on the affected machines, but I'm blowed if I can make any progress. At present, I still cannot deploy an OS to any of my computers anywhere. Gah...

Nope. After much tail-chasing, I am today starting the process of trashing my SCCM servers and building them again from scratch...

From WIM files. I tried to create a new Windows 7 image from scratch after these problems started occurring, but the build and capture task sequence failed as well. Right now, I'm stuck applying the only image that is available to me...

Thank you both for your comments. I think I've decided that, given the multitude of problems I'm facing and also the lack of patience I have in attempting to fix them (!!), I'm going to attempt to get every workstation on the network to a 'working' state before I flatten SCCM and start again. jkirshy - thank you for the info re: site code - that was one of my primary concerns, whether or not the clients would report back to a 'new' SCCM site if it had the same code. Thanks again both - I'll let you know how I get on! -M

I'll try adding the CU2 update to the client into the task sequence and seeing what difference that makes. They're all generic unbranded machines here... Mostly Intel boards (DG61CR, DG41TX, DG41RQ, etc.) with standard components. The ones that gets stuck in provisioning are an MSI H61M motherboard, with an onboard Realtek NIC.

This is a brand new task sequence I created after I installed SP1/CU2, referencing those original packages. I haven't installed R2 - just SP1 with CU2... Although if R2 makes RTM before I've solved these problems, I'd be tempted! The client version currently being installed is 5.00.7803.1000, which is the SP1 one. There is an update to this client for CU2 (taking it to minor version 1300) but I haven't managed to get that installing as part of the task sequence yet. Mostly cos I'm having so many other problems with the rest of the task sequence... I've got the registry keys that get me out of provisioning mode, but since this is only affecting select models of workstation, I'm not sure I want to put them in our catch-all task sequence. Although I suppose it can't do any harm...

Hi folks, I'm coming to the end of my tether with my SCCM installation since I installed SP1 and CU2... Until three weeks ago, I had a perfectly working installation. Workstations would build, software would distribute, everything was rosy. I decided to install SP1 to add support for the Windows 8 devices that are beginning to creep onto my network but, frankly, since then everything has been a complete disaster. I have a catalog of errors trying to build machines now - some apply the OS image, but then never install any packages from the Task Sequence. Some run through the task sequence completely, installing everything, then fail to show up as a client in the SCCM console. Some that worked perfectly before SP1 now fail to join the domain half-way through the task sequence and therefore cannot complete the job. It should be noted that this is the same task sequence in every case. Today, I'm finding that the few machines that were building successfully post-SP1 are getting stuck in provisioning mode, never adding themselves as clients to the console (despite successfully installing the client package) and therefore not picking up any additional assignments. I'm running out of places to look and logfiles to check for clues, and I'm not sure how many more 15-hour working days I can cope with before I go into some sort of meltdown... So I'm beginning to think that it might just be an easier job to destroy SCCM completely and re-install from scratch. What are the caveats of doing this? Is there best practice? Would I need to carefully scrape out the remnants of my current SCCM installation from AD (or anywhere else for that matter) before I go about doing this? Obviously, if anyone has any great ideas about what might be causing my strange range of problems instead, suggestions for that would also be most welcome but I'm figuring that for my own sanity, I'm probably going to have to start from sratch. Thanks in advance, -Matt

UPDATE: Actually, it would appear that software *will* deploy to completed workstations, although it would appear to be a bit hit and miss at the moment... Still no joy on task sequences though.

Hi folks, I'm having a huge amount of trouble with SCCM since I upgraded my system to 2012 SP1 and CU2. Since I installed these two updates, I can no longer successfully install any applications during a task sequence. It would also appear that I get the same errors when attempting to deploy software to completed machines. I have tried re-creating the task sequence from scratch, but the same errors occur. I have tried creating a brand new application and putting that in the task sequence, but the same errors occur. The SCCM admin console shows that the site has green lights across the board for site status and component status. The smsts.log file gives me the following errors for each application in turn: --- Execution status received: 16 (Application failed to evaluate ) Installation failed Install applicaiton action failed: '[application name]'. Error Code 0x80004005 --- Full logs attached. Similarly, the deployment status for applications in the Admin console shows errors on deployments as: Evaluation failed [application name] Error 0x80041013 Provider load failure Any help greatly appreciated - I've been staring at this problem for three days straight without getting any closer to understanding what's going on... MANY thanks in advance, -Matt MP_logs.zip