Systems Management

No one uses a naming convention?

I guess I'm ahead of the curve then.

thanks turbokitty..i'm going to have to steal this format i think.

what is your format for program names? do you just use the pre-existing per-system unattended, per-system uninstall, etc. and use just meaningful names for custom programs?

Sorry, I forgot about this thread. Um, for programs we're using "<action> package name". and I've changed our advertisement convention to "<action> program name"

So..
Install Adobe_Acrobat_801_ALL_Global
Uninstall Adobe_Acrobat_801_ALL_Global

I'm not convinced this is a great way of doing it, but I'm asked around and no one has many good ideas.

I'm also using folders to organize the packages, queries and advertisements.

ROOT > Adobe > Acrobat > 8.0.1 > Install Adobe_Acrobat_801_ALL_Global

We use this same structure to organize the source files on the file share so we know right away which package belongs to which files in case we need to update the package.

Unfortunately, collections are hard to organize as there are no folders.

Hi,
I use this conventions for SMS
(Examples with Office)

Collections (with subcollections)
FR Software
FR Sotware Distribution (for publication)
Distribution | Microsoft Office Professional 2007

FR Software Uninstall (for Uninstall)
Uninstall | Microsoft Office Communicator 2005

FR Software Migration (for migration)
Migration | Office Professional 2007

FR Software Server
Server | SMS Client

FR | USERS
FR | USERS | VISTA
FR | USERS | XP

FR | WORKSTATIONS
FR | WORKSTATIONS | VISTA
FR | WORKSTATIONS | XP

Packages (with subcollections)
Software distribution
Microsoft
Office
Office Professional 2003
Programs: InitialSetup (for ZTI, LTI)
Publication
Assignation
Office Professional 2007
Programs: InitialSetup (for ZTI, LTI)
Publication
Assignation

Same Thing for Advertisements
Advertisements
Software distribution
Microsoft
Office
Office communicator 2007
Microsoft Office Communicator 2007-Publication


Best regards
The Q