<div>
<div class="content wysiwyg-content">
How can I setup so when APP needs to call <br />
DB it uses a PRIVATE or INTERNAL &quot;Virtual Switch&quot; <br />
so traffic does not go out the NetworkCard ?<br />
<br />
Setup<br />
&nbsp; ** one PHYSICAL &quot;test&quot; box<br />
&nbsp; ** three HyperVs (APP, DB, UTILITY)<br />
&nbsp; ** end-users access APP<br />
&nbsp; ** I sometimes access DB &amp;&nbsp;UTILITY<br />
&nbsp; ** all 3 HyperVs are using <br />
&nbsp; &nbsp; &nbsp;&quot;Virtual Switch #1 - External Network&quot; <br />
&nbsp; &nbsp; &nbsp;so I can access them directly if/when needed
</div>
</div>


How can I setup so when APP needs to call 
DB it uses a PRIVATE or INTERNAL "Virtual Switch" 
so traffic does not go out the NetworkCard ?

Setup
  ** one PHYSICAL "test" box
  ** three HyperVs (APP, DB, UTILITY)
  ** end-users access APP
  ** I sometimes access DB & UTILITY
  ** all 3 HyperVs are using 
     "Virtual Switch #1 - External Network" 
     so I can access them directly if/when needed

Windows Hyper-V 2012 R2 -- internal network ?

Hyper-V is a native hypervisor; it can create virtual machines on x86-64 systems and supersedes Windows Virtual PC as the hardware virtualization component of the client editions of Windows NT. A server computer running Hyper-V can be configured to expose individual virtual machines to one or more networks. Hyper-V Server supports remote access via Remote Desktop Connection. Administration and configuration of the host OS and the guest virtual machines is generally done over the network.

Hyper-V

Windows Server 2012 is the server version of Windows 8 and the successor to Windows Server 2008 R2. Windows Server 2012 is the first version of Windows Server to have no support for Itanium-based computers since Windows NT 4.0. Windows Server 2012, now in its second release (Windows Server 2012 Release 2) includes Foundation, Essentials, Standard and Datacenter, and does not support IA-32 or IA-64 processors.

Windows Server 2012

Microsoft Virtual Server was a virtualization solution that facilitated the creation of virtual machines on the Windows XP, Windows Vista and Windows Server 2003 operating systems. Virtual machines are created and managed through a web-based interface that relies on Internet Information Services (IIS) or through a Windows client application tool called VMRCplus. Features included Linux guest operating system support, Virtual Disk Precompactor, symmetric multiprocessing (SMP), x64 host operating system support, the ability to mount virtual hard drives on the host machine and additional operating systems support, including Windows Vista, and a volume shadow copy writer.