What version are you running?
The log talks about
"c:\ldclient\amclient.exe /apm /s" was executed successfully with process ID 00000904 on PF-047-04
... we've not used "C:\LDCLIENT\" since ... I think 8.1 ...?
You'll need to bring up a bit more information here on what your Core / Clients are running please.
LANDesk EMEA Technical Lead.
We are using version 8.7 with sp5.
I guess I should mention I am new with LD and my predecessor has moved on. If you are not currently using LDClient and we still do... is that a problem? Would that be why we have many deployment issues?
Hmm - several possibilities here.
- Your clients are still ancient. That could cause this and other problems.
- The clients are supposed to send the location of their LDCLIENT directory ... it's possible that's somehow broken in your case.
- Throw in certificate errors into the mix, but we'll see..
... on a client where this happens, locate the LDCLIENT directory. Where is it exactly?
... on a client where this happens, what's the version of the LDISCN32.EXE file (that'll be in the LDCLIENT directory). It'll give me an idea of how old your client is.
Let's begin with that, and we'll go from there.
I'm certainly hoping you don't end up having 8.1 clients - they're ... what ... 4 years old or so by now :).
LANDesk EMEA Technical Lead.
LDISCN32.exe is version 220.127.116.11
This may be a dumb question but.... Anywhere in the file?
Just do a search for CLIENTDIR there will be only one entry in the file and its toward the top...
And what exactly will this do?
Just post your CLIENTDIR= entry here from the NTSTACFG.IN# then we can determine next steps...
I did that.
I do not see that you have done that in this thread
Perhaps Im not being clear:
Please open the NTSTACFG.IN# file on your core server find the entry for CLIENTDIR= Copy that entire line and paste it into a reply post here...
OK well that explains the confusion about why the agent is using the old path for the default client location... Is there some particular reason that this was changed from the default for 8.7?
Was this an upgrade install from an earlier version of LANDesk? Is this a new issue that was working before some event like an upgrade, or SP install ETC?
As for the issue, there is no reason that the location you are using should not be fully functional... Can you clarify how you are launching the amclient task that is failing? Is it via the Remote Execute Function of the Remote Control session? If so please launch it from Start Programs or just browse to it from the Run key and run it with an /apm switch.
I do not know why the default path was changed... as long as I have been doing this its been that. I was surprised to hear that amclient is not being used by many.
This issue along with others happen frequently. I am new LANDesk and I am just trying to understand its workings etc.
Yes I am runing apm via the Remote Execute Function of the Remote Control session. I do not understand what you mean by " If so please launch it from Start Programs or just browse to it from the Run key and run it with an /apm switch." If I do not remote execute I have a job and those are the only 2 ways I know how to launch APM.
when you say.. Just bowse to it... can you be more specific?