It is basically the same idea as the previous recipe, but a very different solution; I call it "sitting-on-the-fence", but it is commonly known as a Jumphost.
This solution doesn't require a vApp router, and it works for isolated vApps and isolated Organization Networks. Depending on what you would like to build, you need different parts:
vApp Networks: Create a vApp with multiple VMs and deploy an isolated vApp Network. Then add an additional VM of your preferred OS type (Windows or Linux).
Organization Networks: Create an isolated Organization Network that is connected to some other vApps. Now create an additional vApp with only one VM of your preferred OS type (Windows or Linux).
To add a VM to a vApp, see the Adding a VM to a vApp recipe in Chapter 3, Better vApps.
This additional VM will be the Jumphost VM. Do not power on the Jumphost VM yet, as this is an important step in the recipe.