I'm currently have an open support ticket opened for investigation, but it seems like I cannot create a child policy, whose parent is the "Server Policy" on a lower server. I would always get the error message "Error downloading policy configuration. Policy tree will be refreshed from server..." The tree would look like this to the upper servers view: Default Parent Policy -> Company Global Policy (Server 1) -> Server Policy (Server 2) -> Server Centric Policy (Server 2). If I take Server Centric Policy (Server 2) and not assign it a parent on the lower server, it'll allow me to edit the configuration and make changes. If I place that policy back and make it the child of Server Policy (Server 2) the configuration does not take effect on the clients, nor can I edit the policy. The funny thing is, if I did this tree: Default Parent Policy -> Company Global Policy (Server 1) -> Server Policy (Server 1) -> Server Centric Policy (Server 1) This is allowed. I can make changes to the configuration and the configuration takes effect. This is in light of something I tried doing last year where I had took advantage of the Primary and Secondary Remote Adminstration where I had Server 2 as the Primary Server and Server 1 as the secondary server. The clients couldn't reach Server 2, but could reach Server 1, the ERAS server would have the client show up twice in the client list with different primary servers (which is incorrect.) But that's a different discussion I need to take up with ESET.