Scenario:

You have to manage a server  that is located in another company its network. You've got a big existing infrastructure (SCCM, SCOM, AD integrated, ...) in your company.

There's internet availability in the other company. In some cases, there's a private network link between your company and the other company.  

Running the service in the Cloud, like Azure, is not an option because of huge network traffic volumes towards that server in that other company - you're not going to sponsor an ISP here. Using IPSEC is only possible if there's a connection between the two companies, It should be a more flexible solution.

A Solution:

Is it a workable to use Direct Access as a solution? Configuring direct access client on that server, making it to dial "home" in a VPN (using the internet, or via the private connection between the two companies). Can it still offer services on the local network of the other company (as long there's no double IP address scheme, by example both companies using 10.x.x.x network)?

Or are there better solutions?
Thanks in advance for all replies :)

Kr,
David
PS: The "remote" server is running Windows 2012 R2 and managed via SCCM 2012 R2.

Hi

It wont work.When your DirectAccess client is operational, the firewall mode is public or private. So local computers will not be able to access the server acting as a DirectAccess client.

Ok, that's working the same way for the Cisco VPN client (and probably all VPN client solutions). Thanks to confirm that!

If I have two network interfaces in my server, one I use for the Direct Access Client, one on the local network but different VLAN, will that work?

From a Windows point of view yes but for applications, it's much more complicated. Having a domain controller with multiple network interface is complicated.