|
| | | Forum Newbie
Group: Forum Members
Last Login: 4/28/2008 4:30:12 AM
Posts: 4, Visits: 25 |
| Hi,
Need some suggestions to automate a command run using Prism.
Every week i have to build a update package to install on several machines, this package add some files and deletes one log file.
Now i want to have a command executed automatically on the machines where the log file doesn't exist, because this is the indication that the command needs to be run on the PC and this creates a new log file.
I have the command task in place (assigned as reinstall) and it works but only one time and not every time the machine gets the updated package.
What i'm doing wrong or e need to assign this using a Prism Script file?
___
Rui Paz
|
| |
| | | 
Supreme Being
Group: Moderators
Last Login: Yesterday @ 10:05:18 AM
Posts: 655, Visits: 811 |
| Your best bet is going to be creating a Configuration Group based on the existence of the log file, and then assign the command task to that group and have it assigned as a repeating task. Your repeating options are intervals (hourly, daily, weekly, or monthly) or events (a user logs on or the system starts up). The repeating schedule will only be valid for machines that are currently members of that group.
So, for example, you build the group and assign the task to run daily. When a computer does not have the log file, it will join that group and get the assignment. Because the task has never been run before, it will run the task. The task lays down the log file so the computer ends up leaving that group. This means that the task is no longer assigned, so it will not run again the next day. If, at some point, the computer rejoins the group because the log file is missing, the task will run again because it has been more than a day since it last ran.
New Boundary Technologies Support
support@newboundary.com |
| |
| | | Forum Newbie
Group: Forum Members
Last Login: 4/28/2008 4:30:12 AM
Posts: 4, Visits: 25 |
| Neo (4/24/2008)
Hi,
I have the command task in place (assigned as reinstall) and it works but only one time and not every time the machine gets the updated package.
What i'm doing wrong or e need to assign this using a Prism Script file?
I forget to mention, already have Configuration Group that checks if the log file doesn't exist and have the run task assigned to this group. |
| |
| | | Forum Newbie
Group: Forum Members
Last Login: 4/28/2008 4:30:12 AM
Posts: 4, Visits: 25 |
| New Boundary Support (4/24/2008)
Your best bet is going to be creating a Configuration Group based on the existence of the log file, and then assign the command task to that group and have it assigned as a repeating task. Your repeating options are intervals (hourly, daily, weekly, or monthly) or events (a user logs on or the system starts up). The repeating schedule will only be valid for machines that are currently members of that group.
So, for example, you build the group and assign the task to run daily. When a computer does not have the log file, it will join that group and get the assignment. Because the task has never been run before, it will run the task. The task lays down the log file so the computer ends up leaving that group. This means that the task is no longer assigned, so it will not run again the next day. If, at some point, the computer rejoins the group because the log file is missing, the task will run again because it has been more than a day since it last ran.I did check the scheduling options to repeat the task but didn't understand witch option will work for my case. If i understand your explanation correctly assigning a daily repeat schedule to the Configuration Group it will do the trick. Tanks for your help. |
| |
|
|