none
MDT Deployment Share version error RRS feed

  • Question

  • Hello,

    Upon arriving at work today, our MDT server no longer runs install TS' on pcs. After logging on to the server I discovered that the deployment share has been messed up somehow- trying to connect to it shows an error message reading:

    "The deployment share 'sharename and path' cannot be opened because it was created with a later version of Microsoft Deployment Toolkit. The version of the deployment share is 6.0.2223.0 while the current version is 5.1.1642.1"

    Now I know that I haven't done any updates on the share, and there is another share that is still working on the same server, so I am stumped as to why this has happened! We cannot deploy computers until this is resolved, and I can't see to find any information on it from my research.

    Anyone ever seen this?


    Edit: I've realized that version 6.0.2223.0 is MDT 2012, which we don't use. First of all- how is this possible? Second, can I upgrade to 2012 and preserve my existing deployment shares?
    • Edited by Paul_131 Wednesday, May 9, 2012 5:17 PM
    Wednesday, May 9, 2012 5:16 PM

Answers

  • Update-

    Upgrading the entire console to MDT 2012 and adding the (accidentally) upgraded deployment share seems to have got it back up and running- the OSD TS is currently testing this. I had to also upgrade the second deployment share in order to use it on MDT 2012, but that went through without a hitch.

    Still dumbfounded as to why this happened, or how a DS could be upgraded without the console itself actually upgrading. Luckily, the audit log also showed who did it :)

    • Marked as answer by Paul_131 Thursday, May 10, 2012 8:24 PM
    Wednesday, May 9, 2012 6:47 PM

All replies

  • Update-

    Upgrading the entire console to MDT 2012 and adding the (accidentally) upgraded deployment share seems to have got it back up and running- the OSD TS is currently testing this. I had to also upgrade the second deployment share in order to use it on MDT 2012, but that went through without a hitch.

    Still dumbfounded as to why this happened, or how a DS could be upgraded without the console itself actually upgrading. Luckily, the audit log also showed who did it :)

    • Marked as answer by Paul_131 Thursday, May 10, 2012 8:24 PM
    Wednesday, May 9, 2012 6:47 PM
  • I had this.  Had to open notepad as administrator.  Navigate to Deploymentshare\control and modify the version.xml file and put in the old version and everything worked again.  Not sure why it thought it was updated but something happened and that fixed it.
    Monday, September 16, 2019 10:14 PM