WDS

[warcrow]

We have multiple WDS servers on our (nationwide) network. They're on separate VLANS, but I'm having issues with PXE clients contacting another server.

I know how to inject new drivers into a a boot.wim, but I dont know how to tell it to look (or not look) at a specific server.

Can someone out there, who's smarter than me, help me out?

 

[warcrow]

Oh and to be clear, when I PXE boot the machine it does indeed connect to the right WDS server (I verified the IP), but once we get into WinPE we're gathering all our information from another WDS server.

 

[imagoon]

Which version of WDS and which deployment methods are you using? The Windows Vista/7/2008/2008r2 WAIK style deployments are designed to hit multiple servers while the tools for XP / 2003 are bit more limited.

 

[warcrow]

It's Server 2008 R2 and WDS 6.1 in the console.

I think I figured the boot part out. I generated a new boot image and I think that seems to have resolved the issue, but now it's not pulling up the applications I've added to the work bench.

 

[imagoon]

It's Server 2008 R2 and WDS 6.1 in the console.

I think I figured the boot part out. I generated a new boot image and I think that seems to have resolved the issue, but now it's not pulling up the applications I've added to the work bench.

At that point you will likely need to look at your deployment scripts. I found that in general every time you make a major change you do want to at least do a partial rebuild of the install wim. The scripts can be updated without a rebuild typically though.

 

[warcrow]

deploymentshare$/scripts ?