Jump to content


anyweb

How can I deploy Windows 10 with MDT 2013 Update 2 integrated with System Center Configuration Manager (Current Branch)

Recommended Posts

I am stuck on PXE-E32: TFTP open timeout error. I have been following all of the steps listed as I setup my new CM 1702 and everything seems to be working but I cannot get PXE Boot to work. I double checked that option 66 and 67 are set on the DHCP server and that there isn't a firewall blocking. I even went so far as to install a graphical TFTP client on both my own workstation as well as on the server. I attempted a simple GET command and it results in a connection failed. Something seems to be blocking TFTP but there isn't much to go on. The SMSPXE log seems to indicate that WDS is starting properly so TFTP should be starting with it and TFTP seems to be the only thing listening on port 69 of the server. Is there anything else anyone can suggest for me to check?

Thanks,
Chris

Share this post


Link to post
Share on other sites


I found my issue after a ton of searching. This thread (https://social.technet.microsoft.com/Forums/ie/en-US/a1246f62-6a8a-482b-9323-7e02dfeab196/wds-tftp-errorcode-1460?forum=winserversetup) had the answer. I was getting a TFTP error 1460 which is a timeout and it turns out that a limitation in the block size for files being transferred via TFTP was what caused my issue. This seems like the kind of thing that others would run into so I will post the actual change.

On the PXE Boot DP/MP you need to make a change to the following registry key and then restart the Windows Deployment Service in the Services MMC snap in.

Location:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\WDSServer\Providers\WDSTFTP
Name: MaximumBlockSize 
Type: (REG_DWORD) 
Value range: 512–1456 
Base: (Decimal)

I have experimented with 512 and 1024 block sizes and they both seem to work however my guess is that 1024 will produce faster results when imaging. I am pulling my first image for Windows 10 using PXE Boot but unfortunately I don't have a local DP setup to handle the files so the whole process is being strung out through my WAN. I hope to get a test DP in my location later today so that further testing can move along much faster.

  • Thanks 1

Share this post


Link to post
Share on other sites

Can someone tell me how the actions in step #6 "install Windows Deployment Services files to C:\RemoteInstall"? 

I don't see how this is done. I've enabled PXE as instructed and the WDS service is installed and running. But I was never prompted to configure it when installing the Windows 10 ADK.

Share this post


Link to post
Share on other sites

My mistake. I don't know how I missed it. It's on the H:\ for my server (which is where I should have started looking).

I do have a follow up question. On our SCCM 2007 server, the WDS install created a SMSPXEIMAGES$ share that pointed to E:\RemoteInstall\SMSIMAGES. On the SCCM Current Branch server, no SMSPXEIMAGES$ was created. I'm wondering if that was b/c I enabled PXE for my SMSPKGH$ share (H:\SMSPKGH$).

I have two DP choices in SCCM 2007 (\\sccm2007\smspxeimages$ and \\sccm2007). I'm guessing this is b/c in SCCM 2007, we configured the "ConfigMgr distribution point" and "ConfigMgr PXE services point" site system roles separately? We've always used the \\sccm2007\smspxeimages$ DP for boot images, and the other \\sccm2007 DP for software packages and OS images. 

In SCCM Current Branch, there's only the "Distribution point" site system role to configure - which has a "PXE" tab in the dialog box.  So there's only the SMSPKGH$ file share - b/c I restrict where SCCM can create package source locations on the server (no_sms_on_drive.sms files in root of all other drives).  I've confirmed my boot image has been distributed to my one DP location.

Both our SCCM 2007 and "Current Branch" setups are single site servers. We have one location so all roles are installed to just the one server in both instances.

Is there any need to create a SMSPXEIMAGES$ to point to H:\RemoteInstall\SMSImages?

Are my guesses correct regarding the differences b/t SCCM 2007 and Current Branch?

Share this post


Link to post
Share on other sites

I was getting "Failed to Download Policy" error. https://blogs.technet.microsoft.com/charlesa_us/2015/03/11/smsts-log-showing-failed-to-download-policy-guidhere-code-0x80004005/ helped me resolve the issue. I opened Microsoft SQL Server Management Studio 17 and performed option B. In the example, replace the 12345678-28EB-40E3-9959-1EFEB0453286 with the GUID found in the log from the client machine located in x:\Windows\Temp\SMSTSlog\smsts

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...