6 Replies Latest reply on Mar 18, 2011 1:12 PM by minns

    LANDesk Agent is loaded, but the device isn't in the LDMS


      I finally got around to adding the Macs to the LANDesk family. Sorta. I edited and configured the agent that they are to use. Went to one that we were using as a test platform (a MacBook Pro) connected to the http:\\<CORE>\LDLogon\Mac link. Ran the agent file there (that was a slick install by the way). Rebooted the Mac. Gave it 20 minutes while I put out a fire. Came back - cannot find it in the management console LDMS. I went back to the Mac and opened the agent and ran the software and the standard inventory. looked at the log files on the Mac. Both inventories ran successfully and report their completion to the local agent log - summary. Still no Mac on the management console.

        Certainly, I did something wrong or have something set to not allow macs otherwise they never woulda created a client for them, eh?


      Did I mention that the firewall was totally off on the Mac from the moment that the client was installed?

        • 1. Re: LANDesk Agent is loaded, but the device isn't in the LDMS
          egarlepp Employee

          First make sure you have the latest component patch for the MAC, if you are running v9 SP2.  Here are some important files and locations on the mac for troubleshooting.  I would take a look at the LANDesk Agent.app and see that it has run the appropriate scans.  You can force it to run as well.  Check your Errorscan and ErrorBigScan in LDSCAN folder to see that it hasn't had an issue.  I would also look at the log file for any errors.  Check that you can get to the Mac from the core by putting in http://<MAC IP ADDRESS>:9595 if that pops up then you should be good to go from a network perspective..


          • Library/Application  Support/LANDesk/Bin  -  Location of all things LANDesk on a MAC
          • LANDesk  agent.app –  The LANDesk agent console to see features and settings as well as force running  a software/patch/inventory scan
          • LANDesk  PBD Update.app –  The Software deployment portal on the MAC.  Run it to see what policies are  available on the MAC.
          • LANDesk.log –  the logging information for all thing LANDesk on the MAC.
          1 of 1 people found this helpful
          • 2. Re: LANDesk Agent is loaded, but the device isn't in the LDMS



               We are processing these suggestions. To be honest I know people say that the Mac is the "Computer for the rest of us...", sadly I am not a member of that subgroup and I only recently discovered it runs a Unix/Linux Kernel. So, this may take a bit.


               I did run through the log file and have a couple of things to report. I will add them after this point I would make concerning the conncetivity to the network. I have McAfee's 4.0.0.xxxx agent for sPO release 4.5.x running on that Mac and it has been updating and communicating with the ePO server (which is in the same domain as the LANDesk Core server. With that thought in mind I am certain that the Mac is able to communicate with the network resources if the settings are correct. I also believe that this makes the problem one in which the likely culprit is the LANDesk agent on the Mac itself


              The LOG file is reporting the following:


                Scanning Network

                      Getting AD information from Snow Leopard

                      LDAP Query results: name:dsRecTypeStandard:Computers


                      CN=information not found

                Scanning serial number

                Done with mini scan

            Closing Scan File

            Sending scan file to server <CORENAME>

            Failed to send scan file to server

            Scanning done


               Some agent config issue?

            • 3. Re: LANDesk Agent is loaded, but the device isn't in the LDMS
              egarlepp Employee

              Does the agent have the core server name in it?  Is it FQDN of the core or just the name?  Make sure that the MAC can ping the core using the regular and FQDN.


              Try telnetting to the core over 9535 or 9595 as well.

              • 4. Re: LANDesk Agent is loaded, but the device isn't in the LDMS
                klevitan Specialist

                I noticed that even if I put the FQDN in the agent config, when it gets saved it reverts back to just the server name.  We had to have our network team tweak the DNS to allow clients to find the server since we could not get the FQDN to stick in the client.

                - Kurt

                • 5. Re: LANDesk Agent is loaded, but the device isn't in the LDMS



                     I saw that too. Did you add an A record manually? I can make a change, but since I have a rather large number of people linked to the thing I need to knw a bit more about the specifics of your tweak, please.

                  • 6. Re: LANDesk Agent is loaded, but the device isn't in the LDMS

                    I work with Kurt. We had our networking team add the A and PTR record for our LANDesk server so the hostname was in our default DNS search domain. If everything is configured correctly, you should be able to resolve the IP address of your LANDesk server by typing "host <ldcore-hostname>" into the Terminal.


                    We started with a DNS entry similar to this:

                    • landesk-server.ad.our.university.edu. IN A

                    And had our networking team create the following:

                    • landesk-server.our.university.edu. IN A



                    1. Have your networking team add the search domain of your LANDesk server (e.g. "ad.our.university.edu") into DHCP.
                    2. Run a script on the Mac clients to set the FQDN or IP address of your LANDesk server:
                      • sudo defaults write /Library/Preferences/com.landesk.ldms ServerIPAddress <IP> or <FQDN>


                    I don't recommend the alternatives unless you have no other choice.


                    You can kick off a manual scan by running:

                    • /Library/Application\ Support/LANDesk/bin/ldscan -c <IP> or <FQDN>