There are a few customer that are unable to download Wireshark Patches using the SMP Console. Customer checked with firewall team if any port is blocking the download from the Altiris Console but everything looks fine from their end. They are able to access the download link via browser from our computers and the SMP (The Download link is found in the SMP Logs - open LogViewer to review the logs).
You can also use Powershell Command Test-NetConnection <ipaddress> -port <port> to get similar results to PSPing. More information on Test-NetConnection: https://docs.microsoft.com/en-us/powershell/module/nettcpip/test-netconnection?view=windowsserver2022-ps
Patch Management 8.x
From the SMP Logs we found that the download failed for: https://2.na.dl.wireshark.org/win64/Wireshark-win64-3.2.10.exe
Error message: The request was aborted: Could not create SSL/TLS secure channel.
We also see these download links, and their intended destination:
Start download [from:'https://2.na.dl.wireshark.org/win32/Wireshark-win32-3.4.6.exe' to:':\Program Files\..\Updates\WIRES34-210603\{82584f57-1ff4-4042-8866-04971aa0c13b}\Wireshark-win32-3.4.6.exe' task:Download Software Update Package]
Finished download [from:'https://2.na.dl.wireshark.org/win32/Wireshark-win32-3.4.6.exe' to:':\Program Files..\..\Updates\WIRES34-210603\{82584f57-1ff4-4042-8866-04971aa0c13b}\Wireshark-win32-3.4.6.exe' task:Download Software Update Package time:00:01:00.5092000]
While the URL is the only thing that has changed programmatically, we suspect that this issue is environmental as our testing has shown that these packages can be downloaded and staged in most environments. If you have other information that would help us resolve this issue for our customers, please contact support.
Workaround. Create a Software Package by Importing the Wireshark files as a new Software Package; then create a Managed Software Policy to deploy the Software Package, and finally create a Target of vulnerable systems.
Steps to complete the Workaround #1 using MANAGED SOFTWARE DELIVERY POLICY:
Workaround #2 brings the Wireshark update into PATCH MANAGEMENT by recreating the expected File Structure as if the files were downloaded by another SMP and then Importing the Files.
Part 1 - manually create the staging paths and files:
Part 2 - Importing the Staged files into the SMP