I'm having to train myself so I may be over-thinking this, but I was wondering what effect batch scripts have on reporting in SCCM 2007. It seems like SCCM gathers some information about the install from the command line used for the package's program, but I don't know why I think that and I can't find any information about it.
For example: I want to deploy Putty, but its setup does not create a desktop icon (which my users complain when they can't find). Instead of putting `puttysetup.exe /silent` on the command line in SCCM, my program runs a batch script that calls the silent setup and then copies a shortcut from a network share.
The user is completely unaware and as far as the computer is concerned, the program gets installed correctly and the shortcut gets created. I'm specifically curious as to what difference this makes on SCCM.
We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.
I'm having to train myself so I may be over-thinking this, but I was wondering what effect batch scripts have on reporting in SCCM 2007. It seems like SCCM gathers some information about the install from the command line used for the package's program, but I don't know why I think that and I can't find any information about it.
For example: I want to deploy Putty, but its setup does not create a desktop icon (which my users complain when they can't find). Instead of putting `puttysetup.exe /silent` on the command line in SCCM, my program runs a batch script that calls the silent setup and then copies a shortcut from a network share.
The user is completely unaware and as far as the computer is concerned, the program gets installed correctly and the shortcut gets created. I'm specifically curious as to what difference this makes on SCCM.
Thanks.
Share this post
Link to post
Share on other sites