Jump to content


JakWud

Established Members
  • Content Count

    3
  • Joined

  • Last visited

Everything posted by JakWud

  1. Good afternoon fellows! I'm currently struggling with an issue trying to get our Win 10 task sequence to take off. Just for background info, this task sequence works just fine on all other models that we have except this Acer Switch Alpha 12 tablet we're testing. Smsts.log is attached. -Problem is this: Boot the device into WinPE, select the desired task sequence, it begins to download the boot image and then fails. -Noteworthy errors: Failed to install boot image. Unspecified error (Error: 80004005; Source: Windows) Failed to install WinPE. Code(0x80004005) -Error log interpretation: Going through the smsts.log and looking around I thought this might be telling me that possible the boot image didn't have a driver for the SSD built into the tablet. -What I've done so far: Diskpart/format the drive with UEFI. Received and uploaded AHCI drivers from Acer into the boot image assigned to the task sequence/boot image. Looking forward to any and all input. Thanks! Jake smsts.log
  2. We're currently on CU3. We looked at the fixes in CU4 but didn't see any real fixes in there that would affect us greatly. I just took a look at the CU5 changes and it's looking like the same story as CU4 for our environment.
  3. Morning everyone! I've been working with Config Manager for a couple years now, but recently I've moved up to a role more responsible for computer images. I'm having some problems with the client apparently timing out during the final stages of an OSD task sequence. The image itself will download and apply with no problems, same with the drivers, but then the when it comes to initializing the client it will time out for ~30 minutes before moving on. When finally able to log into the system the client is fully functional and working properly. I've used my google-fu to the best of my ability, and have found several threads of others having this problem including one on this site. Some people suggest needing to create a group in AD named "ConfigMgr Remote Control Users" with no members associated. We've done this and it doesn't seem to have made any difference. I've attached the smsts log file that displays the error at the 8:40AM timeframe. Does anyone have any ideas that I could try? Thanks in advance Edit: Forgot to mention we're using SCCM 2012 R2 -Jake smsts-20150527-084015.log
×
×
  • Create New...