LANDESK Security and Patch News 

Headlines

·       (June 10, 2015) Adobe has released Flash Player Plugin Debugger version 18.0.0.160 for Windows. Adobe has released security updates for Adobe Flash Player for Windows. These updates address vulnerabilities that could potentially allow an attacker to take control of the affected system.Adobe recommends users update their product installations to the latest versions. Please visit the following page for more details: http://helpx.adobe.com/security/products/flash-player/apsb15-11.html     

New Vulnerabilities     

  ·        Vulnerability ID – FLASHPLAYERPLUGINDEBUGGERv18.0.0.160  

Changed Vulnerabilities     

·        Vulnerability ID – FLASHPLAYERPLUGINDEBUGGERv17.0.0.188
(Added the replacement information.)    

New Patch Downloads     

·         flashplayer_18_plugin_debug_18.0.0.160.exe  

Where to Send Feedback           

At LANDESK, we are constantly striving to improve our products and services and hope you find these changes reflective of our ongoing commitment to listen to you—our partners and customers—in providing the best possible solutions to meet your needs now and in the future.  Please continue to provide feedback by contacting our local support organization.    

Best regards,  

LANDESK Product Support  

Copyright © 2015 LANDESK Software.  All rights reserved. LANDESK is either a registered trademark or trademark of LANDESK Software, Ltd. or its affiliated entities in the United States and/or other countries. Other names or brands may be claimed as the property of others.    

Information in this document is provided for information purposes only.  The information presented here is subject to change without notice.  This information is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including any implied warranties and conditions of merchantability or fitness for a particular purpose. LANDESK disclaims any liability with respect to this document and LANDESK has no responsibility or liability for any third party products of any content contained on any site referenced herein.  This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission. For the most current product information, please visit http://www.LANDESK.com.   

LANDESK Security and Patch News  

Headlines

·     (June 10, 2015) Adobe has released Flash Player Plugin ESR version 13.0.0.292 for Windows. Adobe has released security updates for Adobe Flash Player for Windows. These updates address vulnerabilities that could potentially allow an attacker to take control of the affected system.Adobe recommends users update their product installations to the latest versions. Please visit the following page for more details: http://helpx.adobe.com/security/products/flash-player/apsb15-11.html     

New Vulnerabilities     

·             Vulnerability ID – FLASHPLAYERPLUGINESRv13.0.0.292  

Changed Vulnerabilities     

·               Vulnerability ID – FLASHPLAYERPLUGINESRv13.0.0.289

(Added the replacement information.)    

New Patch Downloads     

  ·               install_flash_player_13_plugin_13.0.0.292.exe  

Where to Send Feedback           

At LANDESK, we are constantly striving to improve our products and services and hope you find these changes reflective of our ongoing commitment to listen to you—our partners and customers—in providing the best possible solutions to meet your needs now and in the future.  Please continue to provide feedback by contacting our local support organization.    

Best regards,  

LANDESK Product Support  

Copyright © 2015 LANDESK Software.  All rights reserved. LANDESK is either a registered trademark or trademark of LANDESK Software, Ltd. or its affiliated entities in the United States and/or other countries. Other names or brands may be claimed as the property of others.    

Information in this document is provided for information purposes only.  The information presented here is subject to change without notice.  This information is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including any implied warranties and conditions of merchantability or fitness for a particular purpose. LANDESK disclaims any liability with respect to this document and LANDESK has no responsibility or liability for any third party products of any content contained on any site referenced herein.  This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission. For the most current product information, please visit http://www.LANDESK.com.   

LANDESK Security and Patch News     

Headlines

·     (June 10, 2015) Flash Player ESR version 13.0.0.292 has been released by Adobe. Adobe has released security updates for Adobe Flash Player for Windows. These updates address vulnerabilities that could potentially allow an attacker to take control of the affected system.Adobe recommends users update their product installations to the latest versions. Please visit the following page for more details: http://helpx.adobe.com/security/products/flash-player/apsb15-11.html     

New Vulnerabilities     

  ·       Vulnerability ID – FLASHPLAYERESRv13.0.0.292  

Changed Vulnerabilities     

·       Vulnerability ID – FLASHPLAYERESRv13.0.0.289
(Added the replacement information.)    

New Patch Downloads     

·        install_flash_player_13_active_x_13.0.0.292.exe  

Where to Send Feedback           

At LANDESK, we are constantly striving to improve our products and services and hope you find these changes reflective of our ongoing commitment to listen to you—our partners and customers—in providing the best possible solutions to meet your needs now and in the future.  Please continue to provide feedback by contacting our local support organization.    

Best regards,  

LANDESK Product Support  

Copyright © 2015 LANDESK Software.  All rights reserved. LANDESK is either a registered trademark or trademark of LANDESK Software, Ltd. or its affiliated entities in the United States and/or other countries. Other names or brands may be claimed as the property of others.    

Information in this document is provided for information purposes only.  The information presented here is subject to change without notice.  This information is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including any implied warranties and conditions of merchantability or fitness for a particular purpose. LANDESK disclaims any liability with respect to this document and LANDESK has no responsibility or liability for any third party products of any content contained on any site referenced herein.  This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission. For the most current product information, please visit http://www.LANDESK.com.   

LANDESK Security and Patch News     

Headlines

·     (June 10, 2015) Adobe Flash Player version 18.0.0.160 is available. Adobe has released security updates for Adobe Flash Player for Windows. These updates address vulnerabilities that could potentially allow an attacker to take control of the affected system.Adobe recommends users update their product installations to the latest versions. Please visit the following page for more details: http://helpx.adobe.com/security/products/flash-player/apsb15-11.html     

New Vulnerabilities     

  ·        Vulnerability ID – FLASHPLAYERv18.0.0.160  

Changed Vulnerabilities     

·       Vulnerability ID – FLASHPLAYERv17.0.0.188
(Added the replacement information.)    

New Patch Downloads     

·        install_flash_player_ax_18.0.0.160.exe  

·        install_flash_player_ax_18.0.0.160.exe  

Where to Send Feedback           

At LANDESK, we are constantly striving to improve our products and services and hope you find these changes reflective of our ongoing commitment to listen to you—our partners and customers—in providing the best possible solutions to meet your needs now and in the future.  Please continue to provide feedback by contacting our local support organization.    

Best regards,  

LANDESK Product Support  

  Copyright © 2015 LANDESK Software.  All rights reserved. LANDESK is either a registered trademark or trademark of LANDESK Software, Ltd. or its affiliated entities in the United States and/or other countries. Other names or brands may be claimed as the property of others.    

  Information in this document is provided for information purposes only.  The information presented here is subject to change without notice.  This information is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including any implied warranties and conditions of merchantability or fitness for a particular purpose. LANDESK disclaims any liability with respect to this document and LANDESK has no responsibility or liability for any third party products of any content contained on any site referenced herein.  This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission. For the most current product information, please visit http://www.LANDESK.com.   

LANDESK Security and Patch News  

Headlines

·     (June 10, 2015) Flash Player Plugin version 18.0.0.160 has been released by Adobe. Adobe has released security updates for Adobe Flash Player for Windows. These updates address vulnerabilities that could potentially allow an attacker to take control of the affected system.Adobe recommends users update their product installations to the latest versions. Please visit the following page for more details: http://helpx.adobe.com/security/products/flash-player/apsb15-11.html     

New Vulnerabilities     

  ·       Vulnerability ID – FLASHPLAYERPLUGINv18.0.0.160  

Changed Vulnerabilities     

·      Vulnerability ID – FLASHPLAYERPLUGINv17.0.0.188
(Added the replacement information.)    

New Patch Downloads     

·        install_flash_player_18.0.0.160.exe  

·        install_flash_player_18.0.0.160.exe  

Where to Send Feedback           

At LANDESK, we are constantly striving to improve our products and services and hope you find these changes reflective of our ongoing commitment to listen to you—our partners and customers—in providing the best possible solutions to meet your needs now and in the future.  Please continue to provide feedback by contacting our local support organization.    

Best regards,  

LANDESK Product Support  

Copyright © 2015 LANDESK Software.  All rights reserved. LANDESK is either a registered trademark or trademark of LANDESK Software, Ltd. or its affiliated entities in the United States and/or other countries. Other names or brands may be claimed as the property of others.    

Information in this document is provided for information purposes only.  The information presented here is subject to change without notice.  This information is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including any implied warranties and conditions of merchantability or fitness for a particular purpose. LANDESK disclaims any liability with respect to this document and LANDESK has no responsibility or liability for any third party products of any content contained on any site referenced herein.  This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission. For the most current product information, please visit http://www.LANDESK.com.   

LANDESK Security and Patch News  

Headlines

·     (June 10, 2015) Flash Player Debugger version 18.0.0.160 has been released by Adobe. Adobe has released security updates for Adobe Flash Player for Windows. These updates address vulnerabilities that could potentially allow an attacker to take control of the affected system.Adobe recommends users update their product installations to the latest versions. Please visit the following page for more details: http://helpx.adobe.com/security/products/flash-player/apsb15-11.html     

New Vulnerabilities     

  ·        Vulnerability ID – FLASHPLAYERDEBUGGERv18.0.0.160  

Changed Vulnerabilities     

·       Vulnerability ID – FLASHPLAYERDEBUGGERv17.0.0.188
(Added the replacement information.)    

New Patch Downloads     

·        flashplayer_18_ax_debug_18.0.0.160.exe  

Where to Send Feedback           

At LANDESK, we are constantly striving to improve our products and services and hope you find these changes reflective of our ongoing commitment to listen to you—our partners and customers—in providing the best possible solutions to meet your needs now and in the future.  Please continue to provide feedback by contacting our local support organization.    

Best regards,  

LANDESK Product Support  

Copyright © 2015 LANDESK Software.  All rights reserved. LANDESK is either a registered trademark or trademark of LANDESK Software, Ltd. or its affiliated entities in the United States and/or other countries. Other names or brands may be claimed as the property of others.    

Information in this document is provided for information purposes only.  The information presented here is subject to change without notice.  This information is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including any implied warranties and conditions of merchantability or fitness for a particular purpose. LANDESK disclaims any liability with respect to this document and LANDESK has no responsibility or liability for any third party products of any content contained on any site referenced herein.  This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission. For the most current product information, please visit http://www.LANDESK.com.   

LANDESK Security and Patch News  

Headlines

·     (June 10, 2015) JREv8U45 has been released by Oracle. Java SE 8u45 is the latest Patch Set Update, containing new features
New Features and Changes

LANDESK is dividing the JREJDKv8U45_Manual definition into two definitions JREv8U45(which can automatically download the patch executable) and JDKv8U45_Manual(which still requires the manual intervention to download the patch executable in order to perform the remediation).

Java Packager Tool Enhancements
JDK 8u45 release contains the following enhancements to the Java Packager:

Starting with JDK 8u45 release, the jar tool no longer allows the leading slash "/" and ".." (dot-dot) path component in zip entry file name when creating new and/or extracting from zip and jar file. If needed, the new command line option "-P" should be used explicitly to preserve the dot-dot and/or absolute path component.
A jnlp application, with nested tags within a or tag, can throw an NPE. The issue is now fixed. The tag should be used only if the is actually used.
Nashorn has known issues where it incorrectly compiles try/finally constructs.

Please download the install packages manually from http://www.oracle.com/technetwork/java/javase/downloads/index.html, then put them in the "patch" folder. Please visit the following page for more details: http://www.oracle.com/technetwork/java/javase/8u45-relnotes-2494160.html     

New Vulnerabilities     

  ·        Vulnerability ID – JREv8U45  

Changed Vulnerabilities     

·        Vulnerability ID – N/A    

New Patch Downloads     

Where to Send Feedback           

At LANDESK, we are constantly striving to improve our products and services and hope you find these changes reflective of our ongoing commitment to listen to you—our partners and customers—in providing the best possible solutions to meet your needs now and in the future.  Please continue to provide feedback by contacting our local support organization.    

Best regards,  

LANDESK Product Support  

Copyright © 2015 LANDESK Software.  All rights reserved. LANDESK is either a registered trademark or trademark of LANDESK Software, Ltd. or its affiliated entities in the United States and/or other countries. Other names or brands may be claimed as the property of others.    

Information in this document is provided for information purposes only.  The information presented here is subject to change without notice.  This information is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including any implied warranties and conditions of merchantability or fitness for a particular purpose. LANDESK disclaims any liability with respect to this document and LANDESK has no responsibility or liability for any third party products of any content contained on any site referenced herein.  This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission. For the most current product information, please visit http://www.LANDESK.com.   

Issue

Error: "Failed. Cannot Interpret Data" or "Unable to process vulnerability data stream" occurs while running a Security and Compliance scan (vulscan)

If running a "Security/Compliance scan" task from the Core or Console, the result column may show "Unable to get vulnerability definitions from the core"

The Vulscan.log may show the following:

240 Getting definition data from core <coreservername>
Wed, 23 Sep 2009 13:19:20 HTTP POST: http://<coreservername>WSVulnerabilityCore/VulCore.asmx
Wed, 23 Sep 2009 13:19:26 Success
240 VulnerabilityData::GetData: Unable to process vulnerability data stream
240 Skipping repair step because scan errors occurred.
Failed

Cause

This is due to a failure in the process of creating, compressing, transferring, or parsing the .XML data the client uses to determine what to scan for, or the details of what to repair.

The following basic process occurs:

1. Vulnerability scan runs on the client.

2. The client requests vulnerability data from the core server (basically a set of instructions of what to scan for).    (This depends on IIS connectivity)

3. The server receives client information such as operating system, and what type of vulnerabilities the client is configured to scan for.  (This depends on IIS connectivity)

4. A lookup to the database occurs and the XML data is written to XML based on the database lookup.  (This depends on database connectivity and performance)

5. The XML data is compressed to an .XMLZ file  (This depends on LDZIP.DLL functioning properly)

6. XML data is transferred to the client.  (This depends on IIS connectivity, and proper sharing and NTFS permissions on the VulnerabilityData folder)

7. The XML data is unzipped and parsed at the client and utilized by the vulnerability scanner.

Any one of these steps can be a failure point.

Troubleshooting

Log Files Used for Troubleshooting

There can be various causes for this issue.  The following sections will list the various causes and possible resolutions:

Reset Internet Information Services

As vulnerability data information is processed by IIS, it is a good first step to do an "IISRESET" from the command line on the core server.  There have been instances where IIS is either not functional, or has gotten into a bad state where it hands out stale data.

Core Server Reboot

Often rebooting the core server will clear up an issue like this.  This should be attempted before changes are made.

Incorrectly configured Application Pool in IIS or faulty .NET Framework Installation

LANDESK client computers utilize the WSVulnerabilityCore web service for various Vulnerability Scan functions, including retrieving Vulnerability Data information.  This depends on the Application Pool being configured properly.

The Default application pool used by the WSVulnerabilityCore web service is called "LDAppVulnerability".  The identity (account) used by the LDAppVulnerability application pool should be set to "Network Service".

If the identity is incorrect for the LDAppVulnerability Application pool, this can be modified by highlighting the application pool and selecting "Advanced Settings"  It will then be listed under "Process Model" and then "Identity"

Anonymous access should also be enabled for the WSVulnerabilityCore application in IIS.  To verify this, highlight "WSVulnerabilityCore" within the IIS Connections tree and then double click "Authentication" in the right-hand pane and verify that "Anonymous Authentication" is set to "Enabled".

Additionally, the .NET Framework may need to be re-registered and IIS reset as pictured below (Note: The directory for the .NET Framework version may vary)

For core servers running on Windows Server 2003, it is also important that the Core Server was not renamed after IIS installation.  Verify that the IUSR_<coreservername> and IUSR_<coreservername> accounts truly match the current name of the core server.  (Check account names in IIS Manager or Computer Management vs. what is returned by running "hostname" in a command prompt" window.

Additional information regarding the Optimization of IIS can be found here.

Due to the WSVulnerabilityCore web application utilizing the "Network Service" account to write data to the VulnerabilityData folder, the permissions for the LDLogon folder (and VulnerabilityData as a child folder) must allow "Full Control" to the "Network Service" account.

If writing of the Vulnerability Data to the VulnerabilityData folder fails due to permissions, the following error may appear in the WSVulnerabilityCore.dll.log file on the core server:

RollingLog : System.UnauthorizedAccessException: Access to the path 'C:\Program Files (x86)\LANDESK\ManagementSuite\LDLogon\VulnerabilityData' is denied.

  at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)

  at System.IO.Directory.InternalGetFileDirectoryNames(String path, String userPathOriginal, String searchPattern, Boolean includeFiles, Boolean includeDirs, SearchOption searchOption)

  at System.IO.Directory.GetFiles(String path, String searchPattern, SearchOption searchOption)

  at LANDESK.ManagementSuite.PatchBiz.XML.StreamHelper.DeleteOldFilesExcept(String p, String wildcard, Int32 ageInMinutes, String[] filesToIgnore)

  at LANDESK.ManagementSuite.WSVulnerabilityCore.VulnerabilityData.Serialize(String type, String platform, String language)

  at LANDESK.ManagementSuite.WSVulnerabilityCore.VulCore.GetVulnerabilitiesOfTypeInternal(String type, String platform, String language, Int32 lastUpdated)

INFO  772:3    RollingLog : System.UnauthorizedAccessException: Access to the path 'C:\Program Files (x86)\LANDESK\ManagementSuite\LDLogon\VulnerabilityData' is denied.

  at LANDESK.ManagementSuite.WSVulnerabilityCore.VulCore.GetVulnerabilitiesOfTypeInternal(String type, String platform, String language, Int32 lastUpdated)

  at LANDESK.ManagementSuite.WSVulnerabilityCore.VulCore.GetVulnerabilitiesOfTypeCompressed(String type, String platform, String language, Int32 lastUpdated)

The default permissions for the VulnerabilityData folder are inherited from the parent LDLOGON directory and are as follows:

Note: Permissions should be verified for BOTH the LDLogon and VulnerabilityData folders

In addition the following share permissions for\Program Files (x86)\LDLOGONmust be present and inherited by VulnerabilityData:

Note: Permissions should be verified for BOTH the LDLogon and VulnerabilityData folders

For detailed information on the proper permissions that should be applied to directories, seethis article.

Local Security Policy "Adjust memory quotas for a process" user rights assignment

Open the Local Security policy editor by going to Start --> Run and type "secpol.msc".  Then browse to "Local Policies" and User Rights Assignment

Within the Local Security Policy editor, check that the "Adjust memory quotes for a process" user rights assignment is assigned to the following accounts:

Administrators

LOCAL SERVICE

NETWORK SERVICE

SQLServer20XXMSSQLUser$ServerName$DatabaseInstanceName

Note: The SQL Server account name will vary based on SQL version, server name, and Database instance name.

Client cannot connect to \\CORESERVER\LDLOGON\VulnerabilityData or browsehttp://coreserver/wsvulnerabilitycore/vulcore.asmx

The LANDESK client needs to be able to access the\\CORESERVER\LDLOGON\VulnerabilityData folder on the core server to download the Vulnerability data .XMLZ files.

A basic connectivity test can be done by browsing from a web browser on the client to\\Coreserver\LDLOGON\VulnerabilityData.  This should result in a directory listing displaying various .XML and .XMLZ files.  If this does not appear, a note should be taken on any HTTP errors that appear.

In order to see detailed information about errors in Internet Explorer, "Show Friendly HTTP Error Messages" should be disabled.  (Tools --> Internet Options --> Advanced --> and then uncheck "Show friendly HTTP error messages")

In addition the client should be able to browse tohttp://coreserver/wsvulnerabilitycore/vulcore.asmx from a web browser.  If this fails, permissions for the "Everyone" group and for "IUSR" should be verified on the LDLOGON and VulnerabilityData folders.

The LANDESK vulnerability scanner calls the WSVulnerabilityCore web service and uses a SOAP request for "GetVulnerabiilitiesOfType" and requests vulnerabilities for the type of definition (Windows Vulnerabilities, LANDESK Updates, etc) and for the Platform (operating system) the client computer is running.

On the core server, The IIS log file on the core server can be useful for troubleshooting:

Run a vulnerability scan and then check the following log on your core server:

C:\inetpub\logs\LogFiles\(latest log file)

Within this log file there will be lines similar to the following:

2009-12-02 17:58:21 W3SVC1 192.168.0.69 GET /ldlogon/VulnerabilityData/0_win2k3_ENU.1259766918.xmlz - 80 - 192.168.0.1 3200-LANDESKDownloader 206 0 0

If the HTTP result code (A red "206" in the example above) is in the 400's or the 500's, this can indicate a server-side error.

An internet search of "HTTP ERROR CODES" can aid in diagnosis.

Vulnerability Data corrupt on the core server

The vulnerability data may be corrupt on the core server.  This can be suspected if all clients are experiencing the same symptom, as opposed to a smaller group of the whole.

Delete all files \\CORESERVER\LDLOGON\VulnerabilityData and then reset IIS (or recycle the LDAPPVulnerability application pool)  When the next client runs a vulnerability scan this data will be rebuilt.

Note: Running an IISReset or recycling the application pool is necessary because IIS caches requests.

Vulnerability Data on client is corrupt and client is not updating to new data

Run a "vulscan /reset" on the client.  This will delete all settings and vulnerability data on the client and will force the settings and data to be re-downloaded.

A definition within a particular category is corrupt

1. Run a "vulscan /scan=0 /showui", "vulscan /scan=4 /showui", etc.  Does it fail for any one type of definition?

(/scan=# tells the vulnerability scanner to scan only one type of definition.  Example: 0=Windows Vulnerabilities, 4=Custom Vulnerabilities)

See this article for further information on Vulscan switches.

It is possible for a particular definition within the database to be corrupt. 

1. Run a "vulscan /scan=0 /showui", "vulscan /scan=4 /showui", etc.  Does it fail for any one type of definition?

(/scan=# tells the vulnerability scanner to scan only one type of definition.  Example: 0=Windows Vulnerabilities, 4=Custom Vulnerabilities)

See this article for further information on Vulscan switches.

If it is found that the scan fails for only a particular definition type, it may be necessary to force a redownload of content for that type.

In order for this to occur, the revision for the definitions must be set to 0.  Once this is done, the next time patch content is downloaded to the core server, the core will compare it's revision to the revision on the patch content server and redownload the definitions.

The following SQL query must be done against the database:

update vulnerability set revision = 0 where type = type#

    Note: type# refers to the type of definition and should be replaced with a numerical value - (0 - vulnerabilities, 1- Spyware, 2 - Security Threats, 3- LANDESK Updates, 4 - Custom Definitions, 5 - Blocked Apps, 6 - Drivers, 7 - Antivirus)

After running the SQL query a content download for definition type must be done.

The patch forKB973917has been installed on the Core Server

Refer to the following community article for the fix.

MSXML installation corrupted or missing on client

In order for the VulnerabilityData .XML files to be downloaded and properly parsed by the client, the MSXML installation must be functioning properly on the client.

Obtain the latest MSXML version and install on the client.

The LDZIP.DLL in \Program Files\LANDESK\ManagementSuite\wsvulnerabilitycore\bin on the core server is missing, has incorrect permissions, is corrupt, or not up to date.

The vulnerability data is compressed by the core and saved in the form of a "compressed XML" file.  If anything interrupts the proper operation of LDZIP.DLL, failure can occur.

If this is the case, the WSVulnerabilityCore.dll.log file (In the ...\LANDESK\ManagementSuite\log\ direcotry ) on the core server will likely show the following error:

System.EntryPointNotFoundException: Unable to find an entry point named 'LDCompressFile' in DLL 'ldzip.dll'.
at LANDESK.ManagementSuite.WSVulnerabilityCore.VulnerabilityData.LDCompressFile(String fileIn, String fileOut)
at LANDESK.ManagementSuite.WSVulnerabilityCore.VulnerabilityData.SerializeToFile(String filename)
at LANDESK.ManagementSuite.WSVulnerabilityCore.VulnerabilityData.Serialize(Int32 type, String platform, String language)
at LANDESK.ManagementSuite.WSVulnerabilityCore.VulCore.GetVulnerabilitiesOfType(Int32 type, String platform, String language, Int32 lastUpdated)
System.EntryPointNotFoundException: Unable to find an entry point named 'LDCompressFile' in DLL 'ldzip.dll'.
at LANDESK.ManagementSuite.WSVulnerabilityCore.VulCore.GetVulnerabilitiesOfType(Int32 type, String platform, String language, Int32 lastUpdated)
at LANDESK.ManagementSuite.WSVulnerabilityCore.VulCore.GetVulnerabilitiesOfTypeCompressed(Int32 type, String platform, String language, Int32 lastUpdated)

1. Compare the Version of the LDZIP.DLL in \Program Files\LANDESK\ManagementSuite\wsvulnerabilitycore\bin with the one in \Program Files\LANDESK\ManagementSuite.

2. If the LDZIP.DLL in \Program Files\LANDESK\ManagementSuite is newer than the one in \Program Files\LANDESK\ManagementSuite\wsvulnerabilitycore\bin, copy the LDZIP.DLL from \Program Files\LANDESK\ManagementSuite to \Program Files\LANDESK\ManagementSuite\wsvulnerabilitycore\bin

3. From the command prompt run "IISRESET".

The permissions on the LDZIP.DLL file should match the permissions of the VulnerabilityData folder in the table earlier in the article, with the exception that "Everyone" should not be in the list.

Patchbiz.dll in \Program Files\LANDESK\ManagementSuite\wsvulnerabilitycore\bin on the core server is missing, has incorrect permissions, is corrupt, or not up to date.

1. Compare the Version of the LDZIP.DLL in \Program Files\LANDESK\ManagementSuite\wsvulnerabilitycore\bin with the one in \Program Files\LANDESK\ManagementSuite.

2. If the PatchBiz.dll in \Program Files\LANDESK\ManagementSuite is newer than the one in \Program Files\LANDESK\ManagementSuite\wsvulnerabilitycore\bin, copy the LDZIP.DLL from \Program Files\LANDESK\ManagementSuite to \Program Files\LANDESK\ManagementSuite\wsvulnerabilitycore\bin

The permissions on the PatchBiz.dll file should match the permissions of the VulnerabilityData folder in the table earlier in the article, with the exception that "Everyone" should not be in the list.

Remove the /3GB switch from the BOOT.INI file on the Core Server

BOOT.INI is a hidden system file at the root of the system drive.

Reboot the Core Server after removing the switch.

LANDESK Security and Patch News

Headlines

·     (June 10, 2015) JDKv8U45 has been released by Oracle. Java SE 8u45 is the latest Patch Set Update, containing new features
New Features and Changes

LANDESK is dividing the JREJDKv8U45_Manual definition into two definitions JREv8U45(which can automatically download the patch executable) and JDKv8U45_Manual(which still requires the manual intervention to download the patch executable in order to perform the remediation).

Java Packager Tool Enhancements
JDK 8u45 release contains the following enhancements to the Java Packager:

Starting with JDK 8u45 release, the jar tool no longer allows the leading slash "/" and ".." (dot-dot) path component in zip entry file name when creating new and/or extracting from zip and jar file. If needed, the new command line option "-P" should be used explicitly to preserve the dot-dot and/or absolute path component.
A jnlp application, with nested tags within a or tag, can throw an NPE. The issue is now fixed. The tag should be used only if the is actually used.
Nashorn has known issues where it incorrectly compiles try/finally constructs.

Please download the install packages manually from http://www.oracle.com/technetwork/java/javase/downloads/index.html, then put them in the "patch" folder. Please visit the following page for more details: http://www.oracle.com/technetwork/java/javase/8u45-relnotes-2494160.html     

New Vulnerabilities     

  ·        Vulnerability ID – JDKv8U45_Manual  

Changed Vulnerabilities     

·        Vulnerability ID – N/A    

New Patch Downloads     

Where to Send Feedback           

At LANDESK, we are constantly striving to improve our products and services and hope you find these changes reflective of our ongoing commitment to listen to you—our partners and customers—in providing the best possible solutions to meet your needs now and in the future.  Please continue to provide feedback by contacting our local support organization.    

Best regards,  

LANDESK Product Support  

Copyright © 2015 LANDESK Software.  All rights reserved. LANDESK is either a registered trademark or trademark of LANDESK Software, Ltd. or its affiliated entities in the United States and/or other countries. Other names or brands may be claimed as the property of others.    

Information in this document is provided for information purposes only.  The information presented here is subject to change without notice.  This information is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including any implied warranties and conditions of merchantability or fitness for a particular purpose. LANDESK disclaims any liability with respect to this document and LANDESK has no responsibility or liability for any third party products of any content contained on any site referenced herein.  This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission. For the most current product information, please visit http://www.LANDESK.com.   

brokerconfig [options]

brokerconfig is found in /usr/LANDesk/common.  At times you may have the need to run this program manually and these are the switches associated with this program.

  Certificate Request options: (--request)

    --request                        Request client credentials from core server.

    -r                    

    --user <name>               User name to authenticate to core for certificate requests

    -u <name>

   --pass <password>       Password to authenticate to core for certificate requests

   -p <password>

  Connection test options: (--test)

    --test <maxSizeIn> <maxReturenSize> <numThreads> [userName] [password]

    -t  <maxSizeIn> <maxReturenSize> <numThreads> [userName] [password]

    --user <name>               User name to authenticate to core for certificate requests

    -u <name>

    --pass <password>       Password to authenticate to core for certificate requests

    -p <password>

  Configuration options:

    --update                         Update/create the gateway configuration data with elements passed on the command line.

    -U

    --gateway <address>    Set the IP address of the management gateway.

    -g <address>          

    --host <fqdn>                Set the Host name of the management gateway.

    -H <fqdn>              

    --direct                           Use direct connection mode. Do not fall back to the Management Gateway

    -d                    

    --display                        Show current configuration settings and exit.

    -D                    

    --indirect                       Only connect through the Management Gateway, do not attempt a direct connection to the core.

    -i                    

                                          Note: This setting is only used in conjuction with -U.

    --auto                            Try connecting to the core, if that fails, then try the gateway..

    -a                    

                                          Note: This setting is only used in conjuction with -U.

    --proxy <name>           Proxy host name or address.

    -P <name>

    --proxyuser <name>    Proxy user name or address.

    -PU <name>

    --proxypass <name>   Proxy password or address.

    -PP <name>

  Additional options:

    --output <path>             Set verbose output desination. (stdin, stderr, or filename)

    -o <path>

    --config <path>             Load configuration settings form <path>.  The default is /usr/LANDesk/common/cbaroot/broker/broker.conf.xml

    -c <path>

    --xml                              Dump configuration to stdout as xml

    -x

    -v[n]                              Print application version and exit. [n] = 1-3 and specifies optional formats.

    --verbosity [n]              Set logging verbosity to [n]

    -V [n]

    --help                            Shows help message

    -h                                  Shows help message

Macintosh Agent for LANDESK Management Suite

• This is a list of highly recommended documents for increasing overall knowledge of this component.
• The article's listed below are applicable to LANDESK Management Suite 9.6 and possibly as far back as 9.0.

General Information:

Standard Push: The agent files are located on the core server and distributed via a push task. The credentials used in the Scheduler configuration on the core server are critical for this type of distribution.

For more information regarding Windows Agent Deployment, see: LANDESK Agent Deployment Landing Page

Initial Install and Configuration:

• Where can I find the latest LANDesk Agent for Macintosh?
• Best Known Method for deploying the Mac Agent in 9.5
• Getting Started with the Macintosh Agent
• How to change landesk agent configuration in MAC machine.
• Mac Legacy Agent (OS9, 10.2.8, 10.3.9, 10.4.11, 10.5.8 PPC, 10.6, 10.7)

Inventory:

• Best Known Method for troubleshooting inventory on the Mac Agent in 9.5
• How to Gather an Inventory Output scan for Macs

Remote Control and CSA:

• Brokerconfig command line switches on the Mac Agent
• LDGatewayAssistant [Macintosh Version]

Software Distribution:

• Apple Macintosh Application/Software Deployment Guide with LANDESK Management Suite
• The Commandments of Packaging for Apple Mac Software
• Specific software packaging for Apple Macintosh

Patching:

• Macintosh Vulscan Switches
• Mac OS X Scan and Repair Settings Best Practice for LANDesk Management Suite 9.5

Provisioning:

• Best Known Methods for Mac OS X Provisioning in 9.6 SP2
• ** Required for SP2 ** Mac Provisioning - Creating the folder structure on the PXE Representative

Troubleshooting:

• Troubleshooting LANDesk on Mac OS

NOTE: This article is not a comprehensive list of documents and issues. You can continue to search the rest of the community or the portion specific to the Macintosh Agent if this page hasn't helped.

LANDESK Security and Patch News    

Headlines

·     (June 10, 2015) LANDESK has created JREv8U45_Upgrade content. Java SE 8u45 is the latest Patch Set Update, containing new features
New Features and Changes

LANDESK is dividing the JREJDKv8U45_Manual definition into two definitions JREv8U45_Upgrade(which can automatically download the patch executable) and JDKv8U45_Manual_Upgrade(which still requires the manual intervention to download the patch executable in order to perform the remediation).

Java Packager Tool Enhancements
JDK 8u45 release contains the following enhancements to the Java Packager:

Starting with JDK 8u45 release, the jar tool no longer allows the leading slash "/" and ".." (dot-dot) path component in zip entry file name when creating new and/or extracting from zip and jar file. If needed, the new command line option "-P" should be used explicitly to preserve the dot-dot and/or absolute path component.
A jnlp application, with nested tags within a or tag, can throw an NPE. The issue is now fixed. The tag should be used only if the is actually used.
Nashorn has known issues where it incorrectly compiles try/finally constructs.

Please download the install packages manually from http://www.oracle.com/technetwork/java/javase/downloads/index.html, then put them in the "patch" folder. Please visit the following page for more details: http://www.oracle.com/technetwork/java/javase/8u45-relnotes-2494160.html    

New Vulnerabilities    

  ·        Vulnerability ID – JREv8U45_Upgrade 

Changed Vulnerabilities    

·       Vulnerability ID – N/A   

New Patch Downloads    

Where to Send Feedback          

At LANDESK, we are constantly striving to improve our products and services and hope you find these changes reflective of our ongoing commitment to listen to you—our partners and customers—in providing the best possible solutions to meet your needs now and in the future.  Please continue to provide feedback by contacting our local support organization.   

Best regards, 

LANDESK Product Support 

Copyright © 2015 LANDESK Software.  All rights reserved. LANDESK is either a registered trademark or trademark of LANDESK Software, Ltd. or its affiliated entities in the United States and/or other countries. Other names or brands may be claimed as the property of others.   

Information in this document is provided for information purposes only.  The information presented here is subject to change without notice.  This information is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including any implied warranties and conditions of merchantability or fitness for a particular purpose. LANDESK disclaims any liability with respect to this document and LANDESK has no responsibility or liability for any third party products of any content contained on any site referenced herein.  This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission. For the most current product information, please visit http://www.LANDESK.com. 

LANDESK Security and Patch News

Headlines

·     (June 10, 2015) LANDESK has created JDKv8U45_Manual_Upgrade content. Java SE 8u45 is the latest Patch Set Update, containing new features
New Features and Changes

LANDESK is dividing the JREJDKv8U45_Manual definition into two definitions JREv8U45_Upgrade(which can automatically download the patch executable) and JDKv8U45_Manual_Upgrade(which still requires the manual intervention to download the patch executable in order to perform the remediation).

Java Packager Tool Enhancements
JDK 8u45 release contains the following enhancements to the Java Packager:

Starting with JDK 8u45 release, the jar tool no longer allows the leading slash "/" and ".." (dot-dot) path component in zip entry file name when creating new and/or extracting from zip and jar file. If needed, the new command line option "-P" should be used explicitly to preserve the dot-dot and/or absolute path component.
A jnlp application, with nested tags within a or tag, can throw an NPE. The issue is now fixed. The tag should be used only if the is actually used.
Nashorn has known issues where it incorrectly compiles try/finally constructs.

Please download the install packages manually from http://www.oracle.com/technetwork/java/javase/downloads/index.html, then put them in the "patch" folder. Please visit the following page for more details: http://www.oracle.com/technetwork/java/javase/8u45-relnotes-2494160.html     

New Vulnerabilities     

  ·        Vulnerability ID – JDKv8U45_Manual_Upgrade  

Changed Vulnerabilities     

·        Vulnerability ID – N/A    

New Patch Downloads     

Where to Send Feedback           

At LANDESK, we are constantly striving to improve our products and services and hope you find these changes reflective of our ongoing commitment to listen to you—our partners and customers—in providing the best possible solutions to meet your needs now and in the future.  Please continue to provide feedback by contacting our local support organization.    

Best regards,  

LANDESK Product Support  

Copyright © 2015 LANDESK Software.  All rights reserved. LANDESK is either a registered trademark or trademark of LANDESK Software, Ltd. or its affiliated entities in the United States and/or other countries. Other names or brands may be claimed as the property of others.    

Information in this document is provided for information purposes only.  The information presented here is subject to change without notice.  This information is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including any implied warranties and conditions of merchantability or fitness for a particular purpose. LANDESK disclaims any liability with respect to this document and LANDESK has no responsibility or liability for any third party products of any content contained on any site referenced herein.  This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission. For the most current product information, please visit http://www.LANDESK.com. 

Cloud Services Appliance for LANDESK Management Suite

• This is a list of highly recommended documents for increasing overall knowledge of this component.
• If you want to review additional content regarding this component, please use Documents or Discussions buttons on the overview page.

Where do the cables go on the back of the Appliance?

Take a look at the image below for connecting the gateway. Click to expand.

Initial Install and Configuration

• Quick Gateway (Cloud Service Appliance) Configuration
• Step by Step install of the Management Gateway
• Best Known Method for Configuring LANDESK Cloud Service Appliance (former Management Gateway) version 4.2 and newer
• Download the 4.3 Virtual Cloud Service Appliance
• Request 4.3 Upgrade USB
• Best Known Method for Configuring the Management Gateway Appliance
• Recommended Specifications and FAQ for LANDesk Virtual Cloud Services Appliance
• Installation Requirements for the Management Gateway
• Gateway DMZ Install Quick Reference Sheet
• New Management Gateway Service for 9.0 SP1: Enhancements and Configuration Settings
• What steps have been taken to harden the Management Gateway
• Is there a new version of the Management Gateway for LANDesk 9.0 and if so what are the changes?
• Graphical Overview of the LANDesk Management Gateway
• SSL (TLS In-Session) Renegotiation Vulnerability Statement
• How to upgrade the Cloud Services Appliance from 4.2 to 4.3

Additional Options and Information

• Using a Core server DNS alias with the Cloud Service Appliance
• CSA 4.3 Hardening
• Brokerconfig command line switches on the Mac Agent
• Using the Management Gateway
• Gateway Appliance Administrators Guide
• Video:LANDesk® Management Gateway Appliance
• Video:Remote Control using the Gateway Appliance
• Video:How to use the Management Gateway to recover stolen hardware
• CSA Activation: Organization ID and Key Code
• Cloud Service Appliance Failover Mode LDMS 9.6
• Unattended configuration of the client for the Management Gateway
• What ports are used by the Management Gateway?
• How to use Putty to SSH into the LANDesk Management Gateway Appliance
• How to restore the Management Gateway to factory defaults
• How to restore the 4.3 Cloud Service Appliance to factory defaults
• How to change the IP address on an established Management Gateway
• Can the GSB Administration Page for the Management Gateway be disabled?
• How to download and patch the 4.3 Cloud Service Appliance Manually
• How to download and patch the Management Gateway Appliance Manually
• How to activate the Management Gateway
• What's new in the LANDesk® Cloud Services Appliance 4.3 (Includes the link to request 4.3 USB)

Troubleshooting this Component

• Troubleshooting Tidbits for the 4.3 Cloud Service Appliance
• How to Troubleshoot a Management Gateway new install
• "Activation failed due to an unexepected error" when trying to activate the Management Gateway
• How to troubleshoot the LANDesk Management Gateway activation
• Management Gateway firewall is blocking all private IP addresses listed in the allowed list
• How to enable verbose logging for Brokerconfig and Proxyhost.exe
• SUMO file system report emails are received every 2 hours
• Cloud Services Appliance 4.2 - How To Add a Persistent Static Route
• Cloud Services Appliance 4.3 - How To Add a Persistent Static Route
• The Management Gateway password is lost or certificate won't stay posted on the core
• Devices are not visible when attempting to remote control through the Management Gateway
• After using a restore point on the Management Gateway patching and activation fail
• After reimaging the Management Gateway and using a restore point activation and patching fails
• Management Gateway administration page goes blank or no data is displayed on certain tab

Support Notice: Only the 4.2 and 4.3 versions of the Cloud Services Appliance/LANDesk Management Gateway are currently supported by Landesk Customer Support.

Notice:Any E-Learning content is available by default to Members who have a minimum support agreement at Professional level.

NOTE: This article is not a comprehensive list of documents and issues. You can continue to search the rest of the community or the portion specific to the Cloud Services Appliance if this page hasn't helped.

LANDESK Security and Patch News     

Headlines

·     (June 11, 2015) Microsoft has released KB3054794 which is an Excel 2013 update. Some non-ENU definitions may have been downloaded with ENU content. This was done to provide support for Multilingual User Interface(MUI) applications. The English versions of an MS Office application or other application may support adding localized/language support on top of English installations. So these MUI specific content definitions may download with ENU content to support MUI installations. Please see http://community.landesk.com/support/docs/DOC-30218 for additional details. Please visit the following page for more details: http://support2.microsoft.com/kb/3054794     

New Vulnerabilities     

  ·       Vulnerability ID – 3054794_INTL  

Changed Vulnerabilities     

·       Vulnerability ID – N/A    

New Patch Downloads     

·        excel2013-kb3054794-fullfile-x86-glb.exe  

·        excel2013-kb3054794-fullfile-x64-glb.exe  

Where to Send Feedback           

At LANDESK, we are constantly striving to improve our products and services and hope you find these changes reflective of our ongoing commitment to listen to you—our partners and customers—in providing the best possible solutions to meet your needs now and in the future.  Please continue to provide feedback by contacting our local support organization.    

Best regards,  

LANDESK Product Support  

Copyright © 2015 LANDESK Software.  All rights reserved. LANDESK is either a registered trademark or trademark of LANDESK Software, Ltd. or its affiliated entities in the United States and/or other countries. Other names or brands may be claimed as the property of others.    

Information in this document is provided for information purposes only.  The information presented here is subject to change without notice.  This information is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including any implied warranties and conditions of merchantability or fitness for a particular purpose. LANDESK disclaims any liability with respect to this document and LANDESK has no responsibility or liability for any third party products of any content contained on any site referenced herein.  This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission. For the most current product information, please visit http://www.LANDESK.com. 

LANDESK Security and Patch News     

Headlines

·     (June 11, 2015) Microsoft has released KB2965296 which is an Office 2010 update. Some non-ENU definitions may have been downloaded with ENU content. This was done to provide support for Multilingual User Interface(MUI) applications. The English versions of an MS Office application or other application may support adding localized/language support on top of English installations. So these MUI specific content definitions may download with ENU content to support MUI installations. Please see http://community.landesk.com/support/docs/DOC-30218 for additional details. Please visit the following page for more details: http://support2.microsoft.com/kb/2965296     

New Vulnerabilities     

  ·        Vulnerability ID – 2965296_MUI_ENU  

Changed Vulnerabilities     

·        Vulnerability ID – N/A    

New Patch Downloads     

·         proofloc2010-kb2965296-fullfile-x86-glb.exe  

·         proofloc2010-kb2965296-fullfile-x64-glb.exe  

Where to Send Feedback           

At LANDESK, we are constantly striving to improve our products and services and hope you find these changes reflective of our ongoing commitment to listen to you—our partners and customers—in providing the best possible solutions to meet your needs now and in the future.  Please continue to provide feedback by contacting our local support organization.    

Best regards,  

LANDESK Product Support  

Copyright © 2015 LANDESK Software.  All rights reserved. LANDESK is either a registered trademark or trademark of LANDESK Software, Ltd. or its affiliated entities in the United States and/or other countries. Other names or brands may be claimed as the property of others.    

Information in this document is provided for information purposes only.  The information presented here is subject to change without notice.  This information is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including any implied warranties and conditions of merchantability or fitness for a particular purpose. LANDESK disclaims any liability with respect to this document and LANDESK has no responsibility or liability for any third party products of any content contained on any site referenced herein.  This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission. For the most current product information, please visit http://www.LANDESK.com. 

LANDESK Security and Patch News

Headlines

·     (June 11, 2015) Opera version 30.0.1835.59 has been released for Windows. Opera highly recommends all users to update to the latest release. Please visit the following page for more details: http://www.opera.com/docs/history/     

New Vulnerabilities     

  ·      Vulnerability ID – OPERAv30.0.1835.59  

Changed Vulnerabilities     

·      Vulnerability ID – OPERAv30.0.1835.52
(Added the replacement information.)    

New Patch Downloads     

·       Opera_30.0.1835.59_Setup.exe  

Where to Send Feedback           

At LANDESK, we are constantly striving to improve our products and services and hope you find these changes reflective of our ongoing commitment to listen to you—our partners and customers—in providing the best possible solutions to meet your needs now and in the future.  Please continue to provide feedback by contacting our local support organization.    

Best regards,  

LANDESK Product Support  

Copyright © 2015 LANDESK Software.  All rights reserved. LANDESK is either a registered trademark or trademark of LANDESK Software, Ltd. or its affiliated entities in the United States and/or other countries. Other names or brands may be claimed as the property of others.    

Information in this document is provided for information purposes only.  The information presented here is subject to change without notice.  This information is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including any implied warranties and conditions of merchantability or fitness for a particular purpose. LANDESK disclaims any liability with respect to this document and LANDESK has no responsibility or liability for any third party products of any content contained on any site referenced herein.  This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission. For the most current product information, please visit http://www.LANDESK.com.   

How to uninstall the LANDesk Macintosh agent

For 9.x clients

To remove the Mac agent:

1. Copy the file "uninstallmacagent.sh" from the \ldmain share on the core server to the local Macintosh machine.
2. Open a terminal window and change to the directory that uninstallmacagent.sh is located.
3. Change the execute settings on the file uninstallmacagent.sh using the command "chmod +x uninstallmacagent.sh".
4. Execute the file by running "./uninstallmacagent.sh.".

For 8.8 clients

To remove the Mac agent:
1. Copy the file "ldmacclientuninstall.sh" from the \ldmain share on the core server to the local Macintosh machine.
2. Open a terminal window and change to the directory that ldmacclientuninstall.sh is located.
3. Change the execute settings on the file ldmacclientuninstall.sh using the command "chmod +x ldmaccclientuninstall.sh".
4. Execute the file by running "./ldmacclientuninstall.sh".

Note: If this is not in that directory: (Legacy agents)
1. Open terminal
2. Call the directory /Library/Application Support/LANDesk
3. Run the lduninstall.command script by typing 'sudo ./lduninstall.command' without the quotes.
4. Type in the administrative password to the box.
5. The script will then uninstall everything from the Mac.

To install the agent on the Mac
How to install the LANDesk Macintosh agent for the first time

Configuring COM+ server credentials

When using a Web console server that isn't on the core, or if you want to use domain groups inside the LANDESK Management Suite group on the core server, there is some additional server configuration you must do forManagement Suiteauthentication to work correctly. Remote Web console servers must get database connection information and user information from the core server, but since remote Web console servers use impersonated Web credentials on IIS, they can't communicate with the core server directly.

To solve this issue, the Web console server and core server use a COM+ application to communicate via HTTPS, allowing the Web console server to get core server database and user information. You need to configure this COM+ application on the Web console server to use a domain administrator account. The account that you provide needs to be in the LANDESK Management Suite group on the core server (this allows it to access core server database connection information), and must have rights to enumerate Windows domain members.

If you're using domain groups inside the core server's LANDESK Management Suite group,Management Suitealso needs to be able to enumerate Windows domain members. In this case, you also need to provide an account for the core server's LANDesk1 COM+ application.

To configure the LANDesk1 COM+ application on a core or remote Web console server

1. Go to the Web server or core server you want to configure.
2. From the Windows Control Panel's Administrative Tools, openComponent Services.
3. ClickComponent Services > Computers > My Computer > COM+ Applications.
4. Right-click theLANDesk1COM+ application and selectProperties.
5. On theIdentitytab, enter the credentials you want to use.
6. ClickOK.

Information from LDMS Help Files

LANDESK Security and Patch News     

Headlines

·     (June 11, 2015) Microsoft has released KB3054825 which is an Office 2013 update.
This update fixes the following issue: Memory leaks when you use OneDrive for Business to synchronize files.
Please visit the following page for more details: http://support2.microsoft.com/kb/3054825     

New Vulnerabilities     

·             Vulnerability ID – 3054825_INTL  

Changed Vulnerabilities     

·               Vulnerability ID – N/A    

New Patch Downloads     

  ·               groove2013-kb3054825-fullfile-x86-glb.exe  

  ·               groove2013-kb3054825-fullfile-x64-glb.exe  

Where to Send Feedback           

At LANDESK, we are constantly striving to improve our products and services and hope you find these changes reflective of our ongoing commitment to listen to you—our partners and customers—in providing the best possible solutions to meet your needs now and in the future.  Please continue to provide feedback by contacting our local support organization.    

Best regards,  

LANDESK Product Support  

Copyright © 2015 LANDESK Software.  All rights reserved. LANDESK is either a registered trademark or trademark of LANDESK Software, Ltd. or its affiliated entities in the United States and/or other countries. Other names or brands may be claimed as the property of others.    

Information in this document is provided for information purposes only.  The information presented here is subject to change without notice.  This information is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including any implied warranties and conditions of merchantability or fitness for a particular purpose. LANDESK disclaims any liability with respect to this document and LANDESK has no responsibility or liability for any third party products of any content contained on any site referenced herein.  This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission. For the most current product information, please visit http://www.LANDESK.com.