/build/static/layout/Breadcrumb_cap_w.png

How does everyone organize their software? just curious

How is everyone Organizing their software on their distribution points?
For Example Z:\Software\Vendor\SoftwareName what about version numbers?

All feedback is much appreciated

0 Comments   [ + ] Show comments

Answers (6)

Posted by: nmi 19 years ago
Orange Belt
0
One previous place we use to work at used DFS so it would be :

\\domain\dfs\Software\<package name>\

Inside the package folder would be the various MSI's and scripts to install the MSI.

The version number was part of the package name with a revision id also included eg 01/02 etc.

nmi
Posted by: Bladerun 19 years ago
Green Belt
0
This is our structure, if it makes any sense. Not my design, but its servicable :

-Software
- -ApplicationName (vendor name first only w/ duplicate names)
- - -Version
- - - -Documentation (Package/Install documenation here)
- - - -InstallFiles
- - - - -Source (Application Source here)
- - - - -Development (Package work here)
Posted by: BobTheBuilder 19 years ago
Purple Belt
0
DFS here too...

DomainDFSname\install$\Core\APPNAME - (Core is the directory for apps deployed via machine GPO)

or

DomainDFSname\install$\Dept\CITYCODE-APPNAME - (where city code is the three letter code for a location, say CHI for chicago, and Dept is the directory for apps deployed via User GPO)

Sometimes GPO won't do, so SMS will do the distro.
Posted by: Ipstenu 19 years ago
Senior Yellow Belt
0
Using LANdesk for deployment

Sharepoint1\msiname.msi
Sharepoint2\msiname.msi
SharepointN\msiname.msi

Each person, when they connect their PC to the network and log in, is assigned the nearest local sharepoints (so London doesn't use New York's install point), and then at the end of the list is the master repository.

No attempt is made to split them up by vendor or OS anymore (thank god, it's all XP). We have a folder for MSIs with Transforms, and the install script points to the MSI and MST in said folder.

Install scripts exist only on the master repository. The msiname is allways 'applicationV###.msi' so that's our version tracking.
Posted by: Thegunner 19 years ago
Second Degree Green Belt
0
We dont really use any type of documentation as such.

We have an area where the software is kept N:\Apps\UserApps\MSIfiles\<Software.version>
Posted by: Robb Thomas 19 years ago
Senior Yellow Belt
0
Here, we keep it pretty simple.

D:\Wise\progname\*.doc - Documentation, usually 1 file.
D:\Wise\progname\*.wse,mst,msi,ini - The development Code, usually 3 files
D:\Wise\progname\Image\*.* - a copy of all files and directories as they would appear on the target machine.

D:\Wise\progname\Source\*.* - If the application is 'tiny' the source files would appear here for convenience
\\ALBSVC1\Install$\Souftware\Vendor\Progver\*.* - The source and/or install point for larger programs.

My machine has a backup agent on it, with a big pile of disk, so we are backed up every night. But when I go to compile my deployment package, I work at BUS speeds rather than working at LAN speed :) I suspect this would also help to speed up the conflict reporting as well.

If I get a DLL hell complaint, I can simply use the below high tech conflict resolver to isolate the problem.

CD D:\Wise
DIR/S xxxx.DLL

Once I know where the bad version of xxxx.DLL is coming from, it's a simple matter to resolve and or update the packages to fix the problem.

Regards,
---- Robb ----
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ