mareesa.mandzak -- I have done this before and this is how i did it YMMV:
1.) Create a self-contained agent you want to deploy to the offline client
2.) create a user account on the LD Core server to be used for running broker config:
a.) it must be a member of the LANDesk Management Suite local group on the LD Core server.
b.) I know there is a doc in the community explaining this but i cant find it at the moment, when if i do i will link back to it for good measure.
c.) only enable the account when it is to be used -- in my opinion this is a security concern if you leave it enabled
3.) Run the self contained agent on the client you want to deploy to
4.) run brokerconfig.exe located in \Program Files\Landesk\LDclient\
5.) put in your userid and password in the LANDesk User certificate area and click send
6.) if all is well you should get a success message
7.) disabled the account you created for broker config -- this is my own personal opinion on the matter.
should be good to go.
Thank you for your help Jay and amagi. I'm skeptical of using the brokerconfig.exe. Does this have to be used in order to create the certificates for use with the vCSA? If it's not secure, why use it?
Mareesa.madzak -- I dont think that its brokerconfig.exe itself that is unsecure (in my opinion). Its the need to use an account that is a user on the core server. while the user name and password will not be sent in plain text; its just not an account I keep enabled unless I am actively using it. again this is all just my opinion and how I do it. amagi has the doc on what is suggested; i do believe the user account is still needed and thus my advice on enabling it only when using it still stands.
It seems like a lot of manual work that needs to be done. I have about 500 road warriors is there a way to automate the deployment?
The doc mentioned is the only way to automate once the devices are already out in the wild.
My preferred method is to have the certificate assigned at the point where the agent is installed on the machines when they are within your network. Often this would just be a batch file that calls brokerconfig.exe -r, but this would only work while the client was on your internal network.
MarXtar Ltd/MarXtar Corporation
LANDESK One Development Partner
The One-Stop Shop for LANDESK Enhancements