We’re currently experiencing a high volume of support requests, which may result in longer response times — thank you for your patience and understanding.
If your organization uses Palo Alto Networks GlobalProtect, heads up! Versions 6.0 and 6.1 of Palo Alto Networks’ GlobalProtect will both be reaching their end-of-life date on the 31st of December, 2025. Start managing your software lifecycle better ...
Fortinet just released fixes for two critical zero-day vulnerabilities in FortiWeb (CVE-2025-64446 & CVE-2025-58034), including one that lets unauthenticated attackers create new admin users and fully compromise the device, and another that enables u...
Version 24 (2024, wave 1) of Microsoft Dynamics 365 Business Central will be going end of life on the 7th of October 2025. Audit your environment to discovery impacted devices and their status with the report linked in the Dynamics EOL blog.
Heads-up for vSphere admins: vCenter 7 hits EOL on Oct 2, 2025. No more security patches after that, so make a plan to move to 8.x.
You can find more info on our vCenter EOL blog post.
VMware vSphere ESXi 7 hits End of General Support on Oct 2, 2025. After that, you’ll be in reduced support with no new security patches, so now’s the moment to plan upgrades (to 8.x or 9.x where possible) if you haven't!
You can find all the info in ...
You might need two loops. The first loop will go through your CSV. Once that loop starts and selects the first IP address, the logic will then need to fetch the list of assets, and loop through all of those so it can check whether that IP address fro...
You can send the data to any platform and do with it what you want. However not every platform has a connector, which makes it easier. Outlook, Teams both have connectors, we do not have a connector for HaloITSM (maybe in the future?) or Xurrent. But...
Yeah its a tradeoff, the reason I used Try_convert is that there were enough cases where people had one asset somewhere that had a weird value scanned for X or Y which broke the entire report because it failed 1 conversion.You could try and create a ...
SQL Server 2012 and onward should support it. The only reason I can find Try_Convert is not supported on later SQL versions is if you are running it with a compatibility level < 110SELECT name, compatibility_level
FROM sys.databases
WHERE name = DB_N...
