IP Virtualization for 2012 R2 RDS

RDS - running on 2012 R2 Standard
RemoteApp configured for inhouse application

I've configured IP Virtualization on our RDS server and set to give out IP address from a static IP address range (different subnet - configured in the registry. (instructions: https://technet.microsoft.com/en-us/library/ee382306%28v=ws.10%29.aspx). Logging in as a user to the Terminal server, gives me an ip from the range I configured (, which means IP virtualization is working BUT not when they're just connecting to the RemoteApp (RDWeb) program.

What we're trying to accomplish is to have each user get a different IP address so they don't have access to other network shares.

user1 - IP range (
User2 - IP range (
User3 - IP range (
User4 - IP range (
User5 - IP range (

I know NTFS permissions should be enough to block other users from accessing other network shares, but this is another layer of protection, as it will be different clients accessing the server.

1. Is this setup possible?
2. What are required in the setup?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

That setup is not possible.  The addresses given back are part of the same subnet of the RDS server interface.  You won't be able to have multiple different subnet address ranges given back.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
andrew_transparentAuthor Commented:
how about specifying users a specific block of IP address in the same subnet?

User A gets
User B gets
User C gets
Cliff GaliherCommented:
IP Virtualization was introduced strictly for application compatibility purposes. As such, it simply doesn't offer that granularity. RDS itself wasn't really built for multi-tenancy, which is what it sounds like you are trying to do.  Realistically, in a multi-tenant solution, you'd use something like SCVMM similar to spin up a new tenant RDS server as needed instead of allowing multiple tenants to access the same server. Otherwise your security model is fundamentally broken, since networking functionality is not per-user, or even per-session, but runs at the system level. It would be trivial for a user to bypass any IP boundaries you try to set on a per-user or per-session basis since the underlying network stack still has to have access to the broadcast domains for other sessions. It just isn't a tenable security boundary.
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

andrew_transparentAuthor Commented:
thanks for clearing that up!

how about setting up a front-end VPN so we can at least have the clients get a different IP than the local RDS subnet.
any suggestions? any IP-based restrictions we can setup?

Cliff GaliherCommented:
Not that seem even remotely secure.
andrew_transparentAuthor Commented:
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.