Show-InstallationWelcome -CloseApps Notes



First of all, great product! So, I want to contribute to further developments.

After figuring out that the CloseApps 'Notes' will use an possibly installed NSD.exe to terminate Notes related processes, the following issue has been seen when packaging Notes 9 with it.

1) The NSD tool is being launched ALTHOUGH there is NO related notes process running.
2) The used command: NSD.EXE -Kill always fails with "FATAL (0): The notes.ini could not be found. NSD uses..."

Regarding 1) NSD should only be launched when a process which is in the block list has been identified.

Regarding 2) This is a valid error message because in SYSTEM (when run as SCCM) context there is no Notes.ini or way to identify one when using a standard Multi-User setup. Additionally, no processes are being killed by NSD because it fails completely.
The existing processes seem to killed by the default way.

If you need input or testing, don't hesitate to contact me.

Best regards,

Fabian Köhlmann

file attachments

Closed Apr 14, 2015 at 1:05 PM by mmashwani
We have migrated to a new site. Closing this issue. If it needs to reopened, then please re-open on GitHub.


PowerSheller wrote Mar 2, 2015 at 10:33 AM

Based on your feedback and others we are considering removing the execution of nsd.exe altogether, would this pose an issue for you?

Koehlmann wrote Mar 2, 2015 at 10:59 AM

Not at all. As put in my description, nsd.exe is expected to fail as system account because of no notes.ini file presence.
Best regards,
Fabian Köhlmann

sintaxasn wrote Mar 2, 2015 at 11:38 AM

Hi Fabian,

Do you know what the exit code from NSD is when no Notes.ini is available? I think the simplest thing to do with be to ignore this exit code. Not running NSD when no Notes processes are running is trickier because we have to identify up front what processes this might be and there's a lot more that just notes.exe - we'd need to hardcode all the known and update with new ones when IBM release new versions of Notes.

Thanks, Dan

sintaxasn wrote Mar 2, 2015 at 12:05 PM


Ignore my last post - I actually figured out how to solve this. Can you retest with the latest source code and see if this resolves both issues? All errors should now be ignored when NSD runs and it should only run if a process in the Notes folder is running.

Thanks, Dan

Koehlmann wrote Mar 2, 2015 at 12:53 PM

Where can I download the latest version for testing?

Additionally, I am afraid it will not really solve the issue, but I will try. The problem is, how the NSD.exe is being launched in general. By NSD design, it requires an notes.ini file to be found in the "current user" environment. The current user is SYSTEM, so there is NO Notes.ini file available. This will show a nasty pop-up to the user with the mentioned error message. This pop-up is being cleared by the framework automatically but still it is being shown.
I will test with the new version and let you know. Thank you very much in advance.

sintaxasn wrote Mar 2, 2015 at 1:25 PM

Ah okay. So I've made a change so that if running as LocalSystem NSD doesn't run.

You'll find it under the Source Code tab, then click Download.


Jo_en wrote Mar 9, 2015 at 3:31 PM

Hello Dan,

I had the same behavior in my environment. Running as System Account I got the same nasty pop-up you talked about.
I tried the code of the beta release and I found also the changes you made in the "AppDeployToolkitMain.ps1".
But I want to tell you some of my test results. If you prevent the NSD to run by System Account, you will need the following parameter at "Show-InstallationWelcome": -CloseApps 'notes,notes2' - in order to close all running Notes processes. In my case I wanted to install some additional plug-in for Notes and than I got the message "Launching this application has been temporarily blocked so that an installation operation can complete" - I assume the plug-in need an instance of the notes2.exe to be installed successfully. So this is not a good solution, because I do not want to dispense of the possiblity to block the execution of Notes during the installation process.
As there is no other elegant way to close all running Notes processes, I tried to get this solution running.
Could you please check my suggestion, to do the following change in "AppDeployToolkitMain.ps1" (v. 3.5.0) in line 4652 I added the parameter "-NoNewWindow" to the Start-Process command. Afterwards I tried on different test machines and I got never back the pop-up of the NSD.
Thank you

Regards Johannes

sintaxasn wrote Mar 9, 2015 at 4:41 PM

Hi Johannes,

In 3.5 and above, we check for anything in the Notes folder and remove anything except the main entry point to Notes (notes.exe) from Block Execution. Here is the commit note, from line 4579:

Strip all Notes processes from the process list except notes.exe, because the other notes processes (e.g. notes2.exe) may be invoked by the Notes installation, so we don't want to block their execution.

Are you saying this isn't functioning as expected in 3.5 and/or 3.6? Notes2.exe should not be blocked.


Jo_en wrote Mar 9, 2015 at 6:01 PM

Hi Dan,

if I go for (in 3.6) -CloseApps 'notes' I had some cases where I got the prompt 2 times.
What is correct parameter if I want to have Notes closed in 3.6?
And how to do deal with System Account installation if you don´t use NSD anymore to close all running Notes processes savely?

Jo_en wrote Mar 17, 2015 at 2:25 PM

Hi Dan,

I realised that it is a problem to use the new parameter (in 3.6.0) -PromptToSave. If I use the parameters
-CloseApps 'notes' and -PromptToSave Lotus Notes is never closed and the prompt (see picture)
will never stop. Also, after clicking "Close Program" the Notes application hang and could only be stopped by using NSD.

Further regarding to my last question, how do you close all running Notes processes savely, if you don´t use NSD for System Account installations anymore?

mmashwani wrote Apr 1, 2015 at 11:00 AM

I just committed some improvements to the way the -PromptToSave option works. Please test with the latest 3.6.1 beta found under the "Source Code" tab of this site to see if you are still having any issues with this option.