I don't know for sure that 1803 is supported under vSphere 5.5 or technically vRA 7.2. You may want to open a case and ask GSS because I can't find anything concrete other than support for general Windows 10.
Couple of things to add......
We have an old instance that we are migrating from. VRA 6.3.4. I have created blueprints for v1803 and it worked on there.
I have also tested Win10 v1709 on vRA 7.2 - worked on one tenant, failed on another tenant (Same blueprint, only difference is the network profiles)
So as it stands. Win10 (any version) fails on some tenants but v1709 works on one tenant.
whoops, should also add its vRA 7.3
However everything I need to do that is failing - works on our old 6.3.4 instance
Can you deploy from that template manually using the same vCenter customization spec and assign the hostname, IP successfully?
Yes I can. I'm limited to static IPs as there is no DHCP server. However I can build using same guest script - change hostname and assign static IP from both VMWare manually and also by changing the blueprint to use a static IP.
the issue appears to be when using a network profile / DHCP
I'm unclear. You say you aren't using DHCP. A network profile in vRA isn't DHCP, it's a static IP that is handed out by vRA's internal IPAM. Can you show screenshots of your blueprint and network profile?
You have just triggered a lightbulb moment, and unsurprisingly it may be my fault.....
I had to remove the network component of the network profile and readd it as it hadn't updated to reflect previous changes.
I also changed the assignment type to static. I had it set to DHCP. I don't think this was an option on the older version so my bad!
That's basically what I was driving at and I wanted to see how you had things set up. I've seen people do this before unaware of what vRA is expecting to do. If you assign a network profile using a static network on the canvas, you should be using a static IP. You can always leave this up to the reservation to figure out, but in both cases DHCP is not a network profile assignment.
Thankyou for your help. I'm still not sure its logical....but it works
If you set Assignment type to static....but leave the static IP blank, then IPAM works and dishes out an IP out of the specified range.
If you set Assignment type to DHCP....then it does nothing.
I wrongly assumed IPAM works a little like DHCP so was using that option.