KACE Product Support

I haven't tried this but just thinking about it I can't see why not. Thinking out loud here:

caveat:

• you would need two agents -- one for each ORG, but both could theoretically point to the same file store. e.g. same directory share, or local for one/ share for another.
  
• this configuration is not fully supported so IF it works it could break in future versions or if a problem arose from it you may have to split it up
  

You may run into some locking issues if both agents are writing files at the same time. You could control this with replication share window. If there is a lot of overlap OR, the opposite, uniqueness then you could avoid that. Overlap would avoid contention because you would only need one share aggressively replicating and the other would need only a small slice of time.

As one agent populates files the other will recognize these files when it uploads its share inventory back to kbox.

Anyone else see any issues with it?

I haven't personally done this, but I've seen it work in more than one producition environment actually; not sure if they had any issues down the road or with setup, but the theory Gerald puts forth is solid. Also as Gerald mentioned; it's unsupported so there's always an inherant bit of "good luck" associated with this sort of thing I think.