Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

Deployment Solution Script Repository

Created: 29 May 2009 | 3 comments
Mike.Langford's picture
10 Agree
1 Disagree
+9 11 Votes
Login to vote

We use some scripts that pull values from a SQL server into tokens that are cotained in the script and then drive mappings and other actions happen based off the values that are passed into the tokens.  An issue that we have run into is that when a change is needed in a script, we have to go through the script in every single job to make the update.  It would be great if there was a central repository for commonly used scripts where you could just point a job to that script to run it.  That way there would be only one script to update, but the changes would happen across the board.

Comments

DSnelleman's picture
08
Jun
2009
0 Votes 0
Login to vote

This is already posible

Mike,

We already have configured our DS to do this.
if you just create a folder on your DS (or like we did on a DFS so we can use them from all of our DS Servers) with all of your scripts.
Then at the script job you can just select run script from file and browse to this folder and select the script to use.
The security on the folder should only allow access for your altiris service account.

Regards,
Dennis

Mike.Langford's picture
23
Jun
2009
0 Votes 0
Login to vote

Yes but...

You are correct that you can store scripts in a central place and run them, but the part that we haven't gotten to work is running scripts from a central repository where there is token replacement occuring from the SQL database and from the computer properties.  For all generic scripts that don't require this, we do have them in a central repository.

MurrayW's picture
23
Sep
2009
0 Votes 0
Login to vote

Yes, but...

Can you not keep all your static scripts in a central repository as well as utilising the "temp" folder for resultant scripts from ReplaceTokens? That way all you need to do is update the template file and the next ReplaceToken execution dumps this into the "temp" folder for the systems to use. There is also nothing stopping you from setting the output of the ReplaceTokens command to another folder on the DS and use that location as the central repository.

Maybe I just don't understand.

Quote: "I know not what other much is else. But what other else is there?" - ***** (OP hidden as that was too awful! Lol)