LANDesk® Management Suite 8 Release Notes

The following are known issues with LANDesk® Management Suite 8. New notes for Management Suite 8, version 8.8  covers issues specific to version 8.8. The following sections cover notes from earlier releases that still apply.

• Notes for Management Suite 8, version 8.7 SP3
• Notes for Management Suite 8, version 8.7 SP2
• Notes for Management Suite 8, version 8.7 SP1
• Notes for Management Suite 8, version 8.7
• Notes for Management Suite 8, version 8.6.1
• Notes for Management Suite 8, version 8.6
• Notes for Management Suite 8, version 8.5
• Notes for Management Suite 8, version 8.1
• Notes for Management Suite 8, version 8.0
• Upgrading Management Suite 8 versions
• Notes from earlier releases
• Console setup
• Client setup
• Console
• Remote control, file transfer, and chat
• Software distribution
• Web console
• Macintosh
• Miscellaneous
• OS deployment and profile migration
• Security and Patch Manager Release Notes

Run Windows Update on your core server before installing or upgrading
Before installing or upgrading LANDesk Management Suite, LANDesk Software recommends that you install all of Microsoft's recommended Windows updates on your core server operating system.

New notes for Management Suite 8, version 8.8

Install: You must have administrator rights to run the autorun and setup
Administrator rights are required to run the autorun and setup. If you receive an error message stating 'This action cannot be completed because the other program is busy' or 'One or more ActiveX controls could not be displayed...', make sure you launch autorun with local admin rights. Windows Vista computers with UAC turned on must use "Run as Administrator" mode when launching the autorun. On Vista computers, if you launched setup without administrative rights, you'll need to reboot before trying again.

Install: When SQL Tools are already installed on the core server, setup displays an error during SQL Server 2005 setup
If you see this error you can restart setup and it will resume where it left off successfully. Alternatively, uninstall the SQL Tools.

Install: You must restart setup from the autorun after installing Microsoft Web Services Enhancements 2.0 SP3
If setup tells you that you need to install Microsoft Web Services Enhancements 2.0 SP3 before continuing, install it. After installing it, cancel setup and restart setup from the autorun. If you don't do this setup won't detect that the Microsoft Web Services Enhancements are installed.

Upgrade: During an upgrade you see, "Error 1303: The installer has insufficient privileges to access this directory..."
This occurs because Microsoft's Indexing Service is running and holding the affected directory open. If the Indexing Service is stopped (or if you wait 10 minutes or so), clicking on the Retry option will resume the install. This is the result of a rare timing issue.

Upgrade: Upgrading a core server or Web console server remotely
Core upgrades using an RDP session will fail if not connected in console mode (mstsc.exe /console). If failure has occurred, disconnect the RDP session and restart the upgrade directly from the Windows console. Remote Web consoles should not be installed or upgraded using RDP sessions, since it will report a failure when creating the identity credentials for the LANDesk com+ services. These credentials will need to be added manually after the install.

Upgrade: Don't use Management Suite 8.7 additional consoles with a Management Suite 8.8 core server
Make sure the core server and additional console versions match. If you try to log in to an 8.8 core with an 8.7 additional console, the console appears to connect to the core but you won't see any data from the core.

Upgrade: When doing a side-by-side upgrade, you must manually copy Agent Watcher settings files to the new core server
If you perform a side-by-side upgrade to Management Suite 8.8, you must copy any Agent Watcher settings files that you want to use (.INI files found in the ldlogon\agentwatcher directory) to the same directory on the new 8.8 core server.

Upgrade: LDMS 8.8 Off-core inventory server now requires Microsoft .NET Framework 2.0 or later
If you don't have Microsoft .NET Framework 2.0 or later installed on your LDMS 8.8 off-core inventory server, the inventory service won't start. To fix this, install .NET Framework 2.0 or later and type the following at a command prompt:

C:\Windows\Microsoft.NET\Framework\2.0.50727\regasm.exe /codebase "C:\Program Files\LANDesk\off-core inventory server\Managementsuite.keyvalue.dll"

Note that the version portion of your path to regasm.exe may vary depending on the .NET Framework version you have installed.

Agent configuration: Agent installation on Red Hat 5 Enterprise client does not install patch management correctly
When a management agent is installed on a Red Hat 5 Enterprise client, the vulscan executable is not installed correctly. Patch management will not work on the client. (This issue does not occur when installing an agent to a Red Hat 5 Enterprise server.) Contact LANDesk support for a patch to resolve this issue.

Connection control manager: If you use connection control manager network restrictions, after upgrading to Management Suite 8.8, redeploy your connection control manager configuration to upgraded devices
If you use connection control manager network restrictions on managed devices and then upgrade to LDMS 8.8, those devices will lose their network restrictions and will have unlimited access on their network. You will need to use software distribution to reschedule a connection control configuration deployment to all devices after upgrading to LDMS 8.8.

RBA: RBA zones are no longer in Management Suite/Server Manager
The RBA zones feature, which was added in LANDesk 8.7 SP1, has been removed.

Database: On a Windows Vista Additional Console accessing an Oracle database, the additional console is extremely slow or not responding
To work around this issue, make the following two changes to the NIC configuration on the database server: 1) Disable the "TCP Checksum offload" setting(s) for the NIC in Device Manager Properties 2) Change the NIC TCP/IP Properties WINS NetBIOS setting to "Enable NetBIOS over TCP/IP".

Database: If your core server uses a Microsoft SQL Express database and is firewalled, make sure you add the SQL service executable to the exceptions list
SQL Express doesn't add itself to the exceptions list automatically during installation. If you don't do this, additional consoles won't be able to connect to the core server. The service executable is called sqlservr.exe. To find the path to the executable, check the properties for the "SQL Server (LDMSDATA)" service in Control Panel's Services applet. The default path is: "C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\sqlservr.exe".
You also may have to open TCP port 1433 and UDP port 1434. See http://support.microsoft.com/kb/287932 for more information.

Web: Web console displays the error "Server Error in '/remote' Application
If the above error is displayed when opening the web console do the following:

1. Open the Windows Computer Management window.
2. Go to Services and Applications, Internet Information Services, Web Sites, Default Web Site, remote.
3. Right-click on remote, select Properties, then click the ASP.NET tab.
4. Select 2.0.50727 in the ASP.NET list box and click the OK button.

Remote Control Viewer for Mac: Full localhost name may be required to establish a remote control connection
If you can't establish a remote control connection using the device name shown in console's inventory view, you may have to specify a fully-qualified domain name (for example, mydevice.mydomain.com). This tends to be necessary for devices with non-standard characters in their name.

Agent configuration: If you're deploying all of the Management Suite agents to a Windows Vista computer, that computer needs at least 768 MB of RAM
If a Vista computer has less than 768 MB of RAM, agent configuration may fail when installing all Management Suite agents. If agent configuration does fail with an InPage error, rerunning wscfg32.exe again without rebooting should fix the problem.

SWD: MSI run from source distributions hosted on NTLM or digest authenticated shares will fail
The MSI APIs don't support providing authentication credentials for HTTP shares, so when choosing Run from source for an MSI that is hosted on an HTTP share the task will fail.

Linux: Linux inventory mount space reporting is off by a factor of 10
Multiply the inventory mount space attributes by 10 to get the actual value.

Patch: A server error message appears when launching the Web console or when doing a vulnerability scan
If you see a server error from asp.net when launching the Web console in your browser, your .NET installation may not have its permissions set correctly. Permission problems can also cause vulnerabilty scans to fail with "Server is busy" error messages. To fix this, do the following:

1. On the Web console server, run this command: aspnet_regiis /i. This program is in the c:\windows\microsoft.net\framework\<your framework version> folder.
2. On the Web console server, edit the permissions for the Inetpub\wwwroot\remote folder. Make sure the IIS_WPG group has read rights to this folder.
3. Restart IIS.

Patch Automation Integration with LDMS 8.8
LANDesk Management Suite 8.8 includes a streamlined version of LANDesk Process Manager with a pre-defined patch automation workflow that can be configured and enabled from the Download Updates dialog box in LANDesk Security and Patch Manager. The patch automation workflow includes all of the actions and most of the settings necessary to enable patch automation, and the required database listener is automatically generated. A tutorial that explains how to configure the patch automation workflow is available from the Download Updates dialog box.

Please note that if you use Oracle as your LDMS core database, you will need to manually edit the Update query in order for the event listener to work.

To edit the query

1. In Process Designer, click Configure | Event listeners.
2. Select the LANDesk vulnerabilities downloaded event listener.
3. Click Edit.
4. In the Update query text box, look for PatchAuditTrail_ldn={PatchAuditTrail_ldn};
5. Edit the query so that the PatchAuditTrail string uses all uppercase characters.
6. Click Test to confirm that the database connection is successful.
7. Click OK to dismiss the confirmation message.
8. Click OK to close the Event listener dialog box and save the changes.
9. Click Close to close the Event Listeners list.
10. Close Process Designer.

This is not necessary if you use SQL as your LDMS core database, as SQL is not case sensitive.

Notes for Management Suite 8, version 8.7 SP3

Enabling LDAP group enumeration on managed devices
Management Suite supports LDAP group enumeration on managed devices. Enabling this option allows managed devices to provide information on their LDAP group membership, adding additional LDAP information to the database. As a result, this information speeds up LDAP group targeting in scheduled tasks. This option does generate additional traffic between the managed device and the LDAP server though, so it's disabled by default. If you want to enable it, edit this line in the ldlogon\NTSTACFG.INI file:

• REG54=HKEY_LOCAL_MACHINE, SOFTWARE\LANDesk\ManagementSuite\WinClient\DisableLdapGroupEnumeration, 1, , REG_DWORD

Change the DWORD value to 0 to enable LDAP group enumeration. You will need to redeploy agents to devices once you make this change for it to take effect.

Notes for Management Suite 8, version 8.7 SP2

Install: Due to the size of SP2, it may take a while to install. Please be patient.

Install: Windows Vista isn't supported for additional consoles
There is no workaround at this time.

Agent config: Ubuntu 6.10 isn't supported as a client
Ubuntu 6.10 uses Dash as the default shell script and Dash does not support some commands in ld-install-functions.sh. There is no workaround at this time.

Console: When using the Windows console, the account logged into Windows must have rights to enumerate domain groups if the LANDesk Management Suite group includes active directory groups
If your LANDesk Management Suite group that controls Management Suite console access includes Active Directory groups, the logged-in Windows user account must have rights to enumerate those groups, otherwise the Management Suite console won't be able to resolve users in those groups and those users won't be able to log in to the console.

OSD: When using OSD on brand new devices, make sure the LDMS user isn't using scopes or zones
Devices in the network view that were added through a PXE proxy or manually don't typically have LDAP information in their inventory records. Because of this, these devices won't be visible to console users affected by scopes or zones.

OSD: The ImageX imaging tool in the Windows PE pre-boot environment can't be used to deploy Windows 98
When imaging with the ImageX.exe image tool, ImageX converts the .wim image file to an NTFS-formatted partition. Windows 98 can't read this partition and deployment fails.

OSD: The Windows PE pre-boot environment requires 256 MB of RAM
If your devices have less than 256 MB of ram, or if devices have 256 MB of ram and not all that RAM is available, the Windows PE boot environment will generate an error and leave the device unbootable. You can fix the device's master boot record and make it bootable again by running "fdisk /mbr" on the device.

OSD: You can't multicast images that are larger than 2 GB
Multicast doesn't support file sizes larger than 2 GB, and scheduled jobs that multicast a file larger than 2 GB generate this message in the Scheduled tasks window: "The specified file is too big." ImageX.exe under Windows PE uses a single image file regardless of image size. In particular, Windows Vista images usually exceed 2 GB. If your image files are larger than 2 GB, don't use multicast. Alternatively, use Imagew.exe as it will automatically divide image files into 2 GB chunks.

OSD: Important Windows PE licensing information
The LANDesk® PE Toolkit contains Microsoft® Windows® Pre-installation Environment software (“WinPE”), a third party product. In order to use the LANDesk® PE Toolkit, you must have a valid license to use WinPE. If you purchased a license to use WinPE from LANDesk, your use of WinPE is subject to the applicable terms and conditions of LANDesk’s End User License Agreement for the licensing of LANDesk software.

Remote control: On Vista clients, remote control keyboard and mouse lock aren't cleared when the session finishes
If you remote control a Windows Vista device and enable keyboard and mouse lock, when you end the remote control session the keyboard and mouse lock remains in effect. When the session finishes, the local user won't be able to use their keyboard or mouse to log back in. To avoid this, when remote controlling Vista devices, don't use the keyboard and mouse lock remote control viewer option.

Rollup: Only use one rollup core to publish packages
If you publish packages from multiple rollup cores, you may overwrite published packages from other rollup cores.

Rollup: SQL Express and MSDE are not supported as rollup servers
There is no workaround at this time.

Rollup: If you modify the core database schema, make sure you also update your rollup core database schema
If you don't update both schemas, you may get errors during rollup.

SLM: Applications on network shares can't be blocked if you select a specific file path and size
You can block applications on network shares if you configure SLM to block ANY version of the application.

SWD: Packages distributed to Windows Vista devices need to run silently or be launched using the startasuser.exe utility
In Windows Vista, packages that display UI will cause Windows Vista to display an "Interactive services dialog detection" dialog that interrupts the package installation until the dialog is acknowledged. This happens because the package is being installed by a process running under a different user account or the package is writing to a protected folder, such as Program Files.

To prevent this from happening, do one or more of the following: disable the Vista User Account Control feature, make sure your packages don't display any UI, or use the startasuser.exe utility, which you can use to make sure the package installs under the logged-in user's account. For more information on startasuser.exe, see the "Running commands as the logged on user" whitepaper on the www.landesk.com support site.

Antivirus: Not supported on the Windows Vista platform
LANDesk Antivirus is not currently supported on Windows Vista clients; it will be supported with a LANDesk software update (patch) in the future.

Trusted Access (LANDesk DHCP): Windows Vista IS included in the predefined Windows 2000+ OS Filter
Although the Vista platform name doesn't display in the UI of the Windows 2000+ OS Filter (found in the LANDesk DHCP Manager tool | OS Filter Options object), it IS included in that filter.

Reporting: Table borders in reports aren't visible in Internet Explorer 6 or 7
The table borders for reports display normally in Firefox, but not in Internet Explorer 6 or 7. To correct this, do the following steps:

1. Open Internet Explorer 6 or 7.
2. Click Tools | Internet Options.
3. Click the Advanced tab.
4. Enable Print background colors and images.
5. Click Apply.

The table borders will now display normally.

Macintosh: Agent configuration
With 8.70 Service Pack 2 the Jaguar client has been frozen. The Jaguar client can still be installed using the same process as before, but will not contain updates past 8.70 Service Pack 1.

Macintosh: Agent configuration
After upgrading the LANDesk Agent for Mac with Service Pack 2, if certain features report the status of Stopped in System Preferences then reboot your client. After reboot these processes will be running.

Macintosh: Agent configuration
If the logged-in user doesn't have administrative privileges, changes made in the agent preferences dialog won't be saved because the user won't have rights to change the file where preferences are stored. This is the case even if a user unlocks the preferences dialog.

Macintosh: Inventory scanner
With 8.70 Service Pack 2 support exists for Mini and Delta scans as well as scan encryption. In addition, the LANDesk Agent for Mac now provides Automatic SLM Configuration information to the Core, and can process Custom Data, via XML files on the client, which is then included in Inventory Scans.

Macintosh: Local scheduler
With 8.70 Service Pack 2 the LANDesk Agent for Mac includes a Local Scheduler process (ldcron). The Local Scheduler schedules and executes events based off of the settings in a custom XML file (ldcron.xml), and can be modified via Local Scheduler settings in Agent Configuration.

Macintosh: Patch manager
With 8.70 Service Pack 2 the Vulnerability Scanner (ldpatch) is scheduled for reoccurring execution through Local Scheduler. Vulnerability Scanner execution includes updating the vulnerability files on the client, checking for vulnerabilities using the updated vulnerability files, and remediating any detected vulnerabilities set to Autofix on the Core.

Macintosh: Remote control
With 8.70 Service Pack 2 the user can now remote control a Mac device from the LDMS Web Console (on a Windows machine) by right-clicking the device and selecting “Remote control”.

CCM: Running wscfg32.exe on a client removes all connection control manager configurations and usbmon.exe from the client
When wscfg32.exe runs on a client, it first empties the ldclient folder structure and reinstalls everything from scratch. When it does this, you will lose connection control manager configurations and usbmon.exe on that client. If you want to preserve these items, update client agents with a vulnerability patch or use the SP2 patch client installer (LD87-SP2-Client\setup.exe).

CCM: Blocking all unknown volumes won't block USB thumb drives in Windows Vista
In connection control manager, blocking unknown volumes in Windows Vista will block USB hard drives but it won't block USB thumb drives. If you want to block USB thumb drives in Windows Vista, make sure your connection control configuration blocks USB devices.

Provisioning: Some English strings appear in non-English installations
Not all of the provisioning user interface was available for translation in time for SP2, and so you may see a few English strings in parts of the provisioning interface. These remaining strings will be translated for the next product release.

Provisioning: Unable to create bootable USB drive under VMWare
A known issue with using portable USB drives under VMWare is that some USB 2.0 drives do not work as expected and may cause an unexpected OS shutdown. The VMWare knowledge base reports that this is due to OS or driver limitations in passing USB 2.0 host data to the virtual machine's USB 1.1 controller. A workaround is to plug the USB device into a USB 1.1 hub or host port, which forces the transactions between the host and device to be USB 1.1. If you use a USB 2.0 device under VMWare it is also recommended to take a snapshot of the virtual machine to preserver the current state of the guest operating system.

Provisioning: Date and Time format for provisioning templates
The date and time stamp that is appended to provisioning templates when they are scheduled, cloned, or condensed (for example, TemplateA becomes TemplateA 01 Dec 2006 11:12:13 AM) has an internal default format (dd MMM yyy hh:mm:ss tt). The core can set a registry value that will override this provisioning business layer default. This registry key and string value is HKLM\Software\LANDesk\DateTimeFormatForUIAppend. The contents of this registry key are the format specifier characters in the .NET class DateTimeFormatInfo. For details see http://msdn2.microsoft.com/en-us/library/system.globalization.datetimeformatinfo.aspx.

Provisioning: Provisioning files fail to load on USB boot media target
The Provisioning Windows PE image used to create bootable Windows PE media (USB drives and CD-ROM’s) will not be correctly updated with the core's network name during install. The user can correct this situation by completing the following steps. (The following assumes that LANDesk software was installed to the c:\Program Files\LANDesk directory. If LANDesk was installed to a different location, adjust the command appropriately. Please note that on a machine running x64 Windows LANDesk is typically installed to c:\Program Files (x86)\LANDesk. In the command below, replace YOURCORENAME with the actual network name of your core server.)

On the core server’s desktop, click Start | Run and type cmd.exe, then click OK. At the command prompt, type the following and press Enter:

"C:\Program Files\LANDesk\ManagementSuite\changecorename.exe" "corefilename=\TEMP\CORENAME.TXT" "outeriso=C:\Program Files\LANDesk\ManagementSuite\ldlogon\provisioning\windows\prov_winpe.iso" "isofilename=\I386.ISO" "corename=YOURCORENAME" "console=y" "logto=C:\Program Files\LANDesk\ManagementSuite\changecorename.log"

ThinkVantage: Apply the ThinkVantage SP1 before applying SP2
For customers using LDMS 8.7 for Thinkvantage, there is a patch that we put out for SP1 that included bug fixes (http://www.landesk.com/support/downloads/Detail.aspx?rid=454&pvid=85 is the link for it). This needs to be installed before SP2 is installed in order for the bug fixes to be applied. If you apply this patch after SP2, the Thinkvantage patch can overwrite LDMS SP2 files.

ThinkVantage: Error when deploying ThinkVantage configurations to clients without SP1 or SP2
If a client has not been updated to SP1 or SP2 the following error may occur in the scheduled task when sending a ThinkVantage Technologies configuration to the client: Failed - "The Client does not support the features required by the specified delivery method".

Here is the workaround:

1. In the Console go to Delivery Methods.
2. Select "All Delivery Methods".
3. Select "Policy-supported push".
4. Select "ThinkVantage Delivery", right click, and choose "Properties".
5. Choose "Downgrade" in the left tree view.
6. In the "Agent downgrade options" section choose the "Downgrade functionality to level of agent" radio button.
7. Click Save.
8. Schedule the Configuration again and it will be successfully delivered to the client.

Updating an off-core inventory server

The off-core inventory service won't start if there's a mismatch between the core server and off-core server inventory service files. If there's a mismatch, the core server's and off-core inventory server's event logs will record the following:

• Off-core server Event: Error: Files required for the inventory service are either out of date or missing.
• Core server Event: Error: Disabling off-core inventory service. Critical files are out of date or missing.

Once you apply SP2 or otherwise update the inventory service files on both the core server and the off-core inventory server, do the following:

1. From the core server's Win32 console, re-add the off-core inventory server name to the Configure services dialog (Configure | Services | Inventory tab, Advanced settings button, Off-core inventory server key).
2. Important: Restart the inventory service on the core server first and then restart the off-core inventory server service.

In the future whenever any of the inventory service files for both the core and off-core servers don't match, the off-core inventory server name will be removed from the configure services dialog's parameter list and its off-core service will be stopped.

Here are some other off-core service errors you might encounter.

The core server inventory service is off and the off-core inventory service has been started

In this scenario, the off-core inventory service will record the following event:

• Event: error: Unable to find active license.

The off-core inventory service will start but won't process scans because it couldn't get an active license from the core server's inventory service. You would then need to get the core server's inventory service started, then go back and restart the off core inventory service.

You attempt to add an off-core inventory server while the inventory service on that off-core inventory server is off

In this scenario, a popup message will appear saying, "The inventory service doesn't exist on the supplied off-core server. Do you want to use it anyway." You can go ahead and choose yes, then go and start the off-core inventory service.

New notes for Management Suite 8, version 8.7 SP1

Install: Stop all off-core inventory services before applying SP1
If an off-core inventory server is processing scans while you're applying SP 1 to the core server, the service pack installer may not be able to fully upgrade the database.

Install: Uninstall PXE proxies before installing SP1
You should uninstall any inherited OSD PXE proxies before upgrading to SP1. Uninstall the LANDesk PXE Proxy from Control Panel's Add/Remove Programs. After upgrading the core to SP1, update the LANDesk agents on the device you want to be the proxy, then redeploy the proxy from the upgraded core server.

SLM: Publish application lists from the Windows 32-bit console, not remote Web consoles
If your Web console server isn't on the core server, publishing the application list from a Web console will display an exception and the publish will fail. To work around this issue, publish the application list from the Windows 32-bit console.

Mac: Intel-architecture Macintosh remote control doesn't support a 256-color depth
When remote controlling an Intel architecture Macintosh device with a 256-color depth desktop, remote control falls back to 16 colors.

OSD: The OSD DOS capture image path can't contain double-byte characters
Image capture will fail if your OSD DOS image capture path contains double-byte characters. The DOS utility that maps the drive doesn't support double-byte characters.

OSD: PXE boot menu text containing extended or double-byte characters may not display or work correctly on managed devices
Extended and double-byte characters that are in the PXE boot menu will only display and work correctly if the target devices have BIOS support for those characters. If the BIOS doesn't support the non-English characters, the PXE boot menu may not display or work correctly. To be safe, you should use only English characters in the PXE boot menu.

OSD: Back up custom scripts before applying SP1
With SP1, OSD now stores custom script information in the database rather than in text files. If you've manually customized OSD script text files, those changes will be lost the next time you schedule a job that uses a customized OSD script. To preserve your changes, back up your OSD scripts and instead enter your custom commands in the capture/deploy configuration dialogs. Use the Pre-boot commands or Additional commands pages, depending on which task you're configuring.

Mac: If a Mac OS 9.1 user cancels the remote control permission required dialog, the computer will hang
To avoid this problem, don't enable the permission required remote control option for Mac OS 9.1 devices.

Handheld: After applying SP1, Handheld Manager users need to rebuild Windows CE CAB files
After applying SP1, use Tools | Handheld | Windows CE agent configuration to recompile CAB files for Windows CE platforms you are managing.

SLM: Reports from the Web console time out
If reports generated from the Web console time out before completing, you can increase the ASP.NET request timeout. The request timeout is how long a specific request has to return data before an error is generated. For asp.net you can set this in the web.config file with the executionTimeout attribute of the httpRuntime element. Here is an example:

<configuration>
<system.web>
<httpRuntime executionTimeout = "00:01:50" />
</system.web>
</configuration>

The format of the value is “HH:MM:SS” so this example shows the default setting of 1 minute 50 seconds or 110 seconds. The <httpRuntime> element is not in the web.config by default so you need to add it to the <system.web> (asp.net) section.

Software license monitoring changes in SP1

Notes for Management Suite 8, version 8.7

Install: Rerunning setup after a canceled install generates an error message: "An error was encountered during the database configuration: CoreUpgradeDB"
This error will appear if you cancel setup and then reinstall. If you ignore the error and continue installing, you won't be able to log into the console when setup finishes. The problem is that the database has been created, but tables have not been added (that all happens at end of install). So, if you cancel and/or rollback at this time of the install, then you need to select NEW database instead of EXISTING database when prompted.

Install: When upgrading a core, setup generates an error that you don't have rights to the \upl folder and fails
This error occurs when the uninstall portion of the upgrade couldn't fully delete a file that needed upgrading. If you see this error, cancel setup and let it roll back the upgrade. Reboot your server. This should release the lock on the affected file. Rerun setup again.

Install: If you installed asp.net after installing IIS, register asp.net with IIS before installing Management Suite
If you have IIS installed and then install asp.net 2.0, it doesn't get registered with IIS. To fix this, run the following from a command prompt:

aspnet_regiis /i

The aspnet_regiis application is usually found in C:\Windows\Microsoft.NET\Framework\<Version>.

Install: When installing/upgrading LANDesk products on a VMWare workstation, don't run setup from USB media
When installing/upgrading LDMS/LDSM/LSM/GSM/ISM on a VMWare guest, don't use USB media since VMWare's virtualized controller is limited to USB 1.1 bandwidth and that may cause problems during the install. As a work-around, the install can be copied locally or to a network share.

Install: Repairing an LDMS/LDSM/LSM installation won't restore files in the C:\Program Files\LANDesk\Shared Files\cbaroot\services folder
If you need to repair/restore files in this folder, run cba8inst.msi from the core server's LDLogon folder.

Upgrade: After upgrading to 8.7, the core or Web console server has an error in the Windows Event Log
If you see these errors in the Windows Event Viewer after an upgrade, you can ignore them: "The server certificate for instance "1" does not chain up to a trusted root certificate...." and "The description...in source (MSSQL$LDMSDATA) cannot be found...." If there isn't a certificate installed for the web server we will install our default self-signed certificate, but because it doesn't have a trusted chain IIS will issue the warning.

Upgrade: If several LANDesk services fail to load after upgrading, rerun the instams.exe component
If there's a problem with the AMS install, these services may fail to load: Intel QIP Server Service, LANDesk Device Monitor and LANDesk Inventory Server. Fix this problem by running "instasm.exe UNINSTALL CORE CONSOLE" and then after the reboot, run "instams.exe Core". The instasm.exe program is in the core server's LDLogon folder.

Upgrade: When upgrading, you must provide the same database credentials that you used for the original installation
If you use different database credentials on an upgrade, some tables will be tied to the original user and others tied to the new user. LANDesk products won't work correctly if this happens.

Database: When adding a rollup core to another rollup core's source cores list, attaching a certificate will cause the add to fail
If you're adding a rollup server to another rollup server, don't check the add certificate option.

Inventory: Repairing an off-core inventory server install won't fix the inventory service startup state if it was manually set to disabled
If you've manually set the inventory service startup state to disabled, set it to automatic before repairing or reinstalling the off-core inventory server.

Inventory: If the off-core inventory server is installed on an additional console or a Web console server, uninstalling the console or server will break the off-core inventory server
After uninstalling the additional console or Web console server, rerun the off-core inventory server setup to repair the off-core inventory server installation.

Inventory: LANDesk Inventory Server service generates Windows Data Execution Prevented message
If you see this message, change the Windows Data Execution Prevention settings. To do this, right-click My Computer, click Properties, Performance Settings, and the Data Execution Prevention tab. Either turn on DEP for essential Windows programs and services only, or select the LANDesk Inventory Server service as an exception.

SWD: Make sure package Web shares don't have the IIS "Use default page" option enabled
If this option is enabled and the default Web page exists, devices won't be able to download package files from that folder.

SWD: Using the "Run from source" option to deploy Microsoft products from an HTTP path may not work
Microsoft doesn't fully support installing their products from an HTTP path. For more information, see http://office.microsoft.com/en-au/assistance/ha011401931033.aspx. This affects Office 2003 and possibly other current and future Microsoft products. The workaround is to use a UNC path or a hyperlink to a UNC path.

Patch: Mac patch content downloads fail with a connection closed (protocol error) message
This may happen because one of the Apple URLs includes a space, which won't work correctly with the .NET Framework HTTP implementation. You can bypass this problem by editing the vaminer.exe.config and console.exe.config files (they're in the \Program Files\LANDesk\ManagementSuite folder) and uncommenting the following line:

<!-- <httpWebRequest useUnsafeHeaderParsing="true" /> -->

Note that if you use an HTTP proxy, this change may not work.

Antivirus: The real-time antivirus detection process ignores the filter "Scan infectable files only" if a full virus scan is in progress.
If you configure an Antivirus behavior (settings) with "Scan infectable files only" selected as the file types to scan for BOTH the Virus Scan mode and the Real-time protection mode, and deploy that Antivirus behavior to managed devices, the "Scan infectable files only" filter is ignored by real-time protection during the full virus scan. In other words, file types that aren't typically considered infectable are monitored by real-time protection and may be detected.

Antivirus: LANDesk Antivirus real-time file protection conflicts with eTrust Antivirus real-time protection
If you deploy LANDesk Antivirus with real-time file protection enabled (in the antivirus settings) to a device that currently has eTrust Antivirus real-time protection running, the machine performance is seriously degraded. Either disable eTrust Antivirus real-time protection or remove the eTrust software before deploying LANDesk Antivirus, or make sure the LANDesk Antivirus real-time protection option is not selected when configuring the device. This option can be enabled at a later time with a change settings task.

Trusted Access: SUSE OS filter only filters SUSE Linux 9 clients
To filter other SUSE versions, create your own filter.

Trusted Access: The Cisco NAC implementation of LANDesk Trusted Access installs the 1.0 version of the CTA (Cisco Trust Agent)
If you're using Cisco NAC trusted access and want to upgrade your CTA version, you can obtain it from the Cisco download site.

Agent Watcher: Agent Watcher is not officially supported on Windows NT clients
Windows NT is not included in the official list of supported platforms for LANDesk Agent Watcher.

Reporting: Reports on the rollup core web console not returning data
Remote control and SLM reports on the Rollup core web console don't return any data. Remote control will never return any data on the rollup core because whenever you remote control a machine from the rollup core, the client will report back to its managed core not the rollup core.

Tasks: Custom script names can only consist of alphabetic and underscore characters
If your script name includes other characters, such as a hyphen, the script may not complete successfully.

Agent configuration: HP/UX agent configuration is only available if LANDesk Server Manager or LANDesk System Manager are installed
If you only have Management Suite installed, the HP/UX agent installation option won't be available and you can ignore the documentation about HP/UX agent installation.

UDD: When unmanaged device discovery detects a device running Windows XP x64 Edition, the OS description is Win 98SE
There is no workaround at this time.

Trusted Access: SUSE OS filter only filters SUSE Linux 9 clients
To filter other SUSE versions, create your own filter.

Web: Popup blocker should be turned off
The first time you open the Web console, your browser may show a security alert related to blocking active content. You will need to allow the blocked content to be displayed. If you repeatedly see this warning, change your browser's Internet security settings to always allow blocked content. In Internet Explorer, click Tools | Internet Options | Advanced and check the box labeled Allow active content to run in files on My Computer.

Web: Web console won't work if Microsoft's .NET Framework 2.0 is installed before .NET Framework 1.1
If the .NET Framework 2.0 is installed before .NET 1.1 on your Web console server, the Web console won't work. It can also get into this same state if IIS is uninstalled, reinstalled, and then .NET Framework 2.0 is installed. Since ASP.NET 2.0 becomes the default for the 'Default Web Site', the LDMS/LDSM virtual directories get created and versioned as ASP.NET 2.0. The characteristics of this behavior is when the Web consoles launches, either it can't get pass the license check action (just hangs with error) or it displays a permission issue error.

Below are different ways of fixing the situation:

• To fix before the install, change the ASP.NET version of the Default Web Site to 1.1.
• To fix after the install, change the ASP.NET version of the Default Web Site to 1.1. Validate that the other virtual directories were changed to use version 1.1. If LANDesk Process Manager Server is installed or if any other .NET 2.0 applications are on the server, the remaining virtual directories should remain at ASP.NET 2.0.
• To fix after the install, uninstall ASP.NET 2.0. If Process Manager Server or any other .NET 2.0 applications are installed, you must reinstall ASP.NET 2.0 and manually change their virtual directories back to 2.0.

Handheld: Deploying a remote control thin client agent configuration won't work correctly if the thin client has already has an existing remote control configuration
To fix this, use the Thin-client configuration window to create the configuration's .REG as normal. Edit the configuration's .REG file in \Program Files\LANDesk\ManagementSuite\LDHM\packages, and change the line that says "MRU0" to "MRU". You can then deploy the edited configuration.

Macintosh: LANDesk clients with Macintosh Jaguar OS require service pack 10.2.8
In order to use the Macintosh Jaguar OS on a LANDesk client, the computer needs to have service pack 10.2.8 installed.

Operating system deployment

When capturing and deploying Windows XP x64 Edition images, you must use the Windows PE boot environment
The other boot environments won't work with Windows XP x64 Edition images.

The "Generic sample dir command" OSD script doesn't work with devices running Windows XP x64 edition
You can use this script on devices running other DOS and Windows operating systems.

Injecting non-network drivers into the Windows PE boot environment
If you have hardware that the Windows PE boot image doesn't natively support, you can inject the drivers files into the Windows PE boot image. The Windows PE boot image is located on the core server in C:\Program Files\LANDesk\ManagementSuite\landesk\vboot\ldvpe1.img. Use a disk image manipulation utility like WinImage (www.winimage.com) to open the Windows PE .IMG file. Add the driver's .INF file to the ldvpe1.img file's \i386\inf folder. Add the driver's .SYS file to the ldvpe1.img file's \i386\System32\Drivers folder.

When restoring sysprep images, the restore may fail if the computer name ends up being only numbers
This may happen if the SYSPREP.INF | Naming convention page in the deploy image dialog uses only the MAC address and the MAC address ends up consisting only of numbers. To prevent this from happening, if you're naming devices by MAC address, include an alphabetic character in the name template.

Using an IP address to specify the path to store images may not work correctly
When capturing images, avoid using an IP address to specify the captured file path. IP addresses don't always resolve reliably in OSD.

WSCFG32.EXE displays an application error on the first reboot after an image is deployed
This error is intermittent. When this error pops up, the target system will reboot but the LANDesk agents do install correctly and will work after the reboot.

Deleting profile migration rules that are being used by other capture profile tasks will cause those tasks to fail
Only delete profile migration rules from the Collections panel if you're sure they aren't being used by other migration tasks.

After using the Linux boot environment to image a PXE-bootable device with a Windows OS, the device reboots and shows a grub boot loader logo
The issue is that the Linux uses a different boot loader than Windows operating systems. The LANDesk imaging tool only backs up the partition, not the MBR. You can work around this behavior on devices that boot through PXE as follows:

1) If and only if, you are restoring an image to the same drive, (same size and geometry), and this drive is in the same hardware configuration (ie., master drive on IDE controller #1) you will need to back up the MBR during the imaging process, and restore it before copying the image back onto the drive.  This can be done with dd: 
copy: dd of=mbr.bin if=/dev/hda bs=512 count=1
restore: dd of=/dev/hda if=mbr.bin bs=512 count=1
Then you can image the partition using your previous image.

2) If and only if, you are restoring an image to a different drive than that it was imaged from (different size and/or geometry), but using the same partitioning scheme, and the drive is in the same configuration (ie., same controller, same master/slave assignment), you will need to back up the MBR as indicated above, then you will also need to create a copy of the partition table (ie., using the parted tool or something similar).  Then, when you restore the image, you will need to first, restore the MBR as mentioned above, and then use the partitioning tool to re-write the partition table to match the configuration from the previous drive (using the new drives geometry).  Now the partitions can be imaged.

3) If and only if you are trying to image to a different partitioning scheme or to a different drive hardware configuration (ie., master => slave drive, IDE1 => IDE2) you will need to do the following:
a) Determine which boot loader you're going to use, and write a new boot loader (winnt/grub/lilo) to the primary boot devices mbr.
b) Partition the CORRECT drive to match a similar partitioning scheme used in the original image.
c) Copy the image to the correct partition(s)
d) Update the boot loader with the new partition information, the newly installed OS and possibly any other existing OSs found on other hopefully untouched partitions.
e) Modify the filesystem information in:
i. Windows: registry to point to the correct drive letter, and modify boot.ini to present the correct options in the boot menu, update any other application registry entries that may have previously pointed to an incorrect installation drive letter.
ii. Linux: modify /etc/fstab to mount the correct volumes at boot time and update /boot/grub/menu.lst (or /etc/lilo.conf) to boot the correct kernel from the correct partition.

Notes for Management Suite 8, version 8.6.1

Install: Installing a Management Suite additional to console to a server running Windows Terminal Server generates an error message and the install fails
Uninstall Windows Terminal Server before installing the additional console.

Install: A server error message appears when launching the Web console
If you see a server error from asp.net when launching the Web console in your browser, your .NET installation may not have its permissions set correctly. To fix this, do the following:

1. On the Web console server, run this command: aspnet_regiis /i. This program is in the c:\windows\microsoft.net\framework\<your framework version> folder.
2. On the Web console server, edit the permissions for the Inetpub\wwwroot\remote folder. Make sure the IIS_WPG group has read rights to this folder.
3. Restart IIS.

Upgrade: When upgrading from Management Suite 8.1, verify the distribution rights that console users have
Management Suite 8.1 only had one software distribution right. Management Suite 8.61 includes four software distribution rights. After upgrading, give your users the appropriate new software distribution rights.

Upgrade: After upgrading to Management Suite 8.61, don't modify/repair/uninstall your installation from older installation media
Once you upgrade to 8.61, only use an 8.61 installation image to modify/repair/uninstall Management Suite.

Upgrade: Authentication errors with CoreDataMigration.exe
The account you specify in CoreDataMigration.exe must be the domain administrator or a local administrator for both core servers

Upgrade: When upgrading from older versions of Management Suite, the directory manager tool may not be able to connect to previously configured LDAP directories
After an upgrade, if directory manager reports an error when it tries to connect to an LDAP directory, remove the LDAP directory and reconnect to it again.

Upgrade: If you have a Management Gateway installed, you must refresh the core server's security certificate after upgrading
The 8.6.1 upgrade overwrites the core server's security certificate in the LDLogon folder. If you have a Management Gateway installed, the gateway modified this certificate. These modifications are lost after an upgrade. To refresh the core server's certificate, in the Windows console, click Configure | Management Gateway and then click OK. You don't need to make any changes in the dialog. If you don't do this, any devices you configure after the upgrade won't be manageable through the Management Gateway.

Upgrade: The 8.6.1 upgrade resets the scheduler service login to "LocalSystem"
If you changed the scheduler service login, after upgrading, you need to re-enter those changes. You can do this by clicking Configure | Services | Scheduler tab, and then click Change login.

Database: After changing a CHAR column to VARCHAR2 in Oracle, queries on changed data may not work correctly
If you change a CHAR column to VARCHAR2 within Oracle, Oracle won't remove the whitespace it appended to the CHAR column. You should run the following command to remove the whitespace:

update <table name> set <column name> = trim(<column name>)

This will remove all whitespace from converted CHAR columns. If this statement isn't run, the whitespace will remain in the column and all queries against that column that use an equals (=) operator will fail to find the data.

Inventory: Device inventory may incorrectly list floppy disk drive
In some situations, when a device does not have a floppy disk drive installed, Management Suite may incorrectly list a floppy drive under System information | Hardware | Storage. However, the list of logical drives will correctly state that there is no media for drive A.
 

OSD: DOS OS deployment fails when the OS deployment image or tools are stored in the LDLogon folder
Having the text "logon" in the DOS OS deployment job path causes the OS deployment job to fail. Place these files in a path that doesn't include this text.

Agent configuration: Deploying Management Suite agents to a device with the software distribution package builder on it removes the package builder Start menu items
Package builder is still installed when this happens. You can navigate to \Program Files\LANDesk\Package Builder and run builder.exe to launch the package builder manually.

Trusted Access: If you install the full LANDesk Trust Agent (LTA) on an XP Pro machine (with SP2 and with the firewall enabled) and log in with non-administrator rights, a Windows Security Alert displays
In this specific scenario, a security alert displays on the managed device that prompts the end user to allow/disallow the LANDesk Trust Agent. If you see this alert (or any other LTA related popup message), be aware that the LTA is in fact registered with the firewall and you should allow it to run if you want LANDesk DHCP Trusted Access to function properly for that machine (i.e., scan for and remediate vulnerabilities to ensure a healthy posture before allowing access to your network).

Trusted Access: If you want to install the lite LANDesk Trust Agent (LTA) on a client, it must have version 3.1 or higher of the Microsoft Installer
If the Microsoft Installer is earlier than version 3.1, an "Incorrect command line parameter" error appears when attempting to install the lite LTA (the "Connect to our server" link on the Visitor.html page). If you have reason to believe this might frequently occur on your network, you could download version 3.1 of the Microsoft Installer and add a link to that file by editing the Visitor.html page, so that end users could resolve this issue on their own.

Trusted Access: A scanned, remediated, and healthy managed device still shows as being out of compliance until a security scan (vulscan) runs on the device
Even if a managed device's vulnerabilities are remediated by Trusted Access and the device is healthy, its Security and Patch Information dialog will show these vulnerabilities in the Detected list (not the Installed or Repaired lists), and the device will still show as being out of compliance. Only after a security scan that includes the vulnerabilities in the Compliance group runs on the device will the information be updated to reflect the real compliance status of the device.
Tip: To ensure that compliance status for managed devices is updated with current information, create a Scan and Repair Setting that scans for the Compliance group, and then apply this setting to either a scheduled security task or to the local scheduler.

Configuring COM+ server credentials with Management Suite 8.6.1

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 for Management Suite authentication 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 an account that has the necessary rights, such as the 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 it needs to have rights to enumerate Windows domain members.

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

Starting with Management Suite 8.6.1 there are two LANDesk COM+ applications: LANDesk and LANDesk1. The LANDesk COM+ application is used for System Manager and SDK features. The LANDesk1 COM+ application is used for network authentication (nested domain groups and multi-core support in the Web console).

To configure the LANDesk 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, double-click Component Services.
3. Click Component Services | Computers | My Computer | COM+ Applications.
4. From the LANDesk1 COM+ application's shortcut menu, click Properties. If you're configuring for System Manager or SDK features, do this from the LANDesk COM+ application.
5. On the Identity tab, enter the credentials you want to use.
6. Click OK.

Notes for Management Suite 8, version 8.6

Upgrade: After an upgrade, agent configuration tasks fail
The certificate in an agent configuration must match a certificate on the core server. After an upgrade, you can either move your certificates from the old core to the new core (this is normally done automatically during an upgrade), or you can open each agent configuration, and on the Standard LANDesk agent page select the certificate you want to include.

Upgrade: If setup fails and rolls back during an upgrade, you may be prompted for the original installation media the next time you rerun setup
If you attempt to do an 8.5 to 8.6 upgrade on an additional console that also is a Web console server or a rollup core, and that upgrade for some reason fails and rolls back, the next upgrade attempt may produce a dialog requesting the original install media. In order to get past this issue, browse to the LANDesk Software.msi on the 8.5 install media, and then the upgrade will continue.

Upgrade: When upgrading Management Suite on Windows 2003 Server, a Windows Installer dialog may flash continuously for about 30 seconds while uninstalling Crystal Reports
Ignore the flashing dialog. The upgrade and Crystal Reports uninstall will work correctly.

Upgrade: You can't upgrade directly from a standalone Management Suite core to a combination Management Suite/Server Manager core
If you are upgrading Management Suite and want to add Server Manager to a core, add it by rerunning setup after you've upgraded the core.

Upgade: When upgrading from version 8.x to 8.6, the core's LANDesk Management Agent service may not start after the first reboot
If the LANDesk Management Agent service doesn't start after you've upgraded and rebooted once, reboot again. This will fix the problem.

Upgrade: If you see empty tree items in the Configure | Alert settings dialog after upgrading a core server
If you see empty alert settings, you can delete them by removing *.atd files from the \WINNT\SYSTEM32\AMS_II folder on core server. Once you've done this, restart the Intel Alert Originator service.

Upgrade: Web console server upgrade fails if the original core server isn't available
When upgrading a Web console server, setup assumes the original core server name is correct and tries to use it. If a core server with that name isn't available, setup will fail and roll back. You can work around this error by running setup as follows, replacing <New core server name> with the name of your new core server:

\ldmain\Install\Media\Setup.exe /V"CORESERVER="<New core server name>" WEBCONSOLE_ONLY=1"

Upgrade: Uninstall Patch Manager 8.0 before upgrading Management Suite 8.01
When upgrading an LDMS 8.0.1 additional console, if Patch Manager 8.0 has been installed on the additional console, go to Add/Remove Programs and uninstall the Patch Manager product before upgrading the additional console. This doesn't need to be done for any other version of Management Suite, nor does it apply to a core, rollup core, or Web console upgrade.

Upgrade: Migrated version 8.5 delivery methods and distribution packages appear under the "Public" groups
Management Suite 8.5 didn't support delivery method and distribution package owners, which 8.6 does. Setup puts migrated items in the 8.6 Public groups.

Upgrade: Custom report migration information
Management Suite versions through 8.5 used Crystal Reports* for the reporting engine. Management Suite 8.6 uses a new reporting engine. When you upgrade, Management Suite converts any custom reports you've created. Management Suite does this by preserving the queries your custom reports are based on and applying them to the new report format. If you've customized the appearance of your custom reports, you'll need to reapply that customization in the new report format. Reports you've added under the My reports group with the Add reports option aren't migrated.

Setup: The prerequisite checker doesn't block core server installation on Windows 2003 Server x64 Editions
The prerequisite checker that runs during installation doesn't block installation of the core server on Windows 2003 x64 Editions, even though they aren't supported platforms. If the core server is installed on a Windows 2003 Server x64 Edition, it won't function properly.

Setup: Error message when you install a core or additional console on a computer that already has older Management Suite agents
If the computer you want to install to already pre-8.6 Management Suite agents on it, uninstall the agents first by using LDMain\uninstallwinclient.exe. You can reinstall the agents after installing the core server or additional console.

SWD: Batch type distributions get stuck in 'Active' when using a Pause command in the batch file
If commands are used which stop the progress of a batch file and can only be seen from the command prompt (e.g., Pause), the Batch type distribution will get stuck in the 'Active' state, because there is no visible command prompt for the user to act upon. Don't use commands that do this in batch file distributions.

Connection control manager: Accessing the Management Suite 8.5 connection control manager interface
Connection control manager was redesigned for Management Suite 8.6. This included some feature changes. If you want to use the version 8.5 connection control manager, add this registry key on each console:

HKLM\SOFTWARE\LANDesk\ManagementSuite\CCM\OriginalCCM.

Set it to 1 for the old UI, and 0 for the new UI. Restart the console to activate the change. Note that the documentation is only for the new UI. If you want to see the documentation for the old UI, refer to the Management Suite 8.5 User's Guide. If you don't have it, you can download it from the www.landesk.com support Web site.

Remote control: After using the Management Gateway remote control, normal remote control doesn't work
When you use the Management Gateway remote control, it stops the normal remote control service (the LANDesk Remote Control Service in the Windows Services application). Normal remote control won't work at this point until the managed device reboots or until you have the user manually start the LANDesk Remote Control Service from Control Panel. On Windows 9x, users need to run issuser.exe to start the remote control service.

Remote control: Screen may not redraw completely when remote controlling a Mac OS 9.2.2 computer
If the screen doesn't redraw completely, click Tools | Options in the viewer and set the performance level to medium or slow.

Remote control: When attempting to install remote control from the web console in a different subnet, the remote control viewer can't be installed
If you connect to a web console that's being hosted by a core in a different domain, and right-click a computer in the My devices list and click Remote control, you will get an error saying that the remote control viewer hasn’t been installed properly.

To solve this problem, get the URL for the CAB by reading the tag named "CabUrl" from web.config. The tag CabUrl must contain the core's fully-qualified domain name instead of just the machine name. You need to open web.config and put the fully-qualified domain name in the CabUrl tag.

LANDesk Trusted Access: Devices that have the LANDesk Trust Agent (LTA) installed, but are not included in a DHCP scope, still act as though they are being postured and quarantined
On such a device, the browser launches with the HTML page that shows the device as being quarantined, even though they have not actually been placed on the quarantine network. The best method for avoiding this is to only install the LTA on those devices that are included in a DHCP scope (defined in the LANDesk DHCP Manager tool), instead of installing LTA to all devices on the the network and attempting to roll out LANDesk DHCP trusted access one subnet at a time.

LANDesk Trusted Access: Renamed or deleted DHCP scopes (XML files) can be restored by certain DHCP server processes
It is recommended that you do NOT rename or delete scopes from the LANDesk DHCP Manager tool while the DHCP service is running. Deleted scopes (saved as XML files on the DHCP server) can be restored by certain processes, such as the backup process.

LANDesk Trusted Access: With the LANDesk DHCP solution, you might experience out of sync device IP addresses on the core if the core is visible to the quarantine network
The recommended configuration for a trusted access network (specifically noted in the Users Guide and online help) is for your core server to NOT be visible to the quarantine network. If it is, you might see IP address discrepancies on the core as devices go from quarantine or unhealthy status to healthy status during the posture validation and remediation process. Again, your core server should not be visible to the quarantine network. However, if you need to resolve this IP address issue, you can configure a device with an agent configuration that automatically runs the security scanner when its IP address changes (enable the IP address change option on the Security and patch scan page of the Agent configuration dialog).

LANDesk Trusted Access: Workaround for the LANDesk Trust Agent (LTA) not being able to install on an NT4 device
The HowToInstallLDDHCP.html page (hosted on the core server and published to the remediation server) includes a link that lets the end user install the LANDesk Trust Agent on their device. However, this application doesn't work on NT4 devices. An error message displays: "Missing function in ADVSYS.DLL." As a workaround in order to successfully install the LTA on an NT4 device, copy the lta.msi file (from the core server's Install\TrustedAccess\LDDHCP\LTA folder) to the remediation server, and then run lta.msi on the NT4 device. This should install the LTA on the device.

LANDesk Trusted Access: Need to download some type of security content type before you can use ONLY custom definitions and patches for compliance scanning
If you wanted to use ONLY custom definitions and patches for compliance scanning and remediation with trusted access, you need to first download any type of downloadable security content definitions (such as vulnerabilities, spyware, etc.) in order for the vulnerability scanner to function properly. (The reason is because there aren't any platform or language definitions downloaded yet.) As a workaround, you can download any type's definitions and then purge them with the Purge feature. Then, you can add custom definitions to the Compliance group in order to define your compliance security policy, and the vulnerability scanner will successfully scan and remediate.

Web console: Queries that take more than 20 minutes to resolve won't return more than one page of results
By default, Web console sessions timeout after 20 minutes. If you run queries that take longer than this to resolve, increase the session timeout. Edit \inetpub\wwwroot\remote\Web.config. Change the sessionState timeout attribute to a longer interval, restart IIS, and run the query again.

Remote control: Certificate-based remote control fails if the user logged into the core server isn't in the LANDesk Management Suite group
If you're using certificate-based remote control from the core server, make sure you log into Windows with a user that's in the LANDesk Management Suite group.

Intel AMT Boot Manager may not work if unmanaged device discovery retrieves incorrect DNS information
If the IP address assigned to an Intel AMT device has changed but the DNS information about that device has not been updated, unmanaged device discovery will return the incorrect machine name for the device. If this happens and the device is moved to the list of managed devices, the AMT boot manager will report incorrect information. It may show the device as being powered off even if it is powered on, and boot manager features (such as rebooting) may not function properly. If this occurs, your network's DNS information needs to be updated for the device and the device needs to be discovered again for this issue to be resolved.

Rollup: Database rollup won't work from a core that's only licensed for Server Manger
Any core that you want to roll up must be licensed for both Server Manager and Management Suite.

Application healing: Application healing alerts are still visible on an upgraded core server
Application healing was removed from Management Suite 8.6. If you upgrade a core server to 8.6, the application healing alert group and alerts still appear in Configure | Alert settings. You can ignore this group.

Management Gateway: The core is able to post a certificate to the Management Gateway, and the "Test settings" button returns a "Settings test successful" response, but managed devices are unable to connect to the core though the Management Gateway
This can occur if the core is configured to connect to the Management Gateway through a proxy, but you did not specify proxy settings from the Management Gateway configuration dialog. If you have specified proxy settings for Microsoft Internet Explorer, the Test settings button and the Post to Gateway button in the Management Gateway configuration dialog will use those settings and will succeed, but the Management Gateway service will not use them and will fail to connect. The BrokerService.log file may state that the Gateway service was unable to connect to the Management Gateway IP address or that the configuration was not found. If you encounter this problem,

1. From the console on the core server, click Configuration | Management Gateway.
2. On the Gateway information tab, check Use proxy and specify the same proxy settings that you have specified for Internet Explorer.
3. Click Test settings to test the core server connection to the Gateway.
4. If the test fails, check the information you entered and correct any mistakes, then click Test settings to make sure the connection works.
5. Click OK.

Notes for Management Suite 8, version 8.5

Setup: Don't install agents from one core server onto another core server
Installing Management Suite agents configured from one core server onto a different core server prevents the LANDesk configure services utility from working correctly, among other things. You can install agents on the core server as long as they were configured from the same core server.

Setup: Don't install Management Suite through terminal services
The Management Suite autorun won't launch in a terminal services session. Instead, install Management Suite directly on the server.

Setup: If you cancel setup, the Windows users and groups setup may have created could be left behind
When setup is interrupted and does a rollback, it won't remove any Windows users and groups that it created. You can delete these manually.

Setup: Don't install the Management Suite components on a drive that isn't using the NTFS file system
You must install the core, web console, and rollup core on a drive that's formatted with the NTFS file system.

Setup: When installing a core server, don't point to the rollup database during setup
If you do this, setup will overwrite all rollup data and use that database for the core server.

Setup: Setup reports error 1317 during install
If you see this error, setup needs more disk space. Free more space, even if you have more space than setup said it needed for the components you selected.

Setup: Product activation fails on a Windows 2003 Server
In some cases, product activation on Windows 2003 Server fails while creating the XML activation file. If this happens, run the following commands while logged in as administrator or an equivalent, and rerun product activation.

C:\Windows\System32\wbem\mofcomp cimwin32.mof

C:\Windows\System32\wbem\mofcomp cimwin32.mfl

Setup: Recovering from a canceled or failed core server installation with an Oracle or SQL Server database
Follow these steps to reinstall a core when setup failed, was canceled, or for whatever reason rolled back.

1. After rollback on a non-SQL Express core install, reset the database.
2. During install, DON'T choose the option to use a previous database. You must choose the option to use a new Oracle or SQL2000 database.
3. At the create reports user dialog, choose NOT TO because it was created previous to the rollback and setup won't recreate the user.
4. After the install complete and reboots, rerun setup and select the repair option.

Setup: Reusing an existing SQL Express database
You can reuse an existing database during setup. In setup's Choose a database page, select user-supplied database. Enter the database information. The default SQL Express database information is as follows:

• Server: <servername>\ldmsdata
• Database: lddb
• User: sa
• Password: The password you entered during the original setup.

You can check the SQL Express configuration information in: HKEY_LOCAL_MACHINE\SOFTWARE\LANDesk\ManagementSuite\Core\Connections\Local

Activation: An upgraded core server that runs Symantec Antivirus won't activate
If your core server runs Symantec Antivirus, you've upgraded a 7.0 core server to Management Suite 8.5, and your activation credentials don't work, you may have to reset the core server's device ID. Follow these steps in exactly the order listed:

1. Delete C:\LDISCAN.CFG.
2. Stop the Intel PDS service in Control Panel's Services applet. This will also stop several other services.
3. Run Regedit, and delete these keys: HKLM\Software\Intel\LANDesk\Common Api, and HKLM\Software\LANDesk\Common Api.
4. Open Symantec Antivirus and click File | Unload service.
5. Reboot.
6. In the server's CMOS setup, disable the CPU serial number option.
7. Once your server finishes booting, restart the Symantec Antivirus service by opening Symantec Antivirus and clicking File | Load service.
8. Activate your core server.

Upgrade: When upgrading from 8.x to 8.5 and setup doesn't finish
If Management Suite 8.5 setup doesn't finish because of a problem, or if you cancel setup, your Management Suite 8.0 or 8.1 installation may not work after setup rolls back any changes it made. If this happens, uninstall Management Suite 8.0 or 8.1 and then reinstall 8.0 or 8.1, reusing your existing database.

Upgrade: When upgrading from 8.0, uninstall Crystal Reports first
When upgrading from 8.0, setup doesn't uninstall Crystal Reports automatically. When the newer Crystal Reports version in 8.5 installs over the old version, reports won't work correctly. Uninstall Crystal Reports before upgrading by going to Control Panel's Add/Remove Programs applet and removing CrystalSetup_<language>.

Upgrade: Uninstall any Management Suite 7.0 web console servers before upgrading any components on those servers to 8.5.
If you don't uninstall the dedicated Management Suite 7.0 web console first, Management Suite 8.5 setup may leave some 7.0 files behind.

Upgrade: Custom OSD PXE Boot Menu messages aren't preserved when you upgrade from Management Suite 8.0 or 8.1 to 8.5
If you have a custom OSD PXE Boot Menu message, save it somewhere before upgrading so you can manually restore it later.

Upgrade: Legacy distribution scripts won't automatically be converted to 8.5 delivery methods/distribution packages
Any legacy distribution scripts on an upgraded core server will remain individual distribution scripts. They won't use the new distribution scripts/delivery methods feature. The scripts will still work and you can see them in Tools | Manage scripts.

Upgrade: Securely back up your core server certificates before upgrading or repairing a Management Suite installation
You should back up the contents of your core server's Keys folder in a safe, secure place. If for some reason you need to reinstall or replace your core server, you won't be able to manage that core server's devices until you add the original core's certificates to the new core. Follow these steps to back up the core server's certificates:

1. At the source core server, go to the \Program Files\LANDesk\Shared Files\Keys folder.
2. Copy the source server's <keyname>.key, <keyname>.crt, and <hash>.0 files to a floppy disk or other secure place.

Upgrade: When an additional console setup is rolled back, after a reinstall the console won't launch
Attempting to launch the console in this scenario can cause a message to appear that Windows is repairing the application. If the console won't launch, rerun setup, this time repairing the existing installation. The console will launch after doing this.

Combined Server Manager and Management Suite core server system requirements
If you have both of these products on one server, the server needs at least 1 GB of RAM for good performance.

Upgrade: When upgrading from Management Suite 6.62 or 7.0, Inventory History data (Configure | Inventory History) isn't migrated
You'll need to reconfigure inventory history data in Management Suite 8.5.

Distribution: Files that you want to distribute from a web share mustn't have the hidden attribute set
If a file on a web share is marked as hidden, it won't appear in any distribution dialogs. Also, if you distribute a folder and that folder contains hidden files, the distribution will fail.

Distribution: Disable the IIS "Enable Default Document" option on distribution package shares
Having this option enabled can cause a phantom file to be part of a package if you're distributing an entire folder. This phantom file will cause the distribution to fail.

Distribution: Files with a .map extension can't be downloaded in some IIS configurations
If you create a package that includes files with a .map extension, the distribution may fail because the web server may not allow access to files with that extension. This problem occurs with Microsoft Office distribution packages that include the entire Office folder's contents. In the case of Office, you can remove the *.map file from the package's additional files list and Office will still install correctly.

Distribution: The Distribution package properties Detection page only affects dependent packages
Use the detection page to detect dependent packages or applications that weren't installed through Management Suite. A match on one or more criteria you specify prevents dependent packages from installing. This page doesn't affect the primary package.

Distribution: Deploying a batch file or program that reboots the device results in an "Unknown status code" value
If the executable or batch file that you're running reboots the device, software distribution may not be able to get status back to the console, especially if the executable doesn't allow applications to close gracefully before shutting down the device. The preferred way to reboot a device in a batch file is to run "sdclient /reboot".

Distribution: Selecting the "Use multicast domain discovery and save results" option still causes a domain discovery on subsequent multicasts
If the Use cached file option is checked on the Configure | Services application's Multicast tab, it is assumed that the user wants to use a multicast domain representative that has the file. The mechanism for determining the multicast domain representative that has the most of the file is domain discovery, so software distribution does the discovery in all cases if that discovery option is selected.

Distribution: Packages with a long additional files list take a long time to download
Each additional file in a distribution package takes several seconds start downloading. If you have thousands of additional files, this can make the distribution take a long time, even if the additional files are small. You have the software distribution agent download the files at full speed by configuring the distribution job as follows:

• The primary file must be an MSI format
• The primary file isn't in the local cache
• The files are hosted on a UNC path
• The distribution isn't bandwidth limited. Distributions are bandwidth-limited if you specify any of these options:
  Delivery method Bandwidth page: Limit remote downloads (per subnet) to one device at a time is checked.
  Delivery method Download page: Peer download is checked, Delay between packets when downloading from the source is a number other than 0, Dynamic bandwidth throttling is checked.

Distribution: On Windows 2003 server package web shares, make sure you add MIME types for .INI and other file types that the web server won't allow access to for security reasons
The default Windows 2003 security level prevents web browser access to file types that aren't normally used while browsing. Some of these blocked file types, such as .INI, prevent software distribution from working correctly. The core server installation adds MIME types for the file types Management Suite needs. You need to configure the MIME types manually for .INI files on rollup core and non-core Windows 2003 web servers.

Distribution: Some additional files with double-byte file names get removed from the distribution package file list when you reopen it
The software distribution additional files list automatically removes redundant files. In some SQL configurations, SQL will incorrectly consider double-byte filenames that are named differently to have the same name, so the additional files list removes the file. If this happens, you can work around the issue by putting the incorrectly removed files in a separate folder, and then re-adding them to the additional file list.

Distribution: Configuring a preferred package server
You can specify the default server that devices will check for software distribution packages. This can be important in low-speed WAN environments where you don't want devices downloading packages from off-site servers. To set the preferred package server, add this registry key to managed devices and set its value to the preferred package server name:

HKEY_LOCAL_MACHINE\Software\LANDesk\ManagementSuite\WinClinet\SoftwareDistribution\PreferredPackageServer

Before a package file (either primary file or an additional files) is downloaded remotely, this registry key is checked, and if the file is present on the preferred server, the agent will download it from there. If the file isn't on the preferred server, it will be downloaded from the location specified in the distribution package.

Remote control: Disabling the remote control mirror driver
If you don't want to use the remote control mirror driver on managed devices, you can disable it in future agent deployments by editing the appropriate agent configuration INI file in the LDLogon folder. Delete the line referencing setupmirror.exe. This prevents the mirror driver from being installed. You can also uninstall the mirror driver by running setupmirror /u. The setupmirror.exe program is in the C:\Program Files\LANDesk\LDClient folder by default.

Remote control: The web console uses the new remote control viewer
Management Suite 8.5 ships with two remote control viewers. The old viewer, IRCCNTR.EXE, shipped with versions prior to 8.5. The new viewer, ISSCNTR.EXE, started shipping with version 8.5. The web console only launches the new viewer. You'll also need to use the old viewer with Management Suite 8.1 and earlier device agents. You can launch both viewers from your Management Suite installation folder. The Windows console automatically launches the correct viewer.

Database: Inventory scan files containing extended characters don't get scanned into an Oracle database:
If you're an Oracle user not using the WE8MSWIN252 (English+extended characters) character set:
If you get an ORA-01401 error in your event log stating that the column isn't large enough for the specified data, you will need to change every CHAR column in the "problem" table to VARCHAR2. Doing so will allow the scan file to go in, assuming that the data doesn't truly exceed the size of the column. The Application Event Log will tell you which table to modify.

Web: In web console software distribution, UNC path browsing won't work unless the guest account is enabled on the target server
When you browse for files to add to a distribution package, the web console authenticates with the target server using the guest account. If that account isn't enabled, nothing will happen when you click the browse button.

Web: Web console features don't work or stop working after an upgrade or applying Windows updates
Whenever IIS components are changed after the .NET framework was originally installed, run the following command:

aspnet_regiis /i

The aspnet_regiis application is usually found in C:\Windows\Microsoft.NET\Framework\<Version>.

Console: Query editor doesn't use the SQL standard wildcard character (%)
In the Windows console, use an asterisk (*) as the query wildcard character. The percent (%) wildcard character will work in the web console.

Inventory: Scanning SMBIOS data
The inventory scanner scans SMBIOS data when it's available. If the scanner returns SMBIOS strings that aren't informative or that you don't want to see in the inventory data, edit the LDAPPL3.TEMPLATE file in the LDLogon folder. Add the strings you want ignored to the [SMBIOS Ignore] section.

Inventory: A core server in a VMWare session rejects its own inventory scan file
If you are running the core server inside VMware, you will need to manually increase the size of the SerialNum column in the CompSystem table. It is currently set as a CHAR(60). Our internal testing shows that a CHAR(90) (or VARCHAR) should be sufficient.

Inventory: The inventory extender (developed by Jan) isn't supported by Management Suite 8.5
You can't install the inventory extender on Management Suite 8.5. The inventory extender isn't necessary with this release, since the extender attributes are now part of it.

SLM: Software license monitoring may show outdated device information
If you add, delete, or modify devices in a scope that's based on device groups, those changes won't show in software license monitoring until you relogin to the console or manually refresh the software license monitoring group properties. For example, if you delete a device from a scope, running a report immediately after the deletion on a product using that scope will still show the deleted device. You can manually refresh the device data by clicking Properties from a compliance group's shortcut menu. On the Devices tab, click Resolve.

Reports: Chinese characters appear in the Japanese Vulnerability Threat Overview report
This is an issue caused by the Crystal Reports engine. LANDesk software is working with the Crystal Reports developers on a fix for this.

Reports: Upgraded core server generates an error when you to to publish a report
During an upgrade to 8.5, the Crystal Reports component may not update all the files it needs to. To fix this problem:

1. Uninstall CrystalSetup_<lang> from Add/Remove programs. <lang>: CHS, DEU, ENU, ESP, FRA, JPN
2. Reboot.
3. Run CrystalSetup_<lang> from the LANDesk folder in the Management Suite 8.5 installation image.
4. Accept all defaults except where it asks whether or not this install is for "everyone" or "just me". Choose Everyone if someone else will logs into a console.

File replicator: The file replicator fails to copy some files
If the file replicator log shows that it failed to copy some files, first try getting the file from a browser on the computer that's running the replicator. If you can't get to the file with a browser, the file replicator won't be able to get to it either. Some web servers prevent access to files they don't have MIME types defined for. If it's files with certain extensions that fail, create a MIME type for those extensions. In IIS, you can add MIME types by doing the following:

1. On the web server, launch Internet Services Manager.
2. Navigate to the web site or folder holding the files you want to replicate, and from that folder's shortcut menu, click Properties.
3. Click the HTTP Headers tab and click File Types.
4. Click New Type and enter the file extensions and content types you need.
5. Restart the web site.

Connection control manager: Before applying a new connection control configuration to devices, uninstall any old configurations
In some situations, installing a new connection control configuration over an existing configuration may prevent the new configuration from being applied. You can create an uninstall configuration task by clicking Schedule uninstall from the configuration's shortcut menu in the Connection control manager window.

Connection control manager: If the core server isn't available on a listed network, in some situations clients will have unrestricted I/O device access while on that network
If you select the following options in connection control manager, and the core server isn't available on a listed network, clients will have unrestricted I/O device access while on that network.

• Limit connections to listed networks
• Allow unlisted networks if not connected
• Enable devices while on unlisted networks
• Verify core server existence on the network

Since "Allow unlisted networks if not connected" is checked, if the agent can't find the core on a listed network, it will assume that the network is unlisted. At this point, the "Enable devices while on unlisted networks" option activates, enabling all local I/O device access. This can create a security risk. Make sure the core server is available to prevent this from happening.

Linux: Inventory scanner doesn't run automatically after installation
After you install the inventory scanner, run it manually with this command:

ldiscan -ntt=<Core host name>

Notes for Management Suite 8, version 8.1

Setup: The core server name must only use ASCII characters
Core server activation and some portions of Management Suite won't work correctly if your core server name includes non-ASCII or double-byte characters.

Setup: Don't install a rollup core server on an existing Web console server
If you want a rollup core server on an existing Web console server, uninstall the Web console first. You can install the rollup core server and Web console server at the same time.

Setup: Uninstall Management Suite add-ons before uninstalling Management Suite
If you're uninstalling Management Suite, uninstall all add-ons first.

Activation: The core server activation Contact Name and Password are case-sensitive
When using the Core Server Activation utility, be aware that the Contact Name and Password are case-sensitive.

Activation: On the activation utility's Proxy tab, using a server name with invalid characters may generate an unhandled exception
When specifying the proxy server name, don't include invalid server name characters like "="  or "@".

Activation: Restart the LANDesk Inventory Server service after reactivating a delinquent core
When a core server goes too long without contacting the LANDesk Software licensing server or if it goes beyond the evaluation period, the Inventory service on the core server stops accepting inventory scans. When you reactivate a core that has been deactivated because of delinquency, restart the LANDesk Inventory Server service to restore it to normal operation.

Activation: Deactivating a core
If you need to deactivate a core to release licenses or for another reason, contact your LANDesk sales representative.

Upgrade: Management Suite 8.1 scripts that use a REMCOPY command with a filename containing non-English characters won't run correctly on Management Suite 8.0.1 or older clients
Management Suite 8.1 includes enhanced client agent support for non-English characters. If a Management Suite custom script includes a REMCOPY command that refers to a filename containing non-English characters, the script won't execute correctly on clients that aren't running the Management Suite 8.1 agents.
If clients can't be readily upgraded to Management Suite 8.1, the REMCOPY command can be replaced with a REMEXEC command to sdclient using the /f (for file download) option. Details on the sdclient command line can be found in Appendix C of the User's Guide.

Upgrade: If you installed the Server Management feature from Management 6.62 or 7.0 on any servers, remove it before upgrading the servers to Management Suite 8 clients
The Server Management feature from Management Suite 6.62 and 7.0 has been replaced by LANDesk Server Manager, and it doesn't coexist with the new Management Suite 8 agents.

Upgrade: The PXE Rep Removal script won't run on Windows NT 4 computers
Uninstall PXE Representatives manually on Windows NT 4 computers by using Control Panel's Add/Remove Programs feature and selecting the PXE Representative entry.

Upgrade: Upgrading a Management Suite 6.62 or 7 core server with a DataMart on it won't uninstall the DataMart
When upgrading a core server with a DataMart, do the upgrade to 8.5, and once it finishes use Control Panel's Add/Remove Programs applet to uninstall the DataMart.

Upgrade: Upgrading a Management Suite 7 additional console may cause an error message to appear that interrupts the install until you acknowledge it
While upgrading an additional console, the console setup program uninstalls the previous console version. An error message may appear, saying "Unable to query the status for service Intel AOL Health. You may need to start or stop the service manually." You can click OK on this message and the upgrade will continue properly.

Upgrade: Upgrading a Management Suite 7 Web console server to 8.5 first uninstalls the existing Web console server
When upgrading a Management Suite 7 Web console server, Setup displays a dialog saying "The following products are installed: LANDesk Management Suite 7. Uninstall these products?" Click Yes in this dialog for the upgrade to proceed.

Upgrade: Migrated queries from Management Suite 7 aren't visible in the Web console when accessing the migrated version 8 core
If you exported Management Suite 7 queries prior to migrating a core server, the migration utility will copy the queries to the \ManagementSuite\LegacyQueryFiles folder. To see the queries in the migrated core's Web console, copy them to the  \Inetpub\wwwroot\remote\queries folder.

OSD: Clients appear to hang after rebooting to begin image capture/restore
This can happen when the client fails to fully authenticate with the imaging server, usually because the DOS "net logon" command is trying to authenticate to a domain with an account that isn't local on the client. The DOS "net logon" command needs to use a local account that has rights to the imaging server share in order to connect to an imaging server that's part of a domain.

OSD: When clients attempt to execute an OSD DOS job, you see one of these error messages: "File is fragmented" or "Invalid system disk"
This can happen if clients are using Management Suite agent versions that are older than those that come with Management Suite 8.1. If you see this message, upgrade the clients with the latest Management Suite agents.

Console: Don't use quotes around Local Scheduler script parameters
When configuring a Local Scheduler script, don't use quotes in the Command or Parameters fields. If you use quotes, the command line won't parse correctly.

Web console: you can't log in to a rollup core until a database has been rolled up to it
Before you can log in to a rollup core or create a rollup schedule for a core, you must first roll up a database to the rollup core. This is also true if you've reset the rollup database. This means when you first run the Rollup Utility, you can choose the "Schedule" option to send a rollup task to the rollup core that's visible from the Web console, but you won't be able to log into the rollup core via the web console to schedule the rollup task. First, select the core in the Rollup Utility and click Rollup.

Web console: Can't change the credentials the Web console uses to authenticate with the core server
If the current user is a valid user on the core server, Internet Explorer automatically uses those credentials to authenticate to the core server. If you want to use different credentials, follow these steps:

1. Click Tools | Internet Options, and click the Security tab.
2. Click Custom Level.
3. Scroll to the bottom of the list, then select Prompt for user name and password.
4. Click OK to exit the dialogs.

Web console: An ASP.NET error appears when you log in to the Web console
If you see an ASP.NET error message when attempting to log in to the Web console, ASP and the ASP.NET directory permissions may not be configured correctly. Reset the ASP configuration by running the following command:

ASPNET_REGIIS.EXE -i

Web console: If you change the database a core server points to, you need to update the Web console to point to it also
When you change the database a core server points to using Configure | Services, the Web console will still point to the original database it was configured to use. Edit the Web console's core.asp file to point to the new database. See the Web console help for more information.

Reports: Entering an invalid date range in a report may generate an exception
If you enter a negative value for a report date range, the console may generate an exception.

Remote control: If you have problems remote controlling a client, make sure it has the latest remote control agent on it
The version 8 remote control agent includes support for large DIBs, often used by .NET applications. Prior versions of the remote control agent don't support large DIBs, generating an error during remote control. Note that upgrading an existing additional console to Management Suite 8.5 won't upgrade any client agents (including remote control) you may have installed on that computer.

SWD: MSI-format Office distributions to Windows 98 and Windows NT clients may fail with a non-descriptive error
Windows 98 and Windows NT clients may be missing some components that the Office MSI install expects them to have. The multi-file MSI install for Office XP won't install these components automatically and the distribution will fail on clients lacking these components.

SLM: Importing software license data from XML files
Software License Monitoring can import license data from XML files. If you have license data in an Excel spreadsheet, for example, you can reformat it to match what Software License Monitoring's import feature expects and save it in XML format. The import feature expects an XML file format. When creating this file in Excel, add these headings in this order in row 1, one heading per column. Don't skip any headings.

Product Group, Product Vendor, Product Title, License Number, Product License Type, Quantity, Serial Number, Purchase Date, Unit Price, Order Number, Reseller, Owner, Location, Notes

Complete the information under each column. If you don't have data for a particular column, leave it empty. Each column can contain up to 255 characters of text, except for these special columns:

• "Product License Type" must have one of these values: Unknown, NewPurchase, ProductUpgrade, CompetitiveUpgrade, Shareware, Freeware, PublicDomain, OEM
• "Quantity" is an integer value, 0 or greater.
• "Purchase Date" is a date field.

After saving your Excel spreadsheet in XML format, click the Import XML License File button on the Software License Monitoring window's toolbar. Browse for your XML file and click Open.

Notes for Management Suite 8, version 8.0

Setup: Follow these directions to install ASP .NET on Windows 2003 servers
In Control Panel, double-click Add/Remove Programs. Click Add/Remove Windows Components, then check the Application Server option. Click Details and make sure ASP.NET is selected. Click OK to exit.

Setup: Management Setup's restart my computer option doesn't restart the computer
If after finishing Setup you select the Yes I want to restart my computer option and the computer doesn't restart, shut down and reboot the computer manually.

Setup: Management Suite prerequisite checker fails to find ASP .NET even though it's installed
If you've installed ASP .NET and the prerequisite checker isn't detecting it, run this command: ASPNET_REGIIS.EXE -i. The prerequisite checker should then detect ASP .NET correctly.

Setup: You must shut down all open applications when installing on Windows 2003 Server
When installing Management Suite to a Windows 2003 Server operating system, you must shut down all applications before running Setup, and during Setup make sure no additional processes or users are causing high processor utilization. Setup may hang otherwise and leave a partial installation on the server.

Setup: The core and console must be installed together
Setup won't allow you to install the core without the console.

Setup: Windows 9x clients must have Winsock 2
LANDesk Management Suite 8's certificate-based authentication requires Winsock 2. Windows 9x clients without Winsock 2 don't handle certificates correctly and won't be able to communicate with the core server. The client configuration will install without reporting an error but it won't work.

Setup: Changing the core server name requires a full reinstall of the core server and all clients
We strongly recommend you not change the core server name after installing Management Suite.

Setup: For the Web console to install correctly, verify that the Inetpub folder has the "allow inheritance permissions from parent to propagate to this object" option checked.
If this option isn't checked on the Inetpub folder's Security property tab, the "remote" folder that Setup creates for the Web console won't have any allowed permissions.

Setup: After Management Suite Setup finishes, logging out and back in instead of rebooting will cause the installation to fail
Make sure you reboot when Setup finishes or your Management Suite installation won't work.

Setup: If you install Management Suite, System Manager, or Server Manager agents to the core server, don't uninstall them
Uninstalling any of these agents from the core server prevents some services from loading that the core requires.

Setup: "Reboot if necessary" is now the default reboot option in the prebuilt default client configuration
The prebuilt default client configuration will reboot now clients when the configuration finishes. This ensures the agents load correctly.

Setup: Entering an invalid character for a certificate's organization or name during Setup generates an error
The certificate organization and name need to follow Windows file naming conventions. If you enter an illegal character, see the error, and then go back to fix it, you will need to enter a different organization name and not just remove the illegal characters.

Setup: If clients can't see the LDLogon share folder contents, enable the share's directory browsing privilege
Normally, setup turns on directory browsing for LDLogon automatically.

Setup: If you see a script failure error when installing on Windows Server 2003
If ASP is running and the install fails, open a command prompt, and from the LDMS directory rerun Setup with this command line: setup.exe /z"IgnoreAspExt".

SWD: When deploying MSI packages, don't specify the /qb- (run silently) option in the distribution script wizard
SWD installs MSI packages silently if you select the Hide all feedback from user option. If you manually specify the /qb- option on the MSI command line in addition to selecting this option, the job will fail.

SWD: Multisession download requires IE 5.5 or greater
For SWD's multisession download support to work (where interrupted downloads resume where they left off), clients must have IE 5.5 or greater installed. The distribution script must also use an option that first downloads files to the client cache, such as the peer download or dynamic bandwidth throttling options.

OSD: Understanding the 'Invalid parameters(1)' error message when using the LANDesk imaging tool
If you are using the LANDesk imaging tool and the image job fails and displays the 'Invalid parameters(1)' error message in the console's Scheduled Tasks Result column, it can indicate either an invalid parameter on the tool's command line, OR insufficient disk space.

OSD: You must specify multicast domain representatives in the network view before doing multicast OS deployments
Multicast OS deployments may fail if you don't specify domain representatives for each multicast domain in the consoles Multicast Domain Representatives group.

OSD: Required user rights for removing devices from the PXE Holding Queue group
Users must have the OSD right to add devices to the PXE Holding Queue group, and OSD and Unmanaged Device Discovery (UDD) rights to remove devices from the PXE Holding Queue group or the Multicast Domain Representatives group.

OSD: You must manually install MSI 2.0 on Windows NT 4 computers that you want to be PXE proxies
Before deploying the PXE proxy to a Windows NT 4 computer, install MSI 2.0, otherwise the Scheduled Tasks window will show an error when you try to deploy the proxy.

Remote Control: On-demand remote control from the Web console requires Internet Explorer 6
The new on-demand remote control security model requires Internet Explorer  6 if you are doing remote control from a Web console.

Remote control: Launching the Remote Control Viewer in standalone mode can bypass role-based administration scope and security
Unless you use the new on-demand remote control security option (certificate-based/local template), the Remote Control Viewer will allow users to remote control any computer if they enter a target computer name or IP address inside the Viewer.

R"System.OutofMemoryException."eports: Running many large reports eventually returns a
The Crystal Reports* report engine that Management Suite uses doesn't always release memory when generating large reports. You can reclaim the memory by exiting and restarting the console.

Database: Additional consoles accessing Oracle databases must have the Oracle client driver on them
If the additional console will be accessing an Oracle 8i database, install the Oracle 8i client driver and apply the Oracle OLEDB 8.1.7.3 update. In the update program, you only need to select the OLEDB option.
For Oracle 9i, the Oracle 9i runtime client won't install all of the components Management Suite needs. Install the client by running the main Oracle setup.exe and choosing the Custom installation, then install the Oracle Windows Interfaces 9.2.0.1.0 component.

Database: Oracle 8.1.x client driver installation fails on Pentium 4 computers
You can fix this Oracle issue by doing the following:
1. Create a temporary directory on your computer.
2. Copy the Oracle REBMS Server CD to the temporary directory you created in step 1.
3. Search the temporary directory for this file: symcjit.dll.
4. Rename all instances of symcjit.dll to symcjit.old.
5. Run setup.exe from \install\win32 to install the client.

Database: Use the native language database version for the language of Management Suite you're using
Using a database version that isn't localized for the Management Suite language you are installing to may cause unpredictable results, especially if you are trying to use the Chinese or Japanese version of Management Suite with a non-Chinese or Japanese database version.

Database: In the database Rollup Utility, clicking Help button can generate an error depending how the rollup core was installed
If you install the Web console on a server, then later on add the Rollup Core to that same server, clicking Help in the Rollup Utility generates a runtime error.

Inventory: Windows 9x and Windows NT clients must have Microsoft's Active Directory Extensions installed for the scanner to retrieve Active Directory client locations
They can be installed from microsoft's site:
Windows 9x - http://www.microsoft.com/windows2000/server/evaluation/news/bulletins/adextension.asp
Windows NT - http://www.microsoft.com/ntworkstation/downloads/Other/adclient.asp
The inventory scanner doesn't retrieve Novell eDirectory locations for Windows NT 4 and Windows 9x clients.

Upgrade: An Oracle 8i database upgrade using an Oracle 8i client may prevent some BLOBs from upgrading properly
When upgrading an LDMS 6.62/7.0 database using the Oracle 8i client, some BLOBs may not upgrade properly.  Specifically, the LDBIOS.TXT files. If you upgrade to the Oracle 9i client, and point that client to the 8i database, the BLOBs will transfer correctly. Otherwise, the BLOBs will be updated correctly when the first full scan for that computer comes through.

Upgrade: Pending scheduled client setup tasks from earlier LDMS versions will fail after upgrading to LDMS 8
Upgrade doesn't import client configurations (due to changes in configurations). Attempting to start a scheduled task that references a client configuration, the task fails with an error.

Upgrade: When upgrading to Management Suite 8, remove the Software Metering Client from your managed clients
If you are upgrading your core server to Management Suite 8, you should uninstall LANDesk Software Metering from any of your managed clients that currently have it installed in order to avoid memory usage problems. You can uninstall metering on clients by deploying the default Uninstall Metering Client script found in the All Other Scripts group in the Manage Scripts tool. Do this either before upgrading your core server or shortly after. Metering is no longer supported with Management Suite 8.

Upgrade: After upgrading, ignore the 'Result' status and redeploy the PXE Representative on your PXE proxies
When upgrading, PXE proxy data is migrated with the database, including the 'Result' status message. However, the Deploy PXE Representative script must still be redeployed on all PXE proxies in order to update the proxies to the new core server, even if the 'Result' status message says "Successfully completed installation of package'.

Upgrade: After upgrading PXE Representatives on some machines, Scheduled Tasks may report a 'failed' message
After upgrading to Management Suite 8, when you redeploy the PXE Representative on Windows NT and Windows 2000 machines, Scheduled Tasks might report a 'failed' message. The Deploy PXE Representative script forces the machine to reboot, and then attempts to run an inventory scan. The PXE deployment process is successful, but the inventory scan process fails which generates the message. You can ignore this message since the PXE Representative update completed successfully.

Upgrade: AMS alert actions list is empty after upgrading to Management Suite 8
In some cases the AMS alert actions list is empty after upgrading to Management Suite 8. When a core server or additional console gets into this state, you can fix it with the following procedure:
1. From Control Panel's Services applet, stop the "Intel PDS" service to stop the main Management Suite services.
2. Close any console(s) on the affected computer.
3. Find InstAms.exe
4. If the affected computer is the core server, run this command:
InstAms.exe CORE
5. if the affected computer is an additional console, run this command:
InstAms.exe CONSOLE
6. Restart the "Intel PDS" service or reboot.

Upgrade: After upgrading a Management Suite 7 core to Management Suite 8, version 7 additional consoles can still connect to the core
Once you upgrade a core from version 7 to version 8, don't use the version 7 additional consoles to connect to the version 8 core. This isn't supported and the results will be unpredictable. You must upgrade any version 7 additional consoles that access version 8 core servers.

Console: The console doesn't always refresh the window when moving between tools and the network view
In some cases the console won't refresh network view groups after something you do in a tool updates a group. Press F5 to refresh a view if you aren't seeing what you expected.

Console: Can't log in to an additional console if you previously connected to the core as another user
If you map a drive to the core server as one user, disconnect, then try to log in to the Management Suite console as another user, you'll see an error 1219. You must log out and back in to resolve this situation.

Console: Additional consoles must be able to resolve the core and database server names
You won't be able to log in to a core if the computer you're on can't resolve the core's computer name or the database server's computer name. If you don't have enterprise-wide DNS or WINS support, add a local LMHOSTS file entries for these servers.

Console: Only core server administrators can set a client configuration as the default
When using an additional console, you must be logged in to the core server with administrator privileges to be able to set a client configuration as the default.

Console: When configuring NetWare servers, only run AddNetWareSC.exe from the core server, not additional consoles
If you run AddNetWareSC.exe from an additional console, it generates an error.

NetWare: Deploying agents to a NetWare server fails with an error
When deploying agents to a NetWare server (Configure | Deploy LDMS client to NetWare server), you may see an error message that says "Setup was unable to complete the requested changes." If this happens, copy icpqmon.txt and icpqsys.txt from the core server's LDLogon share to LDLogon\\Netware\ManagementSuite\.

Web: Changing the Web console server name prevents the Web console from working correctly
The Web console uses the IUSER/IWAM accounts on Web console server. These accounts are originally created based on the computer name. If you change your computer name, do the following:
1. If you have .Net Framework installed, uninstall it
2. Uninstall IIS
3. Reinstall IIS
4. Reinstall the .Net Framework if you uninstalled it.

Web: Configuring the Web console to work with a proxy server
If you use a proxy server on your intranet, you need to configure the Web console for that proxy. Edit Inetpub\wwwroot\remote\proxy.asp, and put the proxy URL inbetween the quotes on the "purl" line.

Web: Using on-demand remote control from the Web console
If you've configured your Web console to access multiple cores and you use Management Suite 8's new on-demand remote control feature, you need to change this registry key on the computer you are running the Web console:
HKLM\Software\LANDesk\ManagementSuite\CoreServer
Change the value of this key to match the core server you're remote controlling clients from.

Web: When accessing a rollup core from the Web console, you can't target computers in the Target Cart for scheduled jobs
When accessing a rollup core,you can add computers to the Target Cart, but the Selected Computers list is empty when you try to schedule a task. When working with a rollup core, use queries as scheduled job targets.

OSD: Multicast OS deployments fail because the core server can't authenticate to the package share
When doing a multicast OS deployment, the core server uses the scheduler login credentials to authenticate with the package share. If these credentials don't have access to the package share, the deployment will fail. To prevent this from happening, do one of the following:

• Make sure the scheduler login credentials (Configure | Services | Scheduler tab) have permissions for the package share.
• Change the scheduler login credentials to the default of LocalSystem. Note that this will prevent UDD push agent deployments from working on devices that don't have the standard LANDesk agent loaded.

UDD: The Unmanaged Device Discovery AMS alert isn't available until you discover some unmanaged devices
If you want to configure the UDD alert, discover some devices first. When configuring the UDD alert, you must select "Information" on the Select Action Severity page. If you don't select the information alert severity, the alert won't trigger.

UDD: Scheduling a client deployment with clients from UDD and then deleting the job adds clients to the Pending Unmanaged Client Deployments tree
Clients in the Unmanaged Client Deployments tree won't be rediscovered by UDD, even though they don't have the client agents on them. Delete the clients from the Unmanaged Client Deployments tree if you want them to appear in UDD again.

UDD: UDD scan configurations sometimes won't save
Under rare circumstances UDD will show an error dialog when you try to save a scan configuration. If this happens, restart the Management Suite console and the problem should go away.

Documentation: In the Rollup Utility, dbrollup.exe, clicking a help button when running the utility from a mapped drive generates an error
If you access help from the Rollup Utility when running it locally, help works fine. For information on using the Rollup Utility, see the Management Suite online help. Use the Search tab to look for "rollup", and view "Using rollup databases."

Documentation: The web console help documents SLM reports and denying product execution
These features are no longer in the web console.

Upgrading Management Suite 8 versions

When upgrading Management Suite 8 versions, such as 8.0 to 8.8, be aware of the following issues.

Setup: When installing LDMS or LDSM version 8.8, Setup will prompt to uninstall System Manager if it's present
If you have Intel Server Manager, Gateway System Manager, or System Manager for Clients 8.1, LDMS and LDSM Setup will need to uninstall them. Let Setup continue with the uninstall. If Setup prompts you to uninstall MSDE, uninstall it and choose to delete the MSDE datafile when prompted. If Management Suite is already present and using the MSDE database, you won't be prompted to uninstall MSDE.

Setup: Upgrading from Management Suite 8 to 8.8 overwrites customized .INI files and Web console files
If you've customized ldappl3.ini, ldappl3.template, or any of the default scripts, you must back up these files before installing Management Suite 8.8, since Setup will overwrite them. After installing 8.8, you can restore them.

Setup: Upgrading from Management Suite 8 to 8.8 prevents upgraded Web consoles from accessing version 8 core and rollup core databases
If you have multiple core or rollup core servers, you should either upgrade all of them simultaneously or keep one version 8 Web console server so you can access the non-upgraded core and rollup core databases.

Setup: After upgrading from Management Suite 8 to 8.8, reinstall any additional consoles
Among other issues, you may not be able to view configured alert actions on additional consoles until you reinstall them.

Setup: If you are installing over an existing Management Suite 8 installation, don't select the option to bring over settings from a previous version of Management Suite
Bringing over settings from a previous Management Suite version should only be used when you're installing over Management Suite 6.62 or 7.

Upgrading Management Suite 8 and System Manager

If you have installed LANDesk System Manager 8 on a LANDesk Management Suite 8 core server and are upgrading to a more recent build of Management Suite 8 (such as from 8.0.0.136 to 8.1), you must follow the steps below to make sure System Manager works on your upgraded Management Suite core server. If you don’t follow these steps after upgrading to Management Suite 8.8, you won’t be able to deploy System Manager agents to new clients.

1. On the LANDesk Management Suite core server, use Windows Add/Remove Programs to uninstall LANDesk System Manager for Servers. Select “LANDesk® Server Manager Administrator Console”, then click Change/Remove.  The uninstaller will prompt to confirm the uninstall option, click OK. (Note: Reboot not necessary.)
   
   If you have also installed LANDesk System Manager for Clients, uninstall it using the procedure above, except select “LANDesk® System Manager Administrator Console”

2. Install the current version of LANDesk System Manager 8 for Servers and/or Clients, by running the setup.exe program on the LANDesk Management Suite core server.
   
   (Note: Reboot required after installation.)

3. After the core server has rebooted, uninstall LANDesk System Manager 8 on all managed servers by executing the following on each server:
   
   \\”core server name”\LDLOGON\WSCFG32 /U /N /I=System Manager (Server)
   
   (Note: If you have many servers, you may want to create a script to accomplish this).

4. After the core server has rebooted, uninstall LANDesk System Manager 8 on all Managed clients by executing the following on each client:
   
   \\”core server name”\LDLOGON\WSCFG32 /U /N /I=System Manager
   
   (Note: If you have many clients, you may want to create a script to accomplish this).

5. Install LANDesk System Manager 8 to all desired servers by executing the following on each server:
   
   \\”core server name”\LDLOGON\WSCFG32 /N /I=System Manager (Server) /I=Remote Control for Servers
   
   (Note: If you have many servers, you may want to create a script to accomplish this).

6. Install LANDesk System Manager 8 to all desired clients by executing the following on each client:
   
   \\”core server name”\LDLOGON\WSCFG32 /N /I=System Manager
   
   (Note: If you have many clients, you may want to create a script to accomplish this).

7. Using the LANDesk System Manager Administration console, discover all upgraded servers and clients prior to managing them.

Notes from earlier releases

Console Setup

When upgrading Management Suite, make sure that file shares on the core server aren't being accessed
If a file on a share is being used, Management Suite won't be able to upgrade that file, and Setup will report an error.

Installing Management Suite to a path containing double-byte characters disables remote control
We strongly recommend you install Management Suite to the default path.

License keys are case-sensitive
Make sure you use the correct case when entering the license key. The "LDMS" portion of the key must be upper-case.

For Wake On LAN* to work on a subnet, the multicast domain representative on that subnet must be running
Multicast won't use Wake On LAN to turn on domain representatives.

Client Setup

On Windows 2000 clients, WSCFG32.EXE displays this error message,  "Message source 'Client Setup' not found (id 0x6B). Inserts were:"
WSCFG32.EXE requires administrative privileges to run. Make sure it is running with administrative privileges on client computers.

When client setup (WSCFG32.EXE) runs on a computer where the logged in user doesn't have local administrative rights, client setup freezes without showing an error message
Use Ctrl-Alt-Del or the Windows Task Manager to close WSCFG32.EXE. There isn't a workaround at this time.

Client components that weren't originally installed via a software distribution package can't be uninstalled via a software distribution package.
Unlike software distribution Client Setup packages, WSCFG32.EXE will uninstall components regardless of whether they were originally installed via a Client Setup package or via WSCFG32.EXE. For example, if you have clients with a mix of software distribution and WSCFG32.EXE component installations and you want to uninstall all client components, you can create a default Client Setup configuration that has the components to uninstall and you can then run WSCFG32.EXE on the clients via a custom script (remote execute with no UI), a login script, or manually at the client.

Console

The console displays a numeric code in the console's results column rather than an error message
If you try to deploy a package to a computer that is shutting down, the deployment will fail, and the console will display a numeric message such as "7 : 322" in the results column rather than an error message.

Microsoft's WMI (Windows Management Instrumentation) must be installed in order for the inventory scanner to scan CDROM, USB, and PDA information on Windows 95/98 and Windows NT 4 computers
Windows ME and Windows 2000/2003/XP come with WMI. You can download WMI for Windows 95/98 and Windows NT 4 from http://www.microsoft.com. Do a search on the site for "WMI core". You should see a "Windows Management Instrumentation (WMI) CORE 1.5" link. When this document was created, the direct link was at: http://msdn.microsoft.com/downloads/default.asp?URL=/code/sample.asp?url=/MSDN-FILES/027/001/576/msdncompositedoc.xml.

In the console's Configure Services dialog's Scheduler tab you can't specify an Active Directory user account as the account the Scheduler uses to connect to computers
The Scheduler tab won't accept a username in the Active Directory format, such as username@domain.com.

To work around this problem you can edit the Intel Scheduler service directly from the Services applet in Control Panel and specify an Active Directory account on the Log On tab.

Network View background discovery incorrectly grays out Macintosh* client computers, indicating they don't have LANDesk Management Suite agents on them even if they do
If Network View background discovery (Configure | Agent Discovery Options) is enabled, Macintosh clients with LANDesk Management Suite agents on them will gray out as if they don't have agents. This behavior is incorrect. You can click grayed Macintosh clients with LANDesk Management Suite agents on them it will refresh the client agent status correctly.

Remote Control, File Transfer, and Chat

Remote Control: The LANDesk Management Suite remote control client software on Windows* XP clients doesn't support the fast user switching feature
If someone switches users via fast user switching, the remote control agent won't respond any more. Reboot to reset it.

Remote Control: When viewing Windows XP clients from an operating system other than Windows 2000, you may see screen artifacts in the remote control viewer
Operating systems other than Windows 2000 don't support some of the screen drawing commands that the remote control viewer uses when viewing Windows XP clients. Mainly this seems to affect how icons on Windows XP desktops appear in the viewer, where you will only see desktop icon labels rather than the icons themselves.

Remote Control: When remote controlling Windows XP clients using Remote Control's Windows NT security, you are prompted to log in even though your account is in the Remote Control Operators group
By default, Windows XP authenticates as guest. You can authenticate as yourself by modifying a registry key on clients. Add or edit the DWORD registry key HKLM\SYSTEM\CurrentControlSet\Control\Lsa\forceguest and set it to 0. 

Remote Control: Systems with NVIDIA TNT*/GeForce* video adapter that are in a 3-D screen mode can't be remote controlled
If you try to remote control a computer with a NVIDIA TNT/GeForce video adapter that is currently in a 3-D screen mode, such as with a game or one of the 3-D screen savers included with Windows, the client will blue screen. Remote control doesn't support hardware-accelerated 3-D screen modes on any video adapter. Ensure that clients don't use screen savers using these modes.

Remote Control: Windows XP Plus Pack isn't compatible with remote control
The remote control patch doesn't support the Windows XP Plus Pack. Portions of the Plus Pack (including some of the screen savers) use video modes that aren't compatible with remote control. We recommend you not install the Windows XP Plus Pack on clients you want to remote control.

When viewing query results that include custom data date fields, if the date fields are null they show a date of 1/1/70 12:00:00 AM
Custom data date fields that have a value of 1/1/70 12:00:00 should be considered empty.

File transfer won't display client local drives that appear alphabetically after a mapped network drive
File Transfer assumes that all drive letters after the first letter mapped to a network drive are network drives. For example, if a client has drive B: mapped to a network share, File Transfer won't show the client's local hard drive, which is probably C:, but it will show the client's mapped network drives after B:. Make sure clients you want to use File Transfer with map network drives farther down the alphabet than local drives.

Chat: When using chat with a French Windows XP client computer that's using EN as the keyboard language, the keyboard language used by Chat is FR
There is no workaround at this time.

Software Distribution

Software Distribution: In the Schedule Tasks window, when trying to send a package that was selected using the Browse button (not the URL), the error "Cannot open package" occurs
This happens when using extended characters in the share name. When NOT using extended characters in the share name (the folder name may have extended characters), it works fine. 

Software Distribution: Package deployment fails ("Unable to access package") when the package is stored on a shared Windows XP folder
When creating a Null Session Share on Windows XP, the "ANONYMOUS LOGON" group must be given permission to access the share. If this group is not given access to read from the share, the package can't be accessed and the distribution will fail.

Software Distribution: With Windows XP fast user switching, package installation progress is only visible for the user that logged onto the computer first
If another user uses fast user switching to log on and a package starts installing, that user won't see installation progress, though the package will still install correctly for the initially logged on user.

Software Distribution: With a Windows XP computer not logged into a domain, user-specific package options (such as shortcuts on the desktop) only apply to the user that logged onto the computer first
If another user uses fast user switching to log on, they won't see any options specific to the "Logged on user" as set in the Package Builder. The package will still install correctly for the initially logged on user.

Enhanced Package Builder Setup doesn't create Start menu items when a non-administrator on Windows NT 4 Workstation runs Setup
This issue happens when a non-administrator runs the Enhanced Package Builder Setup (\Program Files\Intel\DTM\install\Enh_pkg_bldr\<language>SETUP.EXE) on Windows NT 4 Workstation.The program runs fine for non-administrators even though Setup doesn't create Start menu items. You can still launch the Enhanced Package Builder by double-clicking the executable directly from Explorer or from Start | Run.  

Clients receiving single-file MSI packages must have the Windows Runtime Installer installed
For Windows 9x/ME clients, you can download the installer from:
http://msdn.microsoft.com/downloads/default.asp?url=/downloads/sample.asp?url=/msdn-files/027/001/456/msdncompositedoc.xml&frame=true

For Windows NT 4 clients, you can download the installer from:
http://msdn.microsoft.com/downloads/default.asp?url=/downloads/sample.asp?url=/msdn-files/027/001/456/msdncompositedoc.xml&frame=true

Microsoft may change these links in the future.

Macintosh

Macintosh: When remote controlling a Macintosh computer with a monitor that is in sleep mode, the screen appears blank
After initiating remote control, moving the mouse or pressing a key will update the window with the remote computer's screen. Also, if a computer is in full sleep mode and in a suspended state, remote control won't wake it up.

Miscellaneous

Application Healing: When an application is broken and you set it to heal on next logon, Application Healing won't heal if the next user to log on is a Windows XP limited user
If the user isn't limited, healing works fine.

SLM: Software license monitoring won't monitor 16-bit applications on Windows NT/2000/2003/XP
On Windows NT/2000/XP, all 16-bit applications run under the NTVDM process and SLM can't track them individually. Windows 95/98, SLM monitors 16-bit applications accurately.

Inventory: When querying for software product names, query on the "Name" inventory attribute rather than "Product Name"
In the console, the "Product Name" inventory attribute refers to a header item gathered from the version data in an .EXE file. This value is only populated when the file contains version data and you use ExtraFileDataLevel=2 in the LDAPPL3.TEMPLATE file. Most of the time this field is not populated. "Computer | Software | Package | Name" returns application names that the scanner discovers with default settings.

Web console

If you install client agents on a web console web server, don't uninstall the client agents
Uninstalling Management Suite client agents on a web console web server prevents the web console's Scheduler service from loading.

Using the search feature in the web console help system generates an error, "Service is not running"
The help system's search feature requires Microsoft's Indexing Service. This service may not be started by default. Go to the Control Panel's Services applet, start the Indexing Service, and set it to start automatically. The Indexing Service may take a few hours to build the index the first time you start it.

Web console queries with double-byte characters in the name don't save correctly
The Microsoft ODBC driver for Oracle doesn't support sending Unicode strings into an Oracle server. Avoid using double-byte characters in query names.

Exact match Web console queries on text strings with extra spaces in them fail
Some scanned inventory strings have multiple spaces between characters. When these strings display in a combo or list box, the box strips out the extra spaces and so the string in the box no longer exactly matches the string in the database. Use a LIKE operator to query on strings that may have multiple spaces. The LIKE operator will match correctly.

OS deployment and profile migration

The following are known issues with the OS deployment and profile migration tool. The issues are divided into these categories:

• Notes from earlier releases
• Useful OS imaging links
• Multicast configuration issues
• Configuring name resolution
• PowerQuest generates Causeway errors when used with Multicast

WARNING: The OS deployment functionality must be used with caution. Operating system deployment involves wiping all existing data off of a computer and installing a new operating system. There is substantial risk of loss of data if the OS deployment function is not performed precisely as described herein or if poorly implemented images are used. Before performing any OS deployment, all data must be backed-up in such a manner that any lost data may be restored.

Notes from earlier releases

PM: Microsoft Office application shortcuts issue
When the target computer of a Microsoft Office application's shortcut uses the Office version number (appearing dimmed and uneditable in Shortcut Properties) instead of the full path to the program executable, the application on the target must be the same version as the application on the source computer; otherwise, the restored shortcut link will be broken. This can occur when the shortcut was created by right-clicking and dragging an icon from the Start menu. Delete the broken shortcut and create a new one. This behavior is peculiar to Microsoft Office applications.

PM: Error when capturing a profile from a Windows NT/2000 computer
Rarely, when capturing a profile from a Windows NT/2000 computer, you may see an error message "Failed to load user registry hive, unable to restore user profile." During profile capture, Profile Migration needs room in the registry to temporarily load information. On Windows NT/2000, the registry file doesn't dynamically resize itself, so if Profile Migration's registry work exceeds this size, it generates an error. If you do see this error, you can increase the maximum registry size in the Windows NT/2000 System Properties dialog.

PM: Rerunning a failed/interrupted profile restore displays a message about the package already being installed
If a profile restore is interrupted or fails, the next time you try restoring the profile, you'll see a message about the package already being installed. You have the choice of selecting Repair or Restore. In this case, you can select either and the profile will be restored correctly.

PM: Running two profile restore instances simultaneously can corrupt the profile restoration
Don't run two profile restore instances at the same time.

PM: Profile Migration capture will fail if a file changes size during the capture process
To prevent a corrupt capture, Profile Migration will fail if a file changes size during the capture process. Typically it is application or system log files that cause problems. An example is C:\windows\SchedLgU.txt, which is a frequently updated log file for the Windows Scheduler. To help prevent capture failures, add problem files to the global exclude file in the core server's DTM\LDLogon directory (pmexclude.lst). You can also use a "File Rule" script and enter the file in the "Exclude" field. User's will still want to manually back the file up if it is important enough to migrate.

PM: Enabling the Italian help and user interface on the user-initiated profile migration client (Italian only)
After installing OSD on your Italian core server, the user-initiated profile migration client help is in English. To enable Italian help, you must replace/rename the English files that are in the LDLogon directory with the Italian ones (ita*.*) listed below. This will only work with OSD/Profile Migration installed.

Rename these four files:
italdprofileui.dll to ldprofileui.dll
italdprofileui.cnt to ldprofileui.cnt
italdprofileui.hlp to ldprofileui.hlp
itafeaturemap.ini to featuremap.ini

OSD: Computers default to logging in automatically after an OS deployment
OSD inserts an AutoLogon=Yes command into the SYSPREP.INF file but it doesn't insert an AutoLogonCount=1 command. If that command isn't already present in the file, the computer will be left in an AutoLogon mode when OSD completes. To prevent this, make sure SYSPREP.INF files that OSD uses include AutoLogonCount=1.

OSD: Deploying images that include applications with "product activation" features, such as those included with many new Microsoft products
Applications like Office XP have a "product activation" feature that detects when they are installed on a system other than the original. You will have to reactivate these products or have a volume license version from Microsoft.

OSD: OSD virtual boot may hang on computers with multiple network adapters
This problem occurs when deploying images to computers with multiple network adapters (NICs) Normally, even if only one NIC is connected to the network, the inventory scanner will detect the other NIC and send the MAC addresses of both NICs to the database. The problem that this causes is that upon OS deployment, OSD loads the DOS driver for one NIC but tries to use the MAC address of the other NIC. By disabling one NIC during the inventory scan before deploying an OS, DOS will use the MAC address of the active NIC and load its driver. This prevents the OSD virtual boot from hanging.

Documentation: OSD help isn't available from Help | Contents
If you've installed OSD but you don't see OS deployment and profile migration information in the contents or index, delete all *.GID files in the DTM directory. Deleting the .GID files makes the Windows help system rebuild its indexes.

Don't install your core server on a computer that is your network's primary/backup domain controller or Active Directory* server
OSD won't work correctly on servers performing these functions.

OSD doesn't support NT Authentication when using Microsoft SQL Server
OSD requires SQL Server authentication.

Don't install your PXE proxy on a DHCP server
The PXE proxy won't work correctly when it's on a DHCP server.

Don't install your PXE proxy on a dual-homed computer
PXE proxies won't work correctly on a dual-homed computer.

Don't create images off of too many computers simultaneously
Targeting multiple computers with an OSD image creation script generates a lot of network traffic to your image server. Depending on your network and server bandwidth capacity, you may want to limit simultaneous image creation to several computers at a time. If the imaging tool can't write to the image because of bandwidth-related delays, it will generate an error.

Make sure the path to your imaging tool is as short as possible
Most imaging tools require very long command lines. Once you add the path to the imaging tool location, the command line can exceed the DOS character limit. If your path is too long, the command line will get truncated and the job will probably fail. If you add your own parameters to the command line, you may have to make the path even shorter. Ideally, put the imaging tool executable in the same directory as your image share or one directory under it.

After you install OSD, computers that run the Intel PDS service send miniscans to the core server
After installing OSD, computers that run the Intel PDS service will send miniscans to the core server. As a result, you may see computers in the database you aren't used to seeing, such as computers running the Web console that may not normally have the LANDesk client software on them. These miniscans don't contain all the information full scans have. Also, these computer scans display the MAC address for the computer name.

PXE proxies have to be removed and re-installed if moving to another core server on the network
If you deploy a PXE proxy from one core server and later decide you want that PXE proxy to use a different core server, you must remove the PXE proxy and reinstall it. Just updating the PXE proxy from the new core isn't sufficient.

The PXE boot prompt doesn't support extended foreign characters
Avoid using extended foreign characters in the boot prompt. Garbled characters will display if you do.

Once you've run an OSD script on a client, WSCFG32 /U won't uninstall the OSD files on that client
Running an OSD script copies additional files to the c:\ldclient directory that WSCFG32.EXE won't remove.

Windows 95B multicast clients must have IE 5.5 or greater
If you schedule a multicast to a Windows 95B client without IE 5.5 or later, you'll see an error about a missing MRAPI.DLL file.

Deployed non-Sysprep images have an LDISCAN.CFG file inserted in their root
If you're deploying a non-Sysprep image and dont want an LDISCAN.CFG file inserted in the root of your image, you should edit the deployment script you will be using and comment out the fworkcl line that inserts LDISCAN.FG with a semicolon. This prevents fworkcl from injecting the LDISCAN.CFG file.

Multicast imaging depends on BIOS drive LBA autodetection
Multicast requires that computers you're imaging properly handle LBA autodetection for drive parameters. Older computers may require BIOS upgrades to support LBA autodetection, especially with larger hard drives.

During a Multicast deployment, if a client fails at the Net Logon point in the script, script processing stops until that client is rebooted manually
If a computer fails Net Logon, Net Logon displays a prompt, preventing the deployment script from continuing. You will have to reboot the computer manually if this happens so your core server can continue processing the script.   If all computers are affected, you will have to reboot all of them.   If there's an authentication problem, for example, a correct username but wrong password, you'll need to fix the script before trying the job again.

When creating Windows XP images, make sure you disable Fast User Switching and the Welcome Screen in Control Panel
OSD requires the username/password login prompt and can't do post-imaging OS configuration when these settings are enabled.

If you deploy OSD images to computers that don't have the required Enhanced Software Distribution (ESD) agent, the status message returned is "Couldn't run at client"
Install the ESD agent and try again.

If your core server is also your database and PXE server, you need 768 MB or more of RAM or you'll see erratic behavior from Management Suite

DOS menu updates fail if your Internet connection uses a proxy server
You need to select the "Bypass Proxy Server for Local Addresses" option in IE if your Internet connection uses a proxy server; otherwise, you'll see this error message when trying to update the DOS menu: "DOS Menu Update web service failed. "Both core servers and additional consoles will need to make this change.

Once you schedule an OSD task, don't select PXE boot menu options on target computers until the task completes
If you interrupt an OSD task once it has started by selecting a PXE boot menu option on the target computer, the task will fail.

Using virus protection with OSD
OSD changes the master boot record (MBR) while imaging. If you have virus protection running on clients you want to image, you may need to disable virus protection if it prevents MBR changes.

Multiple network adapters in your image server
If the image server has multiple network adapters and IP addresses, you need to make sure the IP addresses work for clients accessing images. The DOS network clients use name resolution and use the first IP address returned for the image server.

Failed multicast jobs and PXE
When booting to PXE and there is a failed multicast OSD job for that computer, OSD won't attempt to automatically rerun the job on that computer.

PXE proxy won't deploy to double-byte language Windows NT 4 computers
If you try to deploy the PXE proxy to a double-byte Windows NT 4 computer, the Scheduler reports "A critical error has occurred." Deploy the proxy to a Windows 2000 or Windows XP computer instead.

Deployment fails if a target computer doesn't boot with a keyboard and mouse connected
DOS requires that your target computers boot with a valid keyboard and mouse connected. If the DOS client can't find a keyboard and mouse, the deployment fails and the target computer will stay in DOS. Some keyboard/mouse switchboxes emulate the keyboard and mouse even when the client isn't active. These switchboxes work fine.

Useful OS imaging links

Windows XP:

How to prepare images for disk duplication with Sysprep

http://www.microsoft.com/WINDOWSXP/pro/using/itpro/deploying/duplication.asp

Windows XP Professional how-to articles for IT pros:

http://www.microsoft.com/windowsxp/pro/using/itpro/default.asp

Windows 2000:

Download for the Microsoft Windows 2000 Sysprep tool

http://www.microsoft.com/windows2000/downloads/tools/default.asp

Deploying MS Windows 2000 Professional and MS Office 2000 using Sysprep

http://www.microsoft.com/technet/treeview/default.asp?url=/TechNet/prodtechnol/windows2000pro/deploy/depopt/sysprep.asp

Windows NT:

Windows NT Workstation deployment

http://www.microsoft.com/ntworkstation/technicalresources/deployment/default.asp

Multicast configuration issues

Error, "Could not get file information" from the subnet representative when deploying with Multicast

This error happens when a Multicast domain representative can't access the image share. Multicast requires that the image share be a null-session share accessible to all computers without any requirement for credentials. This requirement is described in the User's Guide.

When creating a new OSD script, the scripts wizard prompts the user for credential information to be used when accessing the image via UNC path. The console even validates this information by attempting to connect to the UNC path with those credentials. However, if "Use Multicast" has been selected on the first page of the wizard, then these credentials are ignored by the Multicast domain representative. These credentials don't apply to multicast deployments.

If your Multicast domain representative can't access the image share, all of the target computers will be left in DOS, running DOSMCAST, waiting for the domain representative to begin sending image information. Unfortunately, the domain representative will already have terminated with a final status of "Could not get file information" because it couldn't access the image share.

To get out of this situation without PXE booting all of the DOS computers (because their partitions have already been changed), you can do one of two things:

• If the computers are close by and there aren't many of them, you can go to each one and hit the Escape key. This will drop each computer back into the dconnect waiting state. At this point, you can run the same custom script again. Nearly all commands (except for the remexec of the DOSMCAST command) will be redundant, but this way allows you to avoid having to edit the custom job script manually. Don't worry that the net use commands fail because the drives are already mapped from the first time the script was run.

• The second method requires you to manually edit the .INI file that controls the job. Make a copy of the original custom job script. In the [JOBPARAM] section, find the "steps" variable, and change it from 2 to 1. Delete the entire [MACHINES] section, and rename [MULTICAST_1] and [MACHINES_1] to [MULTICAST] and [MACHINES], respectively. Rerun the job. In order for this job to work, all targets need to be already running DOSMCAST, waiting for the image file.

Configuring name resolution

OSD requires name resolution to work. In an environment where WINS and/or DNS name resolution isnt available or doesnt work properly, it may be necessary to implement a Static IP address for the LANDesk core server and hard-code the IP address into the PXE and virtual boot images for OSD.

To test if WINS is working on your network

From a DOS 6.22 environment (with Microsoft NDIS/DHCP stack) command prompt, try the following NET USE command to map a drive to your server that houses your images (not necessarily the core server). Management Suite will use WINS/LMHOSTS resolution to map drives to your image server:

NET USE G: \\imageserver\share

To test if DNS is working for your environment

1. From any Windows 2000 or XP workstation that has a DHCP address, type the following from a command prompt: NSLOOKUP
2. At the NSLOOKUP prompt (>), type the name of your core server. Management Suite uses DNS to resolve the name of the core server when deploying operating systems.

For OSD to work properly, your DNS server needs to be able to resolve both the NETBIOS (root servername) and fully-qualified domain name (FQDN, servername.mycompany.com) of the core.

If your DNS server can resolve the name of your core server, everything should work. If not, you may want to implement a static IP address for the core server.

To eliminate name resolution problems from your OSD solution

1. Assign the core server a static IP address. Use your Microsoft documentation for help on assigning a static IP address for the core server.
2. Download and install Winimage* from www.winimage.com onto your core server.
3. Edit the OSD boot images.

Editing the boot images

If you are hard-coding IP addresses, there are three boot images you need to edit.

In the \PROGRAM FILES\LANDESK\MANAGEMENTSUITE\LANDESK\FILES directory, edit:

• BOOTMENU.1
• DOSUNDI.1

In the \PROGRAM FILES\LANDESK\MANAGEMENTSUITE\LANDESK\VBOOT directory, edit:

• LDVBOOT.IMG

To edit the images

1. Using Winimage, extract STARTENV.BAT from the boot image listed above that you are editing.
2. In the SET COREHOST=xxxxx command, change the name of the core server to the IP address of the core server.
3. Save the modified STARTENV.BAT file and re-inject into the root of the image. Remember to save the image after injecting the new STARTENV.BAT.
4. Navigate to the \NET directory of the image. Extract the LMHOSTS file from the image.
5. In the LMHOSTS file, add name resolution for any server that will serve as an image server. Example:

192.168. 2.34 FILESERV2

192.120. 2.14 FILESERV12

6. Save the LMHOSTS file, and re-inject into the \NET directory of the DOSUNDI.1 image. Remember to save after injecting.

Now you're ready to deploy your PXE proxies and begin scheduling OSD jobs. By editing all three images, name resolution works when using virtual boot or PXE to deploy your images.

If you've deployed PXE proxies before following these steps, redeploy so that your PXE proxies have the updated boot images. If you need to change the IP address of the core server, follow the steps outlined above.

PowerQuest generates Causeway errors when used with Multicast

When using PowerQuest to deploy images via Multicast, PowerQuest may generate Causeway errors and fail. PowerQuest's solution for this problem is to run PowerQuest locally. By default, Multicast runs PowerQuest remotely. You can run PowerQuest locally in Multicast jobs by doing the following:

• Edit the OSD script
• Increase the RAM drive size

To edit the OSD script

Open the OSD script you will be using for the Multicast deployment.

Comment out the line resembling the following with a semicolon (your paths may differ slightly):
;REMEXEC23=r:\net\htget -a h:\PQImgCtr.exe, STATUS FACILITY=7

Add a new line as follows, but substitute h:\pq*.* with your path to the PowerQuest program files if they aren't in the root of the share you specified in the scripts wizard. Don't change the drive letter or the pq*.* part.
REMEXEC23=copy h:\pq*.* r:\, STATUS FACILITY=7

To increase the RAM drive (xmsdsk) size for your virtual boot and PXE boot images

Copy the following text to a text file named autoexec.bat:

@echo off

set iar=Y

set iobs=a

c:\net\pworkcl.exe /M 0

REM c:\dos\xmsdsk 3072 r: /y /t

c:\dos\xmsdsk 5120 r: /y /t

md r:\dos

md r:\net

copy c:\dos\*.* r:\dos

copy c:\net\*.* r:\net

copy c:\*.* r:\

set path=r:\;r:\DOS;r:\NET

set COMSPEC=r:\COMMAND.COM

r:

call startnet.bat

Use the copyfile command to insert the batch file into the following boot images:

Core server (for virtual boot non-PXE image):
\program files\landesk\managementsuite\landesk\vboot\ldvboot.img

PXE proxy computers (for PXE booting):
\program files\landesk\pxe\system\images\x86pc\undi\bootmenu\bootmenu.1
\program files\landesk\pxe\system\images\x86pc\undi\dosundi\dosundi.1

You can find more information about copyfile in the User's Guide, Appendix B under "Adding network adapter drivers." The syntax for copyfile is:

COPYFILE <imgfile> <srcfile> <destfile>

Security and Patch Manager Release Notes

The following are known issues with LANDesk Security and Patch Manager 8 (and the previous LANDesk Patch Manager 8 add-on).

New notes for Security and Patch Manager 8, version 8.6

After upgrading to version 8.6, scan devices for LANDesk Updates
After upgrading a core server, additional console, or managed device to version 8.6, you should scan those machines for required LANDesk software updates in order to clear any detected LANDesk updates for version 8.5 that are no longer applicable.

After upgrading to version 8.6, spyware definition counts display as 0 in the console taskbar
After upgrading a core server to version 8.6, the spyware definition counts that display in the console toolbar when you're viewing spyware definitions will be 0 until spyware content is updated again.

Scanning and remediating some very aggressive spyware might cause the desktop to shut down
On rare occasions, if a device is infected with several aggressive forms of spyware, the LSAS.DLL might shut down the Windows explorer and/or Start menu. If this happens, the device must be rebooted.

A repair job can't enable real-time scanning for Symantec Antivirus 2005 installed on a Windows 9x device
If Symantec Antivirus is installed on a Windows 9x system, and real-time scanning (RTS) is disabled, a Security and Patch Manager repair job (created by configuring the custom variable in the Symantec Antivirus 2005 definition's properties) will fail to enable real-time scanning. You must manually enable real-time scanning in this specific scenario. This known issue only applies to Symantec 2005 installed on a Windows 9x system.

New notes for Security and Patch Manager 8, version 8.5

Downloading patches after core upgrade to 8.5
If you're unable to download patch files after upgrading your core server to version 8.5, from version 7.0 or 8.0, run the following command to make sure IIS is properly registered with ASP.NET:

aspnet_regiis /i

Notes for the Patch Manager 8 add-on, version 8.1

Policy-based remediation: Creating an APM query for a large vulnerability group fails if you're using an upgraded Oracle database
If you've upgraded a preexisting Oracle database when upgrading to Management Suite version 8.1, and you try to create a policy-based repair job for a vulnerability group containing more than 33 vulnerabilities, the policy will not be created due to column sizes being too small. You can fix this problem by executing the following sql statements:

alter table query modify querysql varchar(4000)
alter table query modify filter varchar(4000)

Note that this issue only affects preexisting Oracle databases, not new Oracle databases installed with Management Suite version 8.1.

Mac vulnerability detection: Reports back file size of the executable
Be aware that vulnerability detection on Mac clients reports the file size of the actual executable file, not the bundle.

Notes for the Patch Manager 8 add-on, version 8.0

Install: Uninstalling the Patch Manager add-on and Management Suite
If you need to uninstall the Patch Manager add-on and the prerequisite LANDesk Management Suite software, follow the instructions below:

First, remove the LANDesk Patch Manager program via Add/Remove Programs. (Do NOT remove LANDesk Management Suite first.)

Then, remove the LANDesk Management Suite program via the same utility. When the uninstall is complete, reboot the computer as prompted.

Finally, IF you upgraded your core server from Management Suite 8 to version 8.1, after the server reboots you must uninstall the original LANDesk Management Suite program entry that now appears in Add/Remove Programs. In other words, you must uninstall LANDesk Management Suite twice in order to completely remove it from the server.

Additional console: Running Patch Manager add-on from additional consoles
To use the Patch Manager add-on from any of your additional consoles, you must reinstall the additional consoles after installing Patch Manager on a Management Suite 8.1 core server. Once Patch Manager is installed on your core server, any new additional consoles will include Patch Manager functionality. For detailed information on installing additional consoles, refer to the Installation and Deployment Guide.

Patch installation: Patch installation fails if the patch requires installation of a referenced file not on the local hard drive
If a patch requires the installation of a referenced file (i.e., some patches for Microsoft Office call a file from the application's original installation path) that is stored at a resource other than the client's local hard drive, the patch installation fails because the Local Scheduler can't access the resource, such as a network share or CD. For the patch to install successfully, you must first insert the CD or copy the needed file to the local hard drive.

Patch download: Downloading all of the currently available patches can take up to 800 MB of disk space on the core server
This is not a problem as long as your core server maintains at least 1 GB of free disk space. The vulnerability scanner may not run properly on clients if the available free disk space on the core server is too low.

Patch download: Unable to download patch files from a Windows 2003 core server until explicit MIME types have been configured
You must first configure Windows 2003 Web servers for software distribution/patch deployment. This issue is also documented in the Software Distribution chapter of the Management Suite Users Guide. When hosting files on a Windows 2003 server, files without a registered MIME file type will fail to multicast unless you do the following:

To register MIME file types

1. Launch Internet Information Services (IIS) Manager.
2. Expand the local computer in the tree.
3. Click Web Sites > Default Web Site.
4. From the package Web share's shortcut menu, click Properties.
5. Click the HTTP Headers tab.
6. Click MIME Types.
7. Click New.
8. In the Extension box, enter an asterisk (*).
9. In the MIME Type box, enter any name.
10. Click OK twice and apply the changes.

Patch download: If patches have been downloaded to a location other than the default patch repository on the core server, you may need to configure certain web share settings in order for patch deployment to work properly
For example, if you've downloaded patches to a 2003 server, make sure the following settings comply:

On the server hosting the web share,

1. Open IIS (Internet Information Services).
2. Right-click the web share where you're storing patches, and then click Properties.
3. On the Directory tab, make sure there is no default application specified. (This ensures that the user is hosting a virtual directory rather than a web application.)
4. On the Directory Security tab, click the top Edit button, and then check the Anonymous Access check box.
5. Click OK twice, and then close IIS.

On the custom shared directory,

1. Right-click the directory, and then click Properties.
2. On the Security tab, make sure the Internet Guest Account has permissions to access this directory (at least: Read & Execute, List Folder Contents, and Read). If the Interest Guest Account doesn't exist, add it with default permissions.
3. Click OK to save changes.

Nothing in this document constitutes a guaranty, warranty, or license, express or implied. LANDesk disclaims all liability for all such guaranties, warranties, and licenses, including but not limited to: Fitness for a particular purpose; merchantability; non infringement of intellectual property or other rights of any third party or of LANDesk; indemnity; and all others. LANDesk products are not intended for use in medical, life saving, or life sustaining applications. The reader is advised that third parties can have intellectual property rights that can be relevant to this document and the technologies discussed herein, and is advised to seek the advice of competent legal counsel, without obligation of LANDesk.

LANDesk retains the right to make changes to this document or related product specifications and descriptions at any time, without notice. LANDesk makes no warranty for the use of this document and assume no responsibility for any errors that can appear in the document nor does it make a commitment to update the information contained herein.

Copyright ©  2003-2007  LANDesk Software Ltd., or its affiliated companies. All rights reserved.   LANDesk is either a registered trademark or trademark of LANDesk Software, Ltd. or its affiliated companies in the United States and/or other countries.

*Other brands and names are the property of their respective owners.