<div>
Are you saying that the physical server, the one running Hyper-V 2012 is not getting a IP address? If so then that makes sense since the physical server should have a static IP used by the VM's.
</div>


Are you saying that the physical server, the one running Hyper-V 2012 is not getting a IP address? If so then that makes sense since the physical server should have a static IP used by the VM's.

<div>
A few things to check:<br />
- Does the system start off assigning Virtual IPs and then stop or not start at all? &nbsp;If so, that means that you haven't allocated a sufficient amount of IPs.<br />
- Has Virtual IP usage been assigned to the application(s)?<br />
- The Virtual IPs must be in the same subnet as the Remote Desktop server; VIP can't cross subnets.<br />
<br />
Most commonly, the last item is the issue.
</div>


A few things to check:
- Does the system start off assigning Virtual IPs and then stop or not start at all?  If so, that means that you haven't allocated a sufficient amount of IPs.
- Has Virtual IP usage been assigned to the application(s)?
- The Virtual IPs must be in the same subnet as the Remote Desktop server; VIP can't cross subnets.

Most commonly, the last item is the issue.

<div>
<div class="content wysiwyg-content">
Clients connect to the server via RDP. GPO is set properly, registry entries were created for static virtual IP addresses on the local server. Local server has teamed nics. IPconfig shows all the IP address in the static IP address range, but it still doesn't appear to assign a virtual IP address to the local sessions or programs.
</div>
</div>


Clients connect to the server via RDP. GPO is set properly, registry entries were created for static virtual IP addresses on the local server. Local server has teamed nics. IPconfig shows all the IP address in the static IP address range, but it still doesn't appear to assign a virtual IP address to the local sessions or programs.

We are trying to setup virtualized IP on a 2012 r2 hyperV client Remote Desktop Session server.

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

Virtualization is the act of creating a virtual (rather than actual) version of something, including (but not limited to) a virtual computer hardware platform, operating system (OS), storage device, or computer network resources. Virtualization is usually the creation of a system that executes separate from the underlying hardware resources, or the creation of an entire desktop for systems located elsewhere, similar to thin clients.

Virtualization

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.