Intel AMT Release 2.2
Intel AMT retrieves its domain suffix using DHCP Option 15. The CN in the SCS
certificate must match the full domain suffix. The result is that a separate
certificate is required for each domain. For example, the CN in the certificate is
corp.east.yourenterprise.com
and DHCP returns a domain suffix of
east.yourenterprise.com
. The CN contains the full suffix so there is a match.
A CN of
yourenterprise.com
would not match
east.yourenterprise.com
. Because
an Intel SCS installation can only work with one Remote Configuration certificate
at a time, a separate certificate and Intel SCS instance is required for each domain
where Intel AMT-based platforms are located.
Intel AMT Release 3.0
If an Intel AMT 3.0 platform depends exclusively on the domain suffix returned
by DHCP, it behaves the same as Release 2.2.
The Intel AMT 3.0 FQDN option and domain extension option add the following
requirements:
■
If IT enters the FQDN of the SCS through the MEBx menu or with a formatted
USB key or the manufacturer enters the value before delivery, the CN in the
certificate must either exactly match all fields of the FQDN or it must be a
wildcard entry with a match in all but the first field of the FQDN. For example,
if the FQDN is
east.corp.yourenterprise.com
, the CN in the certificate must
also be
east.corp.yourenterprise.com
or
*.corp.yourenterprise.com
.
■
If a DSN suffix is entered, then all fields in the suffix must be included in the
CN. For example, if the entered suffix is
corp.yourenterprise.com
, then the
CN could be
corp.yourenterprise.com
or
east.corp.yourenterprise.com
or
main.east.corp.yourenterprise.com
(but not
east.yourenterprise.com
).
Using one of the above options requires a “single touch,” which should be balanced
against the need for an SCS installation and unique certificate for each domain.
Intel AMT Release 2.6
Release 2.6 supports the 2.2 functionality, with the following additions:
■
Wildcard CN: If the CN in the certificate is preceded by “
*.
”, then the domain
suffix received from DHCP need only match the CN where they have
overlapping fields. For example, if the CN is
*.a.b.org
, then
yyy.a.b.org
,
a.b.org
, and
b.org
would all match (but
c.b.org
would not).
■
If the CN ends with “
.com
” or “
.net
”, then the domain suffix received from
DHCP needs to match only the last two fields in the CN. For example, if the CN
183
Reference topics
Remote Configuration certificate – differences between releases
Содержание ALTIRIS OUT OF BAND MANAGEMENT COMPONENT 7.0 SP3 - V1.0
Страница 1: ...Altiris Out of Band Management Component from Symantec Implementation Guide Version 7 0 SP3 MR1 ...
Страница 6: ......
Страница 30: ...Introducing Out of Band Management Component Where to get more information 30 ...
Страница 48: ...Installing Out of Band Management Component Uninstalling Out of Band Management Component 48 ...
Страница 110: ...Configuring TLS Configuring TLS with mutual authentication 110 ...
Страница 176: ...Troubleshooting Out of Band Management Component Troubleshooting OOB site server installation 176 ...