- MSI SOFTWARE PACKAGING TOOLS HOW TO
- MSI SOFTWARE PACKAGING TOOLS INSTALL
- MSI SOFTWARE PACKAGING TOOLS MOD
- MSI SOFTWARE PACKAGING TOOLS LICENSE
They are often used by administrators to customize the behavior of an existing MSI file. MST files are used to transform the content of an MSI package. Especially in the Microsoft world.Home » Documentation » MST Transformation Files Overall ,things are becoming amazing really fast. i can't name a single novel use for it that is in practice at the moment. MSIX is just too fledgling, and creates far more frustration than anything else.
MSI SOFTWARE PACKAGING TOOLS INSTALL
Universal install packages are indeed the future, and so is containerization. We simply should not be re-creating the same godamn chrome packages, or vpn msi's every few weeks to add a small amount of company specific customization. Microsoft has to(and already is !!!!!) take GITHUB to the next level and make universal safe/signed package repos that autointegrate with everything from VMWare (think docker containers but vmware OVA images) to Azure,AWS etc. And then there are a few new ones whose names i can't think of right now, that are fantastic with JustInTime functionality for todays SCCM admins.
MSI SOFTWARE PACKAGING TOOLS LICENSE
These tools have competition now and Advanced Installer smokes the 20k/per license Admin MSI studio tool that we all wanted back in the day. This is really just a lingering sentiment from my early career days. Tools like Advanced Installer need to be just a bit more affordable. Well it aint happening that fast everywhere and configuration creep is still a thing. I spend most of my time adopting the fascinating devops platforms to Sysops environments, which i know is backwards because (evolve to the cloud and IAAS right?). I am an SCCM expert also, and SCCM NEEDS to be re-created to be a world class devops, git/ops, ci/cd platform that is cloud native.
MSI SOFTWARE PACKAGING TOOLS HOW TO
the way you can structurally modify the OS with zero complaints about permissions is so time saving, AND no one has to learn to script at my level ( I suck but am the highest on my team by far because they don't seem to know how to copy/paste from git hub), and therefore the work is stable and shift-able. I have it in my Azure Build pipeline, and MSI's are ultra integrated on windows.
What I like most about AI and it's frameworks is that it is fully DEVOPS pipeline compatible. I have to add dynamic properties and/or Transforms to change HOW the MSI install is configured by the data that is gathered. I have to add 6 language GUIDS to the thing because it will not be 'detected' correctly. Some of our TOP vendor MSI's require a decent amount of modification by me. I hate MSIX, and hope it dies, but it is good to get ready for it as well. I love the way PSADT lets me practice PWSH, but taking things that are not MSI's and making them into professional code-signed MSI packages just feels right. I wanted tools like that all of my 19 year career, and now that I can afford it it great to have! I constantly take my PSADT scripts and add that functionality into MSI's with AI and they handle it much better. Especially progressive ones like Advanced Installer. Yes there is still a need for these tools. As a general rule, if someone has flair, they almost definitely know what they're talking about.
Microsoft employees typically have MSFT Official flair, and MVPs usually have MSFT Enterprise Mobility MVP with a link to their personal site/blog.
MSI SOFTWARE PACKAGING TOOLS MOD
Please send mod mail if you qualify and would like flair set for your account.
URL shorteners cause this almost every time, but so do strings of apparent gibberish like WSUS and PXE sometimes. It might have been caught by the spam filter. Post your SCCM tips and tricks, requests for help, or links others might find useful! Post not showing up?
0 kommentar(er)
