How did you configure the servername in your agent? Did you use netbios name or FQDN?
We are using FQDN (technically a CNAME that points to FQDN of our landesk core)
That won't work. As a quick and dirty check, change the registry value
on a deployed device to the netbios name of the Core Server and run an Inventory Scan.
It's not using the netbios name.
Example: Our core is landesk9.ad.structure.school.edu.
a cname called landesk.school.edu points to the fqdn.
Cname is used in Agent Configuration.
This has worked in past fine.
SP1 adds a new agent settings option called 'Client Connectivity' have you configured that correctly so that the client knows where to communicate? This is meant to auto-configure systems so that you don't need to use brokerconfig (haven't tested myself yet though).
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
Yes, have that configured and pointing to LANDesk Cloud Services Appliance.
You may be right about not being able to use an alternative CNAME in the agent configuration.
Alternate CNames wont work over the management gateway... it makes me a sad panda.
Ugh. That really sucks. I wish they could make that an enhancement. We use a cname in our agent configuration.
Has this been reviewed? I am currently experiancing the same issue at our site.
The agents installed are connecting to the LDMS Gateway from the net.
I am able to see the computers connected to the gateway.
SP1 is still not creating the certificate is not being created.
Do we really have to manually touch all 200 external user nodes?
I understand this is a really old thread. If I need to make a new post I will
SP1 uses a new configuration item named "client connectivity", the agents need to be at SP1 as well. Have you configured the clients with that configuration item?
If the agents are configured, you may have another issue (permissions to the brokerreq folder in the management suite folder I've seen problems with before).
It's fustrating that LANDesk uses the DNS short name for a majority of it's connections, it causes so many problems in multi-domain environments. (I'm not talking about cnames, just using FQDN for communication to the core.)
Yes it is a fresh install starting @ SP1 + all pre SP2 patches
I have confirmed all the configured off-site agents are connecting to the gateway. We are able to establish a remote control session via mgt gateway. They are not creating a certificate. The deployment vendor, referred to use by LANDesk, has stated we must run brokerconfig on each node manually.
To me LANDesk is an automation tool. It seems really lacking that one must have an administrator log into every remote device and run brokerconfig.
If I now understand correctly all new laptops will need to be connected to an external wifi just to complete the configuration of the agent before the laptop can be given to a new user.
If an agent configuration needs to be reinstalled (like SP2), does one have to manually re-connect to every remote user and re-run brokerconfig?
Is there LANDesk documentation on the topic of brokerconfig -vs- 'Client Connectivity' Agent Settings ?
I don't recall if there is for the "Client Connectivity". See: http://help.landesk.com/Topic/Index/ENU/LDMS/9.5/Content/Windows/csa_h_help.htm
I am very familiar with the broker config annoyance. I created a custom patch definition to resolve it on the clients and set the definition to autofix. (on 9.0).
I forgot to add, I'm using the management gateway without issue with 9.5 SP1.
Here is my agent configuration flow:
1.) agent starts off with an "Intranet Only" connectivity setting (built into the agent)
2.) Query configured for if the hardware is a laptop or tablet, and running intranet only config
3.) "Change settings" job is created to change to the "Mangement gateway" connectivity setting and uses that query
Our vendor set us up with only one Client Connectivity setting...
CSA is enabled and set to Dynamic
From the LDMS documentation link you provided:
Each managed device is required to have a valid digital certificate in order to connect through the CSA. Deploy these certificates by using agent configurations that specify the CSA you want that device to use (in the Agent settings tool, open the Client connectivity settings > Cloud Services Appliance page).
There is no mention of brokerconfig.