You could parse the policy.sync log for a specific key-word ?
That way, you'd only trigger your action once the client actually knows "Hey - I've got poliy X ... gotta do stuff Y!" ?
The log is here (assuming WIn 7 or newer) -- C:\ProgramData\LANDesk\Log\
would that help?
You could use the rollout projects... First step would be to deploy the package to the Portal. After scheduling the deployment you could go to the next step, which could be to push (run directly or after a specified time) another notification program on the client.
Yeah - that'd work great. Like the thinking .
Nice, I wasn't aware of this functionality.
I'll check it out, thanks!
Here's a couple of things to help you along / get started with rollout projects:
This is a video webinar -- may be easier than "just a wall of text" potentially .
From what I read (I didn't watched the webinar yet), it looks like the only exit criteria from step to step are either (1) timer related or (2) success rate related.
In my case, the ideal exit criteria would be: if a step succeeded on a computer, then forward the same computer to the next step, regardless of the total success rate.
A bit of context may help. This is what I have in mind:
- Step 1: push sources on the target computer
- Step 2: publish a package in the portal manager. (The said package executes the sources deployed in Step 1, so the scheduling is important)
- Setp 3: send a mail to the user with the documentation, explaining how to launch the portal manager, etc.
I will ignore the timer related stuff for now, as it is not needed.
From what I tested, it looks like If I don't specify a success rate as an exit criteria (nor a timer one), the "next step" is never launched, which seems logic.
If if specify a success rate < 100%, I fear that Step 2 would be deployed to computers that haven't received Step 1, and thus produce unnecessary errors and user confusion.
To avoid this, I could put the success rate criteria to 100%, but it means I have to successfully apply the first step to all my computers (5000+) before launching the next one, which is problematic because contacting so much machines in our environnement could take months.
Also, the default state of a computer in a "portal manager published" task is "Pending". Is this state considered a success by the Rollout Project module? I hope so, as it would be mandatory in order to pass from Step 2 to Step 3 in the above workflow, ensuring the documentation would be sent to the user before they execute the package.
Am I understanding things right?
1 of 1 people found this helpful
You *CAN* use Bundles instead of "an individual piece of software" ... so "step 1" can in fact be the installation of several steps / bits of software.
Just because it LOOKS like you're installing a single action (a single bundle) - remember that the bundle can include several actions itself (say - One software, One Windows Action package which displays a message box to the user - a reboot - etc.).
So it's not ALWAYS the case that "1 step = 1 and only 1 action" . It can be a bundle as well .