I'm attempting to deploy an Advance Agent via GPO. When AdvanceAgent.exe launches it throws the following error in the event log and fails to complete the agent installation.
"The LANDesk Advance Agent service is marked as an interactive service. However, the system is configured to not allow interactive services. This service may not function properly."
Does anyone know a fix for this?
I've noticed on a lot of machines that I am getting an error when scheduling agent deployment. We're running LANDesk 9,0 SP3 with LD90-SP3-CP_RC-2012-0605 and LD90-SP3-CP_BASE-2012-0605 installed on the core.
The machines will fail with the result "An internal error occured" Return code is 1208
If I view the log, the machines say this....
[Exception occured, last attempted operation] RemoteExecute, program = tmp70B1.tmp exception = Object reference not set to an instance of an object.
or
[Exception occured, last attempted operation] RemoteExecute, program = tmp70B1.tmp exception = Could not find file 'C:\Users\zldsk2\AppData\Local\Temp\tmp78B.tmp'.
The agent install actually seems to work fine and the agent is updated but it is not reporting sucessfully when I push out the agent using schedule agent push
Any ideas?
Hi everybody,
ok so here is my Problem, I'm working on since two weeks already.
When I install an SP3 Agent on a new Machine (Windows 7 or XP) everything works fine for a few minutes. After 5 Minutes nearly every PC loses the Binocular in the Management Console and under Properties it shows "Common Base Agent Status" not loaded- but again, 5 Minutes before it was loaded.
Well at the beginning i thought that it is Windows 7 Problem- but it also came up on XP Machines. My second thought was that it could be our Image (the Agent is not included in the Image) but after installing our LD Software on a clean Windows 7 PC from CD it didn't work either or to be more specific... it worked but only for the famouse few minutes.
What did I try?
- Checking the Agent Settings but I don't find any Option that could be responsible for that Issue (or is there?!)
- Uninstalling the Agent with a /forceclean, deleting the Machine from the MMC and reinstalling the Agent... that works but again... only for a few Minutes =/
- Trying to execute the "cba8inst.msi". I found a Discussion on the Landesk Community where they say that this could help... but in my case it didn't.
- Comparing the Registry Entries of the Agents who work with those who don't but beside the ID's and some other indivudual characteristics, everything looks fine.
That what bothers me is the fact, that from 10 Installations in the same Network, on the same Hardware with the same Image, 1 or 2 Installations work. So therefore I can exclude the Firewall too.
The services are all started and the in the Eventviewer there are no Problems.
Now I know that most of you guys who are reading this are from Great Britain. Therefore I beg you to take out your Sherlock Holmes Pipe and to help me to resolve that case. 
Thank you for every answer in advance,
greetings from Italy
Hi,
in LANDesk 9.0 SP3 I distribute OS with Provisioning. One of the tasks in my Provisioning template is to install the LANDesk Agent.
Provisioning tells me everything went well:
However, when I analyze the client, I'm missing some LANDesk services:
In the LANDesk console, the remote control icon is missing:
When I distribute the agent again by a scheduled task, the agent installs correctly.
How can I troubleshoot this problem? TIA!
After upgrading to LDMS 9.5 we are noticing increased log off times. A normal log off would take 20-30 seconds is now taking 3-4 mintues. There are times when the user will initiate the log off and the computer appears to be frozen but after 3-4 minutes it will then start the log off. It almost reminds me that a scan is happening before the log off.
I know it is tied to this as I rolled a few machines back to the 9.0.3 client and they log off as before, in 20-30 seconds.
I have striped everything out of the client, so there Forms, RTI, Software Monitoring, just the base client and still have the issue.
Has anyone else seen or heard of this?
Thanks in advance.
James
Landesk 9.0.2.3
Is there a way to prevent the Landesk agent from being uninstalled from a machine by the user? Our users have admin access to their machines.
Agent installation return with error code 1081. It is a fresh installation. The client OS version is Windows Server 2003. The firewall and antivirus are already turn off. I can see the folder $ldcfg$ created and the installer file already copied but he installer file seem not executed at all. Can anyone give idea on how to resolve this issue?
Log file:
Tue, 19 Feb 2013 16:01:24 Processing task 3
Tue, 19 Feb 2013 16:01:24 Processing task 3
Tue, 19 Feb 2013 16:01:26 1 machines targeted to task
Tue, 19 Feb 2013 16:01:26 Getting handler associated with scheduled task.
Tue, 19 Feb 2013 16:01:26 1 machines for taskID 3
Tue, 19 Feb 2013 16:01:26 Remote operation timout = 1200
Tue, 19 Feb 2013 16:01:26 Reset remote operation timout = 1200
Tue, 19 Feb 2013 16:01:26 Building LDMS client setup package: C:\Users\Administrator\AppData\Local\Temp\tmp1E4.tmp Log: C:\Program Files (x86)\LANDesk\ManagementSuite\log\cab_3.log
Tue, 19 Feb 2013 16:01:46 Configuring client config thread limit to 1
Tue, 19 Feb 2013 16:01:46 SVR-PNG-001 Sending C:\Users\Administrator\AppData\Local\Temp\tmp1E4.tmp to C:\$ldcfg$\tmp1E4.tmp
Tue, 19 Feb 2013 16:01:46 SVR-PNG-001 creating dir C:\$ldcfg$
Tue, 19 Feb 2013 16:02:12 SVR-PNG-001 Copying to C:\$ldcfg$\IPCheck.exe
Tue, 19 Feb 2013 16:02:40 SVR-PNG-001 Copying to C:\$ldcfg$\tmp1E4.tmp
Tue, 19 Feb 2013 16:05:03 SVR-PNG-001 Copy of C:\$ldcfg$\tmp1E4.tmp to SVR-PNG-001 returned -2147482443
Tue, 19 Feb 2013 16:05:03 SVR-PNG-001 Removing temporary directory
Tue, 19 Feb 2013 16:05:12 SVR-PNG-001 Handling reboot options
Tue, 19 Feb 2013 16:05:12 SVR-PNG-001 Reboot not needed
Tue, 19 Feb 2013 16:05:12 SVR-PNG-001 DONE: retCode=-2147482443 machineRetCode=1081
Tue, 19 Feb 2013 16:05:12 Task complete, status 7
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
I have created an Advance Agent Default Windows Configuration for deployment of LanDesk 9. We installed LanDesk on our D: drive on our core server. I see the AdvanceAgent folder and the files created within the folder.
I tried to Push the Adv Agent to a Windows 7 machine and a Windows XP machine. Both resulted in Failed: Status, An internal error occurred, Return Code 1208. I've been searching for this error and haven't found anything to determine what this error is or a solution. The Management Console for LanDesk9 in on our core server and hasn't been installed on our Tech's computers. Our current version on our client machies is 8.80.0.249 and we are trying to upgrade to version 9.
Hi,
Everytime when I installed the LDMS 9.0 agent (manually, push or via provisioning) on Windows 7 only there is a folder created in the root system (C:\) called %LOCALAPPDATA%. It's look like a variable wrong coded.
Some people can confirm that?? In that case I will open a call....
Regards
Lionel
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
Hi,
I recently purchased Landesk 9 and deployed the agents to most PC's in our office with no problems.
We have a VPN tunnel between our office and another office within europe, the remote office is on a different domain and on a different subnet.
However; we have a trust relationship between the domains and DNS is configured to forward unresolved requests between one another. We have no problem pinging other machines on the other domain even with just the name of the PC.
When i try to deploy the agent to one of the remote PC's (Lets say PC04) i get the following error
[Operation failed] RemoteExecute, cmd /c mkdir C:\$ldcfg$
CBA 8 X509 operation : -2147481845 (8000070b8u) : Unable to contact the remote agent.
NT File Sharing : 1222 (4c68u) : The network is not present or not started.
NT File Sharing : 1203 (4b38u) : No network provider accepted the given network path.
Secure Shell : 1805 (70d8u) : An unspecified error in the protocol occured.
Remote execute using TCP failed, result 0x0000057a (1402)
On unmanaged systems this operation will attempt to access the ADMIN$ file share and remotely start a service
Now at first sight it might seem like it is a shares issue but if i RDP to the PDC on the remote site and execute the command \\pc04\ i see the defualt C$ and Task schedueler displayed, however if i do \\pc04\ from the local domain i get no shares available.
This means that the default shares are enabled but cant be accessed over the VPN for some reason.
I checked the following:
1) Firewalls enable all TCP/UDP traffic between both subnets.
2) Default C$ Admin$ shares are enabled on both domains.
3) DNS works perfectly fine in both sides being able to resolve names without FQDN appended even.
4) i can ping both sides without any issues.
Anyone experience a problem such as this ?
Thanks,
Hi all,
i am having trouble finding the documentation for the recommended methods of the agent upgrade in version 9.5. Can someone point me in the right direction please?
Thank you.
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,
I discovered that if you install an agent using the Remote Control Mirror drivers on a Windows 7 64 bit pc it disabled the Windows Aero feature. This was not the case on a 32 bit Windows 7 machine. The machines I used were a Dell 755 (64bit) and a Dell D820 laptop (32bit). Just wanted to pass this on should anyone else see it. Once I changed the client and rebooted Aero started working again. This was a version 9 client.
A couple of our techs deployed some Windows 7 machines before we had a chance to modfy GPO which deploys the LANDesk agent. The WinClientUninstall.exe doesn't properly uninstall on 64-bit Windows 7. Some files remain in %programfiles%\LANDesk\Shared and a service is not uninstalled.
Is there a better uninstall available? We're still on 8.8 SP3. Is the uninstaller in 9.0 any better
Removed a trial version of LanDESK and am reinstalling with a continued error installing CBA 8. I attempted to reboot, and shutdown all running LanDESK services and reinstall without success. I'm new to LanDESK completely. Any advice is greatly appreciated. Thanks for your time!
Jeff
UPDATE: I am able to register the core server. When I start the Management Console, I recieve an insufficient privledges status. If I try to continue the installation, it starts at CBA, and errors out almost immediately.
Upgraded agents from 9.0SP3 to 9.5AllPatches and a good portion of the agents failed to update during the push deployment. The error received in the scheduled tasks window is "Agent setup program returned an error". I remember seeing this occasionaly the last time we did a deployment but rerunning the task on the computers that had failed generally came back successful. Not the case with 9.5.
Every machine that fails has the same symptoms, which leads me to beleive they are failing for the same reason. If you check the services on a computer that had a failed installation, the ONLY landesk services that are present are "LANDesk Targeted Multicast" and "LANDesk(R) Management Agent". A way to repair the agent on the computer, is that I can run Uninstallwinclient.exe then install the agent manually with a self contained exe and the installer goes through just fine. The problem is I cannot afford to do this on every single computer that has failed. I am still working on a way to identify all of the agents that did not install correctly. At the moment I am considering a loginscript vbs file that checks for the existance of the core landesk services.
I have attached the wscfg32.xlg file with the hops that someone can point out why the agent install is failing on so many machines. If any other information is needed please let me know.
We recently upgraded to LANDesk 9.5. We have a new server and did a clean install of LANDesk 9.5, including the SQL Express database--basically started from scratch. Our core server is called S21.
An odd this has happened. In my Network View under All Devices I see two Core Servers:
Server A: S21 is shown as a server and has an IP address of 10.1.3.1 - this server shows a status of being powered off in LANDesk.
Server B: S21 is shown as a workstation and has an IP address of 10.1.3.48
Server B is the Core Server. That is, the 10.1.3.48 is the static IP address configured on the machine. It has Server 2008 R2 installed.
The IP address for Server A is not on our network. It cannot be pinged. It was not issued via DHCP.
Patching is bizarre. If I right click on Server B I see many patches. I configure them as a task. Run the task. Both A and B show up in the task. A will be successful and B will fail.
Any idea what I should do here?
Hello. I am currently running Landesk 8.7 Recently we pushed a bunch of Microsoft patches to about 1500 remote clients running XP with SP2. The firewall has been disabled on all. More than half the patches failed reporting that they "Cannot find agent" and/or "Cannot find agent (different agent responded"
Can anyone help me interpret that error message?
Thanks!
