LANDesk Management Suite 8.6


Published on

Published in: Technology
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • The Advance Agent is a new deployment option suited to deploying the Standard Agent over slow or unreliable network links. It is not a replacement for the existing Standard Agent, rather an alternative way of deploying the Standard Agent.
  • By leveraging the existing bandwidth aware technologies, peer to peer download capabilities and the HTTP byte level restart capabilities of the existing Standard Agent we can produce a more robust agent deployment process. By optimising the code used to perform these functions it has been possible to produce a download agent which is only 500KB. This is the Advance Agent.
  • The Advance Agent incorporates many of the proven software technologies that are already implemented in the Standard Agent. This includes the HTTPCopy utility used to download from a web server, and the bandwidth shaping technologies which are used by the Standard Agent during software distribution. In addition, the Advance Agent has the ability to install itself as a service if it is not already present, and to set itself to start automatically.
  • The Advance Agent can be deployed in the same way as the Standard Agent, to devices that have be found through Unmanaged Device Discovery process. The problem with this is that, as security on the client operating system is tightened up, the RPC service on which this type of deployment relies, is less likely to be available. The small size of the Advance Agent makes it quite feasible to deploy it through Active Directory Group Policy. If this is your deployment method, you must ensure that the slow link threshold is correctly configured. Since you are probably trying to deploy the Advance Agent to machines with limited bandwidth, the default behaviour of Group Policy, to not download over anything slower than 500 Kbs is not appropriate. More conventional deployment methods such as logon scripts would also be suitable for deploying the Advance Agent. The size of the MSI package makes distribution as an e-mail attachment attractive, although it is not a good idea to allow users to become accustomed to running executables attached to e-mails, even if such an e-mail “claims” to be from their administrator.
  • The LANDesk® Management Gateway is a brand new feature set added to the LANDesk Management Suite product for version 8.6 that breaks the network barrier and gives LANDesk the power to reach beyond the previous limitations by leveraging the internet. This means the LANDesk Administrator now has the capability to go beyond the local or wide-area network to administer the same great functionality that Management Suite provides, and do it with nothing more than an internet connection. LMG communicates workstations to the core server over http protocols making it firewall friendly. Remote offices can use standard internet access technology like T-1, DSL/Cable Modems and even dialup connections to take advantage of the features of LDMS. The technology used to make LANDesk Management Gateway is very low in overhead and requires only a small hardware investment.
  • One of the interesting business scenarios that LANDesk Management Gateway makes feasible is for a single Core server to be used to support a large number of small customers. The customers themselves might be too small to be able to afford the infrastructure costs of running their own core server. As long as the customer has an internet connection they will be able to take advantage of the services offered by the Management Gateway.
  • The Gateway is the key technology. The Gateway is an appliance that runs on a linux based os called LDLinux. It is a minimized version a Linux 2.6 kernel custom built by landesk. This is not a modified distribution of Red Hat, SUSE or any other Linux distribution. It is LANDesk’s own operating system based on the Linux 2.6 kernel with only the necessary linux compnents included. It contains nothing more than what is absolutely needed to do the job. By stripping down the OS, LDLinux is not only extremely efficient, it also decreases the vulnerabilities and risks of attacks from the outside. The recommended hardware requirements are: Pentium 4 processor (dual processors are supported) Any processor currently in the market will work for this machine. It has been designed to function with dual processors although it is not required. 1 Gigabyte RAM This machine will be loading quite a few processes requiring at least 1 Gigabyte of RAM for best performance. IDE disk drive, SCSI and SATA (Serial ATA) are supported, however not necessary) RAID is not supported in this version. VGA video High Speed NIC (100 Megabyte or Gigabyte) You obviously want to use high-speed network cards and you should have a broadband connection. Bootable CD ROM Keyboard Only. X Windows is not part of LDLinux so a mouse not required.
  • The client has been built on the CBA8 “unified pipe” architecture. The unified pipe is designed so that the different agent components communicate using the same processes and protocols. This greatly simplifies troubleshooting and future development. The client uses an http based proxy host. This is built strictly for the agent and should not be used as a proxy service for any other purpose. The proxy agent functions only as a local proxy for the device on which it is installed. The function of the agent is diagramed in the slide. As shown, requests from the client are now received by the Proxy Host. The Proxy Host will first attempt to communicate to the core server normally, upon failure, it will forward the request to the Gateway. Configuration to reach the gateway is done with the executable, BrokerConfig.exe. This utility allow the user to setup where to find the gateway. It also allows you to select how the Proxy Host chooses whether to try to access the Core server directly first or through the gateway first. Because of this communication process, LMG only functions in a pull fashion, meaning that only processes initiating from the client are handled. Processes initiating from the server such as a software distribution using a push delivery method are not allowed. Remote control is an exception to this rule.
  • Since LMG is designed for access over an unsecured network, access to the core from the client via the gateway needs to be secured. In order to do this without repeated account authentication, LMG access the core via certificate services. At the client, a user will launch the BrokerConfig utility, authenticate to the core server via the Gateway and upon successful authentication, will be able to retrieve certificates needed for secure communication across an unsecured network. The account used to authenticate must be a LANDesk administrator account. If abuse of the Gateway service is suspected, the Administrator can block certificates from being used to gain future access Gateway Client, depending on hardware, can handle around 1000 concurrent connections. There are 2 connections per pipe. (1 in 1 out.) Also, the Gateways will have 6 open pipes, and dynamically build as need to add additional pipes, always trying to keep open 6, for additional available pipes. Core server also opens up pipes as needed, and can have open as many as 200 simultaneously. To get to the gateway client,
  • When using LMG, the core server is installed with a reverse proxy agent that translates the http requests from the gateway. The core server maintains communication availability to the Gateway by maintaining available connections of at least 6 connections at a time. Each connection occupies a thread. When the client communicates to the gateway, the gateway sends the request to the core server which examines the certificate sent with it. If the certificate is validated, the requested data is sent to the core server as though it the device was connected to the core server directly. The core server does not examine the data beyond accepting the certificate. It merely passes the data through.
  • Software Packages and Delivery Methods have been modified to allow both public and private instances of each. This is similar to the feature found in queries where a query may be publicly available or be specific to the user who created it or added to a user’s group by the administrator. In the console you will now see a group for the logged in user’s packages and delivery methods, a Public group of each, an A ll group for each and a group called User for each that the admin can view each user’s own packages and delivery methods. Private packages can be configured to be dependant on another package, however the package it is dependent on must be a public package.
  • Assigning targets distribution tasks can now be done with multiple queries, multiple groups, specific device assignments or a combination of all three. While the process is a seemingly simple change in the console, the code has been significantly modified to ensure this process is efficient and trouble free. If a device is meets the criteria of multiple queries assigned as target to the same task. LDMS 8.6 will ensure it is not run multiple time for the same device. When assigning queries, the query will not run until the task is scheduled. Therefore the listing of devices in the details pane of the task will not show the devices until after the task is launched. For example: The administrator decides that a package should only be sent to devices on 2 different subnets. The administrator has already created 2 separate queries, one for each of the 2 subnets. The administrator can now drag and drop both queries onto the scheduled task that has been built to install the package. However, when he looks at the details pane for the scheduled task, the number of devices listed as pending will be zero. In fact the number of devices listed in any of the sections will be zero. This is because the query has not been executed for this task. The query is only executed once the task begins. Once it begins, then the number of devices added will be seen. The administrator can access the properties of the scheduled software distribution task and view the targets and see that the queries have been added.
  • Linux packages are now available for distribution. This packages must be in .rpm format (debian packages or tarballs are not supported). LDMS 8.6 does not create these packages, it only imports pre-created packages and installs them using an RPM command line tool. The RPM Tool calls the file from a web source only. Therefore it cannot be downloaded from a Microsoft Share or Samba Share.
  • The command line field now allows passing values from the device’s database entry to the command line. These values are called Database Macros . The result is the command line field can contain a parameter such as %Device_Name.Computer% that will call up the computer device name from the database for each targeted device and pass that parameter as part of the execution process. Different installations and executables will have switches that will allow a user to pass parameters to the installation package. You can now use the device’s database information as parameters to pass into these switches. This allows you to use the databes to pass parameters when creating Executable and Batch File Packages
  • Reporting has been redesigned from the ground up in LANDesk Management Suite 8.6. There is no longer any requirement to use a third party reporting tool such as Crystal Reports to design custom reports. There are more options for producing reports, including Ad-hoc reports. Reports can be e-mailed directly to users, and the users scope is applied to the report as it is generated. The result is that a user receives a report containing only the information relevant to machines in their scope.
  • Ad-hoc reporting gives you one-click reporting. This type of report can be particularly useful for producing documentation about the current configuration of Management Suite itself. Standard reports are the predefined reports that are provided with Management Suite. The reports are preformatted according to the default template. They already have query properties and chart types assigned and are ready to be used. Predefined reports do not have customization capabilities. CSV Reports provide a quick and easy way to transfer information from Network View to a CSV file. This file can then be imported into another database or spreadsheet application. User Defined reports are based on a database query or are created using the report designer tool. You can create reports that enable you to specify what information will be displayed and how it will be displayed when the report is run. Each report consists of a query (custom or predefined), a layout (custom or predefined) and a graph selection if applicable. The query causes the data to be extracted from the database and populates the report with the data when the report is run. The default report layout is used unless otherwise specified. You can design a custom format using the report designer tool.
  • Ad-hoc reports provide a snapshot, that can not be scheduled. The report will contain the same information as that shown in the management console. You can not define additional fields to be reported on. You can however define a column set and use that to display the required information in the console and then produce a report. Although many nodes in the management console support the “View as Report” not all nodes do so. For example you can produce a report based on the devices listed in the network view of the console. This can be accomplished simply right-clicking the All devices group.
  • To produce an Ad-hoc report simply right click the node and select the “View as report” option. If you want to use a column set, then apply this to the view prior to producing the report. Once the report window opens you will have the option to print the report, or to export it in one of the supported formats.
  • Standard reports are installed as a standard part of Management Suite 8.6. They are arranged by component. There is extensive reporting on almost every aspect of Management Suite. If there is not a standard report that suits your purpose, then it is easy to create a customized report as we shall see later.
  • Some standard reports will prompt for user input prior to generating a report. This allows you to report on a specific machine, or operating system etc. Such reports can not be scheduled. Reports that do not require user input can be scheduled. <Welby – are you positioning this as a practice?>
  • LANDesk Management Suite 8.6

    1. 1. LANDesk Management Suite 8.6 LANDesk Usergroup Konferenz 14. September 2005 Köln Detlef Lüke Technical Consultant Product Overview
    2. 2. What´s New ? <ul><li>LANDesk Advance Agent </li></ul><ul><li>LANDesk Management Gateway </li></ul><ul><ul><li>Enterprise management over Internet </li></ul></ul><ul><li>Software Distribution Enhancements </li></ul><ul><li>Intel AMT Support </li></ul><ul><ul><li>Effective and efficient asset management leveraging Active Management Technology from Intel ® . </li></ul></ul><ul><li>Local Account Management </li></ul><ul><li>RBA Active Directory integration </li></ul><ul><li>New Reporting / -Module </li></ul><ul><li>Platform Support </li></ul><ul><ul><li>Expanded Linux Support </li></ul></ul><ul><ul><li>Expanded Macintosh Support </li></ul></ul><ul><li>Misc </li></ul>
    3. 3. LANDesk Advance Agent
    4. 4. What is the Advance Agent ? <ul><li>A robust, bandwidth aware, boot/install agent </li></ul><ul><li>Used to install a standard agent </li></ul><ul><li>Based on existing LANDesk technologies </li></ul><ul><li>It is not a replacement for the Standard Agent </li></ul>
    5. 5. Leveraging Existing Technology <ul><li>The Existing LANDesk Agent Can </li></ul><ul><ul><li>Give way to non-LANDesk network traffic </li></ul></ul><ul><ul><li>Use a percentage of the available bandwidth </li></ul></ul><ul><ul><li>Get packages from other LANDesk clients </li></ul></ul><ul><ul><li>Detect connection speed </li></ul></ul><ul><ul><li>Carry on file copy from last point </li></ul></ul><ul><li>Why not use the same approach to deploying the agent? </li></ul><ul><ul><li>In Management Suite 8.6 this is what the Advance Agent does </li></ul></ul>
    6. 6. Advance Agent - Features <ul><li>Based on the HTTPCopy Utility </li></ul><ul><ul><li>Restartable copying </li></ul></ul><ul><ul><li>Bandwidth control </li></ul></ul><ul><ul><ul><li>A maximum bandwidth can be specified that will not be exceeded during the copy operation. </li></ul></ul></ul><ul><li>Additionally it can </li></ul><ul><ul><li>Run as a service </li></ul></ul><ul><ul><li>Handle authentication to http location </li></ul></ul><ul><ul><li>Detect presence of http location to restart file copy </li></ul></ul><ul><ul><li>Send status messages </li></ul></ul><ul><ul><li>Use Task completion </li></ul></ul>
    7. 7. Deploying the Advance Agent <ul><li>Deploy to Unmanaged Device </li></ul><ul><ul><li>Just like the Standard Agent </li></ul></ul><ul><ul><li>Relies on RPCs </li></ul></ul><ul><li>Group Policy </li></ul><ul><ul><li>The small size of the agent makes this feasible </li></ul></ul><ul><ul><li>Configure Group Policy Slow Link Threshold </li></ul></ul><ul><li>Logon Scripts </li></ul><ul><li>E-Mail or media </li></ul>
    8. 8. LANDesk Management Gateway
    9. 9. Customer “Pain Points” <ul><li>Need to Manage users outside of the corporation </li></ul><ul><ul><li>without “Punching Holes” in firewall </li></ul></ul><ul><li>Dial up connections </li></ul><ul><ul><li>are to slow, but purchasing a VPN (Virtual Private Network) solution is too expensive </li></ul></ul><ul><li>Distributed sites </li></ul><ul><ul><li>which due to the small size, temporary nature or limited local communication availability the only connection available is an internet link </li></ul></ul><ul><li>Management across the internet </li></ul><ul><ul><li>without compromising the security of the end point or my corporate infrastructure </li></ul></ul>“ RFP for the State of South Carolina, one of the key requirements was to distribute software securely to end points over the Internet ” *State of South Carolina “ Displace the costs of a VPN project for all 300+ of their restaurants, and give them management capability, this would easily build the case for using LANDesk versus another tool” *Outback Steakhouse “ Asked if there is way to utilize the ISS pro technology with a core server and give end point management to nodes over DSL, and Cable modem connections .  A 40,000 node opportunity that has end points that require management through the Internet cloud .” *Sales Opportunity Yellow Region “ Most of their nodes are outside of their network and they have been looking for this solution for a few years, If this functionality was available now I would have a check to give you right now” *David Weekley Homes
    10. 10. “How it works” Ex ample: Outlook Web Access Perimeter Firewall Personal Firewall LANDesk Laptop “ LANDesk Gateway” Managed Devices Personal Firewall Perimeter Firewall <ul><li>Enables communication through firewalls and proxy servers </li></ul><ul><li>Does not require a VPN infrastructure </li></ul><ul><li>Brokers connections and provides authentication </li></ul><ul><li>SSL encrypted </li></ul>LANDesk Corporation LANDesk Core Server
    11. 11. Supported LANDesk Client Features <ul><li>Inventory gathering </li></ul><ul><ul><li>Hardware </li></ul></ul><ul><ul><li>Software </li></ul></ul><ul><li>Software License Monitoring </li></ul><ul><li>On Demand Remote Control features </li></ul><ul><ul><li>Remote Keyboard, Video, and mouse control </li></ul></ul><ul><ul><li>File Transfer </li></ul></ul><ul><ul><li>Chat </li></ul></ul><ul><ul><li>Remote Execute </li></ul></ul><ul><ul><li>Screen Draw </li></ul></ul><ul><ul><li>Reboot </li></ul></ul><ul><li>Software distribution </li></ul><ul><ul><li>Policy based (Client pulls down jobs) </li></ul></ul><ul><li>Security functions </li></ul><ul><ul><li>Patch Management </li></ul></ul><ul><ul><li>Spyware Management </li></ul></ul><ul><ul><li>Security Threats </li></ul></ul><ul><ul><li>Custom Definitions </li></ul></ul><ul><ul><li>Blocked Applications </li></ul></ul><ul><ul><li>LANDesk Updates </li></ul></ul><ul><ul><li>Connection Control </li></ul></ul><ul><ul><li>Anti-Virus Enforcement </li></ul></ul>
    12. 12. Benefits <ul><li>Allows Management of devices without traditional network boundary restrictions </li></ul><ul><li>Gives access to remote computers </li></ul><ul><ul><li>Without investing in expensive point to point WAN infrastructure </li></ul></ul><ul><ul><li>Access to computers over T-1, DSL/Cable, or Dial-up </li></ul></ul><ul><li>Give remote devices access to LANDesk’s most popular features </li></ul><ul><ul><li>Including Remote Control, Software Distribution, Inventory, Software License Monitoring </li></ul></ul><ul><li>Requires minimal hardware investment </li></ul>
    13. 13. Business Scenario Request to Core server as xml sent via http Customer A Customer B Gateway Core Server Client Client Client Client Client Client Client Client
    14. 14. Gateway Machine <ul><li>Runs on LDLinux </li></ul><ul><ul><li>LANDesk’s own Linux distribution based on the Linux 2.6 Kernel. </li></ul></ul><ul><li>Minimal Operating System </li></ul><ul><li>Minimum Hardware Requirements </li></ul><ul><ul><li>P4 Processor (dual processors supported) </li></ul></ul><ul><ul><li>1 GB RAM </li></ul></ul><ul><ul><li>IDE disk drive (SCSI, SATA supported. Hardware RAID is not supported) </li></ul></ul><ul><ul><li>VGA Video </li></ul></ul><ul><ul><li>High Speed NIC (100 mb or Gigabit) </li></ul></ul><ul><ul><li>Bootable CDROM </li></ul></ul><ul><ul><li>Keyboard (mouse not required) </li></ul></ul><ul><li>Private IP ranges and unneeded ports blocked </li></ul><ul><li>Root account is disabled </li></ul><ul><ul><li>Admin account is created with strong password requirements </li></ul></ul><ul><li>Gateway runs as a web service </li></ul><ul><ul><li>Custom built LANDesk proprietary web service (not Apache). </li></ul></ul><ul><li>Configuration performed through web browser </li></ul>Gateway
    15. 15. Gateway Client <ul><li>Uses CBA8 “Unified Pipe” architecture. </li></ul><ul><ul><li>Ensures that all agents communicate using same processes and protocols. </li></ul></ul><ul><li>Uses an http based Proxy Host. </li></ul>Agent Component (example: LDISCN32.EXE) HTTP Proxy Agent Core Server Gateway The agent component is launched. With the Gateway Client installed, the communication in sent to the Proxy agent. The proxy agent determines where to send the communication; either to the core or thru the Gateway. The decision process is configurable through the BrokerConfig utility.
    16. 16. Gateway Client: Secure Access <ul><li>Security is needed since Gateway is built for access over public network. </li></ul><ul><li>Certificate based security. </li></ul><ul><li>BrokerConfig.exe used to initiate authentication to core server through gateway. </li></ul><ul><li>Once authenticated certificate from core is given to client. </li></ul><ul><li>Certificate can be blocked if needed. </li></ul>
    17. 17. Core to Gateway Communication <ul><li>Uses a reverse proxy agent on Core </li></ul><ul><ul><li>Translates requests and processes them </li></ul></ul><ul><ul><li>As though they were locally connected. </li></ul></ul><ul><li>Keeps a minimum of six connections opened </li></ul><ul><ul><li>To receive communication from the Gateway. </li></ul></ul><ul><li>Validates communication by examining client certificate. </li></ul>Request to Core server sent via http Gateway Core Server
    18. 18. LANDesk Software Distribution
    19. 19. Private and Public Ownership <ul><li>Packages and Delivery Methods are now organized with ownership similar to Queries. </li></ul><ul><li>Both can be made publicly available or added to users by the Administrator. </li></ul><ul><li>Private packages can use dependencies. </li></ul><ul><ul><li>Dependency must be a public package </li></ul></ul>
    20. 20. Multiple Queries Added to Target <ul><li>Simple as dragging and dropping of queries. </li></ul><ul><li>Queries are not processed till task is executed. </li></ul><ul><ul><li>Task properties will show queries in the Target Devices window. </li></ul></ul><ul><li>Code has been changed to ensure tasks run efficiently </li></ul>Even though queries have been added as targets, the list of targets is zero. This is because the queries have not been run. Queries on run when the task is executed.
    21. 21. Linux Distribution Packages Added <ul><li>Supports only RPM packages </li></ul><ul><li>Uses a RPM command line format to install the packages. </li></ul><ul><li>RPM files must be downloaded through a web share (MS/Samba shares are not supported). </li></ul>
    22. 22. Database Macro Parameters <ul><li>Allows you to retrieve values from the device’s database entries and pass them as command line parameters. </li></ul><ul><li>Useful for Distribution Packages based on Batch files or Executables. </li></ul>
    23. 23. Reporting
    24. 24. What's New in Reporting <ul><li>Redesigned from the ground up </li></ul><ul><li>Integrated report design tool (“Create your own reports using the LANDesk Report Designer”) </li></ul><ul><li>Reports can be filtered by user scope and e-mailed </li></ul><ul><li>Ad-hoc reporting added </li></ul>
    25. 25. Types of Report <ul><li>Ad-Hoc Reports </li></ul><ul><ul><li>“ View as Report” Option </li></ul></ul><ul><li>Standard Reports </li></ul><ul><ul><li>Cover all aspects of Management Suite </li></ul></ul><ul><li>User Defined </li></ul><ul><ul><li>Based on Inventory Query </li></ul></ul><ul><ul><li>Report Designer Tool </li></ul></ul>
    26. 26. What are Ad-Hoc Reports ? <ul><li>Ad-Hoc reports provide a snapshot </li></ul><ul><li>Report contains same information as screen </li></ul><ul><li>Column Sets may be applied </li></ul><ul><li>No need to define a query </li></ul><ul><li>Useful for producing system documentation </li></ul><ul><li>Not always available </li></ul><ul><ul><li>i.e. Unmanaged Device Discovery </li></ul></ul>
    27. 27. Generating Ad-Hoc Reports <ul><li>Select a Component: </li></ul><ul><ul><li>Network View </li></ul></ul><ul><ul><li>Users </li></ul></ul><ul><ul><li>Software and Patch Manager </li></ul></ul><ul><ul><li>etc. </li></ul></ul><ul><li>Right Click “View as Report” </li></ul><ul><li>View the Report </li></ul><ul><li>Export if desired </li></ul><ul><ul><li>Select a format such as PDF, HTML or RTF </li></ul></ul><ul><li>Print if desired </li></ul>
    28. 28. What are Standard Reports? <ul><li>Predefined Reports </li></ul><ul><ul><li>Built-in </li></ul></ul><ul><ul><li>Arranged by Component </li></ul></ul><ul><ul><li>May not be Customised </li></ul></ul><ul><li>Support Different Output Formats such as </li></ul><ul><ul><li>PDF </li></ul></ul><ul><ul><li>HTML </li></ul></ul><ul><ul><li>RTF </li></ul></ul>
    29. 29. Working with Standard Reports <ul><li>Tools | Reporting / Monitoring | Reports </li></ul><ul><li>Browse and select a report </li></ul><ul><li>Right click and select from: </li></ul><ul><ul><li>Run – Generates a report now </li></ul></ul><ul><ul><li>Publish – Options for location and format </li></ul></ul><ul><ul><li>Schedule Publish – Creates a scheduled task </li></ul></ul><ul><ul><li>Group Membership – Displays other groups containing report </li></ul></ul><ul><ul><li>Copy – Copy a Report to Paste into another Group </li></ul></ul>
    30. 30. Platform Support
    31. 31. Linux Support <ul><li>Linux Version support </li></ul><ul><ul><li>Redhat 3, SuSe 9, Mandrake 10.1 </li></ul></ul><ul><li>Hardware Platforms </li></ul><ul><ul><li>X86 </li></ul></ul><ul><li>LANDesk Products supporting Linux </li></ul><ul><ul><li>LANDesk Server Manager (Redhat, SuSe) </li></ul></ul><ul><ul><li>LANDesk Management Suite (Redhat, SuSe, Mandrake) </li></ul></ul><ul><ul><li>LANDesk Security Suite (Redhat, SuSe) </li></ul></ul><ul><li>Features </li></ul><ul><ul><li>Common Base Agent </li></ul></ul><ul><ul><ul><li>Remote Execute </li></ul></ul></ul><ul><ul><ul><li>File Transfer </li></ul></ul></ul><ul><ul><ul><li>Power Off & Reboot </li></ul></ul></ul><ul><ul><li>Inventory </li></ul></ul><ul><ul><ul><li>Hardware & Software </li></ul></ul></ul><ul><ul><li>Automated Agent Deployment </li></ul></ul><ul><ul><li>Software Distribution </li></ul></ul><ul><ul><ul><li>RPM Distribution </li></ul></ul></ul><ul><ul><li>Patch Management </li></ul></ul><ul><ul><ul><li>Vulnerability scanning </li></ul></ul></ul><ul><ul><ul><ul><li>Redhat & SuSe </li></ul></ul></ul></ul>
    32. 32. Mac OS Support <ul><li>Mac OS Version support </li></ul><ul><ul><li>Mac OS 9.22 </li></ul></ul><ul><ul><li>Mac OS X 10.2.x, 10.3.x, 10.4 </li></ul></ul><ul><li>Hardware Platforms </li></ul><ul><ul><li>G3, G4, G5 </li></ul></ul><ul><li>LANDesk Products supporting Mac OS X </li></ul><ul><ul><li>LANDesk Management Suite </li></ul></ul><ul><ul><li>LANDesk Patch Manager </li></ul></ul><ul><li>New Features </li></ul><ul><ul><li>Mac OS X 10.4 support (Tiger) </li></ul></ul><ul><ul><li>Safari browser supported for Web console (Tiger only) </li></ul></ul><ul><ul><li>OS Deployment </li></ul></ul><ul><ul><ul><li>Profile migration </li></ul></ul></ul><ul><ul><ul><li>Bare-metal provisioning </li></ul></ul></ul>
    33. 33. Misc
    34. 34. Role-based Administration (Ac tive Directory Integration) <ul><li>leverages your existing IT investment in Active Directory for assignment of roles (rights) in the Management Suite console </li></ul><ul><li>No longer required to build/replicate your existing Active Directory structure in the management console users tool </li></ul><ul><li>View Active Directory structures within the Management Suite console </li></ul><ul><li>Assignment of LANDesk rights to Active Directory groups or organization units </li></ul><ul><li>Supports rights inheritance </li></ul>
    35. 35. Local Account Management from LDMS Console <ul><li>Account & group management for customers without Active Directory </li></ul><ul><li>Ability to reset local passwords real-time </li></ul><ul><li>Manage local users and groups with real-time access </li></ul><ul><li>Add, rename, remove, and edit local users and groups </li></ul><ul><li>Reset passwords </li></ul><ul><li>Local account management information is associated with system inventory for queries & reporting </li></ul>
    36. 36. Keyboard Mapping in RC <ul><li>RC machines with different Locale Setting </li></ul>
    37. 37. Fragen ? Applaus !