We are using a push policy on Windows login of the advanced agent through a .msi.
↧
Re: LANDesk mixing different machine information in Inventory Changes History
↧
Re: LANDesk mixing different machine information in Inventory Changes History
That's what I figured. Something I discovered the hard way is that devices that have an agent installed that was NOT installed using the advance agent (for us, all new PCs get the full agent installed during provisioning), will get the agent re-installed via the advance agent method. LD support is correct for devices that had the agent installed via the MSI method though (advance agent) - these will not re-install, thanks to a registry entry it creates the first time the advance agent is installed. The article below has a little more info on this. However, with that said, this doesn't seem like something that would be causing your issue, but I thought the extra info couldn't hurt.
Why Can't I install the Advance Agent over itself on a client?
↧
↧
Re: LANDesk mixing different machine information in Inventory Changes History
Hi John,
I do appreciate the info and yup this sounds like we need to re-think the whole deployment. Really for us it was about getting all machines that are already out there that do not have the agent to receive it. If the agent was to reinstall over top of the one deployed through an image could this issue not be the result?
Thanks again
↧
Re: LANDesk mixing different machine information in Inventory Changes History
looks like a similar issue we have been battling, do these devices have a VPN client? we had to exclude some duplicate MAC address that were coming from our vpn adapter and then change the duplicate device ID settings to look at the SN as well as MAC address and device name. Hope this helps!
↧
Re: LANDesk mixing different machine information in Inventory Changes History
Thank you for the info, this could very well be the issue as the images in question do have a VPN client on them. We have similar settings in our duplicate device ID settings, so you are saying you also added Computer.System.Serial Number or Computer.BIOS.SerialNumber as well? Where did you place the exclusion of the VPN adapter MAC addresses?
↧
↧
Re: LANDesk mixing different machine information in Inventory Changes History
we had to do this to clean up the device IDs after we realized the problem. I would talk to support to verify but it could be the same type of issue. You may have to change your duplicate MAC address settings as well to tell it add them to the MAC exclusions. Really hard to track down the real cause but for us these steps seem to have cleared it up.
↧
Re: Agent Configuration Blank
JonBart - Can you share the documentation that shows the supported methods for deploying the embedded agent and best practice?
↧
Re: Agent Configuration Blank
I am looking into that, in the mean time check out Supported Platforms : Windows Embedded
↧
Multicast address used by agent
Hello,
We need to know which multicast adress is used by LANdesk agent when software is deployed or patching.
I found several documentation concerning the process of MDR, but none mentioning the multicast address.
Any advice ?
thanks
↧
↧
Re: Multicast address used by agent
The current ports list doc here : Ports used by LANDesk Management Suite - Full List
lists the following for the windows clients:
| UDP | 33354 |   | Software Distribution (Multicast) |
| UDP | 33355 | | Software Distribution (Multicast) |
Hope this does the trick for you.
Mark McGinn
MarXtar Ltd/MarXtar Corporation
http://landeskone.marxtar.co.uk
LANDESK One Development Partner
The One-Stop Shop for LANDESK Enhancements
↧
Re: Multicast address used by agent
Thanks for your Reply,
I already have the port, but what I need is the address.
I need to know if the broadcast IP adress 239.83.100.109 or 239.255.255.250 is used by LANdesk, and if not which one is used ?
Thanks
↧
Re: Multicast address used by agent
Sorry, I was being thick and didn't read your question properly.
Try looking in this location: C:\ProgramData\LANDesk\TMCDownload at the downloadermulticastconf.xml file.
Mine shows:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <DownloaderMulticast>
<CacheDirectory>C:\Program Files (x86)\LANDesk\LDClient\sdmcache</CacheDirectory>
<HttpProxy />
<ProxyBypass />
<MulticastCmdAddress>239.83.100.109</MulticastCmdAddress>
<DownloadConnectionPort>49199</DownloadConnectionPort>
<DiscardPeriod>604800</DiscardPeriod>
<TMCClientPort>33354</TMCClientPort>
<PeerConnectTimeout>2500</PeerConnectTimeout>
<TMCMulticastPort>33355</TMCMulticastPort>
<CleanupDelay>28800</CleanupDelay>
<SubnetRepDiscardPeriod>1209600</SubnetRepDiscardPeriod>
<DoFillHoles>1</DoFillHoles>
<DoResends>1</DoResends>
<ResendCutoffPercentage>50</ResendCutoffPercentage>
<MaxResendLoops>5</MaxResendLoops>
<NumberPacketsPerCurlRead>50</NumberPacketsPerCurlRead>
<MaxActiveSockets>8</MaxActiveSockets>
<CanSubnetRep>1</CanSubnetRep>
<ListenTimeout>5000</ListenTimeout>
<DownloadListenTimeout>5000</DownloadListenTimeout>
<PeerReceiveTimeout>10000</PeerReceiveTimeout>
<MinStatusRequestTime>3</MinStatusRequestTime>
<WOLPort>0</WOLPort>
<RequiredFreeDiskSpace>10485760</RequiredFreeDiskSpace>
<EnableMulticastOnWireless>0</EnableMulticastOnWireless>
<EnableMulticastOnVPN>0</EnableMulticastOnVPN>
<DetectVPNKeywords>vpn:Vpn:VPN</DetectVPNKeywords>
<ClientPresentWhenConfigCreated>1</ClientPresentWhenConfigCreated>
</DownloaderMulticast>
Mark McGinn
MarXtar Ltd/MarXtar Corporation
http://landeskone.marxtar.co.uk
LANDESK One Development Partner
The One-Stop Shop for LANDESK Enhancements
↧
Re: Multicast address used by agent
Thanks for your quick reply, it was usefull.
↧
↧
Re: Agent Configuration Blank
Any update on this...Just to add to the discussion. We have installed the agent using the following batch file. Which is pretty similar to what is mentioned in the article above. It appears to work, but I am still not sure why the agent config is blank.
@ECHO OFF
c:
netsh firewall set opmode disable
md C:\LANDesk
copy "\\wdt00040\ldSoftware\Landesk\KentThinClient2015.exe" "C:\LANDesk\KentThinClient2015.exe"
set tmp=C:\LANDesk
set temp=C:\LANDesk
CD C:\LANDesk
KentThinClient2015.exe
set tmp=Z:\Temp
set temp=Z:\Temp
c:
rmdir /s /q C:\LANDesk
ewfmgr c: -commit
↧
Re: LDMS 9.5 Remote Issue with VDI (Support for non-persistent environment)
We've been following the instructions that LANDesk gave for VDI environment. Which is, to delete the unique ID from the registry of the parent image before creating the snapshot and assigning to a VDI pool.
It generates a new unique ID when the landesk services start when the VM first boots up after being created or recomposed.
Thanks for the Response
↧
Re: Common Base Agent status Not Loaded
I would not suggest using the randomiser if you are using a 30min check for policy as this will cause problems. Most of the time I dont use a randomiser for policy but you always want this to fall into the time before the policy runs again.
The policy engine has a very minimal overhead when it runs until there is a task assigned so I do know people running this every 30 minutes. I normally recommend running policy at login and every 4 hours. I find this is a good compromise.
↧
Re: Agent Configuration Blank
Any update on getting this documentation?
↧
↧
Disabling LANDesk Fuse in Mac Agent
Disabling LANDesk Fuse is simple enough in the Windows agent configuration, but is there a way to do it in the MAC agent config?
↧
Re: Disabling LANDesk Fuse in Mac Agent
It is not possible to disable fuse in the Mac agent
↧
wscfg32.exe not found?
Hi,
I'm doing OS provisioning and part of my template is to install the LANDesk Agent. Everything goes smooth and once it boots to windows and continues the template to install the agent it fails with this message:
Action #11
Install LANDesk Agent
FAILED
error:[80001000H]File \\CoreServer\ldlogon\wscfg32.exe not found.
That wscfg32.exe file is located in the ldlogon folder
Any ideas with this one?
Thanks,
↧