As you have just deployed the agent give it a day or so to settle and perform automatic inventory scans. You will find a few things settle after that.
Workgroup is emtpy for those that are members of the directory, instead they will have entried in Domain.
For those with LDAP Group data missing, it may be that at the time of the scan, the devices weren't truly connected to AD so this data could not be seen? Pick one or two fo the devices and try to understand their condition at the time of the scan. LANDesk can only report what it can see when the scanner runs.
MarXtar Ltd/MarXtar Corporation
LANDesk Expert Solution Provider
The One-Stop Shop for LANDesk Enhancements
Update - New Stand-Alone State Notifier Console for Service Desk Operators
Update - State Notifier now detects machine and user Idle states
Update - WoW & State Notifier now integrate for even more functionality
Hi Mark, thanks for the reply. These are not new agent deployments. These agents have been on these machines for at least a month. I have an Inventory (hardware) set to run at each login. I'm unsure whether domain/workgroup would fall under hardware or software. Do you know? So it should scan and write these fields at least once per day, no?
And yes, i understand where machines that have the Workgroup empty and the LDAP Group/Display Name populated are machines that are part of the domain and vice versa. The machines that show no Domain and no Workgroup consist of both XP and Win7 and those that are both attached and not attached to the domain. The wall i'm hitting is how these variety of machines were scanned that same day, but not reporting this information. This leads me to believe that i cannot trust the query output and LDDA reports requiring me to check each one therefore negating the scan then email feature in DA.