As per my understanding you are planning to have differentePO Server for managing Server & Clients. But you should use the sameDistributed repositories.
Configure 1st ePO Server to Manage Servers withbelow
- Configuration of Distributed Repositories
- Schedule replication tasks
- Deploy Agent only for Servers.
If you are already use another ePOServer you can also use “Transfer Systems” so that the managed clients will beautomatically moved to new ePO Server.
Configure the 2nd ePO Server
- Define the Repository location
- Make sure you have not defined any replicationtask(Already managed by 1st ePO Server)
I hope this may help you to have two different servers tomanage Servers & Clients with same distributed repositories.
But instead of using two different ePO Servers you cancustomize the Agent handlers.
You can create two agent handlers with the same ePO Serverwhich can perform same kind of activity. One Agent handler configured to manageServers and another one to manage Clients.
Of course you can use other agent handler if any one agenthandler is down due to any issue.
Unfortunately I'm afraid this won't work at all... the content in a distributed repository is signed by the ePO server that controls it, and the client machines are given the keys by the server that controls them - the clients will only accept content that they have the leys for. Additionally, distributed repositories are date/time stamped - so you'd have to be very careful about the order in which replications were done, otherwise you would wind up with one group of machines refusing to update from a distributed repository because they believe it to be out of date.
To the OP - can I ask exactly what you're trying to achieve? What's the reasoning for wanting to have separate servers? It may be that there's a simpler approach.