1 of 1 people found this helpful
From what I have seen (heard, actually), .PEM certificates are (or should...) still be managed like with previous versions; however now there is the capability to simply put the .PFX certificate in the folder, and LANDesk will "take care of it as part of the automatic process". PEM files are supposed to still work as they did.
On top of it, seems that "PFX support means admin control mode provisioning is pretty much a drag and drop experience". You and me know that it is not the case in our environment ;-) Maybe not "PFX support means", but rather "PFX certs are required in order to"
Hopefully somebody else will come up with some hints or tips...
after import cert.pfx in a testing server LD9.5 with SP1,
I have reinstalled LD agent of this LD9.5 SP1 server in 3 devices already vPro provisioned with Non-TLS option,
the result has been that the devices are vpro provisioned again, tls option has changed, from non-tls to tls (which is better i think, communications are encrypted and more secure).
All vpro options in LD management console remains equal.
If you want to use web user interface you have to surf https://devicename:16993 .. and "go to this site no recommended" is not a issue.
-we don't need to do full-unprovision.
Just a question, when a core server with LD9.5 is updated to LD9.5 SP1, we need reinstall LD agent in devices ?
if not, i think would be enough with "Setup and Configure vPro" optin in LD management console to get back vpro provisioned all devices again.
Yes, the agent needs to be reinstalled.
Theorethically, reinstalling the agent should automatically provision the device. This is not working.