PMs have been sent to TeAm Mates that might be able to help out on this. If
anyone thinks they can help out, please step up.
babbage,
Concerning Point 1:
You can setup your SetiQueue to only communicate with the outside Queue (Mucman's JSetiDoor in this case) during slack hours ... for instance, in the middle of the night. You can adjust this time by going into your SetiQueue's Settings and adjusting the PROCESSING TIMES.
On Point 2:
SetiHide works on my small home LAN with SetiQueue just fine but there may be some issues about a large network that are beyond my pay grade.
That said, there is a non-caching method of installing over a LAN called the "FlexInstaller".
Check out Shuxclams website for Service Installs I have asked
Shuxclams to give you some assistance on this.
I just downloaded the FlexInstaller and ran it to see how it would work. It has a pretty easy interface for installing on your entire network all at one time.
Problems I see here are (1) there are no cached WUs on each Client which means as each WU is completed the Client will have to upload the results and download a new WU from your internal SetiQueue and (2) there is no "built-in" method of starting and stopping the Cli Clients once the process has begun.
Suggestion (until someone can chime in with a solution for us):
Run the FlexInstaller and only put it on a few of your network machines. That way you can at least get Seti going and WUs flowing through
Your Internal SetiQueue and
Mucman's JSetiDoor Queue which he has created especially for your individual use. These "few" machines can then be experimented on to try and find solutions to any issues that may arise. You will need to initially coordinate with
Mucman to get your Q and his JQ working together. After that it should be automatic. He has the capacity to handle your production.