Policy Editor does not launch correctly when changing Proventia Desktop policy
Why does the Policy Editor fail to launch correctly when you want to change a Proventia Desktop policy?
The stand-alone Policy Editor does not launch correctly from the Proventia Desktop Policy Wizard. The Policy Editor may return an error, or instead of launching the wizard will ask for the console operator password, as if the Policy Editor had already been closed. This problem may be caused by corruption of the Java Runtime Environment or Policy Editor files.
To resolve this issue, close the Proventia Desktop Management Dashboard and delete all of the contents of the %TEMP%\ibmpdwiz folder. When the Proventia Desktop Policy Wizard is reopened, the Java Runtime Environment and Policy Editor files will be reloaded.
|Security||Proventia Endpoint Secure Control||Proventia Endpoint Secure Control|