When playing around with SCVMM 2016 TP4, i did want to deploy a service template (NVGRE Windows HA gateway) and i have found out that there is actually a bug in the service template designer.

When you import a service template and then edit it from the service template designer, if you try to do any change to the application configuration section you get the following error:

It looks like a .net issue so probably VMM is doing a call which .net does not know how to handle. I tried to reinstall .net and installed also the last version but it didn’t fix the issue. My VMM 2016 TP4 and Windows Server 2016 TP4 are both fully up to date.

Since we are in a technical preview i didn’t want to spend to much time investigating probably a bug which will be resolved i guess in next release. But at least i have a workaround to propose.

It appears that this bug only comes from the service template designer, we can avoid this issue by simply creating a VM template first on which we will actually configure applications. Then from the service template designer we will use this existing template.

1) create a VM template

2) Now create a service template and select “Blank Template”

3) Add a virtual machine Tier to the template and select your newly created VM template.

4) configure scale out options and availability set

Check application tab on the service template

5) Deploy the service template

Click on refresh preview as usual to refresh host rating

Edit each VM to properly configure network if required.

In the jobs now we should see this job running

it looks like we are doing good, both VMs are being deployed.

After a while we get our service up.

So our service template has been properly deployed. At the time of writing this article i didn’t find any other workaround, if a fix is released before TP5 (yes there will be another TP still before an RTM) then I’ll update this post to provide a link for that fix.