Software Deployment

Vendor_app_ver

Adobe_AcrobatPro_7.0

Out software depository is rather large and we started getting very strict on application naming to cut the confusion.

Oh and we deploy via SMS using a vbscript. Having spaces withing the name just causes problems.

Vendor App Ver

Adobe Reader 7.0 01

our repository has grown to about 100 packages and this convention is suitable for our needs

Usually you should use underscores instead of spaces.It's "safer" this way.
The name convention should be the one that best suites your needs.

Depending on the project we use:
[APP_NAME]-[App_Version]-[Language]-[PackageVersion].msi
or
[AppNumber]-[APP_NAME]-[App_Version]-[Language]-[PackageVersion].msi
or some other naming convention the client wants.

Yep I'd recommend losing the spaces.. whether you replace them with _'s is up to you - personally I just lose the spaces and have _'s between app name, version and package revision - this helps with scripting and automation later as you know the format is always the same - only 2 _'s

Also I never have the manufacturer in the file name.

E.G.

AcrobatReader_6.0.3_a.msi or

Project_2002.SP1_a.msi

Cheers,
Rob.

As far ias i know you should discuss it with your deployment people.
If they are using SMS you cannot have underscores or spaces.

We use: VendorApp Version

We're also struggeling with the naming convention of our packages. I believe it's important to have the actual application name and the application version in the name + some kind of package version.

Suppose you created a package version 1.0 for application WinZip 8.0. The package seems to be OK, it is already in production environment, but afterwards a minor modification has to be made (configuration change) for that application. You create package version 1.1 for example which, for example, installs WinZip 9.0 including the new config (or no install of WinZip and just apply the new config). You could also have package version 2.0 which installs WinZip 9.

Could a package name like WinZip 1.0 for application WinZip 9.0 be advisable?
Or package name WinZip 9.0 for application WinZip 9.0 ... and afterwards (for fixes) WinZip 9.0 FIX1.0 or something... I don't know... please some advice tnx :)

Hi Yeah we have our naming convention sorted and use spaces as we have Altiris CMS as the preferred delivery solution; just keen to find out what others use;

renio - this may be off some assistance in helping you, but I have to say I agree with Rob in not including Manufacture name;


Application_Name
Version
PackageVersion
eg

Acrobat_Reader_5.0.5_P1.0.MSI

although as I said at my current client we use

Acrobat Reader 5.0.5 P1.0.MSI

Hope this helps.

Regards

As far ias i know you should discuss it with your deployment people.
If they are using SMS you cannot have underscores or spaces.

Not entirely true, you can still have spaces and stuff as long as they are enclosed with quotation marks..
We use SMS and use a standardized VB-wrapper script with an XML-config file for deploying our applications.

Ours are a little bit different since we have several groups that package applications.

BusinessGroup_CommonName_Version_WindowsVersion.exe

So it might look like this for WinZip:

RET_WinZip_9.0b_XP.exe or even RET_WinZip_9.0b_ALL.exe.

This helps determine quickly who the package was intended for and what versions of Windows it's compatible with. The RET is some acronym that we would assign to a particular group.

I use spaces, but after reading this I will start to use _'s in my packages.

Cheers lads.

ORIGINAL: mgroover
We use SMS and use a standardized VB-wrapper script with an XML-config file for deploying our applications.


What is the purpose of using a VB-wrapper script?

SMS when it is directly exposed to the MSI file, it will automatically fix autoheal points for the various software packages. By putting a wrapper around your MSI file, would SMS still be able to repair autoheal points for the VB wrapped package correctly?

Regards,
----- Robb ----