dave.dolan

yeah, you can tell I don't work for a union shop right?

bday

Yeah seriously!


Well, your v2 is working flawlessly over here. Thank you so much for making this utility available!!

xrikazen

I know this thread is long dead but I wanted to say two things:

1. Thanks for the prog, its simple and works great but...
2. My solution to this issue was to simply create a folder in the deployment console with all of my jobs listed numerically inside of it in the order I wanted them to run. ie,
1 - Deploy Image
2 - Install Office
3 - Reboot
4 - Install Winzip
etc...etc
Then, all I had to do was instruct our team members to drag the computer to that folder instead of to an individual job. That way Altiris can take care of when the jobs/installations are complete and when to start the next one - and I could create different folders of jobs for computers that needed different sets of software (Laptops and Desktops). Obviously not as clean as some would like, but it works OK for me.

Sachiv

My simple solution was

create a folder
create my jobs under that folders and call them

A-Job name
b-job name
c-job name

and when helpdesk build the machine they just bung the whole folder onto the machine and bada boom.

joshargh

ive done this with a generic vbs script that reads a list of jobs for a build type then calls axsched.exe passing the local computername + jobname too it. It worked well enough for what I intended but decided it felt much to kludgey overall... for me a build job should be as much of a solid unit as possible, within reason of course.

Gibson99

back from the dead... again.

our solution here (granted, it's in ds 6.9sp2) is to make a job with a bunch of scripts with only a single REM statement ion each that, on finish, will run the actual job. it's a bit overcomplicated, but it simplifies job maintenance and still allows techs to drop a single job on a machine or the entire build job.

ie: run script. REM Install Adobe Reader, next, next, on success: Adobe Acrobat Reader 9.1

initial setup was tedious but it gives us so much more flexibility now.

Setral

Replying to dead topic...

We do this exact same thing on many of our "loadsets". This works great, and only time we need to adjust them, is when the old one is retired and a new one created. Versioning and all that jazz.

::Run This script::
REM Install <App Name>
exit 0

**Next**
::On the client computer::

**Next**
::Success:: (Points to App to run)