Windows 7 and 2008 machines are blue screening when using Application Blocking
IssueWindows 7 and Windows 2008 machines are blue screening upon boot. Identifying Affected MachinesMachines can boot into Safe Mode. While inside safe mode navigate to64bit:...
View ArticleHow to patch Office365 Click-to-Run installations efficiently with LANDESK
Introduction As we all know, the latest release of Office from Microsoft comes in 2 flavors. A 'rich client' based installation, which is practically the same as running the Setup as in previous...
View ArticleIssue: Affected Computers window doesn't display any results
IssueAffected Computers window doesn't display any results after right clicking a vulnerability and selected "Affected Computers" from the quick menu.This affects all vulnerability definitions on the...
View ArticleIssue: Windows Devices in another AD domain do not get Patches applied
IssueWindows Devices in another AD domain are not using the FQDN to the LANDESK core server to download the patches and are failing. There is a DNS entry for the LANDESK server in the target AD domain...
View ArticleError: "Node's reported ID is not in the database"
Issue When running a repair job, an error stating: "Node's reported device ID is not in the database" in the scheduled task window.406 Errors may appear in the IIS W3SVC logError "The core (servername)...
View ArticleError: "Hash for patch does not match with host. Discarding" when downloading...
IssueCauses and ResolutionsThe patch content needs to be updated as the local content is out of dateA web caching or other networking appliance within the environment is causing the contents of the...
View ArticleIssue: Security and Compliance Manager (Vulscan) window blank
Issue When running a vulnerability scan, the Security and Compliance Manager (Vulscan or Vulnerability Scan) window is blank. The window shows the title, but the contents are blank. Otherwise the...
View ArticleIssue: Patch Manager Configuration loses settings inside the Download Updates...
Pour la version Francaise consulter l' article suivanthttp://community.landesk.com/support/docs/DOC-23828 Issue Patch Manager randomly loses settings inside the download updates window. In "patch and...
View ArticleAbout the "Use 64-bit registry view on 64-bit windows" setting within Patch...
Situation How does the "Use 64 bit registry view on 64 bit Windows" setting affect my detection rule? Description LANDESK allows configuring custom Patch and Compliance rules to check on patch...
View ArticleHow to reset security scan local scheduler settings using a managed script
ProblemFrom time to time, you may need to change the security scan local scheduler settings using a managed script. Resolution Sample...
View ArticleError: "Could not establish trust relationship for the SSL/TLS secure channel...
DescriptionIn the Vaminer.log you find the following SSL error.LoadingPatchSources : GetStreamForPath https://patch.landesk.com/LDPM8/ldvul.php failed The underlying connection was closed: Could not...
View ArticleError: "Unable to find string with ID message" in Vulscan UI
If you are like me living a country that does not have a localized version of LANDESK, you might run into this issue. You start the Vulnerability Scan en when the message should appear that the vulscan...
View ArticleContent verification in LANDESK Patch Manager
This articles describes the content verification feature within LANDESK Patch and Compliance Manager Content verification can be enabled to cause the LANDESK Core server to add in a hash checking...
View ArticleAbout Patch and Compliance content vulnerability definition title suffixes
This article describes the meaning of the suffixes used in the titles of Patch and Compliance Manager vulnerability definition content. Various suffixes are given to Patch Manager vulnerability...
View ArticleStatus: "No Patches Available" in Scheduled Task status after scheduling...
IssueAfter scheduling a repair task or policy, clients complete with a status message of “Successful” a result of "No Patches Available" CauseThis is caused by patches in the repair task not being...
View ArticleHow to troubleshoot detection problems in LANDESK
LANDESK uses Vulscan and vulnerability definitions to determine what patches are needed on a client machine. These results are then reported to the core server and patches can be installed on the...
View ArticlePatching 101 - A simple, effective method of patching
As the Enterprise LANDESK Administrator of a large company that has had over 15 Core Servers with over 12,000 systems and over 20 other LANDESK tech's to support I have found "how should I patch" to...
View ArticleHow to troubleshoot Patch Manager detection and remediation issues
Introduction LANDESK Security and Compliance Manager enables you to remediate (repair) vulnerabilities on clients with the LANDESK agent installed. There are several situations where this remediation...
View ArticleError: "0x8db3019c All Patches Failed" in Vulscan log file
Issue Scheduled task to repair a vulnerability is failing The vulscan.log file shows the following error:Last Status: Failed: Must reboot before appyling this patch.exiting with return code...
View Article