forgot to mention preferredserver.dat file only contains timestamp. and the IP ranges are correct.
Check if you have preferredservers.dat on cache directory on client station and open this file.
Check your configuration IIS and right NTFS on core server
Log files IIS
Check your configuration on core server in section replication content.
-Policy cache post 8.8 LDMS
No longer stored in the registry now stored in a local sqlite DB.
I use this to open the db http://sqlitebrowser.sourceforge.net/.
DB is located here C:\Documents and Settings\All Users\Application Data\LANDesk\ManagementSuite\Database\LDClientDB.db3
hi mate we have an estate of over 6000 machines and i have only found two clients so far doing this.
So i dont think its an IIS core problem as such as it would be affecting alot more.
Its something unique to the client and the details about it stored in landesk ( hence the problem is still there on complete rebuild ) Oh i forgot to say i deleted the client from the database before reinstalling.
We are only seeing this as we find machines failing tasks so like i said we could have more but its definitely not a huge number as we have nightly tasks running on 90% of our estate with no issues.
the prefferredserver.dat file on the client is only showing the timestamp.. none of the servers that should be listed are present. Yet it still downloads the package to the sdmcache on the client ?
Deleting the LDClientDB.db3 database: If you happen to delete this client database in troubleshooting (This db can be deleted in troubleshooting and not cause any issues. You would want to delete and re-validate this db if tasks are not showing up in it, or if tasks are not showing up in the portal). You have to run the following after:
C:\Program Files\LANDesk\LDClient\Clientdbutil.exe /create
Thanks thats great info.
I have found a lot of machines even though they are operational they have active tasks or delayed ones in the scheduled tasks and policies list. surely they need clearing?
the reason is the active tasks are public ones so the machines in them change all the time. For eg my machine is saying active on a task in its history that its not present in anymore however the task is still there as its a public one - its just my machine was in it at some stage.
how are others dealing with that scenario?
will try the DB delete on the problem machines...
will let you know
On core server test this acces :
http://core server name/landesk/managementsuite/core/preferredserver/PreferredServer.asmx
Use "GetPreferredServers" option and click "invoke" button
you obtain this result :<?xml version="1.0" encoding="utf-8" ?>
if we use that tool i get the correct preferred server from the core.
you can only run that option on the core right? if i run on a client i dont get the invoke option..
Also the policy cleanup tool i ran at start does delete that DB on the client and recreate it. i have yet to try on the problem machine as its in production. and we cant gain access however tried to see if its clearing the cache on my machine and just waiting for my inventory scan to finish..
Ok after running the DB cleanup tool and re inventorying a machine i check the policy history and still see this.
Are these going to cause any issues or is this normal?
the active tasks are still in public but my machine is not in them?
policy.JPG 96.3 K
Restart tasks or use script LMDS to execute policysync
How to is configured your localscheduler on client station ?
The thing is that we have completely deleted the client from landesk and reinstalled and this information is still present?
My main problem is the client does not see the preferredservers list. The policy list seems to be on many machines even ones that are fine. could be red herring but would be nice if that information was cleared properly somehow..
is there an invoke xml tool that can be run from the client?
the preferredserver.dat file only contains the timestamp. no servers
and sorry not sure whhat you mean by how is the localscheduler?
all services are started and correct - the package will fget its way to the machine but the job stays active for ages then the log file says this.Thu, 20 Oct 2011 15:53:27 Failed to start a session with (3)Thu, 20 Oct 2011 15:53:27 Web request to core server failed, result 1803, http status 0Thu, 20 Oct 2011 15:53:27 Cannot get preferred server list from coreThu, 20 Oct 2011 15:53:27 File (\\server02\landesk\packages\planit\HowCadHKeepCheck_001\HousekeepCheck.Vbs) is cached locallyThu, 20 Oct 2011 15:53:32 Failed to start a secure session with (3)Thu, 20 Oct 2011 15:53:33 Failed to start a secure session with (3)Thu, 20 Oct 2011 15:53:33 processing of package is complete, result -2147467259 (0x80004005 - code 16389)
And the preferredserver file downloaded contains no servers. not sure what to try next!
1 ] The thing is that we have completely deleted the client from landesk and reinstalled and this information is still present?
No this information is reiniatilizing with reinstall
2 ] My main problem is the client does not see the preferredservers list.
Test standard push "no multicast method" and check the log file on client station
see if the file is present preferered server.dat in sdmcache
C:\Program Files\LANDesk\LDClient\[MSI Name].log (created during installation of MSI packages)
Software Distribution - Policies