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
Some of my assests do not automatically update with a new IP address when they have been off the network past their IP address lease expiry time. When this happens the device appears to be online but when you connect to it the following message appears:
The IP address of the computer you are attempting to control does not match the IP name on your network. Do you want to continue? Yes or No. If you click Yes this will connect to adifferent machine.
Is there a way to control this?
Adrian
Hello,
We are currently running Novell with Active Directory on the backend. Due to minor infrastructure issues we are having problems querying different departments. The data does append into the registry under HKCU, Volatile Environment in the GROUPS section and I have added this into the LDAPPL3 file and published it. I then ran a full inventory but the info does not show in the custom data field in the inventory report.
The entry I added to the LDAPPL3 file is as follows:
;Novell Groups
KEY=HKCU, Volatile Environment\GROUP,Custom Data - Novell - Default Group
Is there something I'm doing wrong?
Thank you in advance.
Is anyone else having problems with the Inventory Scanner incorrectly reporting LoginName on 64-bit Windows 7? I think I figured out why this is happening, but when I checked this forum to see if anyone else reported the problem I can't find any posts.
It seems the Inventory Scanner is reporting the contents of
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\DefaultUserName
which isn't used by Windows 7/64.
I found some postings on the Internet which suggest using this regkey instead:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Authentication\LogonUI\LastLoggedOnUser
I've opened a support case, but I'm still looking for confirmation that I'm right, so that this is treated as a bug.
To whom it may concerns,
There is a fixed hard drive serial number incorrect situation. We found several customer machines which installed LDMS 9.5 SP3 got this problem. Please see the image file serialnumber2.png, This pic was captured this machine inventory tree, and the hard drive serial number is incorrect. But if see the image file named serialnumber1.png. This pic was captured from the machine powershell command line. and it did returned the correct hard drive serial number. I have checked the workaround solution from https://community.landesk.com/support/docs/32711. But I hope this problem can be fixed future.
Hi,
we are going in production but we have a problem because the customer has many solaris 10 machine and we don't know how inventory they.
Is there a solaris 10 Agent ?
is it expected ?
Thanks
Andrea
I found this on dropped packates but I think I am not doing it correctly; Help please.
I was able to copy the files to the client machine using a batch file. When I tried to execute Step # 2 using another batch file I got an error message stating under the result column "incorrect function"
How to find the number and size of PST files in the organization.
This script is an excellent example of how LANDesk Management Suite can be extended with VBSscript to gather and query just about any random chunk of data.
Distribute the contents of findpst.zip to your client's c:\program files\landesk\ldclient directory (if that's not your %LDCLIENTDIR%, you'll want to edit these two files appropriately).
Send a managed script to execute the script: REMEXEC00="wscript.exe C:\Progra~1\LANDesk\LDClient\FindPST.vbs", SYNC ought to do.
Force an inventory scan.
Query on machines where Custom Data - Total PST Size is larger than you like.
Since this is using an LDSCNHLP.INI extension, you'll want to manually edit that file if you plan on using findpst.vbs in addition to any other scripts that are launched from within that file.
Hello,
I'm doing a distribution using an LDAP query as a target. Since we have a small number of terminals that are shared (people use them for a few minutes, log off and then another user logs in, etc), some of these terminals are showing up on the query as one of the users in the LDAP query is listed as the primary owner of these terminals (it is showing the real PC of this end-user plus the terminals).
Is there a way to force these specific terminals to not keep a primary owner history so that when the inventory scan runs, it doesn't report this info back to the core?
Or is there a way to exclude PCs from an LDAP query?
I normally use Inventory Queries and can exclude PCs with it but due to the nature of this SWD, I need to use LDAP...
Thanks
Hi Good Morning,
Im having a hard time figuring out on what to do.
I need to clean the inventory, that all inactive client that has not been connected in the network for more 2 months should be deleted in Landesk.
How do i know if the unit is active within 2 months? does landesk have the capability to check if unit is active? or there is a time stamp that when a client connects to the network landesk will register that the unit is active?
Thanks,
Joe
Hello,
I'm getting this error on some 2003 servers when I try to run the inventory scan.
Any help on this?
Thanks
We have 90% of our organization outside our internal network. All these clients reach us through the management gateway. However, we get a bunch of them that have trouble sending in their scans. They get the following message when the scan in manually run. It is very intermittent. We can have 2 machines in the very same office, one works one doesn't.
Some things that may help:
Any help would be great.
Also -> Can I do an inventory scan to a file and then dump that file into the ldscan folder on our core server?
Hi
Apologies for what might be a very simple question...
I am having issues with a number of devices not updating in the inventory. I have tried running a manual run of of LDISCN32.exe with the switches /F /L /V (i a have also tried various other swithces) but i can see no evidence of a log file or error report? also I can see no evidence of the scan file being passed back to the server. I am sure I'm just not looking in the right plave for error logging?
On a seperate note these devices do not apply policy, when process runs it identifies a policy is required but does not execute its application. See attached image.
Thanks in advance
We have inventory on the core server that displays mac address at the computer name
This problem is in 8.7 sp6 an 9.0 sp2
When Inventory Scan is launched using the shortcut located in the Start Menu under Landesk management it displays the following error: "Unable to launch custom inventory application C:\Program Files (x86)\LANDesk\LDCLient\ldcstm32.exe /s"
The inventory runs fune after clicking ok on the popup message. Inventry works fine when called by the Local Scheduler. so far the problem has been detected in windows 7 64 bit boxes only.
Hello,
I am working on setting the wake on lan setting in the bios to on for remotely turning on pc's at night to install updates. The question i have is how can i validate the current status of WOL on a machine?
Using the Dell Client Configuration Utility, i can create a package that will read BIOS settings, and write BIOS settings. Once it completes, it creates an XML file with its findings.
Is there a way to have landesk pull this information, or do i need to write some sort of vb script to parce the xml file and create a custom reg key to report against?
Has any one already one this?
Thanks in advance.
- Steve
Has anyone got a decent, reliable method or script to detect all mapped drives? I have the crude version below that works but reporting from this data collection isn't the easiest.
Since we're movng from Novell to AD, I need to filter out my Novell mappings and only report on the non-Novell mappings. I currently do this with an array of known Novell servers then searching their existence in the string of the found mappings, then liminating them. Just looking for a better way.
Thanks in advance!
Rich
Hi,
I have numerous computers that are custom built and I can't seem to find a unique ID or serial that all the computers in my environment have and that LANDesk will pickup.
Has anyone had a similar challenge?
Hi,
I am running a parallel upgrade 95 sp1 to 96 sp1.
I am pushing the new 96 agent using a scheduled task on the 95 server.
I noticed that machines with the new agent are reporting there inventory to both servers.
Inventory has been stripped off some switches that were pointing to the Core server.So I understood that the client was picking the Core server name from the registry. HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Intel\LANDesk\LDWM\coreserver
Since the registry of the machine I am looking at has the correct name for the core server does it mean the client is getting the old server name from the certificates??
Thank you
Dear all,
I have an Static Device Group its called "Server Patch Exceptions" in this Group i insert manually Server from my Network to exclude it from a Patchmanagemant.
Now i have the Problem i have a Dynamic Scope Obejct with an Query this Query search all Server and Devices with Agentname "xy" and will be insert at my List.
How can i modify the Querie to say search all Devices based on Agentname "xy" included the Exclude the static Group.
To Example
Server 1 has Agent Name "xy"
Server 2 has Agent Name "xy"
Server 3 has Agent Name "xy" but its in the Static group "Server Patch Exceptions"
Scope Should be listet --> Server 1 and Server 2
The Backround is when i Create an Patch-Task i Instert the Scope in to the Target and all Device will be Patched but the Server in "Server Patch Exceptions" should be skipped
thank you all
Thomas
Hey everyone,
We have deployed a new client to a few thousand PC's and are noticing that the locally scheduled tasks (vulscan and inventory scan) are not running on some PC's. The same client went on all systems so we don't suspect anything with the client. I know this is a pretty broad question but can anyone offer any suggestions as to what would cause the local scheduler to fail running on some systems?
Thanks