rah215

It appears that i have it figured out. I just rebuilt the task sequence from scratch and it is working now. I have imaged one machine and running it on a second which is near completion, so it is looking positive. I am going to image a third just to play it safe. Best guess as to the cause is that the partition task, first step of the sequence, was not making the C drive the boot partition. I checked this multiple times based on the errors in the smsts log.

I am actually trying a legacy build now. All my current task sequences are geared towards UEFI devices. Fingers crossed.

I am trying to image some new laptops with a newly built Windows 10 EDU image. The image works, I have deployed it to other machines (including other E560s) without any issues. I am struggling with a group of these laptops that will not take the image. The error i get is 80070490, it cannot find a suitable partition. From WinPE, using Diskpart, I can write to and access the drive. I can see folders being created on the C: drive during the OSD process. But it fails pretty consistently, with a few exceptions that imaged fine. I have added new drivers for this configuration and still no luck. I've also tried PXE booting with similar results. Not sure what i am missing here. Anyone see this behavior elsewhere? If so, how did you get around it? Thanks. I am running SCCM Current Branch 1511.

We have removed the group policy deployment and manually entered the wifi config on all the laptops, there are a lot of laptops. Even after working with a few different vendors we still do not have an answer of why this happened. We have moved away from Radius authentication for our XP clients and working to do so with our 7 clients. While I don't have my answer the issue has been resolved.

We recently saw a large portion (if not all) of our Windows XP SP3 laptops lose their wireless configuration. The configuration was and still is pushed out via group policy. Hardwiring the laptop and running gpupdate /force does not re deploy the configuration. Running gpresult /scope computer /v shows the wireless config policy is being applied. RSOP shows that the wireless component is successful(no data). We are looking at two issues here the first is why were the settings lost in the first place and then why is group policy not deploying correctly to reset the configuration? I have ran Network ID, numerous gpupdates all to no avail. I am working with MS on another issue, may or may not be related, and they checked ADDS and said everything is fine, no errors. We are at a loss on this.