.Loading..Loading.
Readme Rev
Service Updates
When the downloaded patch is run, it will extract to a folder and there will be zip files. Those files should be extracted and then Setup.exe can be run. This table outlines the names of the zip files and where they should be run.
Component | Core/Console | Client |
---|
Installation Instructions
The following outlines instructions for installing this update.
This patch requires that Ivanti Endpoint Manager 2017 be installed. For more information about current service packs please see LANDESK Community Doc 1001
Installing on the Core and Rollup Core
Because ADS may block files on Windows systems, it is recommended that you extract the patch on the machine you are going to install it on.
Prior to installing a patch on the Core Server it is recommended to make a backup of the LANDESK database.
Steps
- Disable any services on other machines that interact with the Core Server
- Double-click on the self-extracting executable and extract it
- Extract the files for the Core patch
- From the extracted files, run Setup.exe
- When Setup completes, reboot the machine if a reboot is required
- After applying the patch, you may need to re-activate your Core Server using the Core Server Activation Utility
- Restart any services stopped in Step 1
Note: The installer included with this release writes a detailed log that can be used to help troubleshoot installation problems. After running setup.exe from the patch, the log is located in the \ManagementSuite\log folder.
Installing on Remote Consoles
A Remote Console is any machine that is not the Core Server and has the LANDESK Management Suite Console installed. Console Machines need to be updated to be able to connect to the updated Core Server and Database.
Because ADS may block files on Windows systems, it is recommended that you extract the patch on the machine you are going to install it on.
Steps
- Close the Console
- Double-click on the self-extracting executable and extract it
- Extract the files for the appropriate patch
- From the extracted files, run Setup.exe
- When Setup completes, reboot the machine if a reboot is required
Note: The installer included with this release writes a detailed log that can be used to help troubleshoot installation problems. After running setup.exe from the patch, the log is located in the \ManagementSuite\log folder.
Updating the Agent
The patch should be installed on the Core Server before updating Agents
Use one of the following methods to re-deploy the agent once the patch has been applied to the Core or to apply the patch manually.
Methods of agent deployment
-
Manual: Map a drive to \\Coreserver\ldlogon and run 'wscfg32.exe -f'
This is used for single client installs and testing - Push: Schedule a push of the full agent
- Self-Contained EXE: Create an EXE that can be installed
- Advance Agent: This is a two stage process. The Advance Agent consists of a small MSI and a self-contained EXE. The MSI is deploy to the client and then the MSI downloads and installs the EXE. This allows for bandwidth friendly downloads.
For more information on agent configuration and deployment see LANDESK Community Doc 23482
Manual installation of the client patch
Because ADS may block files on Windows systems, it is recommended that you extract the patch on the machine you are going to install it on.
- Double-click on the self-extracting executable and extract it
- Extract the files for the appropriate patch
- From the extracted files, run Setup.exe
- When Setup completes, reboot the machine if a reboot is required.
Updating the Agent With Patch Manager
LANDESK Patch Manager can also be used to update agent machines with the patch. Content and definitions can be found in Patch Manager as LANDESK Updates and can be used to detect and repair agents that have not been updated. The Core Server must be updated with the Core patch before updating agents.
Not all Component Patches will have Patch Manager Content created. Once it is generally available, this method can be used to update agents. For more information about updating agents using LANDESK Patch Manager see LANDESK Community Doc 24384
Release Information
Please review the following important information about this release BEFORE installing this update.
Feature Changes and Updates
The following features have been changed or updated
Portal Manager
The Portal Manager has recieved an updated user interface. The updated Portal Manager will have a modernized "Workspaces" look and feel.
Defects FixedExpand All / Collapse All
Agent - Config
-
407401 ALS_SVC user profile not being removed by the CreateNewUser code
-
430879 There was a problem saving to the database when deleting the credential immediately after you finish adding the credential.
Alerting
-
430537 Alerting emails don't accept french characters (as "à" or "é","è" ....)
AMT-Vpro
-
427516 Remote Control via KVM not functioning
Content Replication
-
434237 Replicator schedule is set to hourly, however, it doesn't occur hourly
Core Rollup
-
412614 SQL Replication utility fails to properly remove software duplicates
CSA
-
316451 CSA vulnerable to clickjacking
-
409895 Slow download speeds when CSA is set to dynamic
-
435051 Html RC won't start when right click the client connected to the core through CSA and select Html remote control with CSA patch 184
Data Analytics
-
408047 Cannot change Attribute when archiving a computer to asset control in LDMS Console
-
414783 Insight B2B connector fails to import data
-
414861 "Archive Computers" in Database Doctor is giving an error when deleting the device from the console. Error ComputerNotScannedCounts_to_Computer
-
414862 "Archive Computers" in Database Doctor is giving an error when deleting the device from the console. Error R_ClientAuthStatus
-
414952 "Archive Computers" in Database Doctor is giving an error when deleting the device from the console.
-
426634 Data Analytics doesn't correctly recognize licenses for v10.1 (2017)
-
427132 Rename Mode in Console Extender not working correctly
-
430744 B2B - Adobe rule failed because the webpage is changed.
-
432005 Database Doctor - Could not delete computer The DELETE statement conflicted with the REFERENCE constraint "ComputerNotScannedCounts_to_Computer".
Endpoint Security
-
403420 Application File List Sorting
-
405272 CD/DVD writes are not blocked with Roxio burner software
-
408377 Unauthorized Device Pop up message when USB stick is Exception
-
410041 EPS is vulnerable to double agent malware
-
411023 Device control custom user message goes off screen when a device (such as usb thumb drive) is blocked
-
414560 The EPS client can't stop alerting about deleted Windows tasks
-
427104 New folders or empty files will be created even though device control has been set as read-only
-
429636 "Log events only" setting does NOT work.
Inventory
-
334598 Provide a UI option to disable WMIRulesScan
-
382520 Inventory scanner cannot gather the correct OS name for the Windows Embedded OS
-
391316 Encryption method "6 - unknown" in Inventory
-
391354 On a core upgrade to 10.1.10, changes in the schema files are not being applied to the database
-
391861 Update SQL Tables/Columns Size Limits In The Datamart XML
-
398121 Additional logging needed for Device ID actions
-
402828Network drive accesses during inventory software scan causing slow network responsiveness
-
415775 Incorrect IP address information may be obtained via Inventory Scan
-
424381 Agentless scanner service may be Disabled when one subnet is set to Enabled and the other subnet is set to Disabled
-
434398 Improved Inventory Service processing for Core Server self-scan
LDMS Console
-
427933 No RBA Right to restrict "Credential Manager"
Mobility
-
317609 If a network failure occurs when clicking the button to unenroll and then try to enroll again a duplicate Unenroll tab may appear
Patch Manager
-
404745 failed to copy custom sub group in patch and compliance
-
409055 Office 365 Patching doesn't download via CSA
Provisioning
-
415349 Provisioning DB tables can get locked up in certain conditions
RBA
-
434238 Non-Ivanti/LANDESK user with software distribution rights cannot see teamed device groups
Remote Control
-
410551 Pass-through authentication may not work with remote control
-
414906 Default remote control client (RCClient.exe) found on 'Remote Control Agent' page of the CSA does not function
Security
-
425616 Database credentials may be viewed by unauthorized LANDesk users through the use of certain tools and actions
Software Distribution
-
414594 schedqry.exe application may crash when resolving some queries
-
414723 HTTPS directory browsing not working like HTTP
-
414831 LDAP Targeting to USERS - policysync may remove applications when user is logged off
-
416336 Policy requests may fail for users who are members of many AD groups
-
429009 Distributionapi: Tasktemplates return tasks instead of task templates
Tenant Manager
-
410217 Users cannot view task templates even if permissions are assigned
Known IssuesExpand All / Collapse All
The following are known issues that are expected to be fixed in a future update. These issues are generally not caused by installing the update but are just fixes that are still pending.
AMT-vPro
-
430876 Without any certs, the AMT10 device failed to be provisioned into CCM by HBP.
Console
-
355361 Cannot search user/OU while adding user in User Management.
-
410662 In Windows Console the right-click options are different between items in the device view and the scheduler tool
Discovery
-
410639 Cron String in Discovery Services Scheduler UI is Confusing and Raises Questions
-
411691 Handle specified "baseDN" in LDAP URL
-
431073 EANDIS License Optimizer POC: iQuate and ldiscn32 Records for Same Device don't Reconcile in Discovery
Mac
-
410664 When a device is unavailable for remote control the message is not friendly "string change".
Patch Manager
-
411022 After Disabling all rules in a patch definition the overall definition still shows up in the scan group
Software Distribution
-
410916 Bundles do not respect bundle order when using all batch scripts.
-
427946 Different task status on Workspace and Console
UDD-XDD
-
428605 XDD sends managed devices to UDD
Workspaces
-
410549 Upgrade wiped out theme information for Workspaces
-
410845 Pagination in Workspaces is truncated