On non-Windows platforms, the user installing the applet needs to have permissions to write to the browser's installation directory, as the installer needs to put a shared library in there. A possible option would be to have a user with access to this directory (eg. "root") install the applet once.
After further analysis this behavior is caused by Kaspersky Endpoint Security 10 anti-virus running in the background. It seems that this A/V software rescans applets both inside and outside a windows virtual machine. Once this was disabled Kaspersky A/V the Web Client response time returned to normal.
Therefore it is no longer written to c:\winnt\java\lib ( or some equivalent dir in 98 / XP) where admin rights are required, but instead in user's temp location where users have full rights. If customer is having problems with the applet, most likely it's not file perms but IE perms. Also note that if you previously chose to "always trust Serena" you will no longer get the trust prompt, and the applet will be delivered silently.
Preserving Servlet Definitions: Windows proceeding to the next step. Next, launch the Version Manager Application Server Admin utility (vpadmin ) and make sure the "Location of Netscape Configuration Files" and/or "Location of Microsoft IIS Scripts Directory" matches the desired location for the new server installation (as they too will be inherited from PVCSServlets.properties
