Hello All,

I am trying to deploy ZFD6.5 into our tree but have a couple of
questions regarding layout of containers and policies before wanting
to go further forward. My existing tree consists of.

O = ORG
OU = REG1
OU=LOC1
OU=LOC2
OU=LOC3
OU=REG2
OU=LOC4
OU=LOC5
OU=LOC6
OU=REG 3
OU=LOC7
OU=LOC8
OU=LOC9

Each LOC has a NW6 or 6.5 server, and 10 or more workstations
(win2000). Each is seperated geographically, and has full t1's
running between them

Currently I have ZFD6.5 installed on a NW6 server in LOC2 container.
If I wanted to have a central repository(ORG.ZENWS) for all imported
workstation objects am I still able to associate the workstation
object to the local 'branch server' so that it can roll up inventory
to the root server/databse ? I dont want 300 + workstation objects
sending thier STR files across the WAN, i would rather use the LEAF/
ROOT Rollup scenario

Would it be better to import the workstation objects into thier local
LOC container, and create workstation polices at each container to
controll thier association to thier local inventory service ?

Any ideas for this kind if deployment would be appreciated. I need it
to be pretty scalable, as the number of REG's and LOC's are sure to
change.