I have migrated SEP to clients with Outlook and IE running without any problem. Sounds like the script thing is quite unnecesary.

Otherwise this is a great place for scripts: 

http://technet.microsoft.com/sv-se/scriptcenter/dd793612(en-us).aspx

Hi Max,
I've done that on several PC to test, some of them requires restart and some is halt since notes and outlook is still open, and requires user interference to choose cancel, retry or ignore.
somehow, if i choose this as silent installation is much better, but there is lackness, we cant see any progress bar indicating the completion percentage.

so we might think that we insert the script and pskill.exe to the SEP client package or we make it silent but with progress bar (this can be done too via PDW, there is also a progress bar indicated)

anyone, has ever experiencing this?..

thanks,
meon

 If you deploy SEP with the "Push Deplyment Wizard" you can get a logfile at the end of the installation that the package has been copied to the client and the local install has begun.

During the local install process on the client there will be a folder in c:\temp\Clt-Inst that contains the install files. After the install this folder will be emptied/removed.

If you create a script you can check wheter this folder exist or not to know if the install process is finished. If the install fails or is not finished this folder will still be visible.

but how if there is 10-20 users over 5000 users that, let say forget to close their notes or outlook that will halt the installation, even we already announce to close those application, can we edit via instedit to the .msi files? so we just simply disable the command to check those application open or not?

yes, PDW is will become our main deployment, since it has progress bar and log files which computer success and which computer fails during installation.

There will still be no guarantee that the install will be a success just because you add a script that will close some applications. There are many scenarios that will interrupt the install process. It does not matter which 3rd party deployment tool you use you will still have failed installations from time to time. You will gett better logfiles and better possibilities to handle the failures but still you cannot expect to never have the flaws.
 
We have been using Live State for many years in our organisation for software distribution and even though it has been designed to handle automated software installation it fails from time to time.

What I have seen is as long as your going SEP - SEP Outlook being open will not cause a problem.  I can not speak for Notes as we do not use it here.   What I did see was going SAV-SAV or SAV-SEP required Oultlook to be closed so it could remove the outlook plugins.

I used SMS and told it to only run the package if no user was logged onto the system.    I agree outook closed is the best but I did succesfully  do MR upgrade using the SEPM console and asigning packages  to pick up and upgrades SMS missed.   My failure rate was around 1% that needed someone to go look at the machine and take manual action ussually meaning remove and reinstall.  Not bad when we consider anything less that 10% failure a success just do to the number of laptops and not being allowed to do installs that could interupt users during the day.

You are right ShadowsPapa closed outlook is the best and will cause you less problem however I agree with Rick that it do work most of the times even if Outlook is open I have installed many clients this way and yes it did work. If you have the plugin for outlook installed then you are better of by closing outlook but if not just go ahead.

we are doing migration SAV to SEP, so we need to close outlook and notes. I just still worry about rate of failures, even if we announce to close outlook/notes and left desktop/laptops overnight to do upgrade, there might few peoples forgot and causing failure in the upgrade process.

maximilian, when you buys something you expect like what the product offer right? because that is what you need and promise to your customer or your boss. when the product is going not like what you expect then you will configure to suit your organization needs, since the decision already made.

i did piloting here SAV to SEP, with notes/outlook open its halt the installation and with option to close outlook/notes, if not then the deployment will halt and fail. so we have to make sure the outlook/notes is close. even the rates is yes, about 3-5 from 20 desktop/laptop. but during full deployment, we expect smooth migration.

need more luck, okay thanks everyone.

Good luck to you meonfloor!

If you feel worried that you might get in to trouble you should install to small amount of users to begin with and let them have it for a few days. If that runs well you go to a larger number of users and so on. Doing the whole schabang is nothing I would recommend to do (we have 2300 clients).

we are create script that notify users to close the outlook/notes and remind them to save works close, otherwise the script will close outlook/notepad in certain time. this works smooth so far.

thanks,

If we dont have the outlook or loftus and other mail settings on  - this shouldn't be a problem should it?

Unattended was still asking for utlook to be closed.

I beleive Silent worked ok.

 In Unattended Install even if you dont have autoprotect for outlook selected in your package it will tell you to close Outlook.
But if you click on Ignore it will complete the installation and it wont affect the outlook.