Quote:
Originally Posted by Ron_Lang
My question is:
-How do I chain 2 or more individual jobs with individual tasks together?
What I would like is to have one job that is replicated or linked to other jobs in a sense that if that one job is changed, I don't have to go and edit all jobs that this one individual job exists in.
|
I recently did this for my organisation. It was very much a hackjob, but you know what? It works!
Create a new
Run Script task.
Run This Script:
Code:
rem Install Adobe Flash Player
rem This task is a placeholder for existing install jobs in the Console.
rem Update the next line as required.
\\SERVERNAME\EXPRESS\AXSCHED.EXE %NAME% "<Jobname>" /t %TIME:~0,5%
axsched.exe: command-line scheduler.
%NAME%: computer name in the Console.
"<JOBNAME>": the name of your job
exactly as it appears in the Console.
/t: time to schedule
%TIME:~0,5%: The current time in 24 hour hh:mm format.
Script Run Location:
Locally on the Deployment Server
Client Run Environment:
Production
BE WARNED - even though the
Client Run Environment section turns grey when you select
Locally on the Deployment Server, those details are STILL APPLIED. Try
Security Context as
Default (local system account) and see if that works - you can test it with another account later.
Now you can populate that same job with as many different scripts as you need. Mine looks like this:
(
link because it won't embed)
It's split for easy reading, but you could theoretically stick all your AXSCHED.EXE commands into one script file.
EDIT: Background.
The SOE that I inherited originally had the sane set of app deployment scripts (embedded as conditions) for each device model - 7/8 for desktops and another 7/8 for laptops, as well as another, identical set of jobs for machines being put onto the network for the first time. This meant that when Adobe updated their Flash Player (for example), I had to update about 15 sets of conditions in
each of the four (or six, depending) different deployment types. I took four of the six deployment scenarios, re-wrote the scripts to process server-side where possible, merged the deployment conditions, added conditional tasks specific only to laptops or desktops, and migrated the whole shebang to WinPE.
There's now ONE job which queues up all necessary tasks to build any laptop or desktop, be it for the first time or as a rebuild, and adding or updating applications in the SOE build sequence is a question of changing
one associated script in
one location.
ALSO, there's no guesswork with applications on new PCs; the original SOE sequence would say "Deploy SOE". This one will tell you, at a glance, exactly what's been installed on any given machine from the second it's finished imaging.
Hope this helps.
