While exporting the package if you uncheck Single EXE it will create a MSI package

Briallaint!

Is it a single MSI? Will test now!!

I am blind

Hi,
    
      Check this.

Thank You

I am no booking my appointment at the opticians :-)

I hope it creates a single or usable MSI and not jsut the plain contents of the EXE, as I will be at the same place I am no :-)

It does not create a single MSI installation file.  It creates a bunch of files with an MSI installer.

DOH!  Thanks for trying, but it doesn;t work.

As expected it just exports the same as I can do extracting the EXE with winrar :-(

MY QUESTION REMAINS

How can I use an MSI for the custom install of SEP I create?  I want it to know the settings I pick whe  i export the client.

Anyone else able to get.create an UNATTENDED msi of SEP? i.e ANY machine can become a GUP when called upon - only one with win the election rpcess from SEPM anywaqy - so is there another, technical answers why this should not be done?

Not RANtT just typing fast :-) 

 This article might be of your interest
https://www-secure.symantec.com/connect/articles/creating-transform-mst-file-control-installation-symantec-endpoint-protection

Than You Vikram - i was being lazy and didn;t want to play with Orca as I dont like it, but will give it a go - great, clear instructions!

Does that mean I dont need all the files created by SEPM?

If i extract the package from SEP and use ORCA to create MST, aren;t i just configuring the default msi from scratch?

Can it shrink the amount of files i need in the package?

You need all the files in the SEP or SEPMWIN64 folder of the CD (or download). No need to mess with the SEPM installer to get them.

I guess you could eliminate SETUP.EXE if you're installing by running the MSI, but you need the rest.

I'm not an MSI expert, but I've read that while it's possible to combine all the files for a large program into an MSI, it's a bad practice. I do know I seldom see it done that way if the program is more than 2 or 3 MB. Tip 24 discusses this, though without any guidelines for how big is too big: http://blogs.msdn.com/windows_installer_team/archive/2006/05/12/595950.aspx

It is possible to modify the MSI with ORCA, but definitely not recommended. Normally, you use it to create an MST, which leaves the MSI intact. See rule 12 on the same page.

I'm curious about the installation method that requires them all to be in the MSI file. What are you using?

Hi Jeff,

Sorry, if I was not clear - would use Orca to create a transform (MST) not modify the msi!

The SEPM 'packager' allow you to specifiy settings and feqatures and crteates a single (or not) exe.

If we deploy a single exe we can only report if the exe package was successfully delivered to PC's, we wouldn;t know if it ran - would be blind from that point onwards.  If we use msi, we can report and create install logs, that report back that it installed correctly, if it terminated ..etc.  MSI is also the preferred method by the deployment team here for the tool they use.

So in perfect World would be nice if I could of used the SEPM to create the package in MSI format - I think I will need to do some ORCA work to create a transform - shouldn't be too bad hopefully :-)

I am not sure what you are saying about files bigger than 2MB, but I have used MSI's a lot bigger than in the past fine (some from microsoft!) > do you mean a MST bigger than 2MB, which I agree wuld be big!!!