Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Options other than Cloning

Created: 15 Jan 2014 | 10 comments

So I am creating a TON of scripts to  be run on my computers. Currently I am writing a base script, cloning it, and just modifying the section the 1 word that changes per script. 

Is there a way to import a list of stuff into the jobs and tasks so I don't have to keep cloning the job one at a time? 

Operating Systems:

Comments 10 CommentsJump to latest comment

SK's picture

I believe tokens, both default and custom, would probably help you.

Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads.

admobandy's picture

Unfortunately for what we are doing it won’t work. We are creating Printer Scripts so the variable that I am changing is the printer name. Which the computer will not be able to detect. We have 700+ printers so it’s taking time.

Thanks for the suggestion!!!

SK's picture

Are the printers present in AD, and if so, are they located in the same OU's as the users that will use them?

Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads.

admobandy's picture

The printers are in AD but in another Domain than the users that would be using them.

SK's picture

OK, so there isnt a printer to user mapping within AD that we can use then?

Do you already have say a spreadsheet that contains a list of all printers, as well as a mapping to at least user groups?  If so, we could import that data and automatically create the associations.

Do the printers already exist within the Symantec_CMDB?

Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads.

admobandy's picture

I have the printers in a spreadsheet, but I am mapping the printers per computer not per user. Since the users travel we want them to print to the nearest printer.

No the printers are no in the CMDB, I am using a powershell script to map the printer at logon.

SK's picture

So you are using a task server run script at the logon stage to map printers to machines, correct?

Is the mapping based off of IP Address?

Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads.

SK's picture

OK.  Either use an AD Import rule or SNMP inventory data to bring these printers into the database as resources.  The latter would be better as you would then have their IP info I believe.

You should then be able to create a token that updates a variable or variables within your run script with information about the printer.

This would then hopefully allow you to only have one run script.

Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads.