MDT, WDS, and VLANS Oh My!

[wizard210]

I'm having some issues getting my machines to image correctly. I'm pretty sure I have the vlan side of things figured out.

 

I followed this thread http://www.edugeek.net/forums/enterprise-software/157848-issue-mdt-wds.html and added in both the IP helper addresses.

 

What I'm running into is when I get into the task sequence of MDT I get the following error.

 

Now that all makes sense because if I do an IPCONFIG /ALL I see the machine doesn't have an ip anymore.

 

 

What I don't understand is why does the machine lose it's IP address? It grabbed the correct one when PXE booting from WDS.

 

I also added the drivers for the machine I'm testing everthing on updated the deployment share, then replaced the image on WDS.

[wizard210]

should I also add those drivers to the wds boot image?

[DJ-1701]

It appears you already have drivers in the MDT generated boot Wim that you added into WDS. So don't think it's the issue.

Personally I haven't tried WDS/MDT across VLANs. @Iain.Faulkner If you're available, as someone that has tried worked with VLANs and WDS/MDT, any ideas?

[Mustang]

Maybe you could give us some more information on your network layout, this will help the troubleshooting.

 

From the screenshots above, error1 is expected because of the lack of an ip address etc in error 2.

 

What happens if you run ipconfig /renew from the command prompt?

Are you sure you have the correct network card drivers injected in the boot image?

If you boot into windows or live linux distro on the same computer in the same network port can you get an ip address?

Have you tried another computer?

[wizard210]

So before I left work I added the drivers to the wds boot image. When I pxe booted and got to the task sequence it failed again with the same error.

 

This time though when I did an ipconfig the machine received a request.

 

I also tested a ping to the MDT server with success. Tomorrow I will verify if I can manually map a drive to the deployment share of the MDT server.

[free780]

Do you have 802.1x deployed on your switches?

[Davit2005]

MDT/WDS accross vlans should only require adding the WDS server IP as a helper address along with the DHCP server address, put both in every vLAN that you wish to PXE to the WDS server from, you do not need to put it on the vLAN where the server is.

 

 

The error message have you installed the correct WinPE drivers and updated you boot image in MDT and using the new image in WDS??

[SpaceInvader83]

Just checking does the machine eventually grab an IP address? I had an issue with some new machines booting up too quickly during the task sequence so when it tried mapping the deployment share it failed.

[Iain.Faulkner]

I think we had something similar when we first put in the vlan's last summer. Might be worth having a look at the solution in here

 

active directory - Can't connect to DeploymentShare$ from PC attempting to MDT, but can other PCs on the network - Server Fault

[wizard210]

I think we had something similar when we first put in the vlan's last summer. Might be worth having a look at the solution in here

 

active directory - Can't connect to DeploymentShare$ from PC attempting to MDT, but can other PCs on the network - Server Fault

 

That is what is exactly happening to me, only I'm losing my IP address when it goes into the MS Solution Accelerators screen.

[wizard210]

okay so I think I found my mistake. On the switch that the clients are plugged into I didn't have the ip helper address entered for both the dhcp and wds server. Edited June 14, 2016 by wizard210