Packaging and Deploying MSI help

[johbreaking]

Bit of backstory.

 

Past 5/6 years i have been mainly dealing with a cc4 environment and now i have moved back over to a flat vanilla network. I have been used too either importing a msi or using RM package builder to build the packages and then deploy them using package distribution through the RM console. Is there anything similar in a vanilla network or can someone give me a dummies guide to doing it.

 

I want to repackage all my software over the summer and deploy it right but want to know best methods.

Edited July 3, 2017 by johbreaking

[Killer_Bot]

We use EMCO here to good effect. Not free but works a treat.

 

https://emcosoftware.com/msi-package-builder

 

I've also played with WinINSTALL LE in the past but that is no longer free anyway.

 

- - - Updated - - -

 

I should clarify we then use SCCM to delpoy the MSI or Group Policy at a last resort.

[Norphy]

First rule of repackaging is:

 

DON'T

 

unless you REALLY have to. I've found that most installers have command line switches that will let you run them silently. The vast majority of MSIs can be deployed silently. Any piece of deployment software worth its salt will be able to deploy MSIs or EXEs (SCCM can, I know that KACE, ZCM and Altiris can as well). When I've been responsible for this in the past, I've found that the actual amount of repackaging I did was minimal.

[Killer_Bot]

First rule of repackaging is:

 

DON'T

 

Each to his own but I'd hardly call that a 'Rule'. If that's what works for you then great. Myself, I've had to deploy a few exe's for software that have very few switches or require configuration that isn't easy to do post install on mass. Repackaging has been invaluable on both occasions. And for that; we use EMCO.

[RobD]

I used to package in my last job until i found PDQ Deploy.

[Norphy]

Each to his own but I'd hardly call that a 'Rule'. If that's what works for you then great. Myself, I've had to deploy a few exe's for software that have very few switches or require configuration that isn't easy to do post install on mass. Repackaging has been invaluable on both occasions. And for that; we use EMCO

 

There are always exceptions to the rule and yes, I repackage if I have to but IMO repackaging is a last resort, not something I'd do as a matter of routine. I've found that repackaging often causes more problems than it solves. That's why I avoid it if I possibly can.

[johbreaking]

Thank you all for the responses.

 

I am slightly surprised that there is nothing like RM deployment which was so easy, just select the group and use a tick box.

[Fazza]

Most .exe and certainly .msi files tend to have a silent install option so you can deploy via a logon script etc. or using something like SCCM where you can add them to a task sequence when deploying an OS. Some times it can be a bit of an art form as if a poorly written .exe has been used by some random software house it may not be obvious what the silent switches are.

[ReadTheNetwork]

If you create virtual apps, then this is quite an easy 'packaging/deployment' method.

[johbreaking]

How simple is SCCM to setup just to deploy packages from?

[mavhc]

There's lots of programs that will capture changes like RM does, but it's a terrible idea mostly.

 

I'd look at https://wsuspackagepublisher.codeplex.com

 

How do people who just use silent install scripts check that the software isn't already installed?

[Norphy]

If you use SCCM, you can tell it to check the file system or the registry for an entry.

[ReadTheNetwork]

It's pretty straight forward, either by doing silent install scripts and/or using AppV.

 

How do people who just use silent install scripts check that the software isn't already installed?

 

SCCM can run reports on machines to let you know what software is already installed. With applications you create requirements for it to check if it's installed or not (such as registry key, file exists etc), you can set requirements as well. You can set it to upgrade, remove software etc.

 

It's even clever enough to give you reports on how often programs run for, how often they are used, who they're used by. For example if you have a license for some software to run 20 instances at the same time, you can monitor it and review if you need the 20 licenses. Or if a teacher asks for an updated bit of software, you can argue that they havn't used certain software etc etc. This would take a little more configuration but the ability is still there if you wish to enable it.

[Fazza]

How do people who just use silent install scripts check that the software isn't already installed?

 

Like others have said, SCCM is a very clever bit of software and there are some prerequisite checks you could do but to be honest, I dont bother with that. I just silently deploy software out to the relevant computers and if it's already installed then the silent install will simply overwrite it etc. The clever thing is that once pushed out to a computer via SCCM, it wont do it again as it will have recorded that it's been installed. It's the same if you use the Software Center, once you've installed something via the center then it's listed in the installed section so you can't install the same thing again.

[Ertech]

+1 PDQ Deploy