WDS & Deployment Workbench Issue

[talksr]

Hello,

 

Does anyone know how I can resolve this issue?

 

I have WDS all set up on my 2012 R2 server and it works nicely. I had also set up Deployment Workbench and added Windows 10 1809 some time ago.

I have logged on to update this image. I firstly removed Deploment Workbench and reinstalled the latest version.

 

I have added a new 1909 image, put in out of box drivers, Office application and a new Task sequence.

 

When I F12 a client machine, I am seeing 1809 only in the Windows Deployment Wizard within Microsoft Deployment Toolkit.

 

1. I deleted 1809 from Operating Systems in Deployment Workbench, but still, 1809 came up.

2. I did "Update Deployment Share". No change, did it again but completely regenerated images. No change.

3. I "Closed Deployment Share" in Workbench, when I re-added, I can see there are actually two. There is one DeploymentShare in the D:\ drive - this has the old 1809 stuff in and this is what seems to be getting picked up. But there is also, another Deployment share in E:\ and that has my new 1909 images with task sequences etc.

 

How do I get the server to pick up the right deployment share and how has this even happened? I am not too bothered about keeping the old 1809 one as this is old now. Just quite confused about how this has happened in the first place.

 

WDS remote install folder is E:\WDS\RemoteInstall which is a similar area to my new 1909 stuff, so can't see why the D:\ stuff is still there and being recognised.

 

Any help would be great.

[Mako]

Just a wild shot last time I had weird WDS/MDT quirks... after completely regenerating the boot images, have you then updated the boot image in WDS?

[talksr]

Just a wild shot last time I had weird WDS/MDT quirks... after completely regenerating the boot images, have you then updated the boot image in WDS?

 

Hi, thanks for your post. I had a fiddle, I removed the DeploymentShare share from the D:\ drive, the share was DeploymentShare$

 

I then removed the Deployment Share from E which was DeploymentShare2.

I then re-shared the E one but made it DeploymentShare$ and now it is working like a dream. Not sure how I ended up with two DeploymentShares, very strange, but I seem to have solved it through trial and error. Thanks for your post