"System Environment Variables" or "Tokens" available in SWD/Tasks/Jobs
I want to acomplish the following:
- Run SW-installation or any other command with as result a log-file
- Check if the %COMPUTERNAME% has a LOG folder on a netshare. If not create it
- Check if the Task/Policy running has a LOG folder on \\NetShare\%COMPUTERNAME%. If not create it
- Copy the log file in there
This way I always have a centralized log-repository of all that runs on a managed client
Coming from Livestate, one had several tokens to use in cmd/batch scripts like:
\\config\clients\%CLIENTID% --- As specific folder on the NS server (in Altiris terminology) of the managed computer
\\depot\%SWID% -- Repository off all vendor filesets needed to accomplish the needed command(-s) for that specific task running
%SWID% --- Task/Policy name (in Altiris terminology)
I know in DS there are tokens and some tokens are available in Notification Policies, but if and which are available using Software Deployment or Tasks/Jobs?
I did a test by writing all System Environment Variables to a txt file, but that did not give me additional possibilities.
Suggestion / solutions are welcome... and will be honored
Guido
Comments
Guido, I think your best bet
Guido,
I think your best bet for this functionality would be some sort of wrapper around your main installation package. We use VBScript wrappers on almost all of our packages to tweak registry values, delete files before install, check various system values (free disk, etc), and other items. If you want to create a log file/folder on a server after execution you can do that in the script.
You can always look at the "AeX SWD Execution Summary" dataclass to see what tasks have run on a particular machine.
There are a few tokens available you can use when defining a package, for example we use the "Alternate Download Destination" on our Packages to download many of them to \\%COMPUTERNAME%\ShareName\Vendor\App\Version.
Thanks,
Kyle
Symantec Trusted Advisor
For Forum threads, please click "Mark as Solution" if answered.
For all content, please give a thumbs up if you agree with or support the post.
Software Delivery Report
The other benefit of using the built-in SWD Execution summary is that you can report on it easily, without having to parse out a bunch of log files. I have a "Download" or Article here with a report that will show all the machines which have run a program within a specified package. You can view it here.
Thanks,
Kyle
Symantec Trusted Advisor
For Forum threads, please click "Mark as Solution" if answered.
For all content, please give a thumbs up if you agree with or support the post.
Thanks you all
.. for you reply. I know SWD Execution, but especially during development or the troubleshooting of an process, I find it very handy to also have a look at the original created log files. I will have a go with your suggestions.
Thx again!
If others have additional suggestions, please.
At least you'll have my vote
Guido
Guido Langendorff
Arrow ECS Netherlands
Netherlands
Select "Mark as Solution" when it has resolved your problem.
Give a "Thumps up" when you like the comment or "Thumps down" when n
Would you like to reply?
Login or Register to post your comment.