Author Topic: Capture Idle processor times on campus labs - configuration help  (Read 5302 times)


  • Newbie
  • *
  • Posts: 1
Our University is using Qube on 12 client machines, which are also being used as our teaching room/lab. We also have a dedicated render farm of 6 machines.

 What we would like to have happen is when the computer is powered on, with no user logged in, it is available to render.
When a user logs in, the qube supervisor should see the workstation as unavailable to render (qblock).
When the user logs out, the workstation then becomes available using the qbunlock command.

The problem we are having - it works fine if you run the commands logged in as a user, and dropping to a command prompt - but we are trying to add it to a GPO (group policy)
under User Configuration / Windows Settings / Scripts (Login/Logoff) -
Logon Script with the following command : "C:\Program Files\pfx\qube\bin\qblock %computername%"
Logoff Script with the following command : "C:\Program Files\pfx\qube\bin\qbunlock %computername%"

For the machine startup, we have under Group Policy - Computer Configuration / Windows Settings / Scripts (startup/shutdown) -
Startup - "C:\Program Files\pfx\qube\bin\qbunlock %computername%"

we know the Group policy is being applied, as we also have it mapping a network drive, which shows up correctly for the users.

Do you have another suggestion for how to set this up to work in our enviorment?  So far, the product has been great, but if we really need it to function in this manner, so students get the most power out of it when the machines are not being used.  In other words, we are trying to harness the power of the idle machines during the day when they are not being used for class or labs, but do not want them to try to render when a student is using them, as they come to a crawl.

ITS Lab Manager