Jump to content


nate@tamu

New Members
  • Content Count

    2
  • Joined

  • Last visited

Community Reputation

0 Neutral

About nate@tamu

  • Rank
    Newbie
  1. Hey there, Guys. I'm having a problem with WDS, which is why I'm posting here. I mentioned I'd start a new thread about this in another thread as well. Working with a new system, I want to capture an image to my WDS server. This requires putting the drivers for the NIC into the boot image to allow it to actually work, but for some reason, I can't. If I try and use the wizard, I get 'The request is not supported' and the logs complain about 'It is an unsupported scenario to service an up level image using low level dism.' This led me to believe that there was a version issue somewhere. All updates have been done on the box, and the latest ADK has been installed. Thing is, if I try and use WDS's driver tool, it defaults to the older version of DISM. Is there a way to change the version it uses or to update the version it's pointing to to the latest version? If I use the DISM located in Program Files (x86)\10\Assessment and Deployment Kit\Deployment Tools\dism, I get Version 10.0.10586.0, but if I use the version located at C:\windows\system32 (the one I suspect WDS uses), I get version 6.3.9600.17031. Simply put, I need to make the old one go away, point WDS to the new one instead, or upgrade the old to the new. Any suggestions? Thanks. Edit 29 July 2016: Okay, so. I've been poking around the internet and a few suggestions have been thrown out to change the Path in System Properties. Windows/system32 is still first in line, so for grins and giggles, I put the ADK DISM location in front of that. WDS still runs the older version, from what I can tell. I also renamed and deleted all versions of DISM with the same problem, but that led me to realize that WDS is using WDSUTIL, not DISM. The old version of WDSUTIL installed has almost the same version number as the version of DISM. Now I'm trying to see if there's a way to update WDSUTIL to something newer than 6.
  2. I'm having the same problem, and to add a little more information that may help Mr. Strait, it seems that my system is using a DISM version in WDS that is older than the one installed with the windows 10 ADK. This is a brand new installation of Server 2012r2, all updates, and the latest ADK from Microsoft. If I use the DISM located in Program Files (x86)\10\Assessment and Deployment Kit\Deployment Tools\dism, I get Version 10.0.10586.0, but if I use the version located at C:\windows\system32 (the one I suspect WDS uses), I get version 6.3.9600.17031. I'll start another thread with this question, but if anyone knows how to make WDS use a different instance of DISM or to update to the newest version in System32, I'd be more than grateful. Nate
×
×
  • Create New...