brendanhoar
commented
5 years ago This may also be important for handling the move of the Users folder to the private volume on Windows 10. I've had nothing but failures using QWT to do so after Windows 10 is set up (yes I know, QWT is unsupported for Windows 10).
From what I have found, there are some changes to how Windows 10 expects a moved Users folder to work and therefore it is strongly recommended that one use the sysprep functionality before OOBE completes to move the C:\Users folder elsewhere. This can be performed manually, using Audit mode early in the setup to assign drive letters for the optical drive and private volume and then configure an "answer" xml file outlining the Users folder move before the OOBE portion of Windows 10 setup is completed. See: https://www.tenforums.com/tutorials/1964-move-users-folder-location-windows-10-a.html
Perhaps this could be specified using autounattend.xml?
@Yethal - is the drive move part of your autounattend recipie?
Thanks, Brendan
srbhss
Yethal
Qubes OS version:
Global
Affected component(s):
Dom0 Windows-based VMs
Steps to reproduce the behavior:
Create a new Windows-based hvm Attempt to pass the Autounattend.xml file to the VM
Expected behavior:
Option to pass the file is exposed via GUI/CLI
Actual behavior:
The only way to pass the file is to create a bootable usb drive with Windows installation on it, copy the autounattend.xml file to the usb drive, then attach the usb controller with the device to the vm and boot the vm off of it. Not only is this process unnecessarily complicated, it is also error prone and aggravating. An option of passing the autounattend.xml file and/or generating one (the way virtualbox does) would greatly speed up Windows deployments and make any form of corporate integration much easier. Moreover, unattended installation can be performed in a headless vm which makes the process even easier.
General notes:
Related issues: