I would to deploy a batch file, it is save a windows command.
When I deploy to client it have a error.
Status: Failed
Result: Package Deployment Failed
Return code: 1
Log:
Installation result 8DB50001
processing of package is complete, result -1917517823 (0x8db50001 - code 1)
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
Here in our corporate office we've recently rolled out wireless connectivity to the entire space. We're now seeing issues where Landesk cannot keep up with the switching between wired and wireless IP for the device, and the various ip address pools. I'm running LDMS 9.6 SP2.
I understand that while I have "run scan when IP address changes" enabled on the client, this will not help when a pc switches between wired and wireless. I've updated my agent settings to more frequently run inventory scan in hopes of getting better reporting to the core, but that does not really look to be helping, and I'm now having a devil of a time trying to deploy packages. Its unclear whether I need to do anything outside of Landesk, possibly with DNS settings in my environment.
Has anyone else run into this issue and can offer some suggestions.
Good morning,
I'm trying to push an Agent configuration to a site we have that's on a different domain (Unfortunately SBS 2003 so no domain trust possible). I've added in credentials for this domain to the Scheduler.
My plan was to push the advance agent via GPO, which works up to the point of installing the full agent but goes no further. (advance agent msi installs & copies the full exe from our core servers ldlogon folder). Information on the cleint from c:\windows\temp\advanceagent.log as follows:
As an alternative I've tried installing the full agent on a test machine; this works up to the point of trying to run an inventory scan, when I am given the following error:
"Application has failed to start because elogapi.dll was not found. Re-installing the application may fix this problem"
I can only find elogapi.dlm in \windows\system32 on the test client; reinstalling the agent makes no difference. Running an inventory scan from the core fails and gives the result "Unknow Status code (0xC0000135,0:309)
The agent has been tested and known to work correctly on the domain where our core server is located, so I assume this is related to permissions used to install.
Any advice would be appreciated on this matter.
Many thanks
David
I thought our GPO for the LANDesk 9 Agent was working fine but i'm I seem to be noticing an issue on some Windows 7 machines where the agent is not getting installed.
I recreated a new AdvanceAgent and confirmed the path to the .exe was correct.
I did gpupdate /force on my machine.
I get the following error in c:\windows\temp\AdvanceAgent. This is from a previous attempt at installing the Agent. I dont see any new logs being created.
I recently Provisioned a machine and deployed it to a user. The machine is a Dell D410 and received the latest Landesk Agent. Once I deployed the machine to the user, policy.client.invoker.exe began running anywhere from 90-100% CPU usage. I redeployed the LANDesk Agent to the machine but the problem has persisted. Has anyone experience an issue similar to this? Any suggestions to troubleshooting this? I appreciate the advice.
Having a problem with the common base agent not loading onto some of our servers(Server 2003 and Server 2008). Does anyone have any idea why the agent would not be able to load from the deployment. We tried doing it through Unmanaged Device Deployment and through loading the agent directly on the server.
See attached image for details.
Thanks in Advance,
Matt
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
I have a question regarding my LDMS9 Test Environment. I've successfully discovered a device using Unmanaged Device Discovery within my small 2 PC / 1 Core test environment. After I discovered PC1 I wanted to push the Agent I created out to it. When I do so the Scheduled Task fails. It states Unable to contact the specified machine. The machine may be off or unreachable. Well, the machine is on and is pingable from the core. Anyone have any suggestions to why this may be failing?
Other notes: PC1 is a Windows 7 Machine and these computers are in a a WORKGROUP.
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?
Does anyone know if there are any issues with LANDesk and SSD drives? We are looking to mover our advanced users to SSD drives in the near future and don't want to create any headaches without first posting this question. I ask, also, because our test machine which had an SSD drive on it developed 'freezing' issues after the LANDesk agent was installed.
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.
I've been thru the manual, and can only find 1 or 2 instances of "remove agent", and hundreds of instances of either word by itself.
We have one user who is being harrassed by LD. Every day LD wants to install some update/patch...even after we apply everything there is to apply manually, using remote control.
We don't know specifically what it's trying to install. We thought for the moment that we'd just remove the agent. But we don't know how. I had seen LANDesk listed under Add/Remove SW on my PC, but when I connected to his, it wasn't there. We're assuming that my LANDesk listing was for the console, rather than for the agent.
Thanks in advance for the assistance,
Tom
Files all seem to copy but install hangs on LANDesk Antivirus
Executing 'C:\program files\LANDesk\LDClient\vulscan.exe /changeSettingsNoReport /showui=false'
C:\Program Files\LANDesk\LDClient directory has 389 files 7 folders nad the most recent file is:
localsch.log
last entry is:
Sat, 09 May 2009 21:56:53 Starting process: C:\Program Files\LANDesk\LDClient\purgefile.exe $(TMCCacheDir)\preferredservers.<core>.dat 86400
Sat, 09 May 2009 21:56:53 launched "C:\Program Files\LANDesk\LDClient\purgefile.exe $(TMCCacheDir)\preferredservers.<core>.dat 86400"
current time is 22:08
seems to be a hung process.
There are 3 versions vulscan.exe running in taskmanager (1 from me and 2 from system) not sure what that means.
Installed services:
intel local schedular
intel pds
policy invoker
remote control
targeted multicast
management agent
out of band monitor
software monitoring
missing antivirus & resident agent?
For what it's worth we are having issues with the exe install nad the advanced agent install as well.
Before trying to install during this session, I uninstalled using uninstallwinclient and rebooted.
thoughts?
We have deployed LANDesk v9.0 into our enviroment. On 3 Physical Dell R710's an error in the event log states
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7000
Date: 01/0000
Time: 00:00:00 PM
User: N/A
Computer: xxxxxxxx
Description:
The IntcDrv service failed to start due to the following error:
The system cannot find the file specified.
as much googling as i can find tells me the intcdrv is Intel Platform Verification API Support Driver
As the plot thickens this only occurs on the Dell R710 - Windows 2003 R2 x64
tested on IBM hardware works fine
Any help would be greatly appreciated
As part of a trial I installed LANDesk agents on a number of my PC's. Since it was a trial I had the core server on an old piece of hardware that died. Where can I get a copy of uninstallwinclient.exe? I'm using version 8.7.
Thank you,
Not sure if this is correct forum to post this question, but I wonder if it has to do with the way the agent was deployed or created. But, by default, my clients should startup in Direct Mode, but I find from time to time, either after a restart, or maybe even a log off and log on, the client will switch to gateway mode.
Has anyone ever heard of such a thing, and if so, what causes that, and what is the solution?
Hi All,
I am getting 1087 error while deploying the agent from the console.
I have tried all the steps like mentioned below.
1)port 139,135 & 445 open on the firewall.
2)Admin$ & C$ is accessible.
3)Firewall is off.
4)Scehduler service has both local admin & domain admin credential assigned on it.
But still deployment failing, below is what i am getting from the logs.
Mon, 03 Feb 2014 12:39:29 6688 6904 Performing remote execute, target 192.168.248.61:9594, hash 5b38afab
Mon, 03 Feb 2014 12:41:10 6688: WNetAddConnection2() failed 1326, user="systemadmin"
Mon, 03 Feb 2014 12:41:11 6688: WNetAddConnection2() with local domain failed 1326, user="192.168.248.61\systemadmin"
Mon, 03 Feb 2014 12:41:11 6688: WNetAddConnection2() failed 1326, user="Administrator"
Mon, 03 Feb 2014 12:41:11 6688: WNetAddConnection2() with local domain failed 5, user="192.168.248.61\Administrator"
Mon, 03 Feb 2014 12:41:11 CBA8Execute::ProcessSSHRequestHelper
Mon, 03 Feb 2014 12:41:11 CBA8Execute::ProcessSSHRequestHelper AppName = "cmd"
Mon, 03 Feb 2014 12:41:11 6688 6904: Performing SSH remote exec as systemadmin: -ssh 192.168.248.61 "\"cmd\" /c if not exist C:\\$ldcfg$ mkdir C:\\$ldcfg$"
Mon, 03 Feb 2014 12:41:11 6688: SSH remote exec launched: (5116) PLINK.EXE
Mon, 03 Feb 2014 12:41:32 6688: closing SSH (5116) stdin handle due to error
Mon, 03 Feb 2014 12:41:32 6688: SSH (5116) stdout: FATAL ERROR: Network error: Connection timed out
Mon, 03 Feb 2014 12:41:32 6688: The SSH application (5116) has closed its stdout pipe
Mon, 03 Feb 2014 12:41:32 6688: SSH remote exec (5116) exit code: 1
Mon, 03 Feb 2014 12:49:28 4772 1696 Performing remote execute, target 192.168.248.61:9594, hash 5b38afab
Mon, 03 Feb 2014 12:51:09 4772: WNetAddConnection2() failed 1326, user="systemadmin"
Mon, 03 Feb 2014 12:51:10 4772: WNetAddConnection2() with local domain failed 1326, user="192.168.248.61\systemadmin"
Mon, 03 Feb 2014 12:51:10 4772: WNetAddConnection2() failed 1326, user="Administrator"
Mon, 03 Feb 2014 12:51:10 4772: WNetAddConnection2() with local domain failed 5, user="192.168.248.61\Administrator"
Mon, 03 Feb 2014 12:51:10 CBA8Execute::ProcessSSHRequestHelper
Mon, 03 Feb 2014 12:51:10 CBA8Execute::ProcessSSHRequestHelper AppName = "cmd"
Mon, 03 Feb 2014 12:51:10 4772 1696: Performing SSH remote exec as systemadmin: -ssh 192.168.248.61 "\"cmd\" /c if not exist C:\\$ldcfg$ mkdir C:\\$ldcfg$"
Mon, 03 Feb 2014 12:51:10 4772: SSH remote exec launched: (6972) PLINK.EXE
Mon, 03 Feb 2014 12:51:31 4772: closing SSH (6972) stdin handle due to error
Mon, 03 Feb 2014 12:51:31 4772: SSH (6972) stdout: FATAL ERROR: Network error: Connection timed out
Mon, 03 Feb 2014 12:51:31 4772: The SSH application (6972) has closed its stdout pipe
Mon, 03 Feb 2014 12:51:31 4772: SSH remote exec (6972) exit code: 1
Prompt help will be appreciated.
Best Regards,
Sayed Abbas
Hi Everyone,
Question regarding Advance agent deployment via GPO. Our LD tech has told me that we can "redeploy" a new agent using GPO and the advanced agent. Meaning that if we have systems out there with an agent installed already, we can kick off a GPO to deploy the new advanced agent and it will overwrite the existing.
Do you all agree with that? I tired this a while ago and found that GOP would ignore system that had any rev of the LD agent installed already. It would work on fresh, unmanaged systems but not those that were managed by an older agent. According to LD, this behavior is handled by the MSI (as far as detecting).
Appreciate your imput everyone!
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