Thanks for the feedback guys. So it definitely sounds like option (2) is the way to go here.
The client side UI is definitely an interesting idea. I wonder if we could design it in a way so that it’s a compliment to the existing DBR UIs for each renderer. We can build it into the existing SMTD, Maya, and other integrated submitters to submit the “reserve” job and update a list based on which machines have picked up the job. If this could somehow auto-populate the VRay DBR UI for example, that would be really slick.
We’ll have to do some playing around on our end. 
MIght be able to manipulate the DR slaves within the actual 3dsMax file instead of relaying on INI file:
spot3d.com/vray/help/200R1/d … m#settings
Need to have a play to see what is possible or get a feature request in now for VRay v3.
I really like the idea of implementing this properly - DBR that is. It has been my number one deadline wish for some time.
I think a 20 min phone call with Vlado could be enough to come up with a strategy that works. Most of the work would be on his end it seems.
I’m liking the direction of this discussion.
R
Ha! So this is why you gave me the evil eyes re: VMs Chris. 
I honestly hadn’t seen this thread yet hehe. 
Sorry for accidentally breaking your NDA. Yeah we could be down with possibly going for a VM managed system. Assuming it ran really smoothly. Ideally this would be boot-level VMs and not need windows installed. Is that possible?
+1 for DBR I had actually started laying the groundwork thought processes on how I was going to deploy this here as a job plugin like #2. Ideally I would set this as a low priority job like 40 that just sort of jumps in when it’s free. I am pretty sure VRay can now join in mid-render.