The agent install can take a significant amount of time (depending on system) how long have you waited?
if less than 5 min, give it more time.
More than 10, there may be a problem.
If you have tried it several times i would restart the machine and delete any traces of the previous installation.
Thanks, its been almost 2 hours! Ive tried taskkill and ending the process. No luck
Have you restarted the machine, then unistall agent?
I am attempting a manual uninstall of the agent now. The process may not allow the uninstall to complete either though. Thanks
Unfortunately, this did not work. The process stopped but once I attempted to reinstall the agent, the process appears again and thats where it gets stuck
Does this happens with every machine? if so, can't think why.
If it doesn't, toast that install (reimage the pc, may be faster and move on)
-That's all I got, best.
Here's how I'd approach the situation:
1 - Create an agent configuration where you do NOT perform an inventory scan as part of the agent install. That's "less desirable" under normal circumstances, but at least should get you to a full agent situation faster.
2 - Bit curious how / why the taskkill approach doesn't work. Killing off LDISCN32 isn't usually a big thing. Anyway ...
3 - Once you have the agent installed, run an inventory scan with the following parameters:
C:\Program Files (x86)\LANDesk\LDClient\LDISCN32.EXE /V /F /SYNC /O=ZZ_Out.scn /DEBUG /PD
This does the following:
- Forces the inventory scanner to run with a GUI enabled ("/V" - to show you how things are progressing / if there's any problems).
- Forces the inventory scanner to log with DEBUG-mode (which creates a VERY chatty log here -- C:\Program Files (x86)\LANDesk\LDClient\Data\LDISCN32.LOG -- this will keep getting updated as the scan runs. So if nothing else, *THIS* will help you understand what / where the inventory scanner is getting stuck at.
- Forces a full software scan ("/F") -- merely a "good habit" in this sort of situation
- Forces an output file called "zz_out.scn" of the resulting scan (can be useful) via the "/O=ZZ_OUT.SCN" ... feel free to name it something else obviously.
- Forces the send of all product data ("/PD").
Chances are you may need to raise this as a support ticket (having the debug-log for that will be a big help) though ... but with the debug-log's last entries, you should be able to figure out what kind of operation is causing you grief (and just how much time it's takin up).
See how that goes? .
What version is your core? I would also try to see if this might help your issue: Go to WMIRulesScan.xml on the ldlogon on the core and make a copy and save it to a
different directory to have a back up. Then right-click and edit the WMIRulesScan.xml in the ldlogon directory and clear all the contents and save it.