AnonGod
IS-IT--Management
- Jun 5, 2000
- 223
Ooooh, first post. And like a screaming admin on New Years eve, we begin...
This is a continuation of a post from Enterprise Level Desktop Management. The main focus of the post was to get more information about a possible third-party program that will allow me to customize ANY software application install, allowing remote installations using the original install files instead of using a program like SMS Installer that takes "snapshots" of before and after the install then compiling all these into a setup.exe for the client to run.
I have learned a little since then, and realize there are ways of doing this, but only if you know a fair amount of scripting and coding and such. I am not so fortunate, and am holding to my firm belief that there is a better way.
Until that day comes, I have found the easiest way to customize installations is to use the tools the manufacture provides with the install files. Now, this sounds all fine and dandy, but there are so few standards when it comes to this, that I am needing to research the Switches, MST files, MSI files, and INI files that are available for use in each installation program far in advance before we can deploy them.
So, since I am posting a question, here they are....
-How can I keep my hair from falling out (or me pulling it out) while trying to figure out how to deploy the software we use in our organization?
-Are there any websites, books, articles, any info (free?) that will help me understand all of these files used in installs (MSI, MST, INI, etc.) in a logical way, without going into complicated code?
OK, I've rambled on enough. Any questions, comments, thoughts and insights are welcome. Thsnk you.
>
:O> anongod@hotmail.com
"Drawing on my fine command of language, I said nothing."
This is a continuation of a post from Enterprise Level Desktop Management. The main focus of the post was to get more information about a possible third-party program that will allow me to customize ANY software application install, allowing remote installations using the original install files instead of using a program like SMS Installer that takes "snapshots" of before and after the install then compiling all these into a setup.exe for the client to run.
I have learned a little since then, and realize there are ways of doing this, but only if you know a fair amount of scripting and coding and such. I am not so fortunate, and am holding to my firm belief that there is a better way.
Until that day comes, I have found the easiest way to customize installations is to use the tools the manufacture provides with the install files. Now, this sounds all fine and dandy, but there are so few standards when it comes to this, that I am needing to research the Switches, MST files, MSI files, and INI files that are available for use in each installation program far in advance before we can deploy them.
So, since I am posting a question, here they are....
-How can I keep my hair from falling out (or me pulling it out) while trying to figure out how to deploy the software we use in our organization?
-Are there any websites, books, articles, any info (free?) that will help me understand all of these files used in installs (MSI, MST, INI, etc.) in a logical way, without going into complicated code?
OK, I've rambled on enough. Any questions, comments, thoughts and insights are welcome. Thsnk you.
>
:O> anongod@hotmail.com"Drawing on my fine command of language, I said nothing."
