What installation settings did you set when creating the installation package?  Did you do a silent install or unattended?  You can also modify the SEP policy within SEPM to allow the reboot to prompt the user, allow them to postpone, etc.  Is the package acting differently than what your settings show?

I doesn't seem to matter what setting i set/use within SEPM.  Currently i am now using the documented method which involves copying the SEP folder from the cd, creating an administrative image from it and then copying the sylink.xml over to it.

Since wrinting my first post i have gotten round the reboot problem by a combination or modifying both the msi and the setaid.ini file however i now have a new and wonderful problem.  after the GPO deployment has run, if the machine is not logged in fairly soon after wards a perculiar thing happens.  approx 5-10 mins (similar period to the restart problem previously) a black box flashes up very quickly (dos box i presume - it is that fast!) and then the ctrl-alt-del prompt vanishes.  it literally disappears!  it does still function however and if the keys are pressed the logon box appears.  you can even cancel this and the ctrl-alt-del prompt will return.  however this is not an ideal sideaffect from deploying the app?

 

has anyone actually managed to get this to work - if so what did you do?

Hi

 

I believe the best method for deployment of SEP via gpo is to create a proper installation settings and feature and export a package without ticking "create a single exe file" in a shared folder and then add .MSI installation as a software installation package in gpo's computer configuration....I tried this method and it worked.

I found out that if the targeted client machine had Outlook or IE in use then SEP remote installation won't go thru and users tends to click cancel when prompt.............

this was the first method i tried, as have been using said msi package to install manually.  thing is when you install manually and it ends installation it says about needing a restart and you have the option to select "never".  the problems all arise when it is deployed via gpo.

and in answer to the other question - no nothing else is running, this is a computer based policy gpo so no other programs are running - the machines have barely switched on.

 

have to say i have given up on this approach now.  gonna do some hard graft and just push it to desktops-my time constraints are all but exhausted now