locked
unable to map networkdrive to... RRS feed

  • Question

  • Hi everyone

    I try to deploy win 7 with MDT 2010, AIK 2.0 and WDS.
    All tools are running on Win server 2008 R2.
    I built a boot.wim with MDT and generatet a Task (no spezials integrated) and linked it in WDS.
    I startup my machine and load over PXE. After filling up all informations in the wizzard the deployment start:
    "Format and Partition 0"
    "deploy OS"
    at this point the deployment abort with this message:

    Unable to map networkdrive to \\vdc01\share$\\images\win7\install.wim
    Failure (5630) verify file  \\vdc01\share$\\images\win7\install.wim
    Return Code = -2147467259 0x80004005

    First i thougt it has to be a misstake by my self.
    but i built up the server agian and folowed 1to1 the instructions. Same failure...

    I see that the Wizard is building the filepath with the path (.\\images\win7\install.wim) and the share (\\vdc01\share$).
    But why?!!
    Tuesday, December 29, 2009 11:23 AM

Answers

  • Like Tim said, you must also import the source files.
    MDT needs the source files (setup.exe ..) to install the OS.  The image files alone aren't enough.

    Each deployent share needs the source files from each OS you're deploying.

    Just right-click Operating Systems -> Import Operating System, choose 'Full set of source files' to import them to your deployment share.

    • Marked as answer by Moe Z. _ Tuesday, January 5, 2010 8:02 AM
    Monday, January 4, 2010 11:43 AM

All replies

  • It sounds like your network access account does not have the proper permissions on either the share or the file.

    Tuesday, December 29, 2009 11:30 AM
  • You can open a command prompt by hitting F8. In that command prompt try to connect to the share (net use * \\server\sharename).
    If that fails and return an "access denied", you must adapt the permissions on the share.
    Tuesday, December 29, 2009 11:47 AM
  • i tried the net use command and got the network map.
    it can't be a question of permission because its my own test environment.

    one of the skripts try to map a path that doesn't exist because a path can contain only onetime a "\\".
    and if you are looking at the failure message you'll see : \\server\share\\.....

    how can that be? in the MDT i selected the image from the WDS server
    -> Insert operating system -> WDS -> Windows 7 Enterprise
    and i can see path and version under the properties...
    Tuesday, December 29, 2009 12:07 PM
  • Try to look in customsettings.ini to see if the share name is written correctly.
    Tuesday, December 29, 2009 12:41 PM
  • my customsettings.ini looks normal but i have no share names in it....

    after reading many many logs i found an error:
    the wizard starts the command "cscript LTIapply.wsf"
    so i tried to start i manual with the result:

    Unable to map networkdrive to \\vdc01\share$\\images\win7\install.wim

    i also found 3 files named variables.dat. in each of them i found "installfrompath=\\vdc01\share$\images\win7\install.wim"

    now i look whats wrong with the LTIapply.wsf file.
    Tuesday, December 29, 2009 2:32 PM
  • has anyone tried a deployment with MDT and WSD? AND had success...
    i checked the LTIapply.wsf and think its a failure in this script.
    Tuesday, December 29, 2009 4:30 PM
  • It should work.  Can you post your ltiapply.log file?
    Tim Mintner Principal Consultant Xtreme Consulting Group http://deployment.xtremeconsulting.com
    Tuesday, December 29, 2009 7:08 PM
  • <![LOG['debug' parameter was specified.]LOG]!><time="11:58:46.000+000" date="12-30-2009" component="ltiapply" context="" type="1" thread="" file="ltiapply">
    <![LOG[Property debug is now = TRUE]LOG]!><time="11:58:46.000+000" date="12-30-2009" component="ltiapply" context="" type="1" thread="" file="ltiapply">
    <![LOG[Microsoft Deployment Toolkit version: 5.0.1641.0]LOG]!><time="11:58:46.000+000" date="12-30-2009" component="ltiapply" context="" type="1" thread="" file="ltiapply">
    <![LOG[SUCCESS: 0: Create object: Set oScriptClass = New ltiapply]LOG]!><time="11:58:46.000+000" date="12-30-2009" component="ltiapply" context="" type="1" thread="" file="ltiapply">
    <![LOG[Create dFolders object. List of all Folders/Groups for: OperatingSystems]LOG]!><time="11:58:46.000+000" date="12-30-2009" component="ltiapply" context="" type="1" thread="" file="ltiapply">
    <![LOG[Ready to test xPath: /*/*[( @enable = 'True' or not(@enable) ) and ( @hide != 'True' or not(@hide) ) and (@guid != '{FFFFFFFF-FFFF-FFFF-FFFF-FFFFFFFFFFFF}')]]LOG]!><time="11:58:46.000+000" date="12-30-2009" component="ltiapply" context="" type="1" thread="" file="ltiapply">
    <![LOG[ Open Control File: OperatingSystems]LOG]!><time="11:58:46.000+000" date="12-30-2009" component="ltiapply" context="" type="1" thread="" file="ltiapply">
    <![LOG[SUCCESS: Wahr: Create MSXML2.DOMDocument.]LOG]!><time="11:58:46.000+000" date="12-30-2009" component="ltiapply" context="" type="1" thread="" file="ltiapply">
    <![LOG[CreateXMLDOMObjectEx(\\VDC02\DeploymentShare$\Control\OperatingSystemgroups.xml)]LOG]!><time="11:58:46.000+000" date="12-30-2009" component="ltiapply" context="" type="1" thread="" file="ltiapply">
    <![LOG[SUCCESS: Wahr: CreateXMLDOMObjectEx...Length = 2]LOG]!><time="11:58:46.000+000" date="12-30-2009" component="ltiapply" context="" type="1" thread="" file="ltiapply">
    <![LOG[dFolders Dictionary Object Created, count = 1]LOG]!><time="11:58:46.000+000" date="12-30-2009" component="ltiapply" context="" type="1" thread="" file="ltiapply">
    <![LOG[Filter [default] on Selection Profile: 'Everything' and GroupList('').Count = 0]LOG]!><time="11:58:46.000+000" date="12-30-2009" component="ltiapply" context="" type="1" thread="" file="ltiapply">
    <![LOG[Selection Profile: Everything]LOG]!><time="11:58:46.000+000" date="12-30-2009" component="ltiapply" context="" type="1" thread="" file="ltiapply">
    <![LOG[FindItemsByFolderEx: Selection Profile: Everything]LOG]!><time="11:58:47.000+000" date="12-30-2009" component="ltiapply" context="" type="1" thread="" file="ltiapply">
    <![LOG[FindFilteredItems File:(OperatingSystems) xPathFilter: /*/*[( @enable = 'True' or not(@enable) ) and ( @hide != 'True' or not(@hide) )]]LOG]!><time="11:58:47.000+000" date="12-30-2009" component="ltiapply" context="" type="1" thread="" file="ltiapply">
    <![LOG[SUCCESS: 0: LoadControlFile.FindFile: OperatingSystems.xml]LOG]!><time="11:58:47.000+000" date="12-30-2009" component="ltiapply" context="" type="1" thread="" file="ltiapply">
    <![LOG[SUCCESS: Wahr: Create MSXML2.DOMDocument.]LOG]!><time="11:58:47.000+000" date="12-30-2009" component="ltiapply" context="" type="1" thread="" file="ltiapply">
    <![LOG[CreateXMLDOMObjectEx(\\VDC02\DeploymentShare$\Control\OperatingSystems.xml)]LOG]!><time="11:58:47.000+000" date="12-30-2009" component="ltiapply" context="" type="1" thread="" file="ltiapply">
    <![LOG[SUCCESS: Wahr: CreateXMLDOMObjectEx...Length = 1]LOG]!><time="11:58:47.000+000" date="12-30-2009" component="ltiapply" context="" type="1" thread="" file="ltiapply">
    <![LOG[SUCCESS: 0: Create MSXML2.DOMDocument  .ParseErr.ErrCode.]LOG]!><time="11:58:47.000+000" date="12-30-2009" component="ltiapply" context="" type="1" thread="" file="ltiapply">
    <![LOG[FindAllItems(OperatingSystems) size: 1]LOG]!><time="11:58:47.000+000" date="12-30-2009" component="ltiapply" context="" type="1" thread="" file="ltiapply">
    <![LOG[Found ID: {e6a45bb2-f712-4c65-92a9-a007dd8f0717}]LOG]!><time="11:58:47.000+000" date="12-30-2009" component="ltiapply" context="" type="1" thread="" file="ltiapply">
    <![LOG[   FindItemsByFolder(default) size: 1]LOG]!><time="11:58:47.000+000" date="12-30-2009" component="ltiapply" context="" type="1" thread="" file="ltiapply">
    <![LOG[FindItemsExFull(OperatingSystems) size: 1]LOG]!><time="11:58:47.000+000" date="12-30-2009" component="ltiapply" context="" type="1" thread="" file="ltiapply">
    <![LOG[SUCCESS: Wahr: Verify OS guid: {e6a45bb2-f712-4c65-92a9-a007dd8f0717} exists.]LOG]!><time="11:58:47.000+000" date="12-30-2009" component="ltiapply" context="" type="1" thread="" file="ltiapply">
    <![LOG[SUCCESS: Wahr: Open XML with OSGUID: {e6a45bb2-f712-4c65-92a9-a007dd8f0717}]LOG]!><time="11:58:47.000+000" date="12-30-2009" component="ltiapply" context="" type="1" thread="" file="ltiapply">
    <![LOG[------  Applying Windows image using Setup.exe ------]LOG]!><time="11:58:47.000+000" date="12-30-2009" component="ltiapply" context="" type="1" thread="" file="ltiapply">
    <![LOG[LTI applying image \\vdc02.labor1.intern\REMINST\\Images\win\install.wim using SETUP.EXE]LOG]!><time="11:58:48.000+000" date="12-30-2009" component="ltiapply" context="" type="1" thread="" file="ltiapply">
    <![LOG[SUCCESS: Wahr: Verify File: \\vdc02.labor1.intern\REMINST\\Images\win\install.wim]LOG]!><time="11:58:48.000+000" date="12-30-2009" component="ltiapply" context="" type="1" thread="" file="ltiapply">
    <![LOG[ERROR - Unable to find SETUP, needed to install the image \\vdc02.labor1.intern\REMINST\\Images\win\install.wim]LOG]!><time="11:58:48.000+000" date="12-30-2009" component="ltiapply" context="" type="3" thread="" file="ltiapply">
    <![LOG[ZTI ERROR - Non-zero return code by ltiapply, rc = 1]LOG]!><time="11:58:48.000+000" date="12-30-2009" component="ltiapply" context="" type="3" thread="" file="ltiapply">
    Wednesday, December 30, 2009 11:03 AM
  • It is complaining that it cannot find setup.exe.  You will need to import a full set of source files for that OS into the Deployment Workbench.  MDT uses windows setup to apply the WIM image so we need a set of Windows source files in the workbench for every OS you are deploying.
    Tim Mintner Principal Consultant Xtreme Consulting Group http://deployment.xtremeconsulting.com
    Wednesday, December 30, 2009 6:27 PM
  • now im a little bit confused...

    i importet the install.wim from the original win7 DVD into my WDS and the boot.wim into MDT. after preparing the settings, i loadet the boot.wim from deploymentshare\boot\x86 into WDS. is that the wrong way? Do I have to import the install.wim file into workbank?

     
    Monday, January 4, 2010 9:27 AM
  • Like Tim said, you must also import the source files.
    MDT needs the source files (setup.exe ..) to install the OS.  The image files alone aren't enough.

    Each deployent share needs the source files from each OS you're deploying.

    Just right-click Operating Systems -> Import Operating System, choose 'Full set of source files' to import them to your deployment share.

    • Marked as answer by Moe Z. _ Tuesday, January 5, 2010 8:02 AM
    Monday, January 4, 2010 11:43 AM
  • You don't need the complete install source to deploy an image, just to do the build part. But you should never use the original install.wim. This is to be considered as a file repository and not an image.

    No matter which image you end up using, it should be imported in the workbench. When using MDT, boot images should be imported into WDS, everything else is handeled by/through MDT's workbench.
    Monday, January 4, 2010 1:15 PM
  • :)

    ok. this is another situation.
    importing the DVD into workbench and use boot.wim in WDS works. Thanks a lot.
    But now: why, please, why is in MDT an option "WDS" when i have to chose the OS?

    ...i studied the scripts long time. specially the LTIapply.wsf. The WDS option is implemented but doesnt work.
    Monday, January 4, 2010 3:05 PM
  • MDT uses the WDS only as an image repository if you want to store your images from there.  MDT does not use any of the other functionality in WDS.  All of the actual "work" is done by the MDT scripts and executables.
    Tim Mintner Principal Consultant Xtreme Consulting Group http://deployment.xtremeconsulting.com
    Monday, January 4, 2010 11:04 PM