I'm running 2016.3 no patches
When I try to push out a updated Agent I am getting a lot of failures. So I made a batch file to run the self-contained agent with domain admin credentials and I have better luck with it,
More then half the computers are logged in as power users and fail the conventional agent push. so I'm assuming the Normal agent push is trying to use local system credentials is trying to access a remote share.
1. Is there a way to change what credentials the agent runs under?
I have a machine that has agent installed fine, is displaying in the all devices. However i have noticed that the remote agent control status has not been loaded. When i run a scan from the machine itself it seems to work and data has been sent to the core server. When i run a scan from the LDMS server console it fails- cba8, unable to contact the remote agent
when i do a repair job it says straight away- Cannot Find Agent
The agent has been removed and re-installed. Same agent version as other machines.
i have re ran the cba8inst.msi file no issues.
Cant do any repair jobs or scans from the LDMS?!?!?
Any help would be appreciated. **(FYI-im away next week so no reponse until the following week)**
Hi,
I have been handed the role of Landesk.
Now with the write filter disabled i can easily push the agent to the Wyse OS Embedded unit.
now with the writer enabled, a few odd things happen.
1.) files are copied successfully - Odd because when the unit reboots the files will be gone
2.) an attempt is made to disable the write filter which natural results in a failure.
Is there a way to alter the embedded agent installer
1.)Disable the write filter first, using the correct command line.
2.)Copy the files to the wyse unit
3.)Install the embedded agent (with the updated command line strings for the write filter)
4.)Renable the write filter
failing that, anyway to setup the windows agent to do the above?
Thanks
Derek
Can you anybody provide me a copy of UninstallWinClient.exe? I have a server that used to be managed by another company that used LANDESK and I have been trying to remove it with no luck. my email is sarnold@jdvhotels.com
Thanks
Hi all,
Sorry to start a new thread on a old subject but this is really starting to stress us out. In a previous thread I discussed that problems we were having with deploying the AA. Comments pointed to a possible issue with our GPO settings and recomendations were that we needed to capture the MSI logs to assist in troublehsooting. I've followed these steps but as luck would have it the test machines used didn't have any problem.
We have since moved on with the assumption that this was an isolated case and are starting to redeploy the AA using GPO. However now I've got another PC where the same problem as before is happening (please keep in mind that 27 other PC's have installed via GPO without any issue). The issue is that the MSI launches and then calls the exe as expected but then the process "Templdtemp.exe" will sit at 50% utilisation without anything else happening. We've left the machine for up to fours hours with nothing changing. If you reboot the process simply comes back again.
I've killed the process and cleaned up all directories and even removed the machine from the domain and back again. Then tried to do a manual install and the same thing happens. This machine has the same SOE as our others and no obscure software is running.
Can anyone please shed some light on this problem?
Thanks
Hello,
I would like to know how to disable pxe boot from the landesk server, so it stop working. As I have another product to use for deploying images through the network.
Thank you
Edwin
Does anyone have any experience they can share regarding the LANDesk Agent, LANDesk AV and VMWare Linked Clones?
Hi,
When i try to install the agent on an HP t520 Thin Client, nothing happens and it creates a text file called "LandeskClientInstallStatus.txt" with this inside.."Done 643 130839641112355039"
Any ideas?
Thanks
which agent i should push
Whether server or workstation, re-install of 9.0 or my move to LANDesk 9.5. The LANDesk agent install of the Visual C++ library hard-locks the system.
I have to comment out to execution of the library install in the ini configuration file in order to keep systems from locking up during the migrations.Is anyone else having this problem or noticed this? I'm sure if a support ticket is the appropriate channel for this.
Hello everyone.
I would like to comment a weird behavior that I have found when deploying landesk agent via push.
Sometimes I have deployed the agent and the task gave me a 1087 return code ("Unable to contact to the specified machine"). These devices are in a domain and the scheduler service is using a domain admin account to make the install (the account works great with other laptops that I have next to the failed ones, they are on the same network).
When the return code is rised then I check if I can open C$ share on the target device. It opens the prompt for the credentials, I type them but then, the window with the c$ contents of the target device never appears.
I check with net use the open shares on the core server and it is there. Then, if I retry the task for the selected devices the agent finally gets installed.
I think it's due to some kind of timeout related to agent scheduler service that, when it is not capable of open c$ to download the agent on time, then it fails.
Is there an option or parameter to increase this timeout?
Thanks.
Hi - does anyone know the switch you would use in conjunction with your self contained install package for a silent install?
I have tried /An but it does not seem to work?
Thanks,
D.
This has been happening to me with provisioning (i have several other threads posted) where the Configure target OS stage of the template will fail at the point where it tries to install the resident agent. But even on a machine that has a LANDesk Agent installed on it, the resident agent will not start....so i can't communicate with the device from the core....which renders LANDesk useless.
When i try to provision a machine, i get this error: RAInstall result 1073741825
I have tried to google that particular error but I have found nothing. i have attached the complete log.
When I just try to go to a machine that has an agent already installed and run rainstall.exe, i get this error: RAInstall result 0
And if i try to run residentagent.exe, i see it running in the task manager for a second and then it disappears. I am stumped...and frustrated.
I have tried to find the latest version of rainstall.exe and put them in all the right places but again, nothing. And my core is running 8.8, SP3.
Someone please help before my boss starts to think I don't know what I am doing....maybe i don't but he doesn't have to know that.
thanks.
jeff
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.
How do I stop this from popping up?
Hello.
I have in a network over 1000 windows PC with agent installed via landesk console.
All agents have it-s own Endpoint Security settings? including device block policy etc.
Now i need to configure installition package via windows AD GPO.
Is it possible to make package and GPO policy to achieve this goal - install landesk agent (maybe advance agent) only on PC, where agent is not installed yet?
Hello, I have some problem deploying agent on windows 7 workstations.
The deployment task failed with code 1081.
I read a lot about it and already checked most of commons problems:
Firewall client/core OFF
File sharing/printing client/core ON
ping core from client IP and FDQN from client OK
ping client with IP and FQDN from Core is OK
ipcheck from client to client is OK
domain admin user in local admin group on client is the same for scheduler
map from core to client/admin$ OK
create test directory in client/admin$ from CORE is OK
UAC is set to elevate without prompting for admin users
ipcheck from CORE to client Failed with Hostname and IP
I cannot understand how it's possible to have ipcheck failed but ping and nslookup are ok both from client and core.
Anybody could help me to debug that.
Thank you for your help.
Regards,
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?
Background: I work at a college where we have roughly 4,600 PCs. Currently, they have the LANDesk agent 10.0.0.455 installed which reports to our LANDesk Core Server. The Core is running version LDMS 2016 (Base) Service Update 5. We also have another LANDesk Core set up on an individual server, and that's running LDMS 2016.3. That core has no agents deployed. The reason this Core was set up was because I inherited LANDesk back when it was 9.6 (which was just upgraded from 9.5), and we've had a number of irregularities with 9.6 and also 2016 (base) + SU 5. As a manner of trial & error, we decided it would be best if we just started fresh and install 2016.3 standalone; no upgrading. For the most part, it's ready to deploy (once I import my settings, packages, etc. from the current core). But the problem is that with 4,600 devices, it would be a daunting task to deploy 4,600 new agents, especially since I don't have the ability to wake up the thousands of machines I have at other campuses (Power Management has been an ongoing issue, and seems to be problematic across different subnets).
Talks in our department have discussed the future deployment of Windows 10 to all our machines, and they want us to abandon Windows Deployment Services in favor of LANDesk's Provisioning feature. I'm thinking that would be the ideal time to deploy the new 2016.3 agents! But then I'm struck with a conundrum: I don't think I can deploy a new agent that reports to a different core by using the LANDesk provisioning from the current core. For what it's worth, I'm very very rusty on my knowledge of Provisioning. I've signed up for LANDesk/Ivanti's remote course on Provisioning this week to re-learn the function. But if I were to understand it, the target machines need the LANDesk agent on them to use LANDesk Provisioning. If I were to capture & deploy the image on the new Core, I would need to have the target PCs already using the new Core's agent. If I were to capture & deploy the image using my current Core, then it would only include the agent from the Core I'm sending it from, right?
The Question: Is it possible to deploy an agent from a different core in a captured image that's deployed from a Core different than the bundled agent? Should I just deploy the new agent from the new core to 4,600 PCs before we start deploying Windows 10? The only reason I haven't so far is because I'm constantly using LDMS 2016 SU 5 for patching, package deployment, power management testing, etc.
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