EPO OnPrem & AWS Conflicts

[robg3381]

We have ePO 5.10 on-Prem and we have a newer acquired company that has a presence in AWS.  We've been tasked with integrating those instances into our on-Prem EPO.  Network connectivity is already there, etc.  We have also found out there are some IP conflicts with same IP in AWS and internal which could create some communication issues.  I've been debating whether or not this setup could be architected better by either putting a separate EPO in AWS and letting all of AWS report to that EPO and just have them be registered servers of each other.  Or...putting a RelayServer there.  I'm not sure what might be best practice in kind of a situation. 

Note - we are not licensed for any of the Cloud Workflow products.

[cdinet]

What about transferring systems from aws to epo on-prem?  Are you able to register the on prem to aws server for the transfer?  

As far as conflicting IP's go, that should be able to be handled by dns.  Systems will try by IP, NetBIOS and fqdn to connect to the server.  

The ultimate thing is to decide what you really want to accomplish.  If the goal is easier management and consolidated reporting, management, etc, then getting all the systems on one epo server or the other would be the best option, however you choose to do it.  Just registering the servers with each other won't really accomplish much unless you do something with that registration,  

[robg3381]

@cdinet 

Currently we only have 1 EPO which is on-prem.  I was debating if standing up an additional AWS server to handle AWS clients would be a better approach rather than having all clients in AWS report back to primary on-prem EPO as they are now.  

I just wasn't sure if there were any edge cases where EPO would try to use IP over DNS record (e.g. doing a wake-up call) first and therefore communicate with the wrong client instead of the intended one.

[cdinet]

Whether you do that or not all depends really on what you want to accomplish and if there truly are IP range overlaps, that might be your best option.  One thing, however, in server settings, there is an option for agent contact method, where you can set the priority of how epo will contact the clients first, whether it be IP, NetBIOS or fqdn.  If it can't reach the system by the first priority method, it will still try the other 2.

[robg3381]

Thanks.  Yeah unfortunately we've seen DNS issues as well in some spots as well.  But yeah we are 100% sure there are overlaps of IP's between internal clients and aws clients.  

Our contact order is 1-IP, 2-FQDN, 3-Netbios.  We changed that from the default as we had issues with DNS and things have been much more reliable since then.  

[cdinet]

Honestly, you might run into the same issues, unless there are separate dns servers for the 2 environments (the one you acquired and original network).  Otherwise, you might want to consider reworking the network config to eliminate that overlap.  I know that is easier said than done in many cases.  If the 2 environments are separated sufficiently, as un a sub domain type environment, your separate servers may be fine.