Search the Community

Hello all. During OSD my task sequence is failing with error code 0x80004005 at the very end of "Apply Operating System". The attached smsts.log (smtsprobook) seems to indicate something funny going on with partitions? Test Systems: 1. HP Prodesk 400 G3 SFF 2. HP Probook 430 G3 History: I have created a task sequence for deploying Windows 7 Enterprise X64 w/ SP1. This task sequence works great for the HP Prodesk. No issues at all. Task Sequence Steps (in order): Capture Windows Settings Capture Network Settings Install Operating System Restart in Windows PE Format and Partition Disk Apply Operating System Apply Windows Settings The rest doesn't really matter since the task sequence is failing at "Apply Operating System" (On the HP Probook 430 G3) This issue only occurs on the Probook (laptop) and NOT the Prodesk (desktop). The way we are managing OSD here at my company is to have a "Golden" Task Sequence, then just copy that same task sequence for as many different model of systems we have and insert the corresponding driver package as well as rename the task sequence for whatever new model we discover we have or receive. So we received our new shipment of Probooks (laptops) and I did what I always do when we get a new model. I grabbed the Windows 7 drivers for it (Note: These systems come with Windows 10 installed. Our image is Windows 7 Enterprise x64 SP1.) and created/copied a task sequence for the new model by simply switching out whatever driver package was in the task sequence that I just copied with the correct package for that model (a lot of this is irrelevant since again, the task sequence is failing at "Apply Operating System" before it even tries to install drivers.) Things I Have Done: Made sure all content called for in the task sequence is on the DP Deployed the TS as Available (PXE,Media,Blah blah) to All Unknown Computers Read through the provided smsts.log and could not make sense of it. Seems error 0x80004005 is a "beat around the bush" error Created a task sequence from scratch then tested. Still same issue at the same place Thought maybe its an issue with my .wim but I dont think so as this has worked on some of our other models tested Came here for help I am at a total loss as of where to start to troubleshoot this error. Most of the info you will need to help asses the issue is probably contained in the log(CMTrace it). Please let me know of anything I left out that could help. Thank you! smtsprobook

System discovery is finding objects in active directory but they aren't showing up in the console under any collections. I have a CAS and 2 primary Sites.

Question for all the SCCM 2012 R2 Admins: Basic overview: In an attempt to get a customers patching working correctly, I recently remoted in to find critical warnings at every turn. I was able to resolve the storage issue by expanding the drive size. I was able to resolve the sccmadm access errors by having the customer reset the password for that account ( I do not have that ability as a contractor for them) I had to stop/delete/remove all applications/packages/and process that were "hung" due to the storage/access issues. Here's where things get a little odd: I went to remove the SUP role for reinstallation and within 6ms of doing so, the server started showing the below message in the Event Viewer along with nearly every CM log: Login failed for user 'DOMAIN\SCCM2012$' Reason:Could not find a login matching the name provided. [CLIENT:<local machine>]. After a thorough investigation, the problem was located and it appears as if the NT Authority\System account no longer had access to the CM Site DB. Upon adding the NT Authority\System account back in, the errors stopped and all service started back up. The problem here is now, that the customer is telling me this was caused by removing the SUP role and they are not willing to pay for the time to resolve that particular issue. I have never seen this issue before? Could this account have been removed some time ago and the call to remove the SUP role have initiated the NT Authority\System account for removal then noticed it was no longer there? If I understand correctly, the removal of a system account would need domain admin/DBA permissions which neither I, nor the local system account have. Any thoughts as the why this error presented itself during the uninstallation of the SUP role? This has turned into the customer pointing fingers at me, most likely, due to an issue they created for themselves at some point in time.... Thank you in advance for your time and the sharing of your knowlede.

I am trying to query the computer name and user's department info using one query. If possible, let me know. Thanks