none
Using MDT 2012 to recapture a physical machine. RRS feed

  • Question

  • We have about 200 servers to image, using MDT 2012. While Dell does not offer CABs for servers, we built one from scratch on a physical machine and captured it normally. Now, they found they want to modify the image some. Its my understanding that you cannot recapture a physical machine once its been captured through MDT, and you must rebuild it all over from scratch again. Is this true? Or can you do that 3 times because of the rearm scenario? I recall back in PXE that you had to modify the unattend to set the rearm to 0 to recapture. I'm not using physical machines, but VMs, except for this server image since there is no CAB. Otherwise its my understanding that recapturing a physical machine in MDT is not allowed.
    Any suggestion about recapturing a server (physical machine) that's already been captured in MDT?
    Thanks
    Monday, March 14, 2016 6:44 AM

Answers

All replies

  • There is a finite number of times you can rearm the OS. It can be problematic to build and capture on physical hardware. If this is server 2012 or later why don't you just use powershell to export drivers from the OS?

    Logs are very important. https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/ Mention any customizations you have made.

    Monday, March 14, 2016 12:46 PM
    Moderator
  • I agree with Ty, export the drivers and import them into MDT to make your own driver group the same way you would with other models.

    http://deploymentbunny.com/2016/02/26/powershell-is-king-export-drivers-from-windows/


    If this post is helpful please vote it as Helpful or click Mark for answer.

    Monday, March 14, 2016 2:41 PM
  • Is there a step-by-step for exporting/importing and coding powershell? I don't use Powershell at all and am not familiar. If its just a copy/paste code thing, I can do that. But I'm not sure how to put it all into MDT. Ive never worked with Powershell. I'm assuming you're saying this is intended for an image being physically captured, rather than a VM. If I can find somewhere and be a dummy and just copy the text, I'll give it a go. I don't even know what to do once I paste the code into Powershell.
    Any links would be really appreciated!
    Thanks
    Monday, March 14, 2016 5:44 PM
  • You don't run this particular PS in MDT.  Just run it on the model and OS you are building for after you have whatever drivers you need installed.  Dan's link tells you how.

    Logs are very important. https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/ Mention any customizations you have made.

    • Marked as answer by the1rickster Tuesday, March 15, 2016 9:58 AM
    Monday, March 14, 2016 6:59 PM
    Moderator
  • Ok makes sense. So this extracts the drivers. How do they get injected back onto another machine during deploy? Is that done in MDT? Thanks so much for helping.
    Monday, March 14, 2016 7:33 PM
  • Once you've exported the drivers, import them into MDT as per usual.

    If this post is helpful please vote it as Helpful or click Mark for answer.

    Monday, March 14, 2016 7:45 PM
  • That sounds great. One final thought...once I extract the drivers from the physical machine, I can then create a VM for that image and inject drivers into it in MDT? (I guess using the WMI query). This way, if that's possible, I can update my VM endlessly by doing snapshots along the way. Why did I not know about extracting drivers this way before???
    Better than relying on Dell to come up with their CAB.
    Monday, March 14, 2016 8:23 PM
  • You should always build your reference images using a VM so as to not introduce hardware drivers/software. As for how to manage your drivers I suggest using method #3 (Total Control) found here - http://deploymentresearch.com/Research/Post/325/MDT-2013-Lite-Touch-Driver-Management

    This post might also help - http://deploymentresearch.com/Research/Post/357/Building-reference-images-like-a-boss


    If this post is helpful please vote it as Helpful or click Mark for answer.

    • Marked as answer by the1rickster Tuesday, March 15, 2016 9:48 AM
    Monday, March 14, 2016 8:39 PM
  • I would have been making this image from a VM but Dell offers no CAB file for servers. I built it from a physical machine. The issue arose when they wanted to modify that image. My response was to build up from scratch all over again, which is the worst scenario you can want. I will run the Powershell script and grab the drivers, create a VM and inject those drivers during the TS. Thanks!
    Tuesday, March 15, 2016 3:24 AM
  • I'm running Windows Server 2012 R2 and in PowerShell, the command Export-WindowsDriver is not a recognized cmdlet. Also, it says the PowerShell command from the link listed above should export "third party" drivers. Either way, PowerShell tells me that the Export-WindowsDriver is not recognized as a cmdlet.
    Do you have any suggestions?
    Tuesday, March 15, 2016 7:05 AM
  • It is a supported command. https://technet.microsoft.com/en-us/library/dn614084%28v=wps.630%29.aspx

    You might check and see if the PS is enabled.


    Logs are very important. https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/ Mention any customizations you have made.

    Tuesday, March 15, 2016 7:18 AM
    Moderator
  • What do you mean if PS is enabled? I can get to PS and I'm typing:

    Export-WindowsDriver -Destination "C:\Drivers\$((Get-WmiObject -Class win32_computersystem).Model)" -Online

    What I get is a response stating that Export-WindowsDriver is not a recognized cmdlet. Is there something I need to do before running this command? I just installed Windows Server 2012 R2 Standard Core with GUI onto a T430 Dell Server. Also, what does it mean by '3rd party drivers?'


    • Edited by the1rickster Tuesday, March 15, 2016 7:24 AM mistyped command
    Tuesday, March 15, 2016 7:23 AM
  • Additionally, if I right-click on the PS icon and choose PowerShell ISE as Admin, it suggests available commands. When I type Export-, it shows a whole list of available commands, but no Export-WindowsDriver. The only Export-Windows it lists is Export-WindowsImage. Export-WindowsDriver is just not available.
    Tuesday, March 15, 2016 7:29 AM
  • I don't know what to tell you. I have used the command on Windows Server 2012 and later. I was asking you to check roles and features.

    Logs are very important. https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/ Mention any customizations you have made.

    Tuesday, March 15, 2016 7:59 AM
    Moderator
  • I have .NET 4.5 installed and Windows PowerShell 4.0, ISE and Desired State Configuration installed. I don't know if there is anything else. I read about importing a module, if that's something else I need to do.
    Tuesday, March 15, 2016 8:07 AM
  • You might need to import the dism module.

    Logs are very important. https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/ Mention any customizations you have made.

    • Marked as answer by the1rickster Tuesday, March 15, 2016 8:56 AM
    Tuesday, March 15, 2016 8:16 AM
    Moderator
  • Yeah, I installed ADK on the server I wish to export drivers from, but I'm not sure how with DISM. I'm familiar with using DISM on offline images, but this would be running DISM on the live machine, so it wouldn't be a mounted image on the same machine. Im not sure how to use DISM on an active OS. The reference page shows DISM to Export Drivers is for a mounted image. I cant mount the image Im currently in....so I end at this point.
    Tuesday, March 15, 2016 8:46 AM
  • I stand corrected. Once I added ADK, the suggested commands followed the initial command I was trying to run. That was the fix, adding ADK. I'm not sure what drivers are gathered, but I will test-clone one and see.

    Thank you for your help!

    Tuesday, March 15, 2016 8:56 AM
  • The answer is in this thread. Dan posted the PS link and I posted to the cmdlet page. -online is the key.

    Logs are very important. https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/ Mention any customizations you have made.


    Tuesday, March 15, 2016 8:57 AM
    Moderator