Images from Media Creation Tool

-


When importing an Windows 10 image from the Media Creation Tool I was seeing the error

"the source directory specified does not contain an identifiable operating system"

This is because MDT needs a WIM image not an ESD image which MCT uses.

Nice. 

Not.

To convert an ESD image file to one useable by MDT you need to complete the following.


  1. Log into your machine as Admin
  2. Install and create a Windows 10 build using the Media Creation Tool straight to USB
  3. Install Deployment and Imaging Tools onto your MDT box (unless you have it already!)
  4. Run Deployment and Imaging Tools Environment as Admin
  5. Type and run the following to list all the OS's in the ESD file
    1. dism /Get-WimInfo /WimFile:<path to install.esd>
  6. Find the OS you want and note down the Index
  7. Then run the following
    1. dism /export-image /SourceImageFile:<path to install.esd> /SourceIndex:<INDEX> /DestinationImageFile:<path for install.wim> /Compress:max /CheckIntegrity



Note  This takes a while so best do it all locally not across the network (like I did!)



Many thanks to (and lifted from...)

http://www.labareweb.com/converting-windows-10-media-creation-tool-to-install-wim/

Comments

Post a Comment

Popular posts from this blog

PXE booting, MDT and 802.1x

-
Image
Oh dear. We implemented site wide 802.1x when we moved. This has caused numerous issues which we are still tracking down and killing with fire. Again "only-when-we-needed-it" struck as we had a new starter and need to build a machine. Ah.   No PXE.  However thankfully we were able to make a bootable USB using 802.1x and get our build working again from MDT in our 802.1 environment. Here's how we did it.   Caveats:  I'm assuming you know MDT and how PXE works. We use Computer certificates as the 8021x auth method. 802.1x is working in our environment GPO is used to start the wired 802.1x service on built machines. GPO is used to configure the network profile to use 802.1x What you need Get a USB stick to take your WinPE 4GB may be enough Make sure you are running an up to date working MDT installation! Create a machine certificate which has a long expiry date, you don't want to be making USB WinPE images every month!! Export the machine ...
Read more

NetScaler VPX and Exchange 2010

-
Image
From the title you can guess that we have Exchange 2010 (SP1 CU6 - with Hotfix for EVault) and we are using NetScaler VPX to load balance the services.  I used the excellent document from Citrix to configure the NetScalers (we have two in active/active - sort of using VMACs to split the traffic RPC to one, HTTP(S) and SMTP to the other). However I found a document from Microsoft which points out that there is "significant performance penalty" if we configure incorrect persistence for EAS.  The Microsoft document is here: http://technet.microsoft.com/en-us/library/ff625248.aspx This put us in a pickle and no mistake.  This is because in a NetScaler persistence is per vServer.  We have one vServer for HTTPS as we have one IP address for all HTTP traffic.  This vServer would then deal with all HTTPS traffic including OWA,ECP,EWS,RPC over HTTPS and EAS.  OWA requires cookie based persistence, this is also the method the Citrix doc...
Read more

Security Policy 1001

-
We had an annoying warning showing every 5 minutes on our Read Only Domain Controllers.  This didn't affect service but meant we were losing our logs of important events (should the have occurred) "Security policy cannot be propagated. Security Configuration Server (in services.exe) is not ready. This is probably in system reboot. Policy will be tried again in the next propagation." Source: SceCli Event: ID 101 We tracked this down to a GPO which was populating the local Administrators group. Obviously a Domain Controller has no local users or groups so this was causing the issue. Ensuring that the GPO did not apply to the Domain Controllers - yes the GPO was linked at the root! fixed the issue. It is strange that we did not see the warnings on our main Domain Controllers only on the Read Only DC's as this would have affected all DCs the same (I would have thought)
Read more