Share via

Autounattend.xml VS USB Provisioning VS WIM Imaging

Anonymous
2024-02-09T18:43:52+00:00

Hi all,

I'm working on an embedded project where the main OS will be running Windows IoT Enterprise. It will have its drive partitioned off so the OS and loader application are on a Unified Write Protected profile, and the second partition will be a muteable game partition.

My question comes in the form of the restore disk, as I see it there are three options:

  • WIM Image the OS drive and the Game drive, have both restorable with a program/script OR autounattend.xml
  • Use autounattend.xml to all but remove user input and have an install script that runs once then write protects the drive if needed.
  • Use autounattend.xml during the installer but then use USB provisioning to create the accounts and settings.

They all seem to acheive the same effect with not much differences in downsides. The only downside I can see is that if I wanted to update the OS, autounattend.xml and provisioning would make that easier. But then since this device is unlikely to get updated often and the OS drive never changes during use, I can't see how it's much more benficial?

So my question is what are these scenarios for? What are the strengths or weaknesses I am missing and is there a prefference from Microsoft which to use?

Thanks all!

Windows for business | Windows Client for IT Pros | Devices and deployment | Set up, install, or upgrade

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-02-12T07:38:11+00:00

    Hi Darksilro,

    your question involves three different restore methods: WIM image, autounattend.xml, and USB provisioning. Both of these methods can be used to restore both operating system drives and game drives, but there are some differences between them.

    A WIM image is a compressed file format that contains a complete image of the operating system. When you restore with a WIM image, you need to restore the image file to the destination drive. This method takes a longer time but ensures that the restored system is exactly the same as the original system.

    Autounattend.xml is an automated installation file that can be used to automate the installation of a Windows operating system. When you restore with autounattend.xml, you can customize the installation process, such as removing user input, setting defaults, and more. This method saves time but requires some technical knowledge.

    USB provisioning is a method of copying pre-profiles and applications onto a USB drive. When you restore with USB provisioning, you can automatically install apps, set defaults, and more. This method saves time but requires some technical knowledge.

    In your case, if you don't need to update your operating system frequently, using a WIM image or autounattend.xml for restore may be more suitable. If you need to automatically install applications and set defaults, then using USB provisioning may be a better fit.

    Overall, each of these methods has its pros and cons, and which one to use depends on your specific needs. Microsoft doesn't have a preference for one approach, and you can choose the one that works best for your needs.

    Hope this helps.

    Kind regards,

    Lei

    0 comments