If we get the Windows 10 ISO from other websites it is typically in the WIM (Windows IMaging)file format. If we get the Windows 10 ISO from the Microsoft website it is in ESD (Electronic Software Download) file format. May we know if you download the ISO file from Microsoft website? If yes, it's excepted behavior. I wanted to be sure it was the right way to go before actively testing.įinally will configmgr be receiving updates to recognise ESD files in the future?
Is this behaviour expected in configmgr 1906 with W10 1903? Am i working around it in the right way or should i be getting the media from a different place other than the media creation tool? Do I need to keep install.esd or can it be deleted to conserveīandwidth? I haven't tried using the package yet but I will be later in the week.
I put the resulting install.wim alongside the install.esd on my share, i then deleted install.esd and tried to import again and it worked. dism /export-image /SourceImageFile:install.esd /SourceIndex:6 /DestinationImageFile:install.wim /compress:max /CheckIntegrity I decided to use dism to extract the index (index 6 was Win 10 pro) i wanted to install.wim e.g. When i dig a little deeper and try to find install.wim in sources it doesn't seem to exist and instead it is install.esd. Everything i read through google suggested this was related to an older ADK on the server, not true in this case. We are using SCCM Current Branch 1906 with the latest hotfix and the latest ADK is installed on Windows Server 2016.
When i try to import the 1903 package i get this error message: I extracted the ISO and copied it up to our SCCM server share where I have imported previous upgrade packages for previous versions of windows 10.
I used the media creation tool to create a Windiso for 圆4 en-US only. Hi, Got a few questions and observations in relation to creating an operating system upgrade package for Windows 10 1903.
0 kommentar(er)
