it is not recommended to use a image with a embedded agent!
If you use it, you've to change some entries in your image, s. How to image devices with a LANDESK Agent installed
I think your other problems are caused by the inventory scanner settings on the core.
Do you find some files in ..\ldmain\ldscan or below in ErroScan or ErrorBigScan?
Here are some interesting links to set inventory scanner:
If you have an 8.5 core, then you need to find out how someone has managed to put an 8.6 agent on your machines. This is an incompatible version as LANDesk is backwards but not forwards compatible. It also sounds like you have a horrendous duplicate device problem that needs sorting out.
I know this may not be a simple thing to do, but it sounds like your environment is uncontrolled right now. You need to get this system up to a supported version (8.5 is a number of years old now) and bring everyone to the same supprted level. You can sort out this duplicate device ID at the same time. You MUST standardise the way the agents get put onto these systems; your admins are causing your system to become unmanageable and LANDesk (and possibly you) will get the blame.
The advice you got earlier will help you get through the current crisis but there will be another crisis around the corner if this syetm is not correct properly.
Mark Star - MarXtar LANDesk Enhancements
Home of Power State Notifier & Wake-On-WAN for LANDesk
what happened if i removed the LDMS 8.5 and install on the same server LDMS 8.8 and redeploy the Agent Again
can it overrite the agent installed on these devices ?
Pls , i need your recomendation
Also , i have the two problems :
the imaging issue and invenory service stopping
Pls , i need the help urgently
Appreciate your Advices
You may want to take a step back and slow down some.
1 - LDMS 8.5 has been completely EOS'ed for several years, so LANDesk support won't really be able to help you much with that beyond pointing you to the latest service packs.
2 - In regards to the 8.6 agents (kinda curious how they got there in the first place) - you could always uninstall the 8.6 agents and the install the 8.5 clients ... but this isn't really addressing the issue I think (since if they're 8.6, I suspect they may belong to a different Core you may not even know of? Clients don't just upgrade themselves).
3 - The idea to move to 8.8 isn't necessarily bad. HOWEVER - a migration is a project in its own right. Doing a version migration "just like that" is (as per Sod's Law) likely to result you being end up with a broken Core (it's a popular time for backups to break, old OS issues to creep up, and so on). Be careful, haste is a very bad council.
4 - Depending on the state of the Core, an upgrade may be useful (rather than uninstalling and re-installing) But that (same with # 3) is not really addressing the real problem.
The real problem -- it seems that things are out of your control, and that's the first thing you need to fix. You cannot fix other people upgrading LANDesk agents / doing their own things / including them as part of the image, if you don't have the control over the product (as MarkStar pointed out). So the first thing to do really here is to sort out the political issues - who's in charge, and have that person call the shots.
This is not something that an upgrade will help with (nor is it going to particularly help with if you have a case of imaging with the identical DeviceID included) - 8.5 can try to address that problem (via Duplicate Device ID detection), but this will take time (depending on your inventory scanning frequency, normaly withing 3-4 days things should be normalizing in terms of device ID's).
So - yes - there *ARE* some technological problems that need to be solved, however at the moment it does not sound as if you are in a position to do that, with various activities related to the agent deployment being outside of your control. That control needs to be established, and only then can you go about smoothing things out.
Don't expect this to be done within a day or two though, it's possible that what you're seeing now is only the first layer of the "left hand not knowing what the right hand is doing" problems, as usually there ends up being quite a bit of it.
So - remain calm, focus on fixing the social/political problem first - and the technological stuff can then be addressed. Technology cannot fix social problems
LANDesk EMEA Technical Lead
you don't write if you've a lot of entries in your error scan directories...
You can hide the automatic stop of the inventory service on the core if you make some settings on
Configure - Services - Inventory - Advanced settings: (example settings)
DB Error Recovery Tries set to 10000 so 10000 errors per hour are possible
Max Scan File Size set to 25000000 so scan files sizes with 25MB are possible
This are workarounds only, they don't solve basic problem!