I've recently had to reimage a couple of PC's.  No hardware has changed with the exception of a HD in one of the machines, hostnames were reused in both instances.......neither of these workstations show up in UDD.  Any ideas?

Running LD 9.50.0.530

I would like to know how many pcs from my Active Directory OU are missing in Landesk .

Additionally I would create a query linked to my AD OU for Patches missing and to have also the pcs where the agent is not installed or are not discovered by Landesk .

thanks

best regards

Question

How does LANDESK UDD and Agent installation tasks use DNS?

Answer

When UDD is ran with the default parameters it will do the following;

1. It will do a ping sweep for the range that you configured

2. It will do a reverse DNS lookup

3. It will do a WINS lookup

For more about UDD: http://community.landesk.com/support/docs/DOC-31606

After the UDD task

During an agent install task (push or advance) we use IPCheck.exe to verify that we are running the agent install task on the correct machine.

IPCheck runs on the client that the agent install task has been pushed to. It runs at the beginning of the installation, and its only job is to verify that the ip address and host name (for that device) match with what we have on record in the database "unmanagednodes" table. IPCheck uses the Windows API gethostname to gather this information from the client. If there is a mismatch with any of this information then the install will fail, and the device(s) will be moved into the pending unmanaged device group.

Database Table:

NOTE -- IPCheck.exe Does not do any DNS lookups. 

Because most environments use DHCP, it is very possible that the database records from the UDD task differ from the device(s) active host name and ip address. A mismatch would obviously have a higher chance to occur if several weeks have passed from the time the UDD task was run, and the time the agent install task runs.

Best Practice

LANDESK highly recommends that your DNS is configured correctly. It is important that your host name, ip address and dns records all match, otherwise you could experience problems with several different components.

Another tip is to run the UDD scan right before running the agent install task. This will ensure that everything is up to date.

I have created a new LANDesk Agent and need to deploy it to some computers in my environment. The issue I'm running into, seemingly, is that when I go to create the Advance Agent distribution, it ends up being an executable around 1GB in size. I am under the impression this file should be around 50MB. When I create the Advance Agent distribution task, it always fails for every computer it's pushed to.

We are running LDMS 9.5 SP1 on Windows 2008 R2 SP1 in a single domain environment. I saw where there was a patch for LDMS 8.8 related to the size of Advance Agents but am assuming this would still be fixed in version 9.5.

So we have one user that seems determined to keep removing the LANDesk agent from his system. He once admitted to me that he looked up on the Internet on how to do it and it took him 6 hours as i was putting back on his system so he could install software he wanted, now it seems he has removed it again. Any suggestions on how we can prevent this or alert us if it is removed again?

Hi,

I have just been given the task of LANdesk operator..

I am attempting to create an installer for windows XPE 2009, however when it runs i get a text file saying done and no icon in the system tray and when landesk scans the machine doesnt have the agent software.

i tried the scheduler to push the agent, but alas i dont have the script to push this to Wyse XPE2009 units...

can any one help?

Easyk

Environment

LDMS 9.x

Question

What are the agent install logs and where are they located?

Answer

Below is a list of log files and their locations that are related to agent install.

Client side logs are located in the Windows\Temp folder or the %temp% folder (depending on how the task was scheduled to run)

Core Side Logs are located in the \ManagementSuite\logs folder

NOTE -- ScheduledTaskHandler_*.log (* references a taskID and you should be sure that you find the one that corresponds with the agent install task) A good way to do this is to look at the time/date modified for the log.

Hello.

We are in a position where we in near future would like to deploy the latest agent to all our workstations in the environment (+10k devices world wide). Most of the devices are currently on a 9.5 SP1 with LDAV+EPS agent and the latest agent will be a 9.5 SP2 with LDAV+EPS and 0417 BASE + AEM patches.

The component I'm worried about when doing this is LDAV. If we hadn't been using LDAV, then reinstalling using the Advance Agent would be quick and easy and it would work almost always, but it's my experience that reinstalling an agent with LDAV can be a little tricky and just reinstalling on top of the existing agent will probably result in various issues with LDAV afterwards (sort of described in the "Uninstall" section here - How to troubleshoot LANDesk Antivirus 9.5).

As I see it, there's 3 ways this can be done:

1. Use the Advance Agent to reinstall. Expect issues with LDAV and repair via "vulscan /removeav" and "vulscan /installav" on devices that show bad or incorrect inventory data
2. Patch the existing agent with Patch Manager using the client side patches for the "LD-95-SP2", "LD95-CP_BASE-2014-0417" and "LD95-CP_AEM-2014-0417" definitions
3. Use self-made agent reinstalling script/procedure that via Patch Manager downloads the full agent installer and script, completely removes the existing agent incl. AV, reboots devices and automatically installs the new downloaded agent

Suggestion 1 requires minimal preparation and is easy to initiate. Downside is that many issues are expected and can take a long time to fix. Can potentially require a lot of manpower.

Suggestion 2 is not something I've done in large scale before. Only tried to install a component patch on a few devices - never tried something large as a service pack for the agent. Looking at the content of the <patch>-client.zip files, I'm not sure if this will actually fully update the agent at all as a file like LDAV.exe is not in the client BASE zip file and files like LDSecSvc64.exe and viguard.exe are not in the client AEM zip file. Will this still require us to reinstall AV and EPS?

Suggestion 3 requires by far the most preparation, but is also the most automated procedure and the end result will most likely be better and require less cleaning up.

How do you guys handle a situation like this?

Thanks in advance.

Overview

The following LANDesk Health Check VBScript will check various components of the LANDesk 8.8 and 9.0 Agent, and if any of the checks fail, will reinstall an Advance Agent.  It will also send an email when a check fails with the log of the failure.

The script is designed to be used in conjunction with an Active Directory Group Policy that runs the script as a Startup script.  This will run with rights from LocalSystem which will get around any issues with UAC or limited user rights.

The script attempts to map a LANDesk Agent Configuration with an Active Directory OU, and can associate different agents with different OU's.  If a mapping can not be made then the default agent is installed.

Configuration

The following items can be configured in the Agent Health Check VBScript:

LANDesk Executables in LDClient folder - If the files are renamed or missing the Health Check fails and the Agent is reinstalled

Local Scheduler Tasks - If the output for the local scheduler is missing the File names that should exist in Local Scheduler output, the Health Check fails and the Agent is reinstalled.

LANDesk Services - The script will check for the existence of LANDesk services.  If any are stopped, the script will attempt to start the service.  If the script is unable to start any of the services the Health Check will fail and the Agent will be reinstalled.

Email Notification - On script failure, an email is sent to the configured addresses with the log file in the body of the email that shows the reason for the Health Check failure.  The email is sent using the existing MAPI installation on the client.

Log location - By default the script creates an LDMSAgentCheck.log file in the %TEMP% folder.  The Advance Agent also creates a LDinstall.log in %TEMP%. The script will also update the Registry in a configured location to add the information to the LDAPPL3 template if desired.

Agent Mapping to Active Directory OU - The script allows mapping between different agents to Active Directory OU's and checks the .0 Certificate file.  If the .0 file is corrupted or missing, the Health Check will fail.  If the Agent Mapping fails to match any OU's, then the default agent install will be used.

LDMSAgentHealthCheck_SQL.zip  Contains updates to the script provided by Shatterstorm. Most notably code cleanup and abiltiy to store Health Check logs in db instead of sending an e-mail.

Agent Deployment for LANDESK Management Suite

General Information

  Standard Push:The agent files are located on the core server and distributed via a push task. The credentials used in the Scheduler configuration on the core server are critical for this type of distribution.

    Self-Contained Executable: Agent files are compiled into a completely self-contained executable that is portable. This method is efficient and helps with a lot of network configurations however the executable does not get updated when the configuration changes or when files are updates by patches or new releases. It is recommended to keep these executables in a central location and perhaps date them as well so that they can be rebuilt as needed. Two self-contained executables are created for this option one with status (shows GUI to the user) and one without.

    Advance Agent: The primary purpose of this agent deployment method is to control the amount of bandwidth used during agent install. However, the design has many other uses. The agent is broken up into two files (and MSI and an EXE). The MSI will install a temporary service on the client where it will gradually stream down the main executable and install the agent. The temporary service is removed. Since the temporary service comes in MSI form this design also makes it favorable for deployment using an Active Directory login script. (Note: Including security definitions with the agent can make the primary executable very large and greatly increase agent download/install times)

     Wscfg32.exe: This is an executable located on the core server in the ldlogon sub-folder. When executed on a client it will pull the settings in a default windows configuration and launch an agent install window. Changes can be made to the configuration before starting the agent install.

     Other Operating System Information: Macintosh and Linux/Unix agents will work somewhat different than Windows based ones. For details on those agents please check their component landing pages.

Supported Platforms and Compatibility Matrix for LANDesk Management Suite

Install and Configuration

• Video:Agent Installation Methods
• Video:Agent Configuration
• Video:Management Suite 9 Fundamentals Agent Configuration
• How to create an Advance Agent
• How to create an Advance AgentDocumentation for Agent Configuration and Deployment (Best Known Method for LANDesk 9)

Troubleshooting and Known Issues

     General Troubleshooting Recommendations:

• The LANDesk agent (just like any other program) can be affected by Anti-virus, Spyware, and other blocking programs. Closing or suspending such programs may help with agent installation.
• When right-clicking on an agent two of the options will be "Schedule agent deployment" and "Schedule update to agent settings". The difference between these two is that the update will not deploy any files and only make changes to when scan run etc. If a new feature is added to the configuration or removed then a full agent deployment will be required.
• If an error occurs during the creation of the agent (advance agent or self-contained) a log file is generated. Typically the agent configuration was told to include a certain file and the process either couldn't find the file or didn't have access to it.
• Troubleshooting Agent Installs

• Advance Agent install process and troubleshooting tips
• Why can't I install the Advance Agent over itself on a client?
• UninstallWinClient.exe may not run correctly on Windows 7 under UAC
• How to completely remove LANDesk from a remote console or client device

Additional Options and Information

• Video:Agent Deployment via Login Script
• Video:Agent Deployment via WSCFG32
• Customizing the LANDesk Agent using the NTSTACFG.IN# file
• How to uninstall the LANDesk Agent on Windows Platforms
• How to uninstall the LANDesk Agent on Macintosh Platforms

Notice:Any E-Learning content is available by default to Members who have a minimum support agreement at Professional level.

NOTE: This article is not a comprehensive list of documents and issues. You can continue to search the rest of the community or the portion specific to Agent Deployment if this page hasn't helped.

I have pushed the agent out to 10 workstations.  3 workstations are complete.   Now I have three that failed Result Code = Unable to contact the specified machine.  The machine may be off or unreachable.  Return Code = 1087.  I have the log file attached.

Then I have 4 workstations that failed with the Result Code = The agent setup succeeded and is now rebooting.  Return Code = 1086.

If someone can tell me where I need to start looking to resolve these and get the agent on them, I would appreciate very much.

Regards

Cathy

Landesk 9.5 SP2 where core was just upgraded from LD 9.0SP2.

Whenever I try and scan a client with Patch and Compliance Scan Now... from the management console, I get this error:unable to load dll 'shutdownreboot.dll': attempt to access invalid address (Exception from HRESULT : 0x800701E7).

I've seen some posts that reference copying shutdownreboot.dll from one dir to another but that same version dll exists in both places for me so that's of no use.

Thanks

Pete

Hello all, I am currently using landesk 9.0.2.3 and I am scanning the network for switches under unmanaged device discovery... While it finds the IP of the switches it does give me any other info.... I am using SNMP which the switches are using as well... Any thoughts?

what does ldiscnupdate.exe do? what kicks it off? why would it be causing over usage of processor for long periods of time

I have three new HP ZBook 15 laptops.   Agents were pushed.   when we launch the inventory scanner on the laptop, we are getting this error.   Close the message and the scan continues.

If we run the task from the console, the task completes with a result of "Not Specified" and correct Last Hardware Scan time of when the scan completed. 

So it appears the task completes if launched from console.  And will complete after you close the error message regarding GetCMSettings.exe.

Thoughts???   This is a new issue for us, but also the first time we've deployed the new ZBooks.

Hi,

I have problem for security scan, i'm use landesk manament 9.5 sp 2, i push landesk agent for endpoint security with three device :

1.Windows XP : so far so good

2. Windows 7 : security scan always failed

3. Windows 8 : same always failed

Thanks for advance....

We just completed upgrading our LANDesk 9.03 server to LANDesk 9.5.3. I am trying to create an Advanced Agent Installer package. There seems to be a problem locating the wscfg32.exe file. The script is calling for one, but I cannot seem to locate any on the server. Does anyone know to correct this problem or how to upgrade the end users agents from 9.03 to 9.5.3.

Hi we used LanDesk years ago, the servers are long gone and the security team wants the LANdesk agent off the handful of XP machines we haven't been able to decommission.  We were running v8.7 - I would be grateful if anyone could provide me with the UninstallWinClient.exe file.

Thanks!

Paul

pgott@edwardswildman.com

As shown below, I have an agent which includes LD AV. This is also set to my default config. No matter how it is sent : As a scheduled task, a self contained installation, or part of an OSD script, almost all of the time the Antivirus portion of the agent is not installed on client machines. The job reads successful, the remote client and it seems everything else is in place... but the most I will see out of antivirus portion is the Landesk Antivirus Service. Multiple repeat installs will eventually yeild proper results... but this is not only tiresome but not at all practicle. All of my clients with 9.0 SP3 agents are unable to be remoted to unless in gateway mode so they need to be updated to 9.5 clients. However I do not want to push a scheduled task to my entire company and then find out 95-99% of them are running no antivirus as a result. Any advise would be greatly appreciated!

I have tried multiple agent configs, both rebuilt old ones that were at one point tried and true and newly created ones and this is still usually the end result.

I'm running LDMS 9.5 SP2.  I'm trying to find someplace that tells me what settings are actually active on the agent that's running on a particular client.  Some things like which inventory settings have been applied (as far as LDMS knows) are available in the inventory but even that may not be accurate if you just recently made changes.  Not to mention that you only get the name of the settings, such as Inventory Settings 34, not what those settings actually are, and if they've recently been changed you can't see if the change is reflected on the agent.  Other settings, such as when policy updates are run, don't seem to be indicated anywhere though (either on the client, or in Inventory).  Am I missing it somewhere, or is what's displayed under LANDesk Management in Inventory the only info that's available?  Right now I'm looking for things like when the last policy update ran, and if possible from the client side, when the next one will run if it was recently rebooted or got a new IP address, but I'm sure that there's other info that would be useful as well.  Is there a registry key or something on the client that holds all of the settings?