- #EXE TO MSI WRAPPER INSTALL#
- #EXE TO MSI WRAPPER UPDATE#
- #EXE TO MSI WRAPPER WINDOWS 10#
- #EXE TO MSI WRAPPER CODE#
- #EXE TO MSI WRAPPER WINDOWS#
You make a copy of the PSAppDeployToolkit folder for the old version of the app, replace the installer files, tweak the PowerShell file and you're ready to go.
#EXE TO MSI WRAPPER UPDATE#
So why do I think this is a good way to go? First of all, you can swap packages around all you want, you don't have to repackage the app every time an update to the app is released. The important thing is not what it returns, SCCM just checks if anything returns at all. Get-WmiObject sms_installedsoftware -Namespace "root\cimv2\sms" | where-object The WMI class SMS_InstalledSoftware that gets installed with the SCCM agent (if you've enabled those classes in Asset Intelligence) collects registry values from both 32-bit and 64-bit software. Learning this instead of trying desperately to repackage things to MSI will benefit you down the road.Īnd for those where I really don't know, the registry usually knows something. Only start to care about versions when it becomes a problem with superseded apps. When it comes to Detection Methods when actually creating the application in SCCM, just point to the registry or a file and call it quits.
#EXE TO MSI WRAPPER CODE#
The benefit of this is that once you know where to write your code and how the functions work, it becomes a consistent experience. It has functions for easy creation of registry values, shortcuts, taskbar pins, and you can show a GUI. PowerShell App Deployment Toolkit is the toolkit of choice if you don't want to write a lot of code yourself. bat files unless it's only a couple of lines. One tool for everything, don't bother with. I definitely recommend PowerShell for this. Also does MSI.ĭepending on how long you spend, how complex these "configurations" are and how well you understand PowerShell, this might be cheaper, easier to maintain, respects the integrity of the installer (actually lets the installer run instead of just dumping some files and reg values), etc.
#EXE TO MSI WRAPPER WINDOWS#
Microsoft really wants this to be the package format of the future.įlexera InstallShield has been the de-facto Windows installer for years, and it supports repackaging to MSI.Īdvanced Installer was one of the first third party repackagers that began supporting MSIX, so they got promoted by Microsoft for a bit.
#EXE TO MSI WRAPPER WINDOWS 10#
MSIX is new and only supports recent versions of Windows 10 (1703 and up). SCCM natively understands this format and has some cool stuff to support App-V. A tool called App-V Sequencer makes the packages in. This is probably what you've been looking at.Īpp-V is built-in to Windows 10, and needs to be installed on Windows 7. You run it, it records every change to files and registry from when you hit Start and until you hit Finish. But scripting can definitely be worth your while if you want to keep things simple. When you use SCCM, I know it's tempting to convert everything to MSIs so you can forget about the configurations, writing detection methods, etc. There's two approaches, using scripts or repackaging/sequencing. Which has all our personal setting already important I don't mean to be condescending to anyone here. I think the thing to focus on is silent installs so its nice and easy./r/SCCM will get you much higher quality replies. I also see people getting stuck in the MSI CustomAction, I think its more complicated that what is needed. (otherwise you have two entries for the installs).
#EXE TO MSI WRAPPER INSTALL#
You don't then have to hide the MSI install from AddRemove Programs etc. If the MSI is going to install the EXE it must do it silently, why not just give the switches to be used by a deployment tool. I think its a little bit dishonest, it doesn't have to be, but the way I see it used, it is. I have seen people do that when they are 'packaging'. I don't like the idea of wrapping exes in MSI's. In essence you can do that with InstallShield that you already have. You could chain the MSI's (messy) or go down the route of Microsoft Office and the Adobe suites, and have XML driven multiple MSI installations. If they are deploying with GPOs they would need MSI's, but not may people use that now. Most want silent with a preference of MSI, but if its an EXE and silent that is fine. Find out if they want MSI's to install, or just the ability to do it silently. You should be able to create a silent installation of the EXE with all the pre reqs so your customers can deploy it.
0 kommentar(er)
