Patches are unavailable because of connectivity or firewall issues.
Open access to the following websites:
NOTE:Adding hosts on ZENworks server, please use "nslookup" on command to get the IP address for each URLs.
Test your connectivity to the new hosting provider from your ZENworks Primary Server that the Patch Management feature is currently running on:
Log in to the server console, and launch a command prompt or shell window:
If your server is able to connect to the Akamai hosting network without a problem, you see a response similar to the one shown below:
Pinging a1533.g.akamai.net [184.108.40.206] with 32 bytes of data: Replyfrom 220.127.116.11: bytes=32 time=14ms TTL=55 Reply from 18.104.22.168: bytes=32 time=14ms TTL=55 Reply from 22.214.171.124: bytes=32 time=14ms TTL=55 Reply from 126.96.36.199: bytes=32 time=13ms TTL=55 Ping statistics for 188.8.131.52: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 13ms, Maximum = 14ms, Average = 13ms
The ping command shows you the address of the nearest AKAMAI server to your current location.
If you receive the following message:
Ping request could not find host novell.cdn.lumension.com. Please check the name and try again.
The firewall administrator needs to open access to the Akamai network for both ping and HTTP (TCP port 80) traffic.
NOTE:The Ping test is a simple way to establish that a server has a route available to reach the server, it is not used by Patch Management in normal operations.
Ping (ICMP) may be blocked by your corporate firewall, or the server may need to pass through a proxy to reach the hosting provider: In these circumstances the Ping test will fail, so other tests will be needed.
Using a Web browser, type in the following URL:
The browser should display formatted output from the website, as shown in the figure below:
If your browser cannot access the XML file, you experience a browser timeout and receive some kind of error message. If the ping test succeeds and the browser test fails, this indicates that the firewall administrator has limited access to the Akamai network, but that the HTTP (TCP port 80) is blocked.
The license server is still using the same address as in ZENworks Patch Management 6.4. If you want to enter a serial number to register your Patch Management usage, you need to leave the IP addresses of our old servers in your firewall rules.
NOTE:The server needs to use a proxy to get to the outside world, and the browser isn't configured for the same proxy, then the test in the mentioned would fail.
Firewall information for ZENworks 2017:
ZENworks Patch Management license replication goes to the following servers:
ZENworks 2017 Patch Management content replication goes to the following DNS name:
To find out what IP your specific server is using, ping novell.cdn.lumension.com from several machines and enter the applicable address range into your firewall rules.
No patches are shown in the Patches page
Patches do not seem to be deployed on the target device
The Cancel button disappears in the Reboot Required dialog box
Superseded patches are shown as NOT APPLICABLE
When a patch is superseded, it is automatically disabled.
If the patch is re-enabled and detected, in most cases the patch shows as NOT APPLICABLE because it has been replaced by a more recent patch.
Although this is inconsistent with the behavior of earlier versions of Patch Management, this change is an improvement because only the patches that currently need to be installed are reported or analyzed on each device.
Patch deployment might not start when scheduled
“Failed but set to continue” error shows in progress bar
Patch Policy assignment: Bundle stays in ‘Pending’ state forever
Adding / defining new State for Bundle Assignment has more impact as other components on server might be using the value of Effective State for other computations.
Patch Policy assignment: Error Message should be displayed for (failed) assignment to older agents
Linux - Custom Patches: Bundles fail to launch
Airgap Server: User receives trial license email after adding the license info to system variables