none
Trying to configure UWF to work across multiple machines RRS feed

  • Question

  • Hello,

    We are currently tryng to upgrade all are systems to Windows 10 Enterprise LTSC 2019, we are still using Windows 7 currently. 

    We are creating are base Windows 10 image currently but running into an issue with the Unified Write Filter. We setup all are file and registry exclusions and protect the volume C: we then capture an image using Acronis True Image to load that image on another machine with the exact same specs. Issue is the Unified Write Filter is still set to the Device ID of the original machine so none of the exceptions we created are working on the new system without having to recreate them all.

    Is there a way to Unified Write Filter to work with any drive that is the volume C: without it being tied to the Device ID of a drive? We are able to have all the exceptions we created in File Base Write Filter on Windows 7 carry over from one machine to another without any issues and thats what we are trying to do again with Unified Write Filter.

    Any help is greatly appreciated.

    Thanks,

    Donald


    Monday, July 22, 2019 6:55 PM

All replies

  • Hi,

    I'm afraid that this behavior that capture a image and deploy to another device cannot be achieved.  Since the tool used to capture image is a third-party tool, microsoft will not supply support for it, it's recommended to contact with Acronis True Image support for further help.

    Best regards,

    Yilia 


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.




    Tuesday, July 23, 2019 7:43 AM
    Moderator
  • Yilia,

    Acronis True Image is not the issue, the UWF is not being configured how we want it to be even before the image capture. We want UWF to protect the C: drive but to not tie it a device id like it is currently doing, we were able to do this with FBWF.

    Thanks,

    Donald

    Tuesday, July 23, 2019 2:33 PM
  • Something is off here. You have to sysprep the image before capture. Windows doesn't do well when just moved it to another system without roll back. UWF has to be disabled at this point. As each clone of the master boots, you can have a synchronous command run in the sysprep unattended file to enabled UWF.


    Sean Liming - Book Author: Starter Guide Windows 10 IoT Enterprise - www.annabooks.com / www.seanliming.com

    Wednesday, July 24, 2019 3:41 AM
  • We want the inital UWF configuration to not tie a device ID when runnung the uwfmgr protect volume c command. We've never had to sysprep any of are images prior when we used Windows 7, the images are going onto machines that are exactly the same. 

    Is there a way for UWF to just protect a volume C without having a device ID tied to it like we are able to do in Windows 7. Are main concern is if the machine fails and we need to replace it we want tp be able to reload the image that was captured and UWF to not need any reconfiguration.

     
    Wednesday, July 24, 2019 7:20 PM
  • You were getting lucking by simply copying the image to another system. UWF is a different technology than EWF. UWF is tied to the sector level.  Sysprep will work for what you want to do, you have to create another answer file for sysprep pass 4 and 7 settings and add the command to enable UWF for C drive.

    Sean Liming - Book Author: Starter Guide Windows 10 IoT Enterprise - www.annabooks.com / www.seanliming.com

    Wednesday, July 24, 2019 8:43 PM