Directory design

[m1kew1lson]

Anyone have comments on a best method for laying out sites within a system.....

In my case we have a single domain, across 4 offices connected via a wan....should I have a site defined for each office, with a superagent and distributed repository for each. additionally any clients of ours who dialin/vpn use our main office should i make a subset within that site.

I'm a little lost on it, but of course i would want to minimize bandwith usage across my wan links.....
...other than the manuals, anyone have some good resources for learning more about epo?

 

[bfralia]

The best way to learn anything about ePO besides the manual which is confusing is talking with people here. NAI isn't very forthcoming when you have problems.

The way you're going to learn the most is through working with ePO. The things we learn the longest are the things we learn the hardest.

I'd have a distributed repository at each site providing you have storage space on the server. You don't have to have a super agent.

In fact, that's the way I have ePO set up across four domains with a repository in each location. Some of my locations are in foreign countries with slow connections to the internet and wan.

 

[NickFerrar]

I think with WAN links you want to minimise traffic on then SuperAgents seem a good idea as they allow you to scale right back on how often you do scheduled updates.

In my own setup with have 2MB links between our 3 offices so I have distributed repositories at each office that update pretty frequently along with regular update/deployment tasks. I haven't set up Super Agents yet but intend do and will probably reduce the update intervals when I do so.

The Directory itself is first divided by Domain and then by Office (we have muliple domains which span the offices). Then finally within each office I have a Workstation, Server and Exceptions group in which the clients sit as appropriate. I also have a further 'Never Install' group below the Exceptions group.