1 of 1 people found this helpful
LDDwnld.xlg is only there if you manually turn on Xtrace in the registry. How are you deploying the agent and what agent (advanced agent, single exe, pointing wscfg32, etc...) ? If advanced agent deployment check out http://forum.landesk.com/support/docs/DOC-9852 we use DFs so when we create the AA we use a DFS Unc path in lieu of http.
I'm using the push method.
It appears that I first need to create a single XTrace registry key under HKEY_LOCAL_MACHINE\SOFTWARE\Intel\LANDesk\, and then a REG_DWORD value of WSCFG32 on the unmanaged before I can see that kind of data. Is that true? But a managed device appears to have a much thicker registry hive under HKLM\Intel\LANDesk, and I'm sure that's because the agent is already installed.
These documents assume LANDesk administrators know too much about the product. They are not very well-written. Regardless, even after I added the registry key (the single WSCFG32 value that is), there was still no LDDwnld.xlg file and the install was taking too long, leading me to believe that install was going accross WAN and to the Core server. I'm frustrated..
Here is a document for xtrace http://community.landesk.com/support/docs/DOC-1623 wscfg32 trace would most likely be located in windows\temp and be named wscfg32.xlg. No comment about docs. You say you are pushing the client, is this the advance agent or the client exe?