Filtered Index

If you need to brush up on creating SSL Cert Files for your PO, this tip from Tim Heywood should help.

Novell SysOp Jared Jennings details how to use a Microsoft Certificate Authority (CA) or Novell eDirectory Certificate Authority to sign the required certificates for ZENworks 10 Configuration Management. Enjoy!

This workaround tip helps you avoid an unnecessary prompt for a Client certificate during iChain Certificate Authentication.

Neil Cashell and Klaus Gast describe three main problem scenarios you might encounter when dealing with Certificate Authorities. Learn about the tools and tricks that allow administrators to get almost any third party certificate to work with iChain 2.3.

When you install ZENworks Configuration Management, one of the first choices you are asked to make is whether to use an internal or external Certificate Authority.

The managed agent uses .NET code to communicate via TLS with the ZCM server. Installation of the managed agent automatically updates the client's local machine trusted root authority certificate store with the the CA (Certificate Authority) of the server.

The main sticky points I see with DNS are making sure that the URL used to connect to the Primary Server is the same DNS name as the server itself. So long as the CA has signed the cert of the primary server (performed during the Primary Server install) and the DNS name used to connect matches the servers cert exactly, all’s well with the world.

If you want to connect using different IP/DNS names, such as in a NAT environment, they are ways around those problems. Firstly, you can populate “Additional DNS names” and “Non-detectable IP addresses” to tell the primary server about other connection methods. Secondly, you can tell the client to ignore name matching with a reg key. Is that what you went with?