Application Packaging - Batch v VBScript v Powershell and career advice
Community Chosen Answer
I am a full time packager, I am mainly an MSI guy, but do a lot of App-V (4.6 and 5).
I personally don't use a lot of scripts in packaging, mainly just MSI stuff. There is a lot you can do with an MSI......
I have a vbs that adds and removes entries from a file (like the hosts or services file). Also a vbs that I use to run secedit as a CustomAction in an MSI, I have not used either for a long time.
If you don't know ANY scripting language, and you work mainly in Windows, I would go down the PowerShell route. Happy to hear other peoples arguments on that.
I mention this a lot, but there is a free 'limited version' of AdminStudio for SCCM users. You can capture legacy setups to make MSI, but you can't actually exclude files or reg keys in the IRP or edit the ISM file, (its not really limited, its almost pointless). Almost pointless.... it has saved my bacon a few times. You have to clean up the MSI in Orca. I hope to write a blog soon about getting the most out of the 'limited version'. (Watch this space)
There are some more reasonable tools you can but yourself like the Infopulse PACE.