This article describes process of obtaining and installing a digital certificate for OpsMgr agent that is not a member of your AD forest or a trusted forest. This article assumes that your managed computer is running one of the following operating systems: Windows 2000/XP/Server 2003/Server 2003 R2/Vista/Server 2008/7/Server 2008 R2.
Target audience is OpsMgr administrators that have limited or no understanding of what certificates are and how PKI works. Described below is not the only way to achieve the same or similar goal but it implements many of PKI Best Practices.
Note: all steps described in Prerequistes section must be completed in both scenarios.
↑ Back to the top
We suppose you already have some version of Microsoft Windows Server Active Directory Certificate Services (AD CS) Certificate Authority (CA) deployed in your environment and your OpsMgr Management Servers already trust this CA. You could also use commercial certificates issued by a third-party CA but in this case some of the steps described below should be a little bit different.
First you need to export your CA hierarchy certificates.
Now you need to transfer the above file to each of managed computers and import it as described below.
Certification Authority server is configured as Standalone CA and running one of the following operating systems: Windows Server 2003/2003 R2/2008/2008 R2 Standard, Enterprise or Datacenter edition.
[NewRequest] Subject="CN=<FQDN of managed computer>" KeyLength=2048 KeySpec=1 KeyUsage=0xf0 MachineKeySet=TRUE [EnhancedKeyUsageExtension] OID=1.3.6.1.5.5.7.3.1 OID=1.3.6.1.5.5.7.3.2
Note: You should enter the FQDN name of your managed computer into the second line after “=” sign. For non-domain computers, FQDN equals NetBIOS name. Example: Subject="CN=MyWorkGroupPC".
CertReq –New –f path\OpsMgrConfig.inf path\OpsMgr_%computername%.req
Note: you should enter a valid path for INF and REQ files. Request file should not exist yet when you run the command. It is created when you run the command.
Note: You should enter a valid path for the certificate file.
If no error are displayed in CMD window proceed to the next step.
Certification Authority server is configured as Enterprise CA and running one of the following operating systems: Windows Server 2003/2003 R2/2008/2008 R2.
Note: Windows Server 2003, Windows Server 2003 R2 and Windows Server 2008 Standard Edition don’t support version 2 templates.
[NewRequest] Subject="CN=<FQDN of managed computer>" KeyLength=2048 KeySpec=1 KeyUsage=0xf0 MachineKeySet=TRUE [RequestAttributes] CertificateTemplate="OpsMgrAgentV2"
Note: In CertificateTemplate field you must enter certificate template common name rather display name.
Note: You should enter a valid path for INF and REQ files. Request file should not exist when you run the command.
Locate created OpsMgr_%computername%.req file and transfer it back to where you have access to your Certification Authority.
Note: you should enter a valid path for the certificate file.
Maheshkumar S Tiwari edited Revision 3. Comment: corrected typo error and added tags.
Pronichkin edited Revision 2. Comment: Fixed anchors