Cloudbase-init won't apply config file after sysprep

edit

Hi, all. I'm running a packer build for Windows Server core and am running into an issue with cloudbase-init. In my build, I'm installing cloudbase-init with the MSI, then copying custom config files into the proper locations. I've added the unattend.xml to the one I am using for Windows. The syntax for the unattend.xml is correct as I have validated with the SIM tool. After sysprep is ran, I upload the ova into AWS and create an instance from it. The instance has the user 'cloudbase-init' created instead of the one in the config file. The config files that I had copied are in the correct locations but they aren't being applied. Is there a step I am missing here?

Thanks

Hi, all. I'm running a packer build for Windows Server core and am running into an issue with cloudbase-init. In my build, I'm installing cloudbase-init with the MSI, then copying custom config files into the proper locations. I've added the unattend.xml to the one I am using for Windows. The syntax for the unattend.xml is correct as I have validated with the SIM tool. After sysprep is ran, I upload the ova into AWS and create an instance from it. The instance has the user 'cloudbase-init' created instead of the one in the config file. The config files that I had copied are in the correct locations but they aren't being applied. Is there a step I am missing here?

Thanks

Hi, all. I'm having an issue with cloudbase that I'm hoping someone can help me with. I'm creating an ova with a packer build but for some reason, the conf files are not applying. In my build, I'm installing the msi, then copying the files into the correct location and the final step is sysprep. I've added the unattend.xml in the cloudbase files to my sysprep unattend. When deploying a new server from my packer build the conf files are not applied at all. The only way I can get them to apply is to do the re arm (removing the registry key that resets cloudbase). Am I missing a step?