Deploying a chain of packages
A then reboot then B
The community has a fine page for doing this with Provisioning, but this page is to get you started for ad hoc jobs without if you don't know how to use Provisioning yet.
The first question to ask is whether you need to interact with the end user. Do you want to offer deferral? Is this going to be a policy or policy-supported push? If the answer to either of those questions is yes, you need to do a dependency chain.
First, create a rebootnow.bat file that will live on a network share. It contains two lines:
@echo off
C:\PROGRA~1\LANDesk\Shared~1\winrestart.exe
This file is not specific to your job, though you'll use it again with different Distribution Package names...
Now, go to Distribution Packages and define your packages. All three need to be in Public, and we're going to go Last to First. So in this case, I want to install Adobe Reader 8.1.2, reboot, and then install WinImage 8.
This package is one you'll need to create copies of in the future -- remember that if you later need to install Illustrator 30 after removing Illustrator 29 and rebooting, if you call this package it'll install Acrobat Reader 8.1.2, not remove Illustrator 29.
Now set up your method to your preferences:
And schedule it:
If you don't need to interact with the user and you can get by with a Push, you can use preliminary and final packages. Here's an example:
Note that both of these methods do all the software distribution and push all the "instructions" to the target machines before they do anything. That means it won't work for XP Embedded or Deep Freeze, so don't get your hopes up... I'm just using the LDSS Maintenance Window trick.