I did check sdclient.exe exists in the C:\Program Files\LANDesk\LDClient\ folder.
I shouldn't have to but do you think it may work if I add sdclient.exe as an Additional File within my package so that it downloads to the C:\Program Files\LANDesk\LDClient\SDMCache folder please?
I would not add sdclient to additional files. Since it only seems to affect certain machines, I would look at those machines:
Reinstall the client.
Check and make sure there is nothing wrong with the path statement - bad syntax. etc..
See if you have a LDMS_CLIENT_DIR environment variable and see if it is pointing to the correct directory.
Normal cleanup - temp folder, chkdsk, etc...
What OS version are these machines?
Hi zman, thanks for the reply.
I have tried 3 different machines, all XP SP2.
1) Could try I guess.
2) On one machine I didn't see any LANDesk-specific environment variables in the Path statement. What should I be looking for?
3) LDMS_CLIENT_DIR environment variable did exist on the one I checked and I think it was pointing to C:\Program Files\LANDesk\LDClient\Data\. I assume this is correct?
4 ) Could try I guess.
Message was edited by: scottunify
1 of 1 people found this helpful
If that is your "actual" password listed in the log of the first post, I would remove it. LDMS_CLIENT_DIR should be point to the ldclient folder not data. Also make sure you have a full valid inventory scan on the machines. Also see what is in Computer.LANDesk Management.Client Path in the inventory.
Just for S&Gs try using the 8.3 (short path) to sdclient c:\program~1\
Thanks for the tip. I have replaced the password in the logfile.
I have done a quick survey our my office and the LDMS_CLIENT_DIR environment variable on every machine is configured as "C:\Program Files\LANDesk\LDClient\Data".
However, I checked the Inventory (Computer.LANDesk Management.Client Path) of a few different machines and they are all configured as "C:\Program Files\LANDesk\LDClient".
I assume they should both be "C:\Program Files\LANDesk\LDClient"? If so, how could the local LDMS_CLIENT_DIR environment variable on every machine change to the Data directory?
Do you mean should try 8.3 as follows:-
c:\program~1\landesk\ldclient\sdclient.exe /msg="GLA-IMAN1 deleted and GLADMS01 registered."?
I was wrong LDMS_CLIENT_DIR should be pointing to C:\Program Files\LANDesk\LDClient\Data. So everything looks correct env var and db data. Yes that is correct for 8.3 sort name. When in doubt you can use dir /x
I followed your advice to use short names 8.3 format but still fails:-
"C:\Program Files\LANDesk\LDClient\sdmcache\SWPACKAGES\DeskSiteGLADMS01>c:\program~1\landesk\ldclient\sdclient.exe /msg="GLA-IMAN1 not registered."
The system cannot find the path specified."
See logfile attached.
Not sure where I go from here. Any ideas please?
Thanks for your help so far
I would reinstall the client, if that does not work, open a ticket. 8.5 sp2 is somewhat old.
I have reinstalled the LD client on my machine using *
server\ldlogon\wscfg32.exe /f /noreboot /status*, then re-deployed the package but again it fails with the same error. I am dumbfounded by this because other packages utilising sdclient.exe /msg="message" have always worked. Nothing has changed in our environment but something is definitely wrong.
We're hoping to upgrade to LDMS 8.8 later this year after a series of other project commitments (it's out of my hands).
As you say, looks like I'll have to open a ticket with LANDesk Support.
/msg="GLA-IMAN1 not registered."+
The system cannot find the path specified."
Try using progra1 instead of program1
Good catch Jason, I wish spell check would pick up my erroneous posts :_|
Thanks Jason - good spot indeed! This has resolved the error in the logfile (see attached), so it now recognises sdclient.exe and appears to have worked. However, the Message field in the Scheduled Task is still blank, so it has not updated the core server!!! Aaarrgghhh!!
How strange. What is going on?
Are you actually refreshing, because the SDCLient.exe /msg send the data in through a web service, but the batch file ends right after. You may be getting a success before you see the message and if you don't actually click refresh, you won't see it.
Also, it may be that the web service is failing but you can test just a simple batch file with one line that is a message.
I did refresh the Scheduled Task several times but no joy. So I took your advice to create a simple batch file test with just the following:-
and it worked!
So there's something wrong with the original package not updating the server for some reason. Hmm, guess I could re-create it and try again...