need to create MSI packages for Norton, Outlook Web Access etc..

[gman10]

Hi guys,

I need to create msi packages for this school district on Monday.. they are running Windows 2k domain controllers and the msi package will eventually be placed in a GPO on an OU that I create so that when the user signs on they will reveive the published app.. My problem is not knowing whether this MSI package issue will be a breeze or a nightmare to create. IE- Lets say, I copy the contents of Norton AntiVirus to a shared folder on the network (this is my distribution point) on the domain from my DC, will Windows automatically make an MSI installer file out of Nortons setup.exe... if it truly does then I'm home free because I can point that msi file to the OU and make a GPO for that the app will load on as many pc as necessary.. HOWEVER, if this is NOT the case as I'm starting to believe -would I need to find someway of converting this Norton setup.exe to an MSI manually and then point it to my OU etc etc for app distribution.. This is eating away at me and can't seem to find good documentation, the Windows books I have are quite vague..

Any suggestions would be greatly appreciated..

Thanks gman

 

[meastaugh1]

If you're using Wininstall LE (with win2k server) then you do the first scan on a 'clean' machine, run the setup process you want to capture into the MSI. Then run the second scan to capture the changes.

Wininstall LE creates external MSIs, so it will create the MSI in the location you specify (ie your public share), and create a directory structure around it (ie program files, windows etc with the new/changed files within them).

You'll probably want to edit any unncessary files or registry entries before deployment.

I think that's what you were asking anyway...

hth

 

[meastaugh1]

The following link is the Wininstall LE pdf manual.

http://www.uwm.edu/Dept/scetech/SetupNotes/Veritas/wile_rm.pdf

 

[gman10]

Hi guys!

Yes I did install WinInstall LE lasnight and I've been trying a few examples.. It works great and am able to create .msi packages that actually work without a problem.. I was wondering.. Since I've got to do all this work for the school district and the server(domain controller),, would there be any harm in just installing WinLE on the server but also the applications that would need to have .MSI packages created for them? The way I see it, as long as you know where your setup.exe path is located for the new app that you are about to install (this would take place just before WinLE takes the "after" snapshot) it will just create the msi package for the path and name in which the admin (myself) types in the text box.. Wouldn't it be more work to get a client "clean" pc and take a "before" snapshot then install software and take an "after" snapshot then take those .msi packages and copy them up to a distribution point "share" folder on the network? Essentially, the goal is to create an OU then apply a GPO with this .MSI package and send it down to the user anyway.. Please, correct me if what I mentioned about "doing" it all on the server is dangerous...

Thanks all!

Gman

 

[meastaugh1]

It isn't so much about installing things of the server being dangerous, it's just more than likely that the MSI packages you create will be unreliable.

If you keep creating packages on the same 'unclean' workstation, then packages which share common DLLs (and other common files and components) will create package dependencies. For example, if you install package 1 on a clean workstation, create an MSI etc etc, that'll be fine. But if you then install package 2 which also installs a DLL that package 1 has installed, the discovery will not pick it up, as it will already exist on the machine. Thus, package 2 will only ever work on the clients, if package 1 is installed.

If you search for 'clean' in Wininstall help, I'm sure it has a better explanation.

 

[gman10]

Hi Meastaugh1,

I see your point, although I wonder.. essentially when you create these MSI packages I've read that you should install them in separate "distinct" folders.. I'm thinking that if I install the apps on the server in their own respective "distint" subfolders (perhaps with MSI package that it creates) then maybe I could get away with it.. each respective dll file with be contained within their own software subfolder.. maybe, not eh? So, if I've got three different apps I need to create on a clean pc(in this case, Norton Antivirus, DeepFreeze and OWA)I should create an MSI package for each separately and then copy JUST the msi package up to my network distribution share OR do I need to copy the msi package PLUS all the software files from the disk.. See, I'm not sure if the msi package creates the entire software package, would I need to copy msi + all other files up to the network share?? here lies the conundrum..

thanks alot meastaugh!

 

[meastaugh1]

Gman,

When you first start the discover process it asks you where you want the MSI to be stored. For convenience, you can specify your public network share. This is where the MSI + all the relevant files to the package will be stored, therefore you don't need to worry about copying files from the source CD.

I should imagine when it's refering to storing them in distinct folders, it's so that you can tell the packages apart. Whether you store them in distinct folder after the capture process has taken place, has no bearing on what has actually been captured.

A simplified explanation of the capturing process is:
After-Before=Change. If the original state of machine (in the before phase) is not clean it will not capture the changes reliably and correctly.

hth

 

[gman10]

you are correct, point validated!!

Thanks so much!

GT

 

[ashpp]

No you shouldn't use the server, you should use a completly clean workstation. The target OS should be the same as the source OS you used to create the MSI.

Also by installing applications on the server you are just asking for Murphys law to come into effect and mess up the server.

 

[gman10]

You guys are right.. I'll use a clean machine and have the msi package copied to the network share.. I'll only use the server to create an OU of computers/GPO so that when the users sign onto the pc's the software will be "assigned" to those machines.. thanks guys! really!

Gman