none
OS not in Workbench after MDT-ImportOperatingSystem

    Question

  • Running MDT2010 Update 1

    I have a WIM that contains the 4 reference images we generate.  When importing using the Workbench, the Images appear correctly, and can be used fine.  

    When Importing using the MDT-ImportOperatingSystem cmdlet, The wim is moved into the appropriate folder in the file system, but the workbench is not updated.   Also the powershell process is now locking the wim and needs to be exited before the wim can be moved elsewhere.   Powershell script is a straight copy of the script generated by the workbench when importing.  

    Powershell Script:

    Add-PSSnapIn Microsoft.BDD.PSSnapIn
    New-PSDrive -Name "DS005" -PSProvider MDTProvider -Root "E:\DeployWin7"
    import-mdtoperatingsystem -path "DS005:\Operating Systems\20130426" -SourceFile "E:\MDT2010-Win7\Captures\WIN7-20130426.WIM" -DestinationFolder "WIN7-20130426" -Move -Verbose
    

    PowerShell Result:

    PS E:\MDT2010-Win7> .\ImportOS2.ps1
    
    Name           Used (GB)     Free (GB) Provider      Root
    ----           ---------     --------- --------      ----
    DS005                                  MDTProvider   E:\DeployWin7
    VERBOSE: Performing operation "import" on Target "Operating system".
    VERBOSE: Import processing finished.
    
    
    PS E:\MDT2010-Win7>


    WorkBench Result

    Performing operation "import" on Target "Operating system".
    Creating new item named WIN7X64REFDDrive in WIN7-20130426 WIN7-20130426.WIM at DS005:\Operating Systems\20130426.
    Creating new item named WIN7-X64-THIN-20130426 in WIN7-20130426 WIN7-20130426.WIM at DS005:\Operating Systems\20130426.
    Creating new item named WIN7-X86-THICK-20130426 in WIN7-20130426 WIN7-20130426.WIM at DS005:\Operating Systems\20130426.
    Creating new item named WIN7-X86-THIN-20130426 in WIN7-20130426 WIN7-20130426.WIM at DS005:\Operating Systems\20130426.
    Import processing finished.
    

    Is there something I'm missing, or does the MDT-ImportOperatingSystem cmdlet not handle multiple images in the same wim? 

    Monday, April 29, 2013 3:52 PM

Answers

  • So updating to MDT 2012 Update 1 seems to correct the issue.  Which is odd be cause the code behind the cmdlets doesn't seem to change around the area where the issue occurs.

    Thursday, May 02, 2013 12:26 PM

All replies

  • I have 6 images in my WIM although we are using MDT 2012 update 1

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ” How to ask a question that is fixable.

    Monday, April 29, 2013 5:03 PM
  • Are you able to import that wim using the powershell cmdlet, or do you experience the same issue? 

    Monday, April 29, 2013 7:07 PM
  • If I go from the output of your original post your images did import.  You just have to point to them in your task sequences.

    For example:

    Are  you seeing something wildly different?


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ” How to ask a question that is fixable.

    Tuesday, April 30, 2013 12:00 AM
  • Yes it Imports if I use the Workbench.   The issue I have is it does not work when using the powershell cmdlet either via script or the powershell console.    

    I'm trying to automate the reference build process.   I've got it powering on VMs, waiting for them to image and capture.  Then once all the VMs are powered down, combining the resultant Images into one wim.  Then importing that WIM into the deployment share using the cmdlet.   All of the steps before complete fine, but running the cmdlet seems to only partially importing the wim.   Powershell reports success: 

    VERBOSE: Performing operation "import" on Target "Operating system".
    VERBOSE: Import processing finished.

    But the images are not displayed in the workbench nor are they added to the OperatingSystems.xml.   The WIM file is moved into the file system for the deployment share, but powershell does not release its lock on the file.  Any attempt to move, rename, or delete the file is met with an in use error condition until powershell is exited.  

    Tuesday, April 30, 2013 1:05 AM
  • Could virus scan be interfering?  Some, like McAfee VSE, have issues when DISM gets called.

    David Coulter | http://DCtheGeek.blogspot.com | @DCtheGeek

    Tuesday, April 30, 2013 2:45 AM
  • I've tested with AV disabled, and the issue still occurs. 

    Tuesday, April 30, 2013 8:12 PM
  • So updating to MDT 2012 Update 1 seems to correct the issue.  Which is odd be cause the code behind the cmdlets doesn't seem to change around the area where the issue occurs.

    Thursday, May 02, 2013 12:26 PM