I have just upgraded the core server to 2017.3 and will be pushing out the updated agent.  I am planning on including Portal Manager with the agent, but want to do a bit of customization. 

I have been through the Portal Manager agent settings and testing this out on my development server.  Changing the "Taskbar icon" shows what I want it to look like on the taskbar when I preview it.  But, when I save the changes and push it out to a client, the original icon will appear on the taskbar when the Portal Manager is launched.  Also, the icon for the desktop shortcut remains the original one.

I have done an agent uninstall with /forceclean and reinstalled the agent from the core with wscfg32.exe, but no joy.

How can I get this to push out the agent settings the way I want them?  Also, does changing the taskbar icon also change the icon of the shortcut that gets put on the desktop?

Thanks.

Greetings, new LANDesk admin here, question for the group.

What are the most common issues when deploying the LANDesk agent and only some machines are receiving it.  The failures might be related to how some of our machines don't seem to be allowing us to reach the administrative shares on the machines (C$, ADMIN$).  We are also seeing unpredictable responses when we do some NSLOOKUP commands on the troublesome machines so we are looking into possible DNS issues.  If you've rolled out LANDesk client and ran into issues with some of the windows machines in your environment, what did you have to do to fix them?  I don't want to have to install this manually.

Any advice or help is appreciated, cheers!

Hello,

at the moment I'am investigating a alarming situation on all of our 2016 Clients and Servers.

We have very high CPU usage on all of our systems for the tmcsvc.exe (Multicast Services). The Clients work halfway okay with that load - but on our servers I see real performance issues.

We did not even activated Multicast in our Distribution and Patch Settings - so I have no glue where the high cpu comes from.

Perfmon shows me high read/write Operations accompanied by the high CPU peaks.

I would be happy about any advice what is happening here, and what options I have to stop it.

Best Regards, Marco

Hello,

I've recently been confronted to an issue with agent deployment using UDD. (Landesk version 2016.3 - 10.1.0.168)

I've deployed many agents using UDD, browsing through the Active Directory to get the right scope.

The scan works fine, it discovers the targets, but when I drag them to the deployment task, they're not displayed properly. The task show that there isn't any target.

The thing is, when I click on the task properties, I can see all my targets, but they are not displayed when I select the task from the scheduled tasks tab.

Even when I start the task, there isn't any result, it seems like it's working for a while but nothing changes.

The others tasks works fine, when I drag targets that have an agent in any tasks, it works fine, it's only when I run an UDD scan, then drag the targets to the agent deployment task that I have an issue. I've tried to create another task but it's still the same.

How can I handle this issue ?

Rebooting the core server is kind of tricky, as there is hundreds of tasks running 24/7. Is there another way ? Like restart only a service that will not stop the other running tasks ?

Thanks in advance

So if anyone else is having this issue or seeing it I have found something that i wanted to see if i can get a correlation to.

We have random agents that have CBA not loaded - this is causing issues with our depolyments / patching

I have a full clean uninstall powershell script which REALLY cleans the machine and reinstalls the agent - this was not helping

So i tried the removal script again but before removing and reinstalling the agent i deleted it from the Database first. This worked.

I then decided to just try deleting the machine from the Database  - next time i found a machine with the issue. And NOT touching the agent install in anyway.

I then ran a full sync scan manually from the client from the cmd line.

To my surprise when the machine came back into the DB the CBA was fine?

So it appears to be linked with the DB - my question is what in the DB is linked to the agent reporting CBA not loaded? the IP was all the same so it was not that.

This is great as we dont have to remove anything but i am curious to why this is and maybe there is a way or just removing a DB entry rather then the entire Device to fix the CBA -

This of course is in our environment it may be different for others.

Hello,

I have installed latest update of IVANTI2017-3

SInce this update all my agent push installations failed.

Can you help me out please ?

Check the LOG:

Fri, 23 Feb 2018 12:13:40 GATE2-VCENTER Done: retCode=-1 mStatus=3 mRetCode=1087

Fri, 23 Feb 2018 12:13:40 Task complete, status 7

Fri, 23 Feb 2018 12:23:57 Processing task 545

Fri, 23 Feb 2018 12:23:57 Processing task 545

Fri, 23 Feb 2018 12:23:58 1 machines targeted to task

Fri, 23 Feb 2018 12:23:58 Getting handler associated with scheduled task.

Fri, 23 Feb 2018 12:23:58 1 machines for taskID 545

Fri, 23 Feb 2018 12:23:58 Remote operation timout = 1200

Fri, 23 Feb 2018 12:23:58 Reset remote operation timout = 1200

Fri, 23 Feb 2018 12:23:58 Building LDMS old client setup package using wscfg32.exe: C:\Users\ivanti\AppData\Local\Temp\tmp9454.tmp Log: C:\Program Files\LANDesk\ManagementSuite\log\cab_545.log params=/noreboot /configlog /noui /f /c="Default Windows Server Configuration v2.0.ini"

Fri, 23 Feb 2018 12:24:41 Configuring client config thread limit to 1

Fri, 23 Feb 2018 12:24:41 GATE2-VCENTER Sending C:\Users\ivanti\AppData\Local\Temp\tmp9454.tmp to C:\$ldcfg$\tmp9454.tmp

Fri, 23 Feb 2018 12:24:41 GATE2-VCENTER creating dir C:\$ldcfg$

Fri, 23 Feb 2018 12:25:13 GATE2-VCENTER RemoteExecute failed retCode=-2147482239, No response from the target machine. Some common causes are the machine is either has IP change or DNS issue or powered off or disconnected from the network. Did you set scheduler service running with the account that can remote execute the target machine?

Fri, 23 Feb 2018 12:25:13 GATE2-VCENTER Done: retCode=-1 mStatus=3 mRetCode=1087

Fri, 23 Feb 2018 12:25:13 Task complete, status 7

This is a WIN2012R2 Server. The DNS is ok. The IP is ok.

Hi everyone,

I have some questions regarding the deploy of a linux agent on a SUSE Linux unmanaged device.

- It is possible to deploy an agent without a direct connection to the core server?

- It is possible to use ldiscan.sh to create an inventory file to later import it in the core server?

This is because i need only the inventory on a few machines on separate network and i would like to have all device inventory in one place.

I have already tried to manually run ldiscan.sh but while trying to solve all library prerequisites but it gave me this error:

Thanks everyone in advance.

Hello,

In my case: The server which needs to install agent necessary use .NET V.4.5.2 for the specific program.

so  I want to know..

Q: The agent will use .NET V.4.5.2 (existing) or download higher version to use?

Q: How can I check the agent that installed used what version of.NET?

Regards.

Environment: Various

Question:

How to uninstall the Ivanti / LANDESK Agent for Windows ?

WARNING: DO NOT use the switch /FORCECLEAN switch on a Core Server / Service Desk server when removing the Agent for Windwos from the Windows Server as this will break the Core Server / Service Desk Server !!!!!!!!

Answer:

Run UninstallWinClient.exe. This program is located in the ldmain share on the Core Server by default (C:\Program Files\LANDesk\ManagementSuite\ldmain). It can be run from that share or copied to the local client and executed. It is a standalone program and does not rely on any other files in order to run. UninstallWinClient.exe removes the Agent for Windows only.

By design, UninstallWinClient.exe will remove:

• All Ivanti / LANDESK files except some in ‘all users\application data\’ such as the APM DB

• All Ivanti / LANDESK start menu shortcuts

• All Ivanti / LANDESK services

• All registry values and keys except the common API keys containing the LANDESK GUID

UninstallWinClient.exe has the following command-line options:

If you want to uninstall the agent remotely, UninstallWinClient.exe can also be deployed as an Executable Distribution Package.

• No additional files need to be added to the distribution package.

• It's recommended to use the /NOREBOOT switch in the package if there is an end user using the client so that the machine doesn't reboot and cause the user to lose work.

• When you distribute this package, the agent will be uninstalled ,but the status of the task will remain "active" until it times out and eventually fails. This is because the agent is no longer able to report status back to the core.

If UninstallWinClient.exe is failing to remove part of the agent and is causing problems:

• Try the version of UninstallWinClient.exe from the newest service pack.

• Notify customer support.

Related questions:

• How to uninstall the LANDESK client without rebooting?
• What are the UninstallWinClient.exe command line options?
• Is there a way to clean most of the Ivanti / LANDESK remnants after /ForceClean has been used?
  • Yes, merge the attached LANDESK Remnants Removal.reg to the machine(s) where the Ivanti LANDesk agent is removed with the swich /FORCECLEAN has been used.
    • To view the LANDESK Remnants Removal.reg contents, open the file with your favorite text editor.
    • To create your own registry removal.reg, please see Microsoft's article "How to add, modify, or delete registry subkeys and values by using a .reg file".https://support.microsoft.com/en-us/kb/310516

Related errors:

• Xtrace log shows : FAILED: bCriticalError is true. Setting exit code to ERROR_INSTALL_FAILURE

Bonjour,

La tâche planifiées de mise â jour des paramètres de l'agent est bloquée depuis le 22/03/2018 avec un ordinateur qui reste en actif et 1000 en échec (agent non joignable).

Je ne sais pas comment la débloquer ni supprimer la tâche.

Dans l'attente d'une réponse.

cordialement

Landesk Management Suite 2016 (10.0) is using a new service called "Self-electing subnet services" (SESS): https://help.landesk.com/docs/help/en_US/LDMS/10.0/Default.htm#Windows/client-c-self-electing.htm%3FTocPath%3DConfiguration|Agent%2520configuration|_____9

Under some specific circumstances SESS service may cause very high CPU usage in client machines and servers, sometimes intensive multicast network traffic is experienced as well (even if you have not configured your Agents to use Multicast).

Such incorrect behaviour can be identified by checking your Task Manager or Process Manager - you will see Targeted Multicast Client Service Executable (tmcsvc.exe) generating CPU load.

Solution:

Please first check the agent configuration settings for distribution and patch as 'tmcsvc.exe' can be used in multicast and peer-to-peer deployment, so on the agent settings set up for the agent configurations of the clients, you can disable "Attempt peer download" and "Use Multicast" (this can be found in Agent settings -> Distribution and Patch settings -> General settings -> Network Settings).

It will update all the clients at the next daily vulnerability scan run on the clients where this settings is configured.

If the above settings are not used (configured) then SESS can be deactivated in the agent "Client Connectivity Settings" set up on the agent(s) deployed on the clients.

To do that, go to Tools -> Configuration -> Agent Settings and then click  'Client Connectivity' settings and open 'Self-electing subnet services' tab and uncheck box "Enable self-elect subnet service", click 'Save'.
At the next daily vulnerability scan, on each computer having this settings, it will deactivate this option (alternatively you can create a task to deploy updated agent settings to the clients).

Once this is done please check if the the CPU load from tmcsvc.exe has decreased on the agents.

Additional information:

You can also go in the Management Console -> Tools -> Configuration -> Self-electing subnet services -> Select Extended Device Discovery on both LAN/Wireless -> Right-click each subnet and select disable (by default SESS is disabled for wireless networks but enabled for wired networks).

Some additional information on this topic can be find here: Agent 2016 - Targeted Multicast Client Service Executable - tmcsvc.exe very high CPU on all clients/servers

Hello everyone,

I am a new Ivanti user and this is my first post.

I am on EPM 2017.1 SU (2017-0627D), on a Windows 10 Enterprise x64 client the self-contained agent installations fails, it hangs on "rainstall.exe".

I attach wscfg32.log file retrieved from the client.

I really appreciate any useful information or tip on how to "fix" this issue.

Bye

Andrea

Hello,

after upgrading agents to 2017.3, when running inventory scan, many computers experience error  MBBScanner has stopped working.

Event viewer shows the following:

It has not happened on my test machines. So far I have disabled the Scheduled scan, but this is not a solution.

Thank you for any input or suggestion how to resolve this.

Hello,

I'm currently deploying Ivanti Endpoint Manager 2017.3 for one of my customers and the customer wants to have the ability to manage computers which are not on the domain and not on the LAN

We already deployed the Ivanti Gateway so we are able to have remote control on computers with the agent already deployed.

We installed the agent directly from the workgroup computers, agent is in Gateway mode, but the computer don't appear on the Ivanti console

Do we have a specific action to do in order to have this configuration working ?

Thank you,

Regards

Hi,

We have a problem that after installing the LANDesk Agent to Windows Server, the MS Visual C++ 2013 is removed and the new MS Visual C++ 2015 x64 is installed instead. This cause the existing applications (CommVault) on the server cannot operate as normal. So, the server is needed to be re-installed/restore.

Please advice how can we install the agent without removing the existing MS Visual C++ 2013.

Regards,

Paisan P.

The user of schedule Service is Administrator on End Point. The endpoint is on ping, the DNS is ok  and i can share c$ with this user. Any idea ?

Advance Agent Creation

Two files are created when and Advance agent is created on the core server.

• <advance agent name>.msi
  • This is a ~1 MB MSI package. When this package runs on a device it installs the LANDESK® Advance agent service. The Advance agent service downloads the associated full agent configuration package and initiates the install.
• <advance agent name>.exe
  • This is the real agent installation file and it will call wscfg32.exe to install the LANDESK agent.

When creating an Advance agent, the dialog prompts for a path and a name for the Advance agent configuration. The path and name of the agent configuration are coded into the MSI along with the hash value of the EXE. The Advance agent service will use the name and hash to determine the package to download and install. In the Advance agent configuration window bandwidth-friendly distribution options can also be configured. All settings configured in the Advance Agent dialog are included in the Advance agent MSI and are used by the Advance agent service after the MSI is installed.

Deploying the Advance Agent

The Advance agent can be deployed a few different ways. One is to create an advance agent push job from the LANDESK Management Suite Console. This job can be created from the Scheduled Tasks pane.

Deployment Steps

1. When the Advance Agent Push scheduled task is started from the core server, the LANDESK scheduler service will create $LDDIR$ folder under C drive on the client and will copy AdvanceAgent.msi to this folder.
2. Msiexec.exe will run this AdvanceAgent.msi. This will create C:\Program Files\LANDESK\LDClient folder and will install AdvanceAgent.exe and other files to this folder.
3. AdvanceAgent.msi will install the advance agent registry keys,install the advance agent service, install the files to C:\Program Files\LANDESK\LDClient folder, open the firewall policy for AdvanceAgent.exe and so on. And the AdvanceAgent.exe will download <advance agent name>.exe
   Note: An AdvanceAgent.log for this particular step will be created on C:\Windows\TEMP\ folder.
4. AdvanceAgent.exe will create a service called "LANDESK Advance Agent". This service will create C:\Program Files\LANDESK\LDClient\sdmcache\ldlogon\AdvanceAgent folder and download <advance agent name>.exe to this folder.
   Note: Another AdvanceAgent.log will be created for this step under C:\Program Files\LANDESK\LDClient folder. This log file will log the download process.
5. After the <advance agent name>.exe is downloaded to the client machine, Explorer.exe will execute the file, then wscfg32.exe will install the agent.

Troubleshooting

There are two logs on the core that may be useful for troubleshooting advanced agents that fail coreside:

• \Program Files\LANDesk\ManagementSuite\log\core.secure.dll.log
• \Program Files\LANDesk\ManagementSuite\ldlogon\AdvancedAgent\(((AgentConfigurationName)))).exe.log

There are two log files on the client machine for advance agent deployment:

• AdvanceAgent.log under C:\WINDOWS\TEMP folder, this is the log file for advanceagent.msi. After the deployment, this log will not be deleted.
• AdvanceAgent.log under C:\Program Files\LANDESK\LDClient folder, this is the log file for LANDESK Advance Agent service, this will log the download of the EXE file. After the EXE file is downloaded successfully, this log file will be deleted. But if the EXE file is not downloaded successfully, the log file will be there.

Here is a screenshot of these files:

I have the process monitor capture file, IF anyone is interested in researching this, I can offer the file(It's huge, about 400mb, so I can't attach it in this article)

I also attached the AdvanceAgent.log file under C:\WINDOWS\TEMP folder for an example.

Hi,

I'm running LDMS 2017.3 SU1 and must install LANDesk agent in Windows server 2008/2012 that run dotnet 3.5, 4.0.

The server team they don't want to install dotnet4.5 on their servers. How can I  install agent without dotnet or any suggestion?

Thank you.

Hi,

We need to install LD 2017.3 Agent onto 400+ Windows Servers for our customer. The main point is that how can we ensure that there will be no impact to the existing Windows Servers after installing LD 2017.3 agents. Please advice...

1. Will LD 2017.3 agent remove any Windows servers file/components? This might cause the existing applications running on Windows servers not function properly.

2. Can we skip the MS Visual C++ 2013 x86 component (one of the LD 2017.3 agent component) from installing with the LD Agent? Will there be any impact to the LD functionality of not installing this MS Visual C++ 2013 x86 component?

3. What are the files/components of Windows Server be uninstalled after installing the LD 2017.3 agent, if any?

4. How can we ensure that the LD 2017.3 agent will not remove any Windows server files/components?

Please advice.

Regards,

I have accidentally deployed the workstation agent to a bunch of servers, but now when I install the server agent over the top of the workstation agent services are missing. (Using the self-contained .exe method.)

Specifically, the LANDesk(R) Management Agent (CBA8) is missing.

I can re-register the service with "%PROGRAMFILES(X86)%\LANDesk\Shared Files\residentagent.exe" /register but why must I do that? Is this a bug? How am I supposed to reinstall the agent properly? Must I uninstall it and reboot first?

I'm running Ivanti EPM 2017.3 SU2