I've been working on getting Windows deployments (2022 in particular) to customize with Cloudbase-init.

So far I have it:

• Updating the hostname
• Updating the administrator account's password
• Running a command
• And configuring the NIC with a static IP when supplied with the MAC address.

If I don't supply the MAC in the network config, then cloudbase-init throws a bunch of errors in the log looking for the address and does not set the static IP. It doesn't make sense as their doc states that the field is optional. But seems to be necessary to find the NIC.

So to make it work, I need to specify a MAC address in XO when creating the VM. And then paste that into the network config yaml.

So is there a template variable for MAC like there is for {name} and {index} ? And if not... can we get one?

The working network config:
network:
version: 1
config:
- type: physical
name: eth0
mac_address: "56:a7:01:38:75:3f"
subnets:
- type: static
address: 192.168.1.3/24
gateway: 192.168.1.1
dns_nameservers:
- 192.168.1.2
dns_search:
- company.name

Or am I just doing it wrong?

Thanks!
jonathan

@onthegrid Sure!

So with the network config above. Gotta make your own MAC address and have it match the one in the interface field when cloning the template. (Variable would be nice here.)

Cloud config in XO:

Installed cloudbase with defaults. Did not run sysprep. Did not reboot. I plan to handle those IDs later. And trying to sysprep Windows 11 didn't work/broke.

Cloudbase-init.conf:

If i recall correctly, it was just the last three lines I changed/added. Tested on Server 2022 and Windows 11. If we do go into produciton on this platform, I'll do the other config stuff later. I just wanted to make sure I could get the OS config'd with an IP, update the hostname, and reset the administrator password.

I was looking at the pricing page and under XO Proxy it just says 'Optional'. (along with XOSTOR)

It's a little confusing because under the Enterprise license it says 'Complete feature access'.

Does this mean the backup proxies are licensed separately? And if so, how much per proxy install?

Thanks!

I'm working with a Windows 11 VM and testing out templating/deployment stuff.

I made a Win11 VM with vTPM enabled. Installed the citrix management agent. Installed cloudbase init with defaults and did not sysprep. Sysprep kept throwing errors.
I shut it down, took a snap and make a new vm from that snap. Then turned that vm into a template. Same process that i did with 2022. And no problems there.
Went to make a new VM in XO from this template and right at the end i get this error:

VTPM_MAX_AMOUNT_REACHED

To finally get it to work, I had to turn off the vTPM device option when cloning the VM. Even though the UI puts up a warning that the VM needs this device and the OS will probably not boot.
Funny thing is... after the VM was done cloning, the vTPM device was indeed there and with a new UID. And the VM booted just fine.

So is XO trying to stuff a second vTPM (max amount?) into the clone rather than remove the old one from the template first?

Thanks,
jonathan

I've been working on getting Windows deployments (2022 in particular) to customize with Cloudbase-init.

So far I have it:

• Updating the hostname
• Updating the administrator account's password
• Running a command
• And configuring the NIC with a static IP when supplied with the MAC address.

If I don't supply the MAC in the network config, then cloudbase-init throws a bunch of errors in the log looking for the address and does not set the static IP. It doesn't make sense as their doc states that the field is optional. But seems to be necessary to find the NIC.

So to make it work, I need to specify a MAC address in XO when creating the VM. And then paste that into the network config yaml.

So is there a template variable for MAC like there is for {name} and {index} ? And if not... can we get one?

The working network config:
network:
version: 1
config:
- type: physical
name: eth0
mac_address: "56:a7:01:38:75:3f"
subnets:
- type: static
address: 192.168.1.3/24
gateway: 192.168.1.1
dns_nameservers:
- 192.168.1.2
dns_search:
- company.name

Or am I just doing it wrong?

Thanks!
jonathan

@Danp Yup, that will do it. Thanks. No longer pulling out my hair.

I'm trying to use Postman to test out these REST calls to XO and am having trouble setting up the authentication token cookie.

This works in the command line:
curl -b authenticationToken=IJqaWKJGHL9pHv64lRLa-5QH-xG-YC9wzctfv3rypm4 https://server.company.name/rest/v0/vms

But in Postman I keep geeting 401 Unauthorized. So it seems I'm not setting up the token cookie correctly.

The format of the cookie text correct? And/or what should be used for the domain? Or do i put the ip of the xo server there? Path? I've tried a lot of variations, but still no luck.

Thanks,
jonathan