• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 712
  • Last Modified:

What is the best practice for designing an ePolicy Orchestrator Directory Structure?

Hi
I am currently trying to optimise our ePolicy setup, with integration with AD. Currently in AD we have a "Servers", "PCs" and "Domain Controllers" OUs. We also have a disaster recovery site with a different IP range and subnet, but on the same network. Should i create 2 sites in ePo, "Home" and "DR", or have the sites set to the OUs, "Servers" etc? i guess i'm wondering what the best practice for designing the directory structure is.

Thanks in advance
Brian
0
ITUCIRL
Asked:
ITUCIRL
1 Solution
 
aissimCommented:
Personally, I've always tried to keep my ePo structure identical to my AD structure because it makes life simple. Knowing where objects are in ePo without having to think about it is always a benefit.

I think the only reason to split into 'Home' and 'DR' would be if you have some configuration/protection needs (within ePo) that are different between the two sites. But if your configuration on the DR machines are identical to your live/home network, my two cents would be to leave the structure as is! All depends on how specialized your ePo config needs to be....in my environment keeping PCs, servers, and domain controllers separate is the important part with regards to exclusions, scan times, etc...
0

Featured Post

Automating Your MSP Business

The road to profitability.
Delivering superior services is key to ensuring customer satisfaction and the consequent long-term relationships that enable MSPs to lock in predictable, recurring revenue. What's the best way to deliver superior service? One word: automation.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now