Quantcast
Channel: Ivanti User Community : Popular Discussions - Agent Deployment
Viewing all 8000 articles
Browse latest View live
↧

Agent installs but taskbar icon not there

August 24, 2012, 5:59 pm
$
0
0

LD9 SP3

Every now and then a agent installs but the issurer icon does not show in taskbar and is not listed in notification area and in the landesk console only the remote shows.

On the client all services including residentagent are running and all landesk processes are running.

A reinstall does not fix it.

Why it causes a problem is because all installs are done remotely. The users do not want  to be bothered with a complete uninstall and then a install. If i could push a registry fix or something that would help.

Also in hklm\software\intel\landesk\  there is a entry to show in taskbar and it is a 1 (which i believe is correct)

Anyone had this and a fix for it?

↧
Search

Duplicate ID's

November 6, 2014, 2:44 pm
$
0
0

If an agent is detected as a duplicate, can the agent automatically regenerate a new ID?

 


↧
↧

How can I update Landesk Agent settings on an existing Landesk client

October 2, 2013, 12:04 pm
$
0
0

I am running landesk v9.5 with sp1.  I have distributed my landesk agent via UDD.  However now we have added branding to the agent configuration and want to apply these changes to the existing workstations with the landesk client on them.

 

I've modified the agent configuration and selected the "Rebuild all" option so that my settings are written to the advanced agents.  I've tried to right click the Agent Configuration and choose "Schedule update to agent settings".  I run the scheduled update to some test workstations, but it doesnt seem to do anything.  I would rather not have to push the whole agent to the workstations again. 

 

So, how can I get this to work and what is the best procedure to update my existing agents with specific settings that I have changed?

 

PS..I'm not referring to any patches downloaded from Landesk.  Only for agent settings we have changed.

↧

what is "Schedule Update to Agent Settings", really?

April 25, 2012, 2:05 pm
$
0
0

RE:  LDMS 9.0SP3

 

So this is sort of a two-part question:

 

part 1)  lets say I use a single agent config across my deployment.  If I decide I want to add something like Power Management to the Agent Configuration I know how to do that.  My question is this:  do agents that are already in service check in and see that their agent configuration has changed and in this case they would download the appropriate Power Management settings?

 

-I'm pretty sure the answer to this question is NO, so I'd then like to ask "why not?"

 

 

part 2)  I see the option under AGENT CONFIGURATION - > SCHEDULE UPDATE TO AGENT SETTINGS.  What does this really do?  How is it really supposed to be used?

 

-I scheduled one of these in a two-agent config environment and simply assigned all of my clients to the task thinking that only the agents using the one config would update their settings: WRONG! It looked like all of my agents got overwritten, even the ones that were not using the agent config that I wanted updated.  I feel like that I have to be deliberate and manually update my agents when I decide I need to change something and this just seems wrong to me.  Shouldn't this just be an automatic process?

 

 

 

 

 

Anyone have any thoughts on this?

 

a few somewhat related posts on this topic:

no replies here

http://community.landesk.com/support/message/72972#72972

 

this one doesn't really have qualfied advice; why do you sometimes have to redeploy the agent vs just updating?

http://community.landesk.com/support/message/18777#18777

 

this one seems to have the most useful information, but it doesn't really explain what happened in the 2nd part of my scenario above.

http://community.landesk.com/support/message/40082#40082

↧

Certificate-based authentication failed - certificate not presented

May 2, 2017, 11:54 pm
$
0
0

Hello,

 

We have recently upgraded to LANDesk 2016.3 and are in the process of deploying the updated agent to all the machines. Im very new to this Certificate-based authentication.

Once the agent has been deployed i have been going into Configure > client access and approving all the  machines. There are a number of machines that show as Authentication failed and when checking the query the certificate validation result shows as either Pending approval or certificate not approved.

However when i check the approved list in Configure > client access those machines have been approved.

How can this be fixed so they all have valid certificates?

 

Thanks,

↧
↧

How changes to Agent Configurations and Settings are propagated to clients?

June 11, 2015, 10:31 am
$
0
0

I changed some settings in my Portal Manager in Agent Settings, this is part of a deployed Agent Configuration, after I saved the changes, how do I push those changes to the clients?

I set the auto sync to Yes, in both the Portal Configuration an in the Agent Configuration, do I have to wait x amount of time for the changes to be sync? Or auto sync is for a complete different task?

I ran a update to agent settings task which ran successfully, but the changes to the portal are not reflected. Any idea?

 

Thank you!

 

Message was edited by: Carlos Sosa Changed the title to reflect the point more accurately. Auto Sync refers to a different thing (Between Cores and not Agent settings). Thanks to @JonnyB for his help understanding this.

↧

What is the Agent State Service in Client Connectivity Settings/SESS?

October 26, 2017, 6:40 am
$
0
0

Just upgraded to the latest 2017.3 for IEM and there was a new option in SESS for "Enable Agent State Service". I cannot find anything on the community or release notes to detail what this does, but it is enabled by default.

 

SESS_AgentState.PNG

 

I can tell it added a new item in Inventory, but outside of that nothing. Anyone have any information on this?

AgentState.PNG

↧

Self-contained agent installation fails on a client

March 9, 2018, 5:57 am
$
0
0

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

↧
Search

Ivanti agent Configuration-settings-Need info

April 4, 2018, 4:04 am
$
0
0

Hi

 

I Would like to deploy Ivanti Agent to all my client machines and i have few query related to it

 

I want to install Agent with only Inventory settings, I dont want to use other settings, how can i disable other settings on agent configuration

 

What are the basic necessary settings?

 

What is the recommended settings on Agent for low bandwidth/network utilization?

 

If a machine is disabled or removed in Active directory, how to disable or remove it automatically from Ivanti Manager?

 

 

 

 

Thanks

↧
↧

Agent deployment : Return code 1083. How can I resolve it?

June 18, 2013, 12:09 am
$
0
0

Hi,

 

I've deployed my agent on 50 computer, but one of them return the 1083 error code.

He have the same configuration, everything is ok, I don't understand.

The firewall is OK, DNS is OK, Scheduler account is OK...

 

Can you help me please?

 

Thanks.

↧

Standard Agent Push Failure

February 1, 2018, 1:31 pm
$
0
0

I'm running Landesk 2016.3

 

 

Just upgraded to 2016.3 and was trying to get all my clients agents updated. Thought I would put down some of the problems I ran into.

 

 

1. After pushing out several 1000 scheduled agent push about 30% of my clients failed. What I've done to fix it is go to Windows\temp, delete anything related to landesk and also any .tmp files, plus a $ldtmp$ folder. Then run again, I got 100% success.

 

 

2. Tried running a scheduled Advanced Agent on 300 computers. 80% failed and removed the management agent leaving the remote service still running. Now I think I'm screwed as no push will go to client with management agent missing.

I set up PSEXEC  to run a bat file remotely to the client to run the cb8inst.msi from the remote computers ldclient folder, this reinstalls the management agent service. However the in the shared files\cbaroot\certs folder it does not put back the certificates so a inventory will not run. I copy the certs from my computer over to the remote computers certs folder. So now the computer is communicating to the console again. I go into the windows temp folder and do #1 above then scheduled a agent push and all is updated.

 

This is not a question just thought it might help others.

↧

Ivanti2017-3_SU3-Client patch not detected

April 16, 2018, 6:42 am
$
0
0

Hi,

 

I test Ivanti EPM 2017.3-SU3 deployment.

 

After installation to the core server, agents don’t detect “Ivanti2017-3_SU3-Client” patch because the command “IsServiceUpdateInstalled=VerifyFileVersionCore("LDInv32.exe", "10.1.31.63", "10.1.31.999", "c")” doesn’t return the good value.

On the core server, version of LDInv32.exe is 10.1.31.63, but in the core inventory data the version is 10.1.31.58 !

 

Regards

↧

Linux Agent install no core connection

February 23, 2018, 8:28 am
$
0
0

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:

Capture.PNG

 

Thanks everyone in advance.

↧
↧

Agents On An Image

May 6, 2011, 2:05 pm
$
0
0

I've seen this in various docs but still don't have the definitive answer.

 

We build our Windows 7 images, add applications and config, sysprep and then capture the image. With some of my other agent based software, the vendor gives us registry keys to delete or modify so that when we set up the machine for the user, the correct information will be there...no duplicates, etc.  Note that I'm not using LD to deploy the OS.

 

For LD, I've seen: "Can't use an agent on an image" or "change these reg keys" or "sometimes it works, sometimes not", "Forget about it, just do an unmanaged device rollout when the machines are on the domain."

 

So which way to go here? We are now creating student images for our summer rollout.

 

Thanks.

↧

Agent install via GPO fails with error 1612

August 14, 2013, 1:04 pm
$
0
0

I used the 'LanDesk best practices for agent deployment guide' in order to create a group policy to deploy the agent. I've moved my workstation into the test OU and rebooted but LanDesk did not install the agent. Windows Event Viewer reports the following error:

 

The install of application 'Advance Agent' from policy 'LanDesk Agent Deployment Policy' failed.  The error was : %%1612

 

Anyone deal with this before? A quick search didn't reveal any other usefull threads.

↧
Search

Unable to get or apply Agent Settings

August 11, 2017, 8:52 pm
$
0
0

Can anyone help with this problem - or has anyone else seen it.

 

We are migrating our Agents over from a 95 core and this is what we see.

 

A fresh machine and fresh install no problems.

 

I run a uninstallwinclient with forceclean and registry clean, directory clean so there is no trace of the agent.

 

When we install the 2016 agent we can scan it from the console, but if i scan it in a task i get this error.

We can run a repair job for patches however it will return this error - the part of the log file that is the issue is this.

 

 

 

Fri, 11 Aug 2017 20:31:48 Calling 'ApplyBehavior' in 'C:\Program Files\LANDesk\LDClient\InventorySettingsBehavior_Apply.dll'

Fri, 11 Aug 2017 20:31:48 SOFTWARE\LANDesk\ManagementSuite\WinClient\IncludeNET registry value is 1 so we need to check if .NET 4.0 is already on the client or not

Fri, 11 Aug 2017 20:31:48 Already have .NET installed so skip it

Fri, 11 Aug 2017 20:31:48 InventorySettings_Apply.dll Failed to load our behavior from 'C:\ProgramData\vulScan\InventorySettingsBehavior_VM841_v575_38F14.xml'.  Returning failure

Fri, 11 Aug 2017 20:31:48 ERROR: failed to 'ApplyBehavior' for InventorySettingsBehavior, ID VM841_v575_38F14

Fri, 11 Aug 2017 20:31:48 Checking whether to unzip 'C:\ProgramData\vulScan\ClientConnectivityBehavior_Apply.zip'.  Force: false

Fri, 11 Aug 2017 20:31:48 GetFileHash: could not find "C:\ProgramData\vulScan\ClientConnectivityBehavior_Apply.zip"

Fri, 11 Aug 2017 20:31:48 Calling 'PreApplyBehavior' in 'C:\Program Files\LANDesk\LDClient\ClientConnectivityBehavior_Apply.dll'

Fri, 11 Aug 2017 20:31:48 Client connectivity settings pre-apply dll

 

The settings file is downloading from the core - the XML file is on the client

 

I have tried replacing the inventorysettingsbehavior_apply.dll from a working machine. No joy.

 

I have resaved the agent settings - no joy -

 

the problem is this fail in the vulscan.log file will send a fail status back to the core.

 

out of 300 machines 135 of them behave like this. so from a status stand point it looks bad - these are the 300 first machines we are cutting over -

 

Landesk is saying to recreate the agent from scratch and all settings which i am reluctant to do as i have already tried brand new settings and the agent we have works on a fresh machine - we even see it working on machines that have been cut over but the majority are failing with this error.

 

if anyone can chime it would be greatly appreciated - the call is still open with landesk support also just seeing if the community can help.

↧

Authentication issues after enabling Client certificate-based security

January 8, 2017, 3:37 pm
$
0
0

Recently we upgraded LANDesk in our dev environment.

 

In the "Choose your own adventure" path, we went with Method 3 - Clean Core Server Install with an Upgraded Database

To get to this point I

- Created a new VM with a different name (oldcorename vs newcorename)

- Ran through installation for 2016.3

- Upgraded database

- Recreated all new agent settings

- Deployed agent to workstation which has had the agent removed via uninstallwinclinet.exe /forceclean

 

After installation, I enabled the new client certificate-based security. I can confirm my client has the latest agent but in inventory under LANDESK Management > Client certificate-based security > Authentication Status the Certificate validation result key shows Certificate Not Present and it says authentication failed on the core.

 

CBA is installed and working as intended. I am wondering if the certificate being used is the one generated by the old core name...but the new core is showing successfully validated

 

Any tips?

↧
↧

Laptop agent and CSA

July 29, 2015, 8:48 am
$
0
0

Hi,

Can anybody help with this. I installed our laptop agent on a laptop and I want to deploy software to the laptop if the user is on their home network/wifi.

I am testing the laptop with a hotspot connection but when i do an inventory scan it cannot find the core server. I figure the easiest way to deploy software would be through the Portal Manager.

Any ideas? Any settings with the laptop agent that need to be changed?

 

Thanks

↧

Certificate-based authentication failed - certificate not presented

May 2, 2017, 11:54 pm
$
0
0

Hello,

 

We have recently upgraded to LANDesk 2016.3 and are in the process of deploying the updated agent to all the machines. Im very new to this Certificate-based authentication.

Once the agent has been deployed i have been going into Configure > client access and approving all the  machines. There are a number of machines that show as Authentication failed and when checking the query the certificate validation result shows as either Pending approval or certificate not approved.

However when i check the approved list in Configure > client access those machines have been approved.

How can this be fixed so they all have valid certificates?

 

Thanks,

↧

How do I deploy agents to 32 bit XP legacy devices.

January 10, 2017, 12:44 am
$
0
0

Hi

 

We are running tests with LDMS 2016 and have created a standard agent for deployment.

The agent deploys without problems to WIN 10 and Win 7 clients,

When the standard agent is deployed to WIN XP 32bit device we receive a failure message with Return code 1094 - I can see no record of this code.

The message in the result box advises that "Devices running Windows 95, 98, NT4, 2000 and XP/2003 require a legacy or previous version management client"

 

Is there any way to use an older agent and get this to report back to the 2016 core ?

 

Any advice would be appreciated.

↧
Viewing all 8000 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>