Windows DHCP issue when using kitchen

[smackmybitsup]

Versions:

• Version of Chef-Provisioning: chef-provisioning (2.7.1)
• Version of Chef-Provisioning-vSphere: chef-provisioning-vsphere (2.3.1)

Platform Details

Product VMware vCenter Server 6 Standard (Instances)
VMware ESXi, 6.5.0, 10175896

Scenario:

Windows client does not get a usable DHCP during a kitchen converge

  add normal.chef_provisioning = {"reference"=>{"driver_url"=>"vsphere://nscvc65d01ao.petc.local/sdk?use_ssl=true&insecure=true", "driver_version"=>"2.3.1", "server_id"=>"503ca6c3-7bda-3823-1b4c-d7dee2df4f77", "is_windows"=>true, "allocated_at"=>"2018-11-29 17:19:00 UTC", "ipaddress"=>nil}}
  add normal.tags = nil
###run converge again and it "sees" the network###
[2018-11-29T09:29:02-08:00] WARN: Checking to see if {"driver_url"=>"vsphere://nscvc65d01ao.petc.local/sdk?use_ssl=true&insecure=true", "driver_version"=>"2.3.1", "server_id"=>"503ca6c3-7bda-3823-1b4c-d7dee2df4f77", "is_windows"=>true, "allocated_at"=>"2018-11-29 17:19:00 UTC", "ipaddress"=>nil} has been created...
establishing connection to nscvc65d01ao.petc.local
[2018-11-29T09:29:02-08:00] WARN: returning existing machine
Power on VM [kitchen/win-test-windows-0049fc0e]
.IP address obtained: 172.24.201.119
update node win-test-windows-0049fc0e at chefzero://localhost:1
  update normal.chef_provisioning.reference.ipaddress from nil to "172.24.201.119"```

### Steps to Reproduce:
kitchen converge