JetPatch 2.5 Known Issues

The following issues are known to exist in JetPatch 2.5:

1. Active Directory authentication does not work with AD 2003.
2. To upgrade a vAgent from one version of the agent to another, the vAgent needs to be fully removed and the new version then applied.
3. Applying a vAgent as an unauthorized user generates the wrong error log ("vLink no found").
4. Internet Explorer 9 is not supported in security zones that disable javascript (default setting for non-internet zones).
5. Upon disconnecting an endpoint, installed vAgents are properly removed, but the previously running conventional (non-virtual) agents are not restored. To have the conventional agents restored, before disconnecting the endpoint, remove each of its vAgents, upon which the conventional agents are restored.
6. When using Internet Explorer 9, changing the window sized may cause the JetPatch Console to behave unpredictably.
7. Upon restarting the JetPatch server, it may take up to 15 minutes until all endpoint statuses are updated.
8. Upon changing a physical endpoint hostname, it needs to be disconnected from JetPatch and then re-added.
9. Repairing the VMware Tools installation on a vSphere endpoint causes the JetPatch connector to be removed and all vAgents to be stopped.
10. Upon changing the port number in the agent-specific settings of a new vAgent package and deploying the package to a Linux endpoint, the new port number is not added to the endpoint's iptables as a firewall exception.
11. Deploying the NBU vAgent on an endpoint fails with permission denied, when the endpoint already has the NBU legacy (non-virtual) agent, and the "NetBackup Database Extention - Graphical User Interface" is open.