However, deploying a Windows VM with a customization spec adds time and if all you really want is the IP address assignment it can be annoying to have to use a customization spec. In fact, the reason I'm posting this information is because I had a request from a customer to speed up the provisioning time while still using the Static IP feature. The use case was they simply needed to spin up a Windows server for quick QA and then destroy it. Now, there are some other ways to accomplish this (snapshot/revert comes to mind) but it did get me to thinking of ways to avoid running vCenter customizations on Windows clones to speed up deployment.
One way to accomplish this is with vCenter Orchestrator (vCO). This post assumes some knowledge of and experience with vCO, but you may be able to put this together without that background.
In general, a VM deployed with Static IP will have the following machine properties set with the values from the Network Profile:
... and optionally ...
There are other properties for networking, but for our use case we will leverage these specific property values via the vCAC Extensibility Workflows. These are included with the embedded vCO instance and you will want to go ahead and set that up if you haven't already. See this presentation for an overview and setup walk-through.
In addition, I will use the Guest Script Manager Package for vCO to run the configurations directly on the new VM's guest OS - note that this requires VMtools to be installed on the guest.
*Static IP is also supported for AutoYAST/kickstart using the guest agent.