Limitations

Version 1.0

Limitations in viewing the double byte character set (DBCS) versions of the License Agreement

To see the Japanese, Korean, Chinese Simplified, or Chinese Traditional language versions of the License Agreement correctly, you must have one of these East Asian languages installed.

Symptom: If you do not have one of the East Asian languages installed, you cannot see normal DBCS characters. Instead you see boxes that are similar to "□□" for certain characters when looking at the following language versions of the License Agreement:

• Japanese
• Korean
• Chinese Simplified
• Chinese Traditional

Description: The License Agreement document is available in both DBCS languages and non-DBCS languages. Versions of the License Agreement in languages other than the DBCS Asian languages display correctly without installing one of the East Asian languages. However, to correctly view an East Asian DBCS version of the License Agreement, you must have an East Asian DBCS language installed.

Action: Install one of these East Asian languages to view the License Agreement in Japanese, Korean, Chinese Simplified, or Chinese Traditional. Or view the License Agreement in a non-DBCS language.

Limitations in the installation program

The following limitation exists in the installation program.

Setup does not check for disk space during installation.

Symptom: The installation fails when not enough free space is available on the installation disk. The following message is displayed:

Installation Failed

The wizard was interrupted before IBM Deployment Pack 
for Microsoft System Center Configuration Manger 2007
could be completely installed.

Your system has not been modified.  
To complete installation at another time, 
please run setup again.

Click finish to exit the wizard.

Description: The setup program does not check for disk space before beginning the installation. If you have less than the required free space on the disk where you are installing the Deployment Pack, the installation fails.

Action: Verify that you have 1 gigabyte of free space on the installation disk before you begin the installation. See the User's Guide for more information about installation requirements.

Limitations in a context menu function for an advertised task sequence

The following symptom has been reported when disabling an advertisement.

Selecting "No" to disable an advertised task sequence might cause the Administrative console to hang.

Symptom: This defect might occur when you perform the following procedure:

1. Select System Center Configuration Manager > Site database > Computer Management > Software Distribution > Advertisement.
2. Right click a task sequence that is displayed in the list.
3. Select Disable Task Sequence.
4. Select No on the dialog warning that is displayed.

The console displays an hourglass, but does not return control within a reasonable amount of time.

Description: This problem is under investigation.

Action: If you run into this problem, manually stop the console session and restart the console.

Limitations in the IBM® Advanced Settings Utility (ASU)

The following ASU limitations might affect the behavior or result of ASU commands issued during operating system deployment.

The ASU loaddefault cannot load all attributes to the default value on the baseboard management controller (BMC) and on the RSA.

Symptom: The value of some attributes is not reset to the original value, because there is no default value.

Description: This is working as designed. Not all attributes in BMC and RSA have a DEFAULT value in the DEF file for each subsystem.

The ASU tool sets values by issuing IPMI & RSA commands (BMC and RSA respectively) to perform the settings changes. Part of the DEF file for each subsystem contains the DEFAULT value that ASU would use in such a case.

Action: Do not plan to be able to reset default values for attributes that do not have a default value in the DEF file for the subsystem.

On blades, some boot settings were moved from CMOS to BMC.

Symptom: If you change the CMOS_PrimaryBootDevice* value using ASU, ASU reports an error that the target attribute cannot be found.

Description: Some blades no longer use the boot setting CMOS_PrimaryBootDevice*, but use the BMC_PrimaryBootDevice* setting instead.

Action: If you get the error, change the BMC_PrimaryBootDevice* setting instead.

BMC_NetworkIPAddress and other related attributes cannot be modified on blades.

Symptom: You can change the value in ASU, but after rebooting the blade, the management module changes the value back to the original value.

Description: These attributes are controlled by the management module on BladeCenter® chassis units.

Action: Use the management module to change the value.