Home > Reviews > LANDesk Management Suite 8.0
 

AppDeploy.com
            search engine keywords: deployment, remote, installation, software,
            applications, updates, hotfixes, hot fixes, hotfix, service pack,
            sp1, sp2, sp3, sp4, sp5, sp6, IE, Microsoft, SMS, installer,
            install, pdf, package, definition, file, script, KiXtart, kix,
            logon, logoff, bat, NT, shell, batch, installation software,
            software installation, remote installation, installer, wise
            installer, SMS installer, window installer, windows installer, 
            ghost image, imageing, drive image, drive image pro, 
            warez drive image, drive image download, drive image powerquest,
            powerquest drive image, warez drive image, appz, drive image 3, imaging software, disk imaging software, free imaging software, perl script, vb script, free script, shell script

 
Overview

LANDesk is one of those desktop management suites that does it all. I, for one, am always skeptical of suites that “do it all” because it often means that certain features are noticeably lacking. It seems that all too often features are added simply to boost the length of the feature list and, to a disappointingly lesser extent the value of the suite as a whole. I am happy to say that this is not the case with LANDesk Management Suite 8, which has somehow managed to provide a very long list of features while maintaining a very well thought out implementation for each.

Installation

Instead of simply listing requirements, a nice front end is provided that checks for requirements and notifies if you have met them or not (see image at right). If any requirements are not met, download links to Microsoft’s website areLANDesk Prerequisites Check Dialog provided to help you obtain them. Installation requires Windows Server (NT/2000/2003) and the system must not be a domain controller on the network. Once requirements are met and you begin the installation, setup prompts for a Windows NT 4 Server CD so it may obtain files from the \CLIENTS\MSCLIENT\DISKS directory. You are also prompted to provide a licensed Windows 98 CD so it can obtain files from BASE5.CAB. In each case, you must browse to the specified directory. While the reasons may be good ones, I found it odd to have to provide Windows NT Server and Windows 98 CDs during installation of a product on a Windows 2000 server. Additionally, having to navigate to paths on the disk that were documented in the dialogs seemed like an unnecessary inconvenience that could have been better automated.

[Page 1 of 5]     1 | 2 | 3 | 4 | 5