The issue shelling out form the client is user privileges,  I would suggest from the client down compile a list of what it takes to delete the jvm folder and the you can  write a shell script , batch file or .net program to perform those steps.

What does the NICE programs say when running it in ui mode?

Make sure there aren't any rouge notes services running or java in the task manager that is not letting the nice tool remove the directory.  New is a link to a technote http://www-01.ibm.com/support/docview.wss?uid=swg21459714.

Nice does not force the services down but dos taskill can do this . http://www.computerhope.com/taskkill.htm

Here is a url https://groups.google.com/forum/#!topic/comp.groupware.lotus-notes.programmer/0_Av4brIC4c 

on how to write a reg field and then execute it via a shell command so possible doing this and then the install might work.

I really appreciate your response, but unfortunately I have considered those points.

There are no rogue Notes processes in play here. Some of the fonts in the Notes client 'jvm\lib\fonts' folder have been registered in the Windows registry.

The operating system maintains a hold on them, and they cannot be deleted until the fonts are de-registered in Windows.

Problem is, once they have been de-registered, the computer needs to be re-booted before the operating system releases its hold on them.

That being the case, the logic is no good embedded in an unattended Smart Upgrade process.

So, I was resorting to deployment of the logic well before the upgrade is initiated.

We use a custom corporate homepage database, so I was hoping to distribute the logic to de-register the fonts use the database script.

The limited user privileges has prevented me from doing so successfully though.

I'll look into the potential use of the 'taskkill' command - perhaps that has some merit here.

I will keep on trying, as the success of the entire project relies on this working.

Many of the users are upgrading to Windows 10, and I believe that FP4 is the first version that is officially supported - aaaaaarrrgh!!

you have 2 choices.

Work with desktop group and have them push out a msi that will do the cleanup, leave a tag file behind that you can tell in smart upgrade that the machine got fixed and reboot the pc.

The other choice is  to

Add to a post open of a always used db (user mail file) logic that would

check for ini variable like cleanup=1

If not found would shell out and do what it needs to do like unregister the files  set ini cleanup = 1 and have user reboot

Have smart upgrade check for the cleanup=1 flag or the tag file and if it exists do the upgrade,

Thanks for sticking with this Barry. The solution you described is what I was trying originally. Unfortunately, it is impossible to 'shell out' to perform any type of registry manipulation because of the limited privileges.

Instead, I focussed on an entirely different solution (after trolling through hundreds of forums and happening on a totally un-related post)...

Rather than trying to effect registry settings, I simply generated a batch file that renames every font in the 'jvm\lib\fonts' folder. Once the machine is re-booted, the entire 'jvm' folder can be removed.

The difference between this and my original solution is that I can run this batch file (shell out) without the elevated privileges required to perform registry manipulation and it has the exact same effect!!

Therefore, I can incorporate the logic into the database 'Open' script well before the R9 upgrades are scheduled for deployment, and the clients can be pre-prepared when the users open Notes and then subsequently re-boot their PC's.

I hope this helps someone else in the same predicament one day!

Cheers!

This may be something to do with the security patches that Microsoft released which stopped fonts from being removed.

This caused havok on a lot of RDS boxes exspecially when printing from programs like Adobe which created fonts on the fly and then can't remove them.

Thanks for sticking with it. Same problems. There was a lot of really helpful information.
Olivia at http://www.ampronix.com/