Last week Microsoft has released the November refresh of its Azure Stack TP2 release bits. There are a lot of improvements, so it is recommended to do a fresh deployment of the TP2.
What I have discovered editing the following files, is that we got an additional VM in the November refresh.
-> F:\CloudDeployment\Configuration\Roles\Infrastructure\BareMetal\OneNodeRole.xml
-> F:\CloudDeployment\Configuration\Roles\Fabric\VirtualMachines\OneNodeRole.xml
As you can see, it is the MAS-WASP01 VM that was added in the November refresh. Due to this I had to align my vCPU and vRAM settings for the VMs.
| VM name | vCPU | vRAM in GB |
| ACS01 | 2 | 3 |
| ADFS01 | 2 | 1 |
| ASql01 | 2 | 2 |
| BGPNAT01 | 2 | 2 |
| CA01 | 2 | 1 |
| Con01 | 2 | 1 |
| DC01 | 2 | 1 |
| Gwy01 | 2 | 2 |
| NC01 | 2 | 2 |
| SLB01 | 2 | 1 |
| SUS01 | 2 | 1 |
| WAS01 | 2 | 2 |
| WASP01 | 2 | 2 |
| Xrp01 | 4 | 5 |