Hi all and thanks in advance for helping!
I was wonder if there is a way to limit jobs by user instead of workstation?
We have a workflow based on AD where we give permission to users so it will be very helpful to find a way to create a limit based on Users instead of adding each workstation to a Machine Limit everytime the user of the workstation changes (I mean…maybe the first user has acces to a project but the second one doesn’t).
Waiting answers, thanksss!
To phrase your request another way - you only want the user who submitted the job’s computer to work on the job? You can do that with the dequeuing options here.
If you mean you want to have a limit per user, so each user’s jobs would have a limit in how many tasks would be worked on concurrently you could look at creating a limit per user and automatically applying that limit to any job submitted by them.
To do that, you’d probably want to automate making the limits using the Scripting API and using SetLimitGroup to create the resource limit.
And to set the limit automatically on job submission you’d use an event plugin like this one. Just in this case you’d check the username associated with the job and set the limit based on that.
Hi Justin! Thanks for your reply but seems I didn’t explain myself very well…
We have several users, each one working on different projects and having access only to those projects folders they’re working on. These permissions are managed by Active Directory at User level so we can have User1 can access Project1 and Project2 using Workstation1. If I add User2 using Workstation2 and only having access to Project1, my Allowed Machine Deadline Limit for Project1 will become [Workstation1, Workstation2] and [Workstation1] for Project2. But User2 moves to another workstation (3) so we should modify the limit to add Workstation3 to Project1’s Limit and “delete” Workstation2 from the Limit.
What we’re asking for is if there is a way to manage limits where we can list the users (Project1=[User1,User2]) instead of the workstations.
Sorry for the confusion. I expect now it is better explained 
Ah, gotcha. There isn’t a way to set limits like that without some scripting on your side.
Are the machines Windows or Linux? If they’re Linux machines the Render As User feature has the Worker impersonate the user that submitted the job and could simplify your setup enormously. The Windows implementation isn’t as smooth so I’m less quick to recommend it in those cases.
Or could you run the Worker as a separate user that has permission into all projects? To do that, re-run the installer and choose ‘run launcher as a service’ and set your new render user as the user for that service. And then update the shortcut to the monitor to run the deadlinemonitor.exe instead of deadlinelauncher.exe. That way the user will be able to open a Monitor while the Launcher and Worker run as the render user.
We were trying to render with the worker as a different user but we haven’t been able to do that but we haven’t tried it as a service we will give it a try, thanks!
Machines are Windows so we first give a chance to first option hahaha
Keep you updated with news, thank you again!
Here is an update!
We’ve deployed the worker as service to our workstations and it is working as we expect, thanks!!
Once done that, we have a small question:
We have seen the Worker Scheaduler does not work when using worker as a service, Is there a way to make it work or we should use the Windows Task Scheaduler from now on?
You mean for idle detection, right? There isn’t a work-around there, services on a machine aren’t allowed to peek at what users are doing, so if you’ve got a Windows Task Scheduler workaround that’s doing what you’d like then I’d carry on.
If you’re instead talking about worker scheduling starting the Worker at specific times that should work. If you check the deadlinelauncher log around when you expect the Worker to fire up, what’s it doing?
The logs will be on the machine in one of these locations:
Windows: C:\ProgramData\Thinkbox\Deadline10\logs
Linux: /var/log/Thinkbox/Deadline10
Mac OS X: /Library/Logs/Thinkbox/Deadline10
The Launcher should be explaining why it is or isn’t starting the Worker, and if it succeeded.