If your Configuration Manager 2007 hierarchy uses languages with double-byte character sets (DBCS) and you want to use the out of band management feature, you might need to take additional configuration steps before these computers can be provisioned for AMT.
 Note |
|---|
| The information in this topic applies only to Configuration Manager 2007 SP1 and later. |
Public key infrastructure (PKI) standards do not currently allow for double-byte character sets, and out of band management connections require PKI certificates. Additionally, the AMT firmware does not support double-byte character sets.
If the site system server with the out of band service point role or the AMT-based computers are configured with domain and computer names that contain double-byte characters, rename them so that these computers have fully qualified domain names that use only single-byte characters.
Additionally, do not use double-byte characters for the following configuration settings in the out of band management component properties:
- The Active Directory container that is
used to publish the AMT accounts in Active Directory Domain
Services. This value should not contain extended ASCII characters
and is restricted to the following characters: a-z, A-Z, -
(hyphen), _ (underscore), and spaces.
- The Default IDE-redirect image path
and file name (also can be specified in the out of band management
console). This value can contain extended ASCII characters.
- The following wireless settings
(Configuration Manager 2007 SP2 only): Profile name and
Network name (SSID). These values should not contain
extended ASCII characters.
The data store in Configuration Manager 2007 SP2 also does not support double-byte characters or extended ASCII characters.