Once that is done you can delete the install.esd file if you want, to save space. Make sure the path for /SourceImageFile and /DestinationImageFile are correct for you and change the /SourceIndex to match the index you noted earlier. Now use the following command to create an install.wim file that contains the SKU you want: dism.exe /Export-Image /SourceImageFile:C:\Temp\Windows10_20H2\sources\install.esd /SourceIndex:3 /DestinationImageFile:C:\Temp\Windows10_20H2\sources\install.wim /Compress:max /CheckIntegrity Make a note of the index of the SKU you want (in my case, I want the Enterprise SKU which is index 3). This will list each of the SKUs in the install.esd file. Open a CMD prompt and use the following command (changing the path for /WimFile to match where your install.esd file is): dism.exe /Get-WimInfo /WimFile:C:\Temp\Windows10_20H2\sources\install.esd wim file (for example, if you’re planning to use it with MECM/SCCM). Depending on what you are doing, you may need the. When you have downloaded the ISO, you may unpack it and find that the it does not contain an install.wim, but instead contains install.esd in the sources directory. If you want to download the 32-bit version of Windows 10 Enterprise instead, you should change /MediaArch to x86. If you don’t specify the /MediaLangCode switch it will default to downloading an ISO with the same language pack as the OS you are running it from. So, for example, to download Windows 10 Enterprise 20H2 with French installed and set to the default language, you can use this command: MediaCreationTool20H2.exe /Eula Accept /Retail /MediaLangCode fr-FR /MediaArch 圆4 /MediaEdition Enterprise This will download an ISO containing the same SKUs as above, but with en-GB installed and set to default.Īs far as I can tell, this works for any of the language pack region tags listed on this site. If you’d prefer to get en-GB, use the following command: MediaCreationTool20H2.exe /Eula Accept /Retail /MediaLangCode en-GB /MediaArch 圆4 /MediaEdition Enterprise This will download an ISO that contains the various Enterprise SKUs (Enterprise, Enterprise N, Education, Education N, Professional and Professional N) with en-US installed and set to default. When you’re prompted for a product key, you can use the Windows 10 Enterprise KMS client key from this site on Microsoft Docs. Open a CMD prompt, change directory to the directory you saved the Media Creation Tool in and enter the following command: MediaCreationTool20H2.exe /Eula Accept /Retail /MediaLangCode en-US /MediaArch 圆4 /MediaEdition Enterprise To download Windows 10 Enterprise 20H2 using the Media Creation Tool, log in with a local administrator account (for some reason it isn’t good enough to run the tool using Run as administrator, you actually do have to be logged in as an administrator) and download the tool. If you want to download the Enterprise version of Windows 10, but don’t have access to Microsoft VLSC, Visual Studio or Action Pack subscriptions, it is possible to download it using the Media Creation Tool if you know the right command line switches. Using the GUI, you can download the consumer ISO which contains the Home, Professional and Education SKUs of Windows 10. Historically Microsoft has called these xx09 (for example, 1809 or 1909) but starting this year it is referred to as 20H2, meaning year 2020 half 2. The October 2020 update to Windows 10 is now available to download using the Media Creation Tool. Implementing Ivanti Patch for SCCM (Part 2): WSUS Code Signing Certificate March 31, 2020.Implementing Ivanti Patch for SCCM (Part 3): Ivanti Settings April 1, 2020.Implementing Ivanti Patch for SCCM (Part 4): Publishing a Third-Party Update April 2, 2020.Implementing Ivanti Patch for SCCM (Part 5): End-to-end Demonstration April 3, 2020.Download Window 10 Enterprise 2004 with the Media Creation Tool (including en-GB and other language versions) May 28, 2020.One way to fix error 0x87d00231 in ClientIDManagerStartup.log September 30, 2020.Download Window 10 Enterprise 20H2 with the Media Creation Tool (including en-GB and other language versions) October 20, 2020.Enabling HSTS and selecting most secure ciphers and protocols for HTTPS for ConfigMgr March 15, 2021.Fixing issues with ConfigMgr client log collection March 17, 2021.Hands on with Office 365 Cross-tenant mailbox migration (preview) October 20, 2022.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |