Assuming you have created a VMware View Desktops Pool, the end result will be that RDP is enabled on the View Desktops. 
In the context of MS12-020 , this means potential trouble especially when PoC is already available. It does not matter they are no directly accessible from the Internet, a worm targeting MS12-020 downloaded by one user on its virtual desktop could impact all the View Desktops local to it.
Even if you take the measure described in , I did not test so I’m not sure, I think the exploit still works.
So if you did not do it so far, make sure you install the MS12-020 patch on all your View Desktops. If you use Linked-Clone Desktops, patch the parent virtual machine, take a snapshot and recompose the Linked-Clone Desktops.
Alternatively, if for some reasons you can't apply the patch yet and if you’ve deployed vShield App, you can filter (deny) inside the port group were virtual desktops are located; add a deny rule for the RDP application selecting as both source and destination the port group while direction being inside for both of them.
 Prevent Access to View Desktops Through RDP
 Why We Rated the MS12-020 Issue with RDP "Patch Now"
MS12-020 RDP vulnerabilities: Patch, Mitigate, Detect
 Proof-of-Concept Code available for MS12-020