MSEndpointMgr
Home » Microsoft Endpoint Manager » ConfigMgr » Operating System Deployment » WIM Witch v1.3.0 – Server Support, OneDrive, and Command Line

WIM Witch v1.3.0 – Server Support, OneDrive, and Command Line

With the release of WIM Witch v1.3.0, she now has new capabilities that were requested by the community. While there have been plenty of functional updates to WIM Witch since its release, this version brings enough change to warrant documentation. The features introduced in this release are all from user requests, and I want to thank everyone who has submitted feedback on WIM Witch.

To download WIM Witch, open PowerShell and use the following command:

save-script -name WIMWitch -path [path to save folder]

Then, simply run the script and follow the prompts.

If you are running version 1.2 or later of WIM Witch, she will automatically detect the latest version and prompt for the upgrade.

Server Updates

WIM Witch now supports Windows Server 2016 and 2019. By simply checking the required version in the “Updates” tab, Windows Server updates are downloaded and applied just like Windows 10 updates have been from the beginning.

After selecting a Server WIM file in the “Source WIM” tab, certain Tabs and functions are disabled. These disabled items are Autopilot, APPX removal, and OneDrive updating, and are disabled because they are not applicable to server operating systems.

When updating a Server Core images, WIM Witch will skip Adobe updates as they are not applicable to Server Core operating system.

WIM Witch only supports the LTSB versions of server operating and it is not advisable to attempt to update a Current Branch version of server. If there is enough demand from the community, I can add that support in a later version.

Now with server goodness!

By adding Server support, the underlying folder structure of the updates had to change. In previous releases, the updates folder contained subfolders that were labeled with the release version of Windows 10. Now, the first sub-folders are named after the major operating system.

What the updates folder should look like after downloading updates. Please delete any numbered folders i.e 1709 or 1903

The impact is that any existing updates folder will no longer be used. These folders could be moved to a subfolder called “Windows 10”, but it is advisable to take the easy route and just delete them. Once deleted, the updates can be re-downloaded, allowing WIM Witch to store them automatically.

OneDrive

Windows 10 comes with a OneDrive installer that runs when the first user logs in. The installer is frequently out of date, and users are prompted to update this agent if it is. WIM Witch now downloads the latest OneDrive agent installer any time Windows 10 updates are downloaded. To apply the update, simply click the “Update OneDrive client” checkbox in the “Make It So” tab.

Update Supersedense

In previous versions, all updates were checked to see if they were superseded, and then deleted if found to be.  Now, only the updates of the operating system version that is being downloaded will be checked. This allows administrators to keep older updates for other OS’s while updating only the ones they wish to update.

Additionally, the -Superseded command line option has been deprecated because of how supersedense is now handled.

Command Line Functions

CLI functions have been overhauled to make them easier to use, and to support the new Windows Server functionality.

-auto

This switch enables WIM Witch to run a saved file, or a batch of saved files.

-autofile

This switch tells WIM Witch to run a specific saved configuration by providing the name and location of a file. It will not work if the -auto parameter is not provided.

  • Example: WIMWitch.ps1 -auto -autofile d:\wim witch\configs\server2016_updated

-autopath

This switch tells WIM Witch to run every found saved configuration in a give path. This is useful if multiple images need to be created. It will not work if the -auto parameter was not provided.

  • Example: WIMWitch.ps1 -auto -autopath d:\wim witch\configs\

-UpdatePoShModules

This switch tells WIM Witch to update the OSDUPATE and OSDSUS modules if they are found to be outdated. Updating the modules will require PowerShell to be restarted, so this switch is not recommended for fully automated tasks.

  • Example: WIMWitch.ps1 -UpdatePoShModules

-DownloadUpdates

This switch allows WIM Witch to check for, and download, new updates for a given operating system. The operating system version must be supplied.

Specifying which versions of Windows to download updates for

-Server2016

This switch tells WIM Witch to download updates for Server 2016.

-Server 2019

This switch tells WIM Witch to download updates for Server 2019.

-Win10Version

This switch tells WIM Witch to download updates for Windows 10, and requires the version to be specified. The options are All, 1709, 1803, 1809, 1803, 1909. All tells WIM Witch to download for every supported version of Windows 10.

Thank you again for using WIM Witch. The reception it has received from the community has made undertaking this project worth the time I have invested. Please let me know what you think!

To read the previous walk though of WIM Witch, which contains discussion around the remaining features, please use the following link: https://msendpointmgr.com/2019/10/04/wim-witch-a-gui-driven-solution-for-image-customization/

(3504)

Donna Ryan

Donna Ryan is a Principal Consulting Engineer with CDW Corporation's Integrated Technology Services Mobility practice. She began her formal IT career in 2011 as an Associate Engineer with CDW. Her primary skills are around System Center Configuration Manager, specifically operating system deployment, software update delivery, and application packaging. Having consulted hundreds of clients in a variety of industries, she has also delivered projects in multiple other Microsoft technologies such as Hyper-V and Remote Desktop Services. In 2016, she was awarded CDW’s Coworker of the Month for her leadership and dedication to a large and highly visible Windows 10 deployment project for a school district in the Pacific North West.  In 2018, Donna was invited to participate in Microsoft's Mini Enterprise Mobility MVP Summit, as well as the Microsoft CLIP event for the Windows 10 1809 rollout. Her passion for technology and the tech community is a driving force that keeps her exploring the latest and greatest.

15 comments

    • It is the consumer version as that is what is included in the Windows 10 image. I did not include the business version as you cannot inject office into a WIM file.

  • Nice update. Since using this updating our install WIM is much easier. Thanks heaps!

    Any news when adding a language pack will be introduced? I think you’d mentioned it was on the to-do list already.
    Currently I’m just using a pre-prepared WIM with the language pack already added, but would be nice to cut that step out for future OS’s.

    • You are welcome! I am very happy to hear you are finding WIM Witch useful.

      I don’t have a time frame for language packs yet. I’ll probably start working on that feature some time in late January or early February. Maybe by spring it’ll be released?

      • Thats awesome, i’ll keep an eye out for that release :o)

        Looking at adjusting our build process for servers to include updating the WIM for them with this too now.

  • Hi,

    Any idea why I am getting the following error when I try to import an ISO?

    “Mount-DiskImage : A virtual disk support provider for the specified file was not found.
    At E:\Tools\WIMWitch\WIMWitch.ps1:2025 char:17
    + $isomount = Mount-DiskImage -ImagePath $file -NoDriveLetter
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : NotSpecified: (MSFT_DiskImage:ROOT/Microsoft/…/MSFT_DiskImage) [Mount-DiskImage], CimException
    + FullyQualifiedErrorId : HRESULT 0xc03a0014,Mount-DiskImage”

    • Offhand, no. If I were to guess, it is likely a permissions issue. Do you have administrative rights on the box you have WIM Witch installed?

      • Hi Donna,

        Yes I have admin rights. I thought maybe it was because the file was on a share and copied it locally, but it made no difference.
        Only think I can think of, would it make a difference because I am running this on a VM (Win2016) ?

      • It being a 2016 VM isn’t the issue. My main dev box is a 2019 VM. I would try and mount a normal ISO, just to make sure that works. What WIM Witch is doing behind the scene is mounting the ISO without a drive letter. There may be a GPO preventing the ISO from mounting.

        Barring that, you can copy the install.wim file from the iso manually and place it where ever you want. The imports/wim folder is where WIM Witch places them, but you don’t have to. You can also copy out the two .Net cab files from the iso [drive]:\sources\sxs and place them in the wimwitch\imports\dotnet\[windows version] folder. IF that folder doesn’t exist, go ahead and make it. The folder should be the version number (1709,1803, etc).

        That will bypass all of the import functions and allow WIM Witch to do her thing. If you are getting permissions issues after manually creating the packages, something else is going on.

        Out of curiosity, do you have WIM Witch installed in Program Files or Program Files (x86)?

      • Hi Donna,

        Ok, I was a numpty and was pointing to a WIM file rather than the ISO (they both had the same name).

        So now it mounts but complains that it can’t find install.wim – I’ve mounted the ISO manually and can confirm it’s there.

        12/10/2019 16:05:20 Information – Mounting ISO…
        Get-WindowsImage : The system cannot find the path specified.
        At C:\Tools\WIMWitch\WIMWitch.ps1:2027 char:19
        + … indowsver = Get-WindowsImage -ImagePath $iso\sources\install.wim -Ind …
        + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo : NotSpecified: (:) [Get-WindowsImage], COMException
        + FullyQualifiedErrorId : Microsoft.Dism.Commands.GetWindowsImageCommand

        C:\Tools\WIMWitch is where I have installed WIM Witch.

      • I’m not really sure what is going on. Reboot the computer and try again. If that doesn’t work, you can email me your log. It should exist under [installation folder]\logging\wimwitch.log

      • Hi Donna,

        For info – In the end I had to add “-PassThru” to get the image to mounts correctly on Win2016, can’t figure out why but hey 🙂
        For reference:
        $isomount = Mount-DiskImage -ImagePath $file -NoDriveLetter -PassThru

  • Hi

    cannot fine download info for this version, or the past versions now

    is there a new link for downloading?

    thanks

    • To download WIM Witch, open PowerShell and use the following command:

      save-script -name WIMWitch -path [path to save folder]

      Then, simply run the script and follow the prompts.

      If you are running version 1.2 or later of WIM Witch, she will automatically detect the latest version and prompt for the upgrade.

Sponsors

Subscribe

Do you want to be notified of new posts on our site?

Please enter your email address below:

Categories

MSEndpointMgr.com use cookies to ensure that we give you the best experience on our website.