Can you give us more detail as to when you see this error? Have you logged a ticket with support?
I have the same issue with Ivanti SM 2017.1 on-premise. After deployment of the discovery agent via DSM, this message pops up soon after Ivanti Discovery Agent launches the SaaSLanProbe service.
Even with LanProbe binding "disabled" in client.xml. The popup message can take up a few minutes until it shows.
Strange thing is, that it seem to appear randomly on different clients. My colleague next to me does have Win 10 1607 and the message popped up two days in a row shortly after Windows has booted.
On the third day, it didn't show up again. Myself is using a virtual client in Parallels with Win 10 1709 and it never showed up. The colleague on the opposite of the one next to me, does have Win 10 1607 as well and it popped up only once after install. After the next reboot it didn't show up again.
There is a note about this in the Release Notes for HEAT SM 2017.2.1 (I think, it is from Sep. 15, 2017), but it is only mentioning Windows 7. A customer of us also has this Problem with Windows 10 1709...
There is a Known Issue during installation of the 2017.2 Discovery Client Agent. Installation pops up Windows Warning for digital signature requirement from Microsoft. Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source To correct this, digital signature certificates have been updated. However, Ivanti recommends to apply updates to support Code Signing issues in Windows 7 and Windows Server 2008. For windows 7, please make sure that System has SP1 installed and install KB from https://technet.microsoft.com/en-us/library/security/3033929
The Lanprobe driver is also the part of the software that collects the hardware info like BIOS ID and other motherboard info. If you are seeing this on win 7 machines please follow the release note RWA listed in his reply, if you are seeing it on Win 10 machines, please log a support ticket. I don't have the info on hand as I've not worked with that product for a while but I recall development was working on a win 10 driver signing issue as win 10 will not let you bypass the unsigned driver. There may be a patch available from support if that effort is complete.