Software deployment methods

[sparkeh]

Just wondering how people go about deploying software in a Windows domain.

 

I have been using/looking in to three methods.

 

1) GPO

Pros: When you move a machine into an OU you know what software is going to be automatically installed. When combined with an imaging solution that puts machines into correct OU you have a completely automatic process.

Cons: Quite inflexible, no way to easily force a reinstall and requires user to wait while software is installed before logging on. Only installs msi.

 

2) Purgos

Pros: Silent installs work flawlessly and installs msi and exe.

Cons: Can't assign software to groups of machines in the same way as using GPOs meaning if you reimage you have to manually plug in all the required packages.

 

3) WPKG

Pros: Silent installs work flawlessly, it can install MSI, InstallShield, PackagefortheWeb, Inno Setup, Nullsoft, .exe packages, .bat and .cmd scripts. You can assign software to groups as per GPO and after reimaging change hostname to match WPKG record and auto install software. Also has a great repository of installer files.

Cons: Fiddly to use when mucking about with config files (but haven't checked out the new front end yet)

 

What do other people do?

[pwaddington]

I am currently trialling admin arsenal. Windows Administration Software | Admin Arsenal you can deploy either msi's or .exe's quite easily.

 

More info and vids on their website

[sparkeh]

Thanks looks interesting I'll take a look.

[jamin100]

I use ghost solution suite, basically creates a snapshot before installation, you install the software and make any customisations. Then it creates a snapshot after installation and compares the two.

 

From there it make a exe which can be assigned to a group of computers and it gets pushed out when you want it too...

 

Only downside is that its not automatic, you have to push the image out manually.

 

Works well here though

[irsprint]

I m a GPO fan, it has its cons (needing to reboot) but I always make sure my machines shutdown overnight and startup early morning plus I like to keep everything in one place

[Michael]

As a general recommendation installing as many applications and updates on a single image will save you the most time. You're also clear in your mind what applications users have access to. For the rest MSIs are definitely preferable or alternatively scripts.

 

I generally use scripts for tweaking or registry edits. Not so much application deployment.

[Roopert]

Here i use a combination of msi through group policy and scripts for registry tweaks or single dll file installs.

As you have pointed out there are limitations to this, but due to not being able to purchase any software relating to software distribution this was simply the only option available rather than the best choice.

[SimpleSi]

I use WPKG as it works with any server be it W2K3/8, Linux Samba or Win98SE

 

I use it if time taken to debug why it doesn't work is less than time taken to go around all computers and install manually

 

I don't worry about scripts installing silently as I just run it as an all users/startup folder bat file.

 

I use whatever scripting language comes to hand - bat,vbs and Autoit ones.

 

regards

 

Simon

[chrbb]

Gpo for straightforward small msi's and msts made with orca.

 

Purgos for larger applications, and exe's with silent install.

 

If I have a few updates eg adobe, flash etc I will use purgos to install on pupil machines, but will visit staff laptops as it gives me a chance to give them the once over:) (only 15 so not many to get round)

[waldronm2000]

For what it's worth, GPOs can be used to deploy EXEs as well as MSIs, by creating a ZAP file (fairly straightforward as I recall), but that's when they really become inflexible. As long as you're deploying MSIs, then the options on the GPOs allow some flexibility in when installation occurs.

[6Foot2]

...GPOs can be used to deploy EXEs as well as MSIs, by creating a ZAP file (fairly straightforward as I recall)...

 

Link: How to publish non-MSI programs with .zap files

 

Some limitations: Applies to Windows 2000.

[plexer]

GPO at the minute. You can also use mdt to deploy apps which could be useful after deployment.

[waldronm2000]

Link: How to publish non-MSI programs with .zap files

 

Some limitations: Applies to Windows 2000.

 

I think the limitation is due only to the age of the article, and ZAP files work in XP too (and probably Vista and 7, tho I haven't tried these). Thanks for the link though. As I recall, I created ZAP files in the past based on the sample one in this article, and discovered there's an error - the sample is missing an newline somewhere.

[A5Ben]

We use Specops Deploy in our environment to deploy software to 6000 workstations. It's very powerful with the ability to target a computer with all kinds of targeting criteria. Can install MSI's and legacy apps such as exe's.

 

 

HTH,

Ben

[sparkeh]

GPO at the minute. You can also use mdt to deploy apps which could be useful after deployment.

 

I have been looking into MDT today actually, latest version looks quite good and may evaluate it to replace current FOG and GPO app deployment setup.

 

Has anybody used its app deployment functions?

[6Foot2]

For what it's worth, GPOs can be used to deploy EXEs as well as MSIs, by creating a ZAP file (fairly straightforward as I recall), but that's when they really become inflexible. As long as you're deploying MSIs, then the options on the GPOs allow some flexibility in when installation occurs.

 

I have just tried to create a ZAP file to deploy an EXE. When I select the ZAP file [created as described on the MS site] I get the following error:

 

Cannot deploy down-level application packages (*.zap) to computers.

 

Server OS: Windows Server 2008: SP 2: 64 Bit.

[gshaw]

90% of the software is on the image then any updates \ additions are pushed out with SMS 2003 (soon to be SCCM).

 

Can't beat the reporting on SMS, makes me much more confident in what's been sent out and whether everything worked as expected