faq
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| faq [2021/03/17 12:57] – support | faq [2022/01/25 10:29] (current) – [How can we have Job Control to automatically start in every single machine when a user logs in? (Windows environment)] support | ||
|---|---|---|---|
| Line 8: | Line 8: | ||
| ==== Is there a JobCTRL® mobile application? | ==== Is there a JobCTRL® mobile application? | ||
| - | Yes! you can download the application from clicking [[ https:// | + | Yes! you can download the application from clicking [[ https:// |
| ----- | ----- | ||
| Line 18: | Line 18: | ||
| To be productive, you must be active too, because inactive and offline time on a productive app/task won't be productive time. | To be productive, you must be active too, because inactive and offline time on a productive app/task won't be productive time. | ||
| ----- | ----- | ||
| + | |||
| + | ==== How can we have Job Control to automatically start in every single machine when a user logs in? (Windows environment) ==== | ||
| + | So we should achieve JC to be installed. It can be done with a pure LOGON script, which checks whether the JobCTRL directory exists and if not then it creates it and copies JC files there from an existing installation (eg file server) | ||
| + | \\ (HINT: JC can be " | ||
| + | |||
| + | a sample script may looks like this: | ||
| + | ** | ||
| + | TargetDirectoryShouldBeWrittenHere** | ||
| + | |||
| + | |||
| + | the **" | ||
faq.1615985854.txt.gz · Last modified: 2021/03/17 12:57 by support