I have seen this to, however, I've been on a little rest away from work so I've not be able to troubleshoot the issue - 8.8 SP1 - XP SP2.
I am seeing the exact same at my site.
LD 8.8 SP1
This has been fixed and will be in 8.8 SP2, which should be out this week (I think). For those of you that aren't going to immediately apply SP2, here is the patch for SP1 http://community.landesk.com/downloads/patch/SWD-1395088.1-2.zip
Any special reason why database.dll is not branded (e.g, no version tab etc...)?
Thanks Tracy for the quick response.
Thanks for the update, I am seeing this issue as well...
...but to clarify regarding the patch:
I first run setup.exe on the core server and on any additional consoles from SWD-1395088.1-2\setup.exe
After the installation finishes, I then either:
1) rebuild my agents and redeploy
2) tell my clients to run wscfg32.exe from the core server.
I think I have that correct...
One question, by running wscfg32.exe will this uninstall and reinstall the agent or simply append to the currently installed agent on each client?
It's normally easier to rebuild the agentry & redeploy.
Running "WSCFG32" on its own will NOT uninstall - it'll just check whether the Core has a newer version of the client's configuration - and if it does, the client pulls that (and the files) down.
In order to uninstall the client, you need to run a wholly separate binary.
LANDesk EMEA Technical Lead
Yes install on the core first. Then rebuild your client install packages. Then here is where you will get differing views, and most of this is conditional based on what the update actually entails. In this case the only file to be updated is database.dll. The standard view from LANDesk is to reinstall the clients. Well if you have tight change management, thousands and thousands of clients, this may be somewhat difficult.
So another viewpoint. Create a custom definition based on the date of the file (the dll is not branded with version so you have to use date). And just use the client side patch (setup.exe with the -s switch. This makes it silent). So to avoid the reboot, stop the service. So the actions are Stop service, run setup.exe-s, and start service. This has minimal impact on bandwidth, change management gods like it, users like since it is silent no reboot, easier on you as an administrator, and Jack is happy.
This is sort of like asking how do you peel a potato? Some people use a peeler, some don't peel, some use a knife, some use that weird glove from the infomercial, some boil it first and just rip it off, etc...