Jump to content


thamoomin81

Established Members
  • Posts

    6
  • Joined

  • Last visited

Recent Profile Visitors

2,579 profile views

thamoomin81's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. This is the issue really, usually when I have had a task sequence fail in the past it has failed while in WinPE with a specific error message/code, I can then F8 and check ipconfig etc but this is just failing and rebooting into Windows 10 with no drivers installed. This is looking like another NIC issue the more I look at it, tbh I just wanted someone to check the smsts.log to see if I was missing something. What was also making me think it was not NIC related was that for example the Lenovo laptop I had downloaded the SCCM package, which I would hope had the correct NIC drivers. Thanks for the input, I'm going down the path of NIC related and will try some different driver versions.
  2. Apologies, the model laptop for the log I attached was HP 400 G3 DM, not G4, it was the G3 model I tested it on and it does correctly find the driver package, it even downloads the drivers, they are in the _SMSTaskSequence folder. Expand a string: SELECT * FROM Win32_ComputerSystem WHERE Model LIKE "%HP ProDesk 400 G3 DM%"
  3. Wondering if anyone can help, I have recently upgraded our SCCM environment to allow for us to start deploying Windows 10, I have created the Windows 10 image and imported it into SCCM and created the deployment task sequence. The issue I have is that I have tested a deployment on two different devices (Lenovo L470 laptop and HP 400 G4 DM), both appear to fail at the same point, from what I can tell from the smsts log (attached) just before joining the domain and installing any applications/packages, I can see no obvious red flags in the log, just a mention of not being able to release the task sequence related to the Windows image (BRS0007E) but this is further up the log, pretty much every other task sequence I have had failed in the past has been related to the NIC driver but there are none of the usual error messages and this task sequence isn't failing mid-way, the O/S reboots and boots up into Windows 10 but with no drivers or applications/packages installed and also not joined to our domain. If someone can please take a look smsts.log to see if I'm missing something glaringly obvious. Details: SCCM 5.0.8412.1000 - Client 5.0.8412.1307 - ADK 10.1.14393.0 - Windows 10 1607 image Thanks smsts.log
  4. Update for anyone else having the same problem, I have resolved mine, I amended how I applied my drivers from Auto Apply Driver to Apply Driver Package, it appears it was the NIC driver causing the problem, I can only assume it was possibly picking up another version of the driver from my other HP laptop driver packages but I did break those down with WMI queries so not sure how it could, I changed it to Apply Driver Package breaking them down again with WMI queries so it picks up the correct package and this appears to have resolved the issue.
  5. Thanks for the reply I.hv.yang, I dont think that is related to my issues but thanks anyway, my latest TS has no applications or packages in it so I'm quite sure that is not causing the issue. Just to update, reading the logs some more (actually found the config. manager trace tool which is majorly helpful in tidying things up), there is a description next to the error code of 0x80004005 of Task Sequence Manager could not release active TS request if that is any help.
  6. Hi, Wondering if anyone can help, we have created a Windows 7 x64 OSD task sequence for deployment to our laptops which has been working perfectly up till now, I have managed to deploy the task sequence via PXE to 4 different laptop models but I'm having issues with a HP Pro 6560b laptop. It is coming up with error code 0x80004005, it finishes the task sequence but doesn't carry out a number of the task sequence tasks which include not adding the laptop to our domain and not installing any of the applications, but it is installing two packages I have created for VMWare and Java Run-Time which happens to be the last steps on the task sequence. I have read around and tried a number of things including removing the driver package and re-adding and removing all the steps to install any applications or packages so the task sequence is just bare bones, no applications or packages being installed. I have attached the smsts log, if anyone can take the time to possibly read through the log and point me in the right direction I will be grateful. Cheers, Ross PS: I'm new to SCCM so still very much learning. smstslog.txt
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.