Hello,
Is there a way to query systems that are dual boot capable?
Thank you,
↧
Query to detect systems with dual boot capabilities
↧
Error connecting to inventory database.
Hi all
This is what i get when i try to point existing 9.5 SP3 installation to the new (SQL 2012) database server. I tried a number of username/password configurations but its not working all the same All and any ideas/suggestions would be greatly appreciated.
↧
↧
Remove LANDesk computer objects
I am working on trying to ensure my LANDesk database stays in sync with my Active Directory computer objects. Currently our process for retiring machines requires the technicians to delete the Active Directory computer object, and then go into LANDesk and remove the associated computer object.
I know that you can set the server to automatically delete objects after x days, but due to our installation being very new and our management gateway not being completely configured, we don't want to delete LANDesk computer objects that might still be active machines, but just don't connect to our VPN consistently enough to do an inventory scan.
Is possible that when we delete the active directory object, that a maintenance task simply scans Active Directory to retrieve the current list of computers, then compares it to the inventories in the database and deletes machines that don't have an Active Directory computer object? I am guessing that a script would work for this task, but if it is possible without having to script something, that would be even better.
↧
IP address of managed device isn't updated
I have an issue where the core is seeing Devices using their old IP Address and will not update, making any control of the device pointless.
I can PING from the core to the device and visa-versa.
Inventory scans work on the device.
I have followed this article by francesco.baldini to no avail - The IP address of the managed device isn't updated - the IP address of the wrong network connection is reported
↧
Ports for LDMS 2016
Hi,
Do you know if the ports list is the same as 9.6 ?
↧
↧
Inventory Scanner crashing
Hello all,
I've got a group of devices in LANDesk with a recurring inventory scan crash condition. Whenever the inventory scanner is run, it will crash within 5-10 seconds of opening.
Running with the /debug flag doesn't seem to generate any (additional) logs.
uninstallwinclient.exe and agent reinstall doesn't appear to resolve the issue.
MS Visual Studio debug log below, may indicate a User Rights issue? Can't quite tell.
| MS Visual Studio 2010 |
|---|
'LDISCN32.EXE': Loaded 'C:\Program Files (x86)\LANDesk\LDClient\LDISCN32.EXE', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\ntdll.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\kernel32.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\KernelBase.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\sysfer.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\ELOGAPI.DLL', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\user32.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\gdi32.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\lpk.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\usp10.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\msvcrt.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\advapi32.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\sechost.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\rpcrt4.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\sspicli.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\cryptbase.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\winmm.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\ws2_32.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\nsi.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\loc32vc0.dll', Binary was not built with debug information. 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\version.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\mpr.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\psapi.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\netapi32.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\netutils.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\srvcli.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\wkscli.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\samcli.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\cfgmgr32.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\shlwapi.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\msimg32.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\winspool.drv', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\shell32.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\uxtheme.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\ole32.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\oleaut32.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\userenv.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\profapi.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\wtsapi32.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\powrprof.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\setupapi.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\devobj.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\oleacc.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\winsxs\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.23407_none_5c02a2f5a011f9be\GdiPlus.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\imm32.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\msctf.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\ntmarta.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\Wldap32.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\clbcatq.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\msxml3.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\bcrypt.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Program Files (x86)\LANDesk\LDClient\rollinglog.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\pdh.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\perfos.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Program Files (x86)\LANDesk\LDClient\enuSCN32.DLL', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Program Files (x86)\LANDesk\LDClient\enuSCN32.MRL', Binary was not built with debug information. 'LDISCN32.EXE': Unloaded 'C:\Program Files (x86)\LANDesk\LDClient\enuSCN32.MRL' 'LDISCN32.EXE': Loaded 'C:\Program Files (x86)\LANDesk\LDClient\libhttp.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\mswsock.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\WSHTCPIP.DLL', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\apphelp.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'ImageAtBase0x22b0000', Loading disabled by Include/Exclude setting. 'LDISCN32.EXE': Unloaded 'ImageAtBase0x22b0000' 'LDISCN32.EXE': Loaded 'ImageAtBase0xa40000', Loading disabled by Include/Exclude setting. 'LDISCN32.EXE': Unloaded 'ImageAtBase0xa40000' 'LDISCN32.EXE': Loaded 'ImageAtBase0xa40000', Loading disabled by Include/Exclude setting. 'LDISCN32.EXE': Unloaded 'ImageAtBase0xa40000' 'LDISCN32.EXE': Loaded 'ImageAtBase0x22b0000', Loading disabled by Include/Exclude setting. 'LDISCN32.EXE': Unloaded 'ImageAtBase0x22b0000' 'LDISCN32.EXE': Loaded 'ImageAtBase0x4100000', Loading disabled by Include/Exclude setting. 'LDISCN32.EXE': Unloaded 'ImageAtBase0x4100000' 'LDISCN32.EXE': Loaded 'ImageAtBase0x22b0000', Loading disabled by Include/Exclude setting. 'LDISCN32.EXE': Unloaded 'ImageAtBase0x22b0000' 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\IPHLPAPI.DLL', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\winnsi.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\dhcpcsvc6.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\dhcpcsvc.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\FirewallAPI.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\hnetcfg.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\atl.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\slc.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\gpapi.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\cryptsp.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\rsaenh.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\RpcRtRemote.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\netshell.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\nlaapi.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\wbem\wbemprox.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\wbemcomn2.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\wbem\wbemsvc.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\wbem\fastprox.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\ntdsapi.dll', Cannot find or open the PDB file First-chance exception at 0x0041488c in LDISCN32.EXE: 0xC000001D: Illegal Instruction. First-chance exception at 0x00414908 in LDISCN32.EXE: 0xC0000096: Privileged instruction. 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\taskschd.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\xmllite.dll', Cannot find or open the PDB file First-chance exception at 0x00414908 in LDISCN32.EXE: 0xC0000096: Privileged instruction. First-chance exception at 0x0041488c in LDISCN32.EXE: 0xC000001D: Illegal Instruction. 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\wevtapi.dll', Cannot find or open the PDB file First-chance exception at 0x777bfa02 in LDISCN32.EXE: 0xC0000008: An invalid handle was specified. Unhandled exception at 0x777bfa02 in LDISCN32.EXE: 0xC0000008: An invalid handle was specified. 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\wintrust.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\crypt32.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\msasn1.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Program Files (x86)\LANDesk\LDClient\ldavhlpr.dll', Binary was not built with debug information. 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\msi.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\winsta.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\MMDevAPI.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\propsys.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\wdmaud.drv', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\ksuser.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\avrt.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\rdpendp.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\msacm32.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\AudioSes.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\msacm32.drv', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\midimap.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Program Files (x86)\LANDesk\LDClient\ldaccount.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\samlib.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\cscapi.dll', Cannot find or open the PDB file 'LDISCN32.EXE': Unloaded 'C:\Program Files (x86)\LANDesk\LDClient\ldaccount.dll' 'LDISCN32.EXE': Loaded 'C:\Windows\SysWOW64\logoncli.dll', Cannot find or open the PDB file
STATUS_STACK_BUFFER_OVERRUN encountered LDISCN32.EXE has triggered a breakpoint The thread 'Win32 Thread' (0x6b0) has exited with code -1073740791 (0xc0000409). The thread 'Win32 Thread' (0x730) has exited with code -1073740791 (0xc0000409). The thread 'Win32 Thread' (0x1538) has exited with code -1073740791 (0xc0000409). The thread 'Win32 Thread' (0x15d4) has exited with code -1073740791 (0xc0000409). The thread 'Win32 Thread' (0x974) has exited with code -1073740791 (0xc0000409). The thread 'Win32 Thread' (0xd9c) has exited with code -1073740791 (0xc0000409). The thread 'Win32 Thread' (0x17b4) has exited with code -1073740791 (0xc0000409). The program '[460] LDISCN32.EXE: Native' has exited with code -1073740791 (0xc0000409). |
↧
Missing Attributes From Inventory
Hello there,
I was adding custom attributes into LDMS inventory to import some data into it. Then I was asked to change the location of these attribute (Instead of being the device, they wanted to have them under Custom Data). So I deleted the old attributes and added them again under Custom Data.
Now I am not able to see these attributes under the Custom Data. However, if I try to create a new column set, the attributes will show up (Including the ones that I deleted)
Can anyone help with that?
↧
Last Software Scan Date is NOT updating
I have an issue where several thousand machines are not updating their Last Software Scan Date value after a full scan is performed.
Using a LANDesk script to force a full scan, the following command runs:
REMEXEC1=<qt/>%LDMS_CLIENT_DIR%\LDISCN32.EXE<qt/> /NTT=%server%:5007 /S="%server%" /I=HTTP://%server%/ldlogon/ldappl3.ldz /NOUI /NOCD /F /SYNC
On almost 4000 machines, 3500 report as successfully scanned.
When I run a report or a query on LAST Software Scan Date - the date does not change and remains between 10 and 30 days ago. Other "Last scanned" fields update with the current date.
1. Why is this date field not updating?
2. Can I be reasonably sure that Software scans are not occuring?
3. What can I do to make sure that software scans are occuring and that the date field gets updated?
Running LD 9 SP3
↧
Inventory Query for PowerShell Version
Hi there,
Wondering if anyone has had any success in getting reliable data back from Inventory on the version of PowerShell installed? If so, would you mind sharing the secret sauce?
Thanks in advance,
Kevin
↧
↧
Security Update for Microsoft Windows not showing in inventory
I have a Window 10 client (1607) that has the patch for wannacrypt installed (KB4013429) along with a number of other patches. KB4013429 was installed 4/5/2017. However, inventory just shows 5 updates installed and KB4013429 is not one of them. I'm trying to scan for how many machines are patched. There are other machines that do report that patch installed.
I've tried running full sync scans from the console end, running inventory from the client end, re-installing the client, deleting the client from the console and again re-installing the client with the same results. Inventory\Name\OS\Updates\updates still only shows 5 installed updates.
Last Software Scan Date and Last Updated by Inventory Scanner all show today's date and the time is just after client installation
LD version is 9.60.2.48
Patch was originally installed through our WSUS server
↧
Can you add other assets to Inventory?
I am looking to associate monitors and docks to a workstation? Is this possible?
I am also looking to track peripherals (wireless headsets) to users, can we add other hardware types, and if so how can we do so?
-Adam
↧
Lot of error scan files under Ldscan folder
Hi,
I have lot of error scan files under core\ldmain\ldscan\errorscan.
Do I need worry about that??
What is causing this issue??
How can I fix this issue??
Thanks in advance..
Dinesh
↧
How does the inventory really work ?
Hello everyone,
I am a new Ivanti user and this is my first post.
I am a bit frustrated regarding the inventory local scheduler and I wonder if is there somebody that is facing the same issue.
Basically, in the Local Scheduler Command I configured the settings you can see in the attached file but I am not able to handle these tasks as desidered.
Although these settings, all my PCs run the inventory scan in different days and not the same days I would like for.
I mean, I would like that my inventories always run on Monday-Wednesda and Friday from 1:00pm to 2:00pm but it is not and I do not understand why !!
I configured the inventory starting from Monday till Friday but it seems that it considers Saturdays and Sundays too.
So, is it right (by design) or is it a bug ?
Just another example of a PC which will try to start the inventory on Saturday (...but it will not start it because of it will be turned off on that day):
7: C:\Program Files (x86)\LANDesk\LDClient\ldiscn32.exe /noui
handle : 777
start : Sat Mar 10 13:00:02 2018
frequency : 172800
Filter 1 : Time of Day 13 to 14
Filter 2 : Day of Week 1 to 5
I can understad a mini-inventory (in different days) only when a PC changes its IP address but this is a setting that has been rightly configured:
8: C:\Program Files (x86)\LANDesk\LDClient\ldiscn32.exe /mini /noui
handle : 778
start : Fri Mar 9 09:25:34 2018
frequency : 600
Filter 1 : IP Address Change Filter
Lastly, but not less important:
I have some users that complaint about the inventory because of it takes long time before finishing (sometimes till 2 or more hours) and I can not understand this too.
As far as I know, based on this URL:
Inventory Delta Scan Whitepaper
the PCs should run a really slight inventory if there is nothing changed from the previuos one but it does not seems because, as I wrote, it seems that inventory always scans all the folders and path that have been already scanned.
I really appreciate any useful information or tip on how to "fix" my issues.
Bye
Marco
↧
↧
Inventory Failing On 2016 Datacenter Servers: bCriticalError/LookupAccountName Failed '1332'
We're on LDMS 2016 SU4. I have inventory failing on two servers. The scans aren't making it into the ldscan folder on the core at all, so nothing is showing up for this server in the ErrorScan folder. Other servers on the same subnet scan in fine, and windows firewall is off (domain, private, and public) on this guy. I have completely uninstalled and reinstalled the agent, and I get a failure on the inventory scan portion of the agent installation (see below wscfg32 log). The OS on both of these is 2016 Server Datacenter, and these are the only two servers in our environment currently running this OS. Could this possibly be a compatibility issue?
WSCFG32 Log:
Mon, 13 Mar 2017 10:27:15 SUCCEEDED: Running application: C:\Program Files (x86)\LANDesk\LDClient\localsch.exe /taskid=410 "/exe=C:\Program Files (x86)\LANDesk\LDClient\BrokerConfig.exe" /cmd="/n" /freq=86400 /autodelay="1|60"
Mon, 13 Mar 2017 10:27:15 INI: EXEC04=C:\Program Files (x86)\LANDesk\LDClient\vulscan.exe, /changesettingsnoreport, INSTALLONLY
Mon, 13 Mar 2017 10:27:15 Starting process: C:\Program Files (x86)\LANDesk\LDClient\vulscan.exe /changesettingsnoreport
Mon, 13 Mar 2017 10:27:49 Processes returned : 229835193
Mon, 13 Mar 2017 10:27:49 WARNING: Non-standard return code for: C:\Program Files (x86)\LANDesk\LDClient\vulscan.exe, Exit code: 229835193
Mon, 13 Mar 2017 10:27:49 SUCCEEDED: Running application: C:\Program Files (x86)\LANDesk\LDClient\vulscan.exe /changesettingsnoreport
Mon, 13 Mar 2017 10:27:49 INI: EXEC01=C:\Program Files (x86)\LANDesk\LDClient\LDISCN32.EXE, /NOUI /NOCD /SYNC /F, INSTALLONLY
Mon, 13 Mar 2017 10:27:49 Starting process: C:\Program Files (x86)\LANDesk\LDClient\LDISCN32.EXE /NOUI /NOCD /SYNC /F
Mon, 13 Mar 2017 10:28:37 Processes returned : -1073740791
Mon, 13 Mar 2017 10:28:37 CheckProcessExitCode processed app name: LDISCN32.EXE
Mon, 13 Mar 2017 10:28:37 FAILED: Running application: C:\Program Files (x86)\LANDesk\LDClient\LDISCN32.EXE /NOUI /NOCD /SYNC /F
Mon, 13 Mar 2017 10:28:37 FAILED: bCriticalError set to TRUE. Processing C:\Program Files (x86)\LANDesk\LDClient\LDISCN32.EXE
Mon, 13 Mar 2017 10:28:37 Overall Install Status:
Mon, 13 Mar 2017 10:28:37 FAILED: Finished
Mon, 13 Mar 2017 10:28:37 SUCCEEDED: Delete (c:\ENUNTCFG.MRL)
Mon, 13 Mar 2017 10:28:37 FAILED: bCriticalError is true. Setting exit code to ERROR_INSTALL_FAILURE
LDISCN32 Log:
Mon, 13 Mar 2017 10:27:50 Query for processor idle time: '\Processor(_Total)\% Idle Time'
Mon, 13 Mar 2017 10:28:02 Checking if firewall is enabled : ({9A6CFA40-5CE3-4D5D-A70A-D87C22FCF3ED})
Mon, 13 Mar 2017 10:28:02 Firewall service profile found
Mon, 13 Mar 2017 10:28:02 pszwDeviceName = Hyper-V Virtual Ethernet Adapter
Mon, 13 Mar 2017 10:28:02 pszwName = vEthernet (HNS Internal NIC)
Mon, 13 Mar 2017 10:28:02 pszwDeviceName = vmxnet3 Ethernet Adapter #2
Mon, 13 Mar 2017 10:28:02 pszwName = Ethernet0 3
Mon, 13 Mar 2017 10:28:02 Global firewall is not enabled
Mon, 13 Mar 2017 10:28:03 IsAMD = false, Initial Logical Processors = 1
Mon, 13 Mar 2017 10:28:03 SMTSelectMask:00000000, CoreSelectMask:00000000, PkgSelectMask:ffffffff, PkgSelectMaskShift: 0
Mon, 13 Mar 2017 10:28:03 Core Bits = 0, Logical Bits = 0
Mon, 13 Mar 2017 10:28:03 Package 0: Cores: 1
Mon, 13 Mar 2017 10:28:03 Package 2: Cores: 1
Mon, 13 Mar 2017 10:28:03 Package 4: Cores: 1
Mon, 13 Mar 2017 10:28:03 Package 6: Cores: 1
Mon, 13 Mar 2017 10:28:03 Number of processors = 4, number of cores = 1, hyperthreading = false
Mon, 13 Mar 2017 10:28:03 We can not verify the platform!
Mon, 13 Mar 2017 10:28:03 We can not verify the platform!
Mon, 13 Mar 2017 10:28:03 We can not verify the platform!
Mon, 13 Mar 2017 10:28:03 We can not verify the platform!
Mon, 13 Mar 2017 10:28:03 vulscan app path dir: C:\Program Files (x86)\LANDesk\LDClient\
Mon, 13 Mar 2017 10:28:03 Failed to get the windefender auto protect state
Mon, 13 Mar 2017 10:28:03 LookupAccountName failed '1332'
Mon, 13 Mar 2017 10:28:03 Checking if firewall is enabled : ({9A6CFA40-5CE3-4D5D-A70A-D87C22FCF3ED})
Mon, 13 Mar 2017 10:28:04 Firewall service profile found
Mon, 13 Mar 2017 10:28:04 pszwDeviceName = Hyper-V Virtual Ethernet Adapter
Mon, 13 Mar 2017 10:28:04 pszwName = vEthernet (HNS Internal NIC)
Mon, 13 Mar 2017 10:28:04 pszwDeviceName = vmxnet3 Ethernet Adapter #2
Mon, 13 Mar 2017 10:28:04 pszwName = Ethernet0 3
Mon, 13 Mar 2017 10:28:04 Global firewall is not enabled
Mon, 13 Mar 2017 10:28:20 LookupAccountName failed '1332'
Mon, 13 Mar 2017 10:28:20 open key Software\Utimaco\SGEasy with flags 0x20019 returns handle 0, status 2
Mon, 13 Mar 2017 10:28:21 LookupAccountName failed '1332'
Mon, 13 Mar 2017 10:28:21 CPolicyHistory::LoadHistoryFile: Failed to parse C:\Program Files (x86)\LANDesk\LDClient\Data\TaskHistory.xml
Mon, 13 Mar 2017 10:28:21 CPolicyHistory::LoadHistoryDaysToKeep: No task history maintenance to perform, registry settings for task history maintenance mode is '-1'
↧
MSSQL Query to get Asset Information
Hi,
I am trying to figure out a way to write a SQL query to the Landesk database to provide all the information found in the dbo.Computer table along with the OS.
Does anyone have a snippit of SQL that I can run to get this information? The idea is for me to create a web front-end for other departments in IT to query asset inventory information from a custom web application. I just don't know where the OS info is stored. I would imagine there will be some joins to other tables.
Any help would be appreciated.
↧
Inventory Issue
Hello - I'm hoping someone could help me out! I am not sure if I'm having two separate issues or if they are related. This is for Management Suite 9.6 SP3.
First - we noticed that the agents weren't reporting accurate inventory scans. Example: we would update a program on a device and, even though we did full inventory syncs, it would never update within LANDesk. I checked the Event Viewer and we keep seeing "Login failed for user 'NT AUTHORITY\SYSTEM'. Reason: Failed to open the explicitly specified database 'ReportServer'. [CLIENT: <server IP address>]. Would that be the reason why the agents inventory is updating in LANDesk?
Second - we noticed that the LANDesk InventorySync Service isn't started (even though it's set for Automatic Startup) and when we go to start it, we get the following error: "Windows could not start the LANDesk InventorySync Service service on Local Computer. Error 1053: The service did not respond to the start or control request in a timely fashion". When we go into C:\Program Files\LANDesk\ManagementSuite\MobInvUpServ.exe to try to run in manually, we get an APPCRASH message for that application showing the Fault Module Name as KERNELBASE.dll. How would I go about fixing this?
↧
Distribution Package End User Notifications - Distribution and Patch Build
Good Evening all,
I wonder if anyone could help with a quick inquiry ... hopefully.
I shall apologies, I'm not only new to this site and discussion, I am also a rather new LANDesk Administrator in my organisation having only shadowed previous Administrators before their departure. But was deemed okay for the role / to help out **cringe .. I know**.
IEM 2017 V 10.1.10.287
Problem:
I have been attempting to compile a Software Bundle for the Deployment of Office 2016 in our Organisation, whilst removing any previous installations of Office and including the recommended reboot in between and then afterwards.
I have it working is the good news, using two batch files.
By: Running a Batch file (run Offscrub and run uninstall string), reboot (using the new Package Bundle Inter Package action), batch file to silent mount iso, install, run config file and then another reboot (again using Inter Package action).
I realize people will all have different opinions, but this is what was done in crude terms before so I have simply copied and updated.
However, now the problem.
I have built a Agent Setting with Distribution and Patch set up for informing the user and allowing a deferral, but despite toggling the Progress Options , I'm unable to get any sort of Notification that the task is still running after the first Reboot and Whilst it's Installing 2016, even the System Try icon appears to disappear and as a result the next instant the user knows it's running is when the Reboot appears.
Is there anyway I can achieve this? or anything similar?
Thanks
↧
↧
Duplicate Device IDs overwriting Inventory records in Endpoint Manager
This article addresses how to resolve a specific issue with inventory records being overwritten due to duplicate device IDs in your environment caused by a misconfigured image or an imaging process that was done without correctly following your internal imaging process. Most likely the LANDesk agent was added to the image or was installed to a machine out of order during a new build.
How to determine if you are having a duplicate device ID issue resulting from the imaging process already including a LANDesk agent
Unfortunately, some of this is going to be you, your admin, or other console users saying that devices are just missing or not displaying in the network view. Noticing this issue may be occurring requires more detective work than a distinct and clear error.
If you are seeing weird behaviors with a batch of similar machines disappearing/reappearing in Inventory, review your Core server ldscan folder
[COREPATH]\Program Files\LANDesk\ManagementSuite\ldscan\ErrorScan
When opening the various .scn files (.scn file extension is the OOTB default for EPM, your environment may be configured differently), you will be looking for the following information:
Device ID ={***************************************}
Device Name =***********
Network - TCPIP - Host Name =************.domain
If you see multiple files with matching device IDs but different device name/hostname then you probably have an issue with how the machine was imaged
The reason these items are showing up in ErrorScan is because the core doesn't recognize the information even though it thinks it already has a matching device ID. Prove this by looking at the LANDesk Inventory Server warnings in the Application section of Event Viewer on the core
Run eventvwr.msc
Expand Windows Logs
Click Application
You can filter or sort by Source (this may take a few minutes)
How to resolve duplicate device IDs overwriting inventory records caused by an image with the LANDesk agent
NOTE: As a user with Administrative privileges on the client device
1. STOP all LANDESK related services
2. Delete the following Registry Keys for 32bit clients:
HKLM\SOFTWARE\Intel\LANDesk\Common Api\UniqueID
HKLM\SOFTWARE\LANDesk\Common Api\UniqueID
HKLM\SOFTWARE\LANDesk\Inventory\LogonHistory\Logons
HKLM\SOFTWARE\LANDesk\ManagementSuite\WinClient\SoftwareMonitoring\MonitorLog contents
Delete the following Registry Keys for 64 bit clients:
HKLM\SOFTWARE\Wow6432Node\Intel\LANDesk\Common Api\UniqueID
HKLM\SOFTWARE\Wow6432Node\LANDesk\Common Api\UniqueID
HKLM\SOFTWARE\Wow6432Node\LANDesk\Inventory\LogonHistory\Logons
HKLM\SOFTWARE\Wow6432Node\LANDesk\ManagementSuite\WinClient\SoftwareMonitoring\MonitorLog contents
3. C:\ProgramData\LANDesk (delete the entire directory and subdirectories, this is a hidden directory)
4. Run Security Scan - look for this line "Sending current settings information to core. Failed: Core has no inventory data for this computer" (this is important to make the inventory scan work, otherwise it will fail and you will see the entry in Event Viewer)
Without this step, I was encountering an error stating "LDISCN32: The inventory server [CORE] did not respond"
5. Open command prompt and run C:\"Program Files (x86)"\LANDesk\LDClient\LDISCN32.EXE /V /F /SYNC
You do not have to wait for Security Scan to finish, it will probably fail anyways until it can properly sync up with the right inventory information
↧
Scan empty
Hi !
We have Landesk Management Suite Version 8.70.0.109
The server is in DMZ
The workstation can speak with the server but the server can't speak with the workstations.
When we open Landesk in the server, we have only the IP Adress (screen)
The Landesk Agent is installing in the workstation by GPO
Thanks in advance for any help.
↧
LookupAccountName failed '1332'
Preface: I'm new to landesk so take it easy on me but please let me know if there are easier ways to do what I'm trying to do
I have multiple cores in my environment and I recently tried to migrate a couple hundred servers from one core to another by pushing a new Server Agent Configuration. The majority seem to have worked but there are several that have not reported their inventory scans to the new core.
After connecting to one of the failed machines I tried to run this to get a full scan uploaded to the core:
LDISCN32.EXE" /NTT=core.domain:5007 /RSS /F /S= /I=core.domain HTTP://core.domain/ldlogon/ldappl3.ldz /V /sync
In the ldiscn32.log file I see the following error:
LookupAccountName failed '1332'
The scan does end up going to the new core but ends up under the ldscan\ErrorScan directory.
Anyone know how to troubleshoot this?
↧