We're on LD v8.70.0.109.

The last several months it seems we've had problems with LD preforming an inventory scan.  Which, it appears, has been due to the Inventory service needing to be stopped and restarted.  ( The first time I did this, I bumped the retry value to as high as it would go, if I recall correctly. )

But one of the things I noticed back then, and see that we still have...is some sort of DNS issue.

I thought that DNS was supposed to be automatically updated.  Yet our DNS server has multiple computer names associated with one IP address.  Not every machine, mind you, but some.  Some have two (2), some have three (3), and at least one I just saw has four (4).

I also checked Reverse Lookup.  And the record that it had, had the correct computer name, with an address that didn't match ANY of the multiple address records.

Consequently...I'm really confused.

I went looking in this forum to see if anyone else was having a similar problem.  I found a discussion in Remote Control I believe it was, named: IP / Name mismatch.

One of the things mentioned was making sure that the "Register this connection's addresses in DNS" checkbox was checked in Advanced of the TCP/IP properties.  I myself have always made sure that this was checked, and have assumed that my co-workers have done likewise.  But because I saw it mentioned, I asked one of my co-workers.  He said that he always does on a server, but hasn't necessarily been doing so on a client, because..."It's supposed to do it automatically.".

The thread also mentioned about setting the agent to update the inventory db on an ip change, to keep the LD db current.  I've gone looking, but can't seem to find where I would do this in 8.7.  Perhaps it's only in 8.8?

Is there a way to write a script so I could easily check all of our clients to see if the update DNS box has been checked?  All these bad DNS entries have me really concerned.  How do I fix my DNS?

As usual, any thoughts, ideas, suggestions are welcome...thanks in advance.

Tom

Hello,

I'm getting this error on some 2003 servers when I try to run the inventory scan.

LDISCN32.exe - Application Error

The application failed to initialize properly (0xc0150002). Click on OK to terminate the application.

Any help on this?

Thanks

Hi

I'm trying to setup Landesk 9 to scan for Microsoft access files (mdb's etc) on machines throughout our estate. Reading the forums I have got up to the point where I have to update the ldappl3.template, but after that I'm not too sure what to do.

Some posts point to the SLM and some others point to manage software list.

Could someone point me in the right direction?

Cheers

We're on LANDesk 9 SP2 and I seem to have a problem lately where Inventory Scans are timing out on Windows XP client computers. I'm getting an error in the Application log on affected clients...

"Event ID 1002"

"Application Hang"

"Hanging application LDISCN32.EXE, version 9.0.2.120, hang module hungapp, version 0.0.0.0, hang address 0x00000000."

We first noticed the problem because we use a command in our OS deployment process to send a full inventory scan after a machine is re-imaged. On some OS deployment jobs we started to see clients that would hang and never complete the Inventory Scan section of the script. I had to terminate the ldiscn32.exe process in Task Manager. If I run an Inventory Scan from the Start Menu shortcut I see that Hardware Inventory is complete, Software Inventory runs to about 80% on the progress bar and then just stays there, having processed around 37,400 files. (The actual number of files processed varies.)

I'm not sure how many of our client computers are affected, but I suspect it's quite a few because I see a number of inventory records that have not seen an updated software inventory in many weeks, even though the machines are connected to the network every day. I don't think it's a problem on the core because my ldscan folder is not filling up with SCN files, and some clients are sending inventory successfully.

Any help would be greatly appreciated.

Jayson

Bonjour quelqu’un connaîtrait l’ URL permettant de lancer l’inventaire LanDesk ?

merci pour votre aide !

Hi,

I have installed LDMS2016 on a Windows 2012 r2 server, I deployed the agent on this server. I ran an inventory scan but it say "lost contact". Do you have any idea ?

Hello,

I have created an Agent Configuration Windows with 1 Day frequency scanning (Every day at 18:00).

I have installed 5 days ago the Agent, but I have seen, on Core Server,  that the last scanning date is 5 days ago.

It seems that the scheduling doesn't start every day at 18:00.

How Can I verify it ?

Is it possible change the scheduling scanning Agent side ?

Thank you.

Andrea.

Topic was edited by: Paul Hoffmann (LANDesk EMEA Technical Lead)

Bonjour,

Pour le compte d'un client, je dois effectuer un inventaire sans agent de son parc informatique. La premiere etape consiste a decouvrir les poste par le bias des peripherique non gerés UDD en specifiant les plages Ip à analyser.

Pour infos :

CoreServeur : LDMS 8.8 SP3        Windows 2003 Entreprise

Postes du parc informatiques : Windows XP avec des configurations heterogene ( SP1 ; SP2 ; SP3)

La deuxieme etape, consisteà faire un inventaire sur la machine cible à l'aide de l'outil lddiscover. J'ai ajouter les fichiers necessaire à l'execution de ldiscn32.exe dans le repertoire de lddiscover (environ une dizaine, je les citerais dans un prochain poste, j'ai mit  les fichiers des version precedente de landesk et les nouveaux relatif au SP3). J'ai créer le script permettant de copier l'ensemble de ces fichiers sur les postes clients.

Dans l'ensemble, ca fonctionne tres bien, sauf pour des cas isolés, et la j'aurais besoins d'un peu d'aide

1 - Sur certains postes cibles le firewall de windows ( ICF) est activé , donc mes trames tcp de lddiscover ne passe pas !! ya t'il un moyen de contourné ce systeme ?

2 - Certains postes sont en XP SP1, donc depourvu du firewall windows , pourtant je n'arrive pas à les contacter. Pourquoi ??

3 - Les partages administratifs comme le C$ que j'utilise pour y copier les fichiers necessaire au deroulement de l'inventaire, n'est pas joignable depuis mon coreServeur pour certaines machines cibles. Puis-je contourner cette methode ??

4 -J'ai constater une erreur de ldiscn32.exe sur un poste XP SP3 une fois la copie terminée. Normalement mon script lance automatiquement un scan et par la meme occasion me renvoi un fichier *.scn dans un repertoire scpecifque ( mieux vaut deux verification que pas assez =). et la rien !!!!???!!!!

Je me suis deplacer sur le poste en question, et avec grand etonnement, quand j'execute ldiscn32.exe, normalement je devrait avoir une popup avec les parametres à passer pour les lignes de commande. Or la, l'application plante carrement avec l'erreur "0xC0150002". Je suis inquiet car je risque d'avoir d'autre cas identique. Auriez vous une idée de la raison de cette erreur !!!

5 - Mon client utilise des adresses IP de classe A. hors son parc n'avoisine que les 6000 postes. Ce qui est totalement disproportionner pour son besoin, bref passons. le souci, c'est que quand j'effectue un scan UDD pour decouvrir les machines sur le reseau, celui-ci prend un temps monstre pour decouvrir un seul sous reseau. ( Par exemple je scan le sous reseau 10.8.0.0 -> 10.8.31.255 /19 ) , soit 2^13 - 2 = 8190 machines par sous reseau. Sachant qu'il y en a environ 800 sous reseau et qu'il me faut environ 1h30 pour scanner un seul de ces sous reseau. d'ici la fin de l'année je pensse terminer le "scannage" de son parc informatique =). Sinon n'y a t'il pas moyen d'acceler le ping entre chaque machine, et de ne pas s'attarder sur les adresses IP non utilisée ????

6 - Des erreurs lors de la phase de decouverte avec lddiscover concerne le protocol RPC. indiquant que ma connexion ne peut s'etablir. D'apres la documentation de lddiscover, cela implique que mes postes sont des win9x , hors tous les postes sont bel et bien des XP. Est-ce du a une mauvaise gestion des machines de mon client, comment retablir le protocol RPC ??

7 - Dans le fichier ldiscn32.log, je constate une ligne indiquant " can't connect the database " , ou quelque chose de ce style ( je mettrais les bon termes dans mon prochain poste). je voulias savoir si cela concernait la base sql de landesk, ou une base d'inventaire. Car je vois pas pourquoi ce message s'affiche, normalement mon serveur est bien operaionnel. Jusqu'a preuve du contraire =D

Bon courage, a celui qui pourra me repondre. Je termine ma mission vendredi, j'espere avoir des news rapidement

++

Cordialement

Jeremy

I would like to have the ability to capture logs under "Applications and Services Logs" in the event viewer using LANDesk.  More specifically Applications and Services Logs > Microsoft > Windows > Offline Files > SyncLog.  From what I can tell only "Windows Logs" are currently being captured and put into inventory.  Does anyone know if this it is possible to add these to inventory?  We are trying to find computers that have sync issues by using a query and/or if possible send alerts from alerting.

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'

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.

I work in a secure environment and I have been looking at Landesk data.

I see many systems that have been identified as having a Payments Gateway Client which was concerning due to our PCI requirements.

When I looked into this further, I see data similar to:

Not sure why the package name points to binary in the Microsoft Hyper V guest installer location.  How are packages determined in Landesk?  Is it via a hash database?

What do i need to do to make the scan files get processed faster?

I have a gig link between the servers and SQL server is on SAN. Processor wise, both server have enough to work but seems like creation of .scn files is faster than the processing of the server.. what can be done to help LANDesk with that so that the system does not go out of disk space.

LD9 SP1

Hi All,

We have almost 1500 devices in Core server as client. I am sure there are many systems which has been de commissioned but still showing in network view. How can we configure in Core server which automatically remove any system which was not inventoried in last 1 months.

Regards,

Pawan Kumar

Hello,

I am having an issue with the inventory scan on some of my machines.  The scans all end up in the Errorscan folder.  I have narrowed it down to one item these scans all have in common.  That one line appears to be about 1543 characters long and reads as:

OS - Drivers and Services - Service - (Name:Energy Server Service WILLAMETTE) - Path ="C:\Program Files\Intel\SUR\WILLAMETTE\ESRV\esrv_svc.exe" "--AUTO_START" "--start" "--address" "127.0.0.1" "--port" "49330" "--depend_on_key" "SYSTEM\CurrentControlSet\Services\ESRV_SVC_WILLAMETTE" "--depend_on_value" "run" "--time_in_ms" "--pause" "5000" "--library" "C:\Program Files\Intel\SUR\WILLAMETTE\ESRV\intel_modeler.dll" "--no_pl" "--watchdog" "10" "--watchdog_cpu_usage_limit" "50" "--end_on_error" "--kernel_priority_boost" "--shutdown_priority_boost" "--device_options" " time=no output=w output_folder='C:\ProgramData\Intel\SUR\WILLAMETTE\IntelData' limit_output_by=time output_limit=3600000 output_buffer=1024 il='C:\Program Files\Intel\SUR\WILLAMETTE\ESRV\intel_process_input.dll','process_input_options.txt' il='C:\Program Files\Intel\SUR\WILLAMETTE\ESRV\intel_system_power_state_input.dll' il='C:\Program Files\Intel\SUR\WILLAMETTE\ESRV\intel_quality_and_reliability_input.dll' il='C:\Program Files\Intel\SUR\WILLAMETTE\ESRV\acpi_battery_input.dll' il='C:\Program Files\Intel\SUR\WILLAMETTE\ESRV\sema_thermal_input.dll' il='C:\Program Files\Intel\SUR\WILLAMETTE\ESRV\wifi_input.dll' il='C:\Program Files\Intel\SUR\WILLAMETTE\ESRV\devices_use_input.dll','service=yes' il='C:\Program Files\Intel\SUR\WILLAMETTE\ESRV\intel_disktrace_input.dll','pause=60000 working_dir=C:\ProgramData\Intel\SUR\WILLAMETTE\IntelData override_existing_tracing=no limit_output_by_filesize_mb=10' os='C:\Program Files\Intel\SUR\WILLAMETTE\ESRV\os_counters.txt' "

I noticed that every line item in that section of the SCN file starts off with "OS -"  This scanned item starts off the same way, but it is so long that it continues onto the next line.  My SCN file looks something like this...

OS - Drivers and Servic...

OS - Drivers and Servic...

ESRV\acpi_battery_inpu...

OS - Drivers and Servic...

OS - Drivers and Servic...

As a test, I removed the long entry including the part that continues to the next line.  Saved it, moved it back to to the ldscan folder, and watched it successfully import the inventory.

I believe the inventory scan is getting this entry from the machine's registry.  Is there a way to have it ignore a specific registry key from inventory scans just like you can have it ignore specific folders on local drives?

I am running 9.6 SP1.  Errorscan file attached.  Long entry can be found at line 3564

Thank you in advance for any help.

Hi,

All managed devices have a LANDesk agent with Enabled XDD via ARP and all subnets inside the company are displayed under "Self-electing subnet services" tool. When I check the list of unmanaged devices to get computers which were discovered by XDD via ARP I found only devices which belongs to 2 subnets. I found out that there is an XDD IP filtering applied by default by LANDesk core server and I want to adapt this settings to my network.

In the documentation they said that I have to add a DWORD registry key to the core server to disable this feature (HKEY_LOCAL_MACHINE\SOFTWARE\LANDesk\ManagementSuite\XDD\Filter ) or create new DWORD Registry key to adjust the first and second octet monitoring ranges (HKEY_LOCAL_MACHINE\SOFTWARE\LANDesk\ManagementSuite\XDD\FilterThreshold1 and HKEY_LOCAL_MACHINE\SOFTWARE\LANDesk\ManagementSuite\XDD\FilterThreshold2)

The problem that in LANDesk core server there is no registry entry named "XDD" following that path. Is that okay.

With this feature does the client send information to the core server but the core server ignore them (so they will not displayed under unmanaged devices discovery list) or this settings will be uploaded by all XDD-enabled devices this way they will not try to discover any device which not belong to the default ip range?

LDMS version is 2016.3 and I am in testing phase

This is what I found in XDDClient.log for the elected device in one subnet (please note that in another elected device for another subnet I have the same error messages in the XDD log but devices from that subnet are listed in UDD)

Wed, 16 Nov 2016 10:04:13 ERROR: PostCGI: GetRogueClientHostName failed to get the rogue machine name, error was [11004].

Wed, 16 Nov 2016 10:42:28 ERROR: PostCGI: GetRogueClientHostName failed to get the rogue machine name, error was [11004].

Wed, 16 Nov 2016 10:47:20 ERROR: PostCGI: GetRogueClientHostName failed to get the rogue machine name, error was [11004].

Wed, 16 Nov 2016 10:52:17 ERROR: PostCGI: GetRogueClientHostName failed to get the rogue machine name, error was [11004].

Wed, 16 Nov 2016 10:59:22 ERROR: PostCGI: GetRogueClientHostName failed to get the rogue machine name, error was [11004].

Wed, 16 Nov 2016 11:07:21 ERROR: PostCGI: GetRogueClientHostName failed to get the rogue machine name, error was [11004].

Wed, 16 Nov 2016 11:11:59 ERROR: PostCGI: GetRogueClientHostName failed to get the rogue machine name, error was [11004].

Wed, 16 Nov 2016 11:16:17 ERROR: PostCGI: GetRogueClientHostName failed to get the rogue machine name, error was [11004].

Wed, 16 Nov 2016 11:30:33 ERROR: PostCGI: GetRogueClientHostName failed to get the rogue machine name, error was [11004].

Wed, 16 Nov 2016 16:56:37 ERROR: PostCGI: GetRogueClientHostName failed to get the rogue machine name, error was [11004].

Wed, 16 Nov 2016 19:49:01 ERROR: PostCGI: GetRogueClientHostName failed to get the rogue machine name, error was [11004].

Thu, 17 Nov 2016 08:13:28 ERROR: PostCGI: GetRogueClientHostName failed to get the rogue machine name, error was [11004].

Thu, 17 Nov 2016 09:59:57 ERROR: PostCGI: GetRogueClientHostName failed to get the rogue machine name, error was [11004].

Thu, 17 Nov 2016 10:03:35 ERROR: PostCGI: GetRogueClientHostName failed to get the rogue machine name, error was [11004].

Thu, 17 Nov 2016 10:25:29 ERROR: PostCGI: GetRogueClientHostName failed to get the rogue machine name, error was [11004].

Hi,

there is a Inventory Property - "Computer"."Mass Storage"."Drive Encryption"."Recovery Key"

Unfortunatelly the Inventory Information is not populated by the inventory scanner.

Some of the other informations are collected by the Scanner:

So my question is, is there a build in support for reading out the Recovery Key to this Inventory field or do I have to run additional scripts for populating this Inventory Entry?

Thank you, Marco

five(9)s.GmbH.Support.Account

I've just upgraded my core server from Management Suite 8.7 SP5 to Management Suite 8.8 SP3 and rebuilt the Agent Configurations. When I upgraded some test system with the new Agent Configurations, the inventory scanner gives the above error message. The really odd thing is that it seems that sometimes it works because the core is intermittently getting new scans from these test systems, but manually running the inventory scanner produces the error message. I wasn't able to telnet to the core server on port 5007, but I'm not sure it it's because we have a management gateway that these devices need to connect through. There doesn't seem to be a problem with the services on the core, as scans are still coming back from the non updated agent devices. Also, these devices all have the client certs present and are able to update the virus definitions via the core server.

Any ideas would be appreciated.

Having an odd issue. On newly imaged devices (Lenovo x220), we install the Advanced Agent (9.0sp2) via group policy. After the client is installed, scans will not run. We get "the Inventory Server 'Core Server FQDN' did not respond". From the same machine we can ping the core by the FQDN and the core is processing all other scans just fine. The machine is part of a domain (different than the core) and we've tested with the machine not in a domain with the same issues. Even stranger, if we leave the machine(s) on for the day, and come back in the a.m., the scans ALL work, no issues. No change to the device/core, nothing.  The issue is primarily happening on a single image for these x220's, and can't determine what might be blocking communication with the core. The firewall service is disabled on the client. No AV installed on the client at the time. Thinking it's something in the image or that the LANDesk client is not installing properly on this image. However, why it works the day/hours after the client install is still a mystery.

Additional Info:

I just tried the inventory scan using the Core Server Name instead of the FQDN and the scan worked.Both the server name and FQDN are resolvable by the client.

O/S: XP Sp3

Any thoughts?

I'm looking for some direction.

We have a virtual desktop environment (Citrix Xen Desktop) of about 6,000 desktops. These desktops have a LANDesk inventory/remote control (not SWD) agent on them. Occasionally, when using the LANDesk console to remote to a virtual desktop, LANDesk connects to a different desktop (not the one selected).

• The desktops are all pre-generated with unique device names (xendesk####).
• Those desktops all have unique MAC addresses as well.
• When the desktops are generated (using the Citrix tools) they are essentially "frozen" in the state of the "source" desktop, other than the unique name (which is tied to AD). I don't know if the desktops have had the LANDesk unique device ID stripped currently, but I'm pretty sure at one point they did.
• Once a week (give or take) the "master" image is unfrozen and edited, then refrozen. As the desktops that are derived from that master reboot, they get the new version of the master image.

Should we be stripping the LANDesk unique ID from the master image every time it is edited?

If we do that, every time a desktop reboots (potentially daily) it would generate a new unique LANDesk ID (but still have the same name and MAC address).

My fear is that thousands of devices have the same unique LANDesk ID and that could cause problems from a remote control standpoint.

My other fear is that if we strip the unique ID, I'll end up with (literally) hundreds of database entries with the same name and MAC address but unique LANDesk device IDs.

Any idea what the best approach is here?