Sameul

Hi all, I have stuck in an odd scenario,I'm trying to deploy a task sequence to a tablet (clean SSD without OS installed). After winpe load completely it says "Windows is starting" then "Preparing Network Connections" after the 2 messages, client reboots.When the system center background appears hit F8 and run an ipconfig, find client cannot get ip address immediately and after several attempting it get an ip address then ping the sccm/ADDS server, return successfully. So NIC driver should be correct. What's the odd phenomenon is that when I try to deploy the task sequence to another tablet(with OS installed and joined in domain) it can get task sequence UI smoothly. Fail client log says "reply has no message header marker" "Failed to get client identity (80004005)".Attach log for your reference. What's portion missed? Hope your help and appreciate for any idea. BR. Will smsts.log

Hi, Use the "Test Connection" function to verify this and the account which I specified can access the share file successful. Reenter the password and deploy the TS,still get the same error,thus it may not be related. any idea?

Hi, Jorgen Another info.is that the task sequence can be deployed successful via USB media stick method.

Hi,giftedwon The client get IP from the DHCP server and the ip address should be in the range.However, I will recheck this point and feedback to you.BTW,what shall I do if IP subnet is not in the boundary?

Hi, Jorgen Many thanks for your hints. Does it means that the account have not sufficient privilege to get the specify file? or the account has wrong configuration. however, i use the domain administrator as network access account.I will recheck it and feedback tomorrow. Thanks.

has encounter same error code,bomb and wait for hint.

Hi all, The title is the issue that i encounter and its from the smsts.log attach the log file and hope your help! I will feedback this topic ASAP if you give any direction. Any help is appreciate. smsts.log

Hi all, I have two different platform device in my lab, one is Dell Venue 11 tablet which has UEFI BIOS and with CSM supported.it's a x64 architecture device. The other is a Dell Venue 8 tablet which only has UEFI BIOS, it's suppose to a x86 architecture device. i have create two collection called x64 and x86, I want to separate the two platform to the target collection by their architecture automatically,what variable should i use in the collection query option? Need your help and any advise is appreciate.

Rebuilding is a huge work,there is a very useful guide from anyweb in this forum you can refer to. however,for further use,it's worth to record your steps in the setup progress. good luck and hope feedback.

Hey guy, through above thread you have set it to “HTTP” and then --> In lab environment, there is a simple and valuable method to try:Turn off the firewall of your SCCM server and client. This just to check where the issue occur at the DP or server configuration and JUST IN THE LAB. hope help~~

Did your usb network card is a USB 3.0 device? try to replace with a USB 2.0 one or import your usb network card driver into your Boot Image.

Have success deployed win8.1 by ASIX/Realtek USB-LAN dongle on Dell Venue 11,please verify your task sequence firstly.

does your "HP DL380p" is tablet platform only with uefi supported? no legacy/CSM and 32-bit OS installed?

Hi topic owner, any feedback?

hi guy,I have same toy Dell venue 11 Pro with 32-bit operating system on x64 based processor and stuck in same issue with you. There should be two separated symptom you have. Scenario 1. screen flashes quickly when download NBP file in the UEFI PXE progress. -->the right behavior of this step should be "download NBP file successful" message (WDS Boot Manager)solid displayed and waiting for user to press enter key to continue the progress for this symptom:what your version of boot image? did you use the SCCM native contained(6.3.9600.16384)? If yes,update to 6.3.9600.17031 and try again.after that it works properly in my here. Scenario 2. the client don't download the right .wim file accordingly -->maybe anyweb's comments is the right point.Deploy both x86 and x64 TS to unknown computers collections should the root cause of this failure.Need separate the deployments using collections targetting the computer architecture firstly sorry for poor English and hope help!!