LANDesk® Management Suite 9 release notes

The following are known issues with LANDesk® Management Suite 9. For the latest version of these release notes and product documentation, visit:

http://www.landesk.com/resources/product-documentation.aspx#ldms90

Additional release notes from prior Management Suite versions are also available:

http://www.landesk.com/resources/product-documentation.aspx#ldms88

New post-release 9.0 notes

The following notes were added after LANDesk Management Suite shipped.

Activation: After installing and activating the Automated Patch Process, reboot
Customers that choose to install the patch process should reboot their server after running Core Server Activation.

Macintosh: Macintosh devices aren't sending inventory scans
If an Inventory Scan isn't returned to the core server after pushing an agent to a Mac, manually send a scan from the client by opening \Applications\Utilities\LANDesk Agent.app and clicking the Scan Now button for the Inventory Scanner. Future scan files will update this record.

Notes for LANDesk Management Suite 9.0

Setup: When uninstalling a core server, uninstall the LANDesk Management Agent first
Uninstalling the core server from Windows Add/Remove Programs won't remove the LANDesk Management Agent.

Setup: Installation fails when creating the database tables for databases with case-sensitive collations
Case-sensitive collation on SQL Server is not currently supported.

Upgrade: Make sure you point to a backup of your 8.x database during setup, and not your production database
Setup will upgrade the 8.x database you select to version 8.8 SP3. Consoles from Management Suite versions earlier than this will no longer be able to access the database you selected for the upgrade.

Upgrade: Upgraded agent configurations need some manual changes

After upgrading to 9.0, open upgraded agent configurations and change the following:

1. On the Standard LANDesk agent pageunder Trusted certificates for agent authentication, make sure the 9.0 core's certificate is checked.

2. In the core server name box on the same page, change the name to match that of your new 9.0 core.

3. On the Security and patch scan > Custom variables page, change the Custom variable settings to match your 8.x configuration. 

Upgrade: Thin client configurations aren't upgraded
After upgrading to 9.0, if you had any thin client configurations, you'll need to recreate them.

Upgrade: HIPS settings are migrated, but the service must be enabled via Endpoint Security in Agent Configuration
After upgrading to 9.0, HIPS settings files are successfully migrated to the new core database. However, the HIPS agent/service is not enabled because it is now considered one of the components of the new Endpoint Security service which is not yet enabled. You can check the new Endpoint Security checkbox on your migrated Agent Configuration's Start page, and make sure the desired HIPS settings is selected, in order to re-enable the HIPS service on target devices.

Upgrade: Agent Watcher monitoring of the Targeted Multicast service is not upgraded
If the Agent Watcher utility is set to monitor the Targeted Multicast service in LDMS 8.8 and you upgrade to LDMS 9.0, the setting is not preserved, and should be reset. The reason is the name of the service changed from Intel Targeted Multicast in version 8.8 to LANDesk Targeted Multicast, and so the string values do not match in the database.

Upgrade: Upgraded server agent configurations need to be re-saved
Due to the integration of Server Manager with Management Suite, there are issues with upgrading Windows server agent configurations. After the upgrade, existing server agent configurations will show the operating system as Windows and won't be valid to push to servers. Open each server agent configuration, adjust settings if necessary, and save your changes. After saving, these agent configurations will be updated to correctly show that they are Windows server agent configurations.

Upgrade: Inability to perform an upgrade with existing LDMS 8.8 (side-by-side)

This occurs during a side-by-side upgrade with SQLExpress as the Target database.

Workaround on the LDMS 8.8 SQL Express Core:

  1. Add SQLSrvr.exe as firewall exception
  2. Add SQLbrowser.exe as firewall exception
  3. Launch SQL Server Configuration Manager, Click on SQL Server 2005 Network Configuration, Click on Protocols for LDMSData, Click on IP Addresses tab, Identify port number in TCP Dynamic Ports field. This number will be used during the upgrade.

Workaround on the LDMS 9.0 Core:

  1. Launch autorun
  2. Select Core
  3. Select Upgrade
  4. Choose MSSQL for 8.8 Core database type
  5. Enter <Database Server Name>\LDMSDATA,
  6. Enter ‘sa’ as user name
  7. Enter 8.8 db password
  8. Enter port obtained from 8.8 core
  9. Choose SQL Express for 9.0 Core database type
  10. Enter all other data normally

Activation: Resolving a "Not all required services are running" activation message
If you see this message when you try to activate the core, the "Avocent Management Platform ESB" service may not have finished starting. Exit the activation application, wait five minutes, and try activating again. If this doesn't work, restart the "Avocent Management Platform ESB" service from the Windows Services application, wait another five minutes, and try activating again.

Activation: LDMS core would not activate. The activation file was invalid
Occasionally, the LDMS core activation fails. If you see this issue, please wait a few minutes and try to activate again.

Agent: When creating agent configurations in mixed-language environments, make sure the agent configuration name is ASCII (English character set)
If the agent configuration name uses a non-ASCII code page, such as Japanese, Chinese, or Russian, the agent configuration will only work on devices using a code page that matches the configuration name's code page.

Agent: Creating a self-contained agent configuration package with a period in the name may cause the filename to be truncated after the period
When entering a filename for an executable self-contained agent configuration package, don't include a period followed by an extension with a Windows file association, such as .txt in the filename. Characters after the period will be truncated.

Console: Console users with active directory passwords that contain brace characters "{" or "}" won't be able to log into the console
Make sure your console users don't have braces in their active directory passwords.

Console: Additional consoles won’t work correctly if the additional console user logs into the operating system with an account that has a different password than that same account on the core server
For example, if an additional console user logs into the operating system as “administrator” with password A, and the “administrator” account on the core server has password B (the passwords are different), the additional console’s remote registry request to the core server to get the database connection string will fail. The console will launch but most tools won’t work.

Console: "Insufficient rights" error may occur when trying to log into the Windows console after upgrading from LDMS 8.8 with AMP 2.1 installed

After upgrading from LDMS 8.8 with AMP 2.1 installed, the core activates successfully, but when trying to log into the Windows console, the message "You have insufficient rights to launch the console" displays. This may occur in both Oracle and SQL databases. 

Workaround: You should enter the user name and password for AMP 2.1 during the LDMS installation. If these are entered correctly, then the script below will run successfully. If there was a problem, you can rerun the script with the real user name and password after the installation.

cscript.exe InitializeAmpAuthentication.vbs <username> <password>

On a 32-bit system, run this from a command prompt. On a 64-bit system, run %windir%\SysWOW64\cmd.exe and then rerun the script.

Web console: In the Web console, don't create new groups or copy groups into the software distribution My package or Public packages folders
Instead, do these actions in the Windows console. If you do this in the Web console, the next time someone tries to open a Windows console, it displays an error and won't let you log in. LANDesk will have a patch that fixes this problem in January 2010. If you have this problem after creating groups in the Web console, run the following SQL statement to fix your database:

update CustomGroup set ParentCustomGroup_Idn = null where ParentCustomGroup_Idn = CustomGroup_Idn

Web console: Provisioning users need additional RBA rights
In addition to the “OS deployment – provisioning” RBA rights, Web console users that need to do provisioning must also have the “Basic Web console” right and software distribution “Deploy“ rights.

Database: If a Windows Server 2008 core server joins a domain after the Management Suite install, the Windows firewall will block database port
If a computer joins a domain after installing the core server, the Windows Server 2008 firewall will start enabled but it won't open the port for the database. You will need to open this port in the domain profile.

Rollup: Don't combine 8.x and 9.0 rollups in a single scheduled task
If you're doing rollups in a mixed version environment, combining 8.x and 9.0 rollups in a single scheduled task will cause the task to run continuously. To work around this in a mixed-version environment, schedule the 8.x rollups individually in separate scheduled tasks. You can mix rollup versions if you start the rollup manually with the Rollup Utility's Rollup button.

Rollup: 8.x scheduled rollup jobs will run multiple times when if ran from a scheduled task

This can be a problem if you're rolling up a lot of data or the rollup is happening over a slow link. To work around this, launch 8.x rollup tasks from the Database Rollup Utility.

Reports: In Internet explorer 6, the BIOS summary information report content may not be clickable
If the BIOS summary information contains spaces, Internet Explorer 6 may not let you click on that item. View the report in a more recent browser to fix the problem.

Antivirus: Automatic removal of EPO software not supported via policy-based (pull) agent configuration
If you deploy LANDesk Antivirus via a policy-based (pull) agent configuration with the option to remove any existing antivirus product enabled, be aware that an installation of the McAfee ePolicy Orchestrator (EPO) product will not be automatically removed from the client. EPO software will be automatically removed if the agent configuration is push-based. Otherwise, EPO software must be removed manually before LANDesk Antivirus is enabled.

Antivirus: If the root node of a drive is added to the Trusted Items list, it displays as a blank line
If users are allowed to add items to the Trusted Items list (that are ignored by antivirus scans), and they attempt to add the root node of a drive, it will not appear in the list by its name but rather display as a blank line. This is neither an anticipated nor recommended usage of the Trusted Items feature, but you should be aware that this is the result for the time being.

802.1X NAC: Clients must have a final release version of the OS installed for a successful 802.1X NAC deployment
Make sure your clients have a shipping release version of the operating system installed before deploying LANDesk 802.1X NAC. This includes service pack releases such as Windows XP SP3. Pre-release versions of the OS software may not fully support 802.1X NAC functionality and should NOT be deployed in a production environment.

UDD: WAP discovery doesn't work from Windows 2000 devices
Do WAP discovery from devices that aren't running Windows 2000. ARP discovery will work from Windows 2000 devices.

Remote control (Macintosh): Monitor size and use of dual monitors can cause problems when remote controlling Macintosh devices

Remote controlling a Macintosh device with a monitor that is 20 inches or larger is slow.

Remote controlling a Macintosh device with dual monitors will be successful only if the secondary monitor is configured to the right and at the same height or lower than the primary monitor. If the secondary monitor is configured higher than or to the left of the primary monitor, attempting to remote control the device will generate an error.

Provisioning: Users with the "OS Deployment - Provisioning" right are unable to use the Scripts option in the Web console
In this version of Management Suite, the Provisioning tool is not available from the Web console, but there is a Scripts tool that you can use to schedule scripts. To use this tool you must have the "Software distribution - Distribution packages - Deploy" right. Users who have the "OS Deployment - Provisioning - Deploy" right will see a Scripts tool in the Web console, but are not able to use it to schedule scripts. To schedule scripts from the Web console, these users need to also have the "Software distribution - Distribution packages - Deploy" right.

Profile migration: Windows XP 64-bit not supported; saving profiles across domains not supported
Use caution when capturing user profiles with the User Migration Assistant. In some cases an apparently successful migration fails to create an output file. Windows XP 64-bit is not supported for profile migration: if you try to capture a profile, the Scheduled task window may indicate a successful capture even though no output file is created. Also, if you save the profile output to a network share location that is not on the same domain as the source computer, a false positive is generated as well. We recommend that you check the output directory to verify that captured files have been saved, before you delete any data.

Licensing: Targeted multicast and 45-day trial license
Targeted multicast is not part of the 45-day trial license.

Core synchronization: Alerting service not fired after import
When importing an alert ruleset, copying to core or performing an auto-synchronization, and then distributing to clients, the alerts will never trigger. To fix this, after the ruleset is imported, manually restart the alert service on the target core before distributing to clients. This would also be true for agent configurations that have custom/modified alert rulesets attached.

Software license monitoring: SLM won't open after installation
This is due to the failure of SetCert.exe to set the SSL port. To fix this, run the file \LANDesk\ManagementSuite\install only files\SetCert.exe.

Software license monitoring: Product Usage by Product standard report does not return any data for custom products
If a user has added any custom products to SLM, the Product Usage by Product standard report will not return any data for those custom products. The report works as expected when an ESID product is selected, but when a custom product is selected, the title bar is blank and the body of the report is empty.

A workaround that produces nearly the same report is to open the SLM console and drill down until the specific custom product is selected. In the lower frame, click the "Get all records" button as long as there are less than 10,000 records. Once the usage for the custom product is displayed in the lower frame of the SLM console, click the "View as report" button. If you edit the name and description of the report, it can be made to look almost identical to the canned report.

Software license monitoring: Updating ESID product data used in software license monitoring
The database of normalized product data that is used by the software license monitoring feature can be updated to incorporate data for new software products. This update is available as a patch in Management Suite. New data is added once a month to this patch. To update the data, click Tools > Security and Compliance > Patch and Compliance. Click the Download updates toolbar button, and in the Definition types list, select SLM ESID Update. Select a source site and any other download settings, then click Download now or Schedule download. The new data is then added to the product database for software license monitoring.

Software license monitoring: Microsoft Office 2003 Professional does not display correctly in Product list

Microsoft has two versions of Office 2003 Professional—Enterprise and Retail—that are essentially the same. The Enterprise version is sold only through site license agreements, while the Retail version can be purchased through retail sources. The two suites contain the same combination of products, and their version string is the same except for a suffix (“(Ent)” and “(Retail)”, respectively). Both products are found in the ESID database used for software license monitoring data management, so they are treated as the same product. If you have both versions of this product installed in your environment, when you select "Microsoft Office 2003 Professional" in the product list no product data is displayed. To work around this issue, create a custom product group that includes either of the two versions of Office 2003, or both versions. When you select that group, you will see usage data for the version(s) of Office 2003 Professional in that group.

Software license monitoring: Display problems with the SLM console
If you are using software license monitoring on a VMware workstation or virtual machine, you may have problems with the display of the console. For correct display, we recommend that you set hardware acceleration to a setting less than Full in your VMware settings (see your VMware documentation for instructions on changing this setting).

If you connect to a Management Suite core server from an additional console, you may experience display problems if your computer has an older video driver. This usually happens only the first time you open the console. If you continue to have display problems, try updating your video driver on the additional console.

Software license monitoring: Some products with multiple versions aren’t displayed in Discovered super group
If there are products in the database with multiple versions (including multiple service pack versions of a product), all of the products may not display when you select the Discovered super group. For example, patched versions of Internet Explorer are identified with numbers in brackets after the main version number (such as 7.0[1]. 7.0[2], and 7.0[3]). If your database includes multiple products with multiple versions of each, when you select the Discovered super group, some products may not be displayed in the product details view (for example, .Net Framework is displayed while Internet Explorer is not displayed even though both products have multiple versions). This problem only occurs when you select the Discovered products super group, so to view all versions of a product, select the manufacturer group or a custom product group that includes the versions of the product you want to see.

 


Legal notices

Copyright © 2009 Avocent Corporation. All rights reserved. Avocent, LANDesk, Touchpaper, ITBM and their respective logos are either registered trademarks or trademarks of Avocent Corporation and/or its affiliated companies in the United States and/or other countries. Other names or brands may be claimed as the property of others.

LANDesk and Avocent do not warrant that this document is error free and each retains the right to make changes to this document or related product specifications and descriptions at any time without notice. LANDesk and Avocent do not assume any obligation to update the information contained herein. This document is provided “AS IS” and without any guaranty, warranty, or license, express or implied, including but not limited to: fitness for a particular purpose, merchantability, non infringement of intellectual property, or other rights of any third party. Any LANDesk or Avocent products referenced in this document are not intended for use in medical, life saving, or life sustaining applications. Third parties may have intellectual property rights relevant to this document and the technologies discussed herein.