- Más nuevo
- Más votos
- Más comentarios
One possible issue is that AWS Image Builder might not be using the same unattend.xml settings you're familiar with, including the CopyProfile and PersistAllDeviceInstalls flags. Although AWS Image Builder automates the sysprep process, it may have its own custom configurations that differ from your manual approach. Unfortunately, there isn't always direct documentation about how sysprep is invoked specifically in Image Builder, but I would recommend checking the latest AWS Image Builder docs, especially for customization options like using custom components, as well as reviewing log files (such as those in the Panther directory) for more clues about what's being applied. It might also be worth exploring Image Builder pipelines to ensure the unattend.xml is correctly utilized.
Contenido relevante
- preguntada hace 10 meses
- preguntada hace 4 meses
- preguntada hace 5 meses
- preguntada hace 9 meses
- OFICIAL DE AWSActualizada hace 3 años
Thank you. I was able to find in the sysprep logs that it was being called with same unattend file as the ec2launch v2 method. However, by putting some log print statements in my build components, I was able to see that the build user is not Administrator, like I had assumed, but rather the system default user. So whoami = nt authority\system, and Home directory = C:\Windows\system32\config\systemprofile. This does pose some quirks, but at least knowing this I should be able to work around them. (The nvidia driver issue was separate and simply due to the fact that the build instance also needs to have a gpu or the driver won't install.)