Known problems and workarounds
The following known problems and workarounds apply to Lenovo XClarity Integrator Deployment Pack for Microsoft System Center Configuration Manager.
A Test Sequence Error (0x00000001) occurs when performing "Set RAID Config" action or "Bare Metal Server Deployment" using SCCM 2012 SP1
This action or task sequence might fail when performing the RAID configuration. The reason is that the scratch space size becomes too small to perform further actions.
Workaround: This is a known issue for SCCM 2012 SP1. Increase the scratch space to resolve the issue:- Right-click the boot image that is used in your task sequence, then select Properties.
- Switch to the Customization tab, and select 256 or a larger size for the Windows PE Scratch Space.
After WinPE is loaded, it reboots immediately and fails to run the task sequence.
WinPE reboots immediately after it is loaded and fails to deploy on Lenovo server Flex System x220 Compute Node and System xiDataPlex dx360 M4. The deployment fails because the task sequence runs before WinPE acquires its IP address. This is a known issue of WinPE network drivers.
Workaround: Follow the steps below to continue the task sequence.- Press F8 to open the command window after WinPE loads.
- Run the ipconfig /renew command to make sure that WinPE acquires the IP address.
- Run x:\sms\bin\<architecture>\tsbootshell.exe to restart the task sequence.
The Get BIOS action may fail on a system with a lower BIOS version.
The GetBIOS action might fail to get BIOS information when you create a Lenovo customization action with BIOS Config selected as the configuration action type, and Get selected as the action type.
Workaround: Upgrade the BIOS version to the later version.
The pre-existing task sequence does not work after the reinstallation of the Lenovo XClarity Integrator Deployment Pack.
After the Lenovo XClarity Integrator Deployment Packhas been reinstalled, the pre-existing task sequence does not work on the client machine. Some error messages are displayed, such as Failed to resolve the source for SMS package_ID....
The package ID changes after reinstallation; therefore, the package ID that is referenced in the pre-existing task sequence must be refreshed.
Workaround:- Open the task sequence in edit mode.
- Make a small modification to the task sequence, such as adding a space in the description field.
- Click Apply. The package ID in the task sequence will be refreshed.
The Diskpart clean and Apply Driver Package tasks need to be reassigned after you uninstall or reinstall the Lenovo XClarity Integrator Deployment Pack.
For pre-existing task sequences that were created through the Task Sequence wizard, the Diskpart clean and Apply Driver Package tasks need to be reassigned after the uninstallation or reinstallation of Lenovo XClarity Integrator Deployment Pack.
This is a normal behavior of OSD.
Workaround: After reinstalling or uninstalling the Lenovo XClarity Integrator Deployment Pack, open the Task Sequence Editor to reconfigure the Diskpart clean and Apply Driver Package tasks by clearing the red flags.
The Lenovo XClarity Integrator Deployment Pack fails to uninstall if the Microsoft System Center Configuration Manager server has already been uninstalled.
If you uninstall theMicrosoft System Center Configuration Manager server before uninstalling the Lenovo XClarity Integrator Deployment Pack, the uninstallation of the Lenovo XClarity Integrator Deployment Pack will fail.
Workaround: Uninstall the Lenovo XClarity Integrator Deployment Pack before uninstalling the Microsoft System Center Configuration Manager server.
PXE boot fails on the client machine after you restart the Microsoft System Center Configuration Manager server.
After you restart the Microsoft System Center Configuration Manager server, PXE boot will fail on the client machine with the following error message: TFTP Error, File not found.
The PXE boot files on the Microsoft System Center Configuration Manager server are erased after restarting, so PXE boot cannot take place.
Workaround: After you restart the Microsoft System Center Configuration Manager server, perform the following steps:- Stop the Windows Deployment Services (WDS).
- Either delete or rename the windows\Temp folder and create a new windows\Temp folder.
- Restart the WDS.
Error messages might be displayed when you create a Lenovo bare metal task sequence.
When you create a Lenovo bare metal task sequence, an error message might be displayed: CreateTaskSequenceTemplate: Unable to add the task sequence to the task sequence package.
If you click OK, another error message is displayed: CreateTaskSequenceTemplate: Could not create task sequence package.
Workaround: Restart the Microsoft System Center Configuration Manager server, and try creating the task sequence again.
A task sequence automatically picks up the operating system image when you select Do not select now during the task sequence creation.
If you select Do not select now for the operating system image when creating a task sequence, the task sequence picks up an available operating system image by default after it is created. And if you apply the task sequence, an error message is displayed indicating invalid values in some fields.
Workaround: This problem is due to the default operating system selection mechanism. To resolve the problem, select the default operating system again, click OK, and click Apply.
During task sequence editing, the sub-items need to be validated even if the group is disabled.
When you edit a task sequence, even if you disable a group, you still need to validate the sub-items of that group.
Workaround: Select the proper values of the sub-items to validate them according to the error icons, and apply the task sequence.
The Logs/Return Files tab displays errors although all the fields contain valid values.
When you try to configure a get action in the Lenovo task sequence, even if all the fields contain valid values, an error icon still appears on the Logs/Return Files tab. In this case, you cannot save the configuration by clicking either Apply or OK.
Workaround: Click in another field on this tab, for example, in a text box. The error icon disappears, and you can save the configuration settings.
A task sequence can be saved although some fields are missing and display red error icons.
When you generate a new task sequence that contains errors in some fields, the task sequence can be launched and closed and does not prompt messages. This task does not check errors before closing the task editor.
Workaround: The error icon will disappear if you click another field on this tab, for example, a text box or a check box. You can then save the configuration settings.
The disk should be in active or "unconfig good" state before you can perform the Set RAID Config task in the Lenovo XClarity Integrator Deployment Pack.
The Set RAID Config task will fail if the disk state is either not active or is in the "unconfig good" state. You can check the disk state from the WEBBIOS/RAID configuration page.
Workaround: Reboot and set the disk to an active state in WEBBIOS/RAID configuration.
The uninstallation operation does not remove all components if the account lacks SCCM administrator authority.
If you try to uninstall the Lenovo XClarity Integrator Deployment Pack without the SCCM administrator authority, the uninstallation procedure does not remove all components. The Lenovo XClarity Integrator Deployment Pack can be removed from the Add/Remove program list, but you can still find the packages, drivers and other driver package items in the MicrosoftSCCM console. If you want to uninstall the Lenovo XClarity Integrator Deployment Pack, ensure that the account is in the system administrator group and SCCM administrator group.
Workaround: Remove the Lenovo XClarity Integrator Deployment Pack with the system administrator and SCCM administrator authority.
Some files in the installation folder still remain after the Lenovo XClarity Integrator Deployment Pack has been uninstalled.
Some files in the installation folder are not removed after the Lenovo XClarity Integrator Deployment Pack is uninstalled.
Workaround: Delete the files manually.
Some imported files in the Configuration Manager installation path might not be removed when the Lenovo XClarity Integrator Deployment Pack is removed with the Import Wizard or during the uninstallation process.
Some imported files in the Configuration Manager installation path may not be removed after you remove the Lenovo XClarity Integrator Deployment Pack with the Import Wizard or during the uninstallation process.
Workaround: The next import or installation procedure will not be affected. Restart the machine, and delete the files manually. For detailed information, refer to the Troubleshooting section of the User's Guide.
Some menus in the Configuration Manager Console may be not removed after the Lenovo XClarity Integrator Deployment Pack has been removed with the Import Wizard or during the uninstallation process.
Some menus in the Configuration Manager Console that were generated when the Lenovo XClarity Integrator Deployment Pack was imported might remain after you remove the Lenovo XClarity Integrator Deployment Pack with the Import Wizard or during the uninstallation process.
Workaround: The next import or installation procedure will not be affected. Delete these files manually, and restart the Configuration Manager Console. For detailed information, refer to the Troubleshooting section of the User's Guide.
The boot image is not selected automatically when you create a Lenovo Bare Metal Server Deployment task sequence.
When you create a Lenovo Bare Metal Server Deployment task sequence, the task will not select the boot image automatically.
Workaround: It is a known issue. You can select the new boot image by using the following procedure:- Right-click the created task sequence, then choose Properties.
- Switch to the Advanced tab, select the Use a boot image check box, and then browse to select the boot image.
A window confirming the uninstallation may be blocked by the processing bar of the installation program.
While the product is being uninstalled from the system control panel, a confirmation window opens at the end of the uninstallation process; however, the processing bar prevents you from confirming the uninstallation.
Workaround:- Bring the underlying uninstallation confirmation window into focus by clicking on it, then click OK to complete the uninstallation.
- Use the uninstallation shortcut option from the Start menu to uninstall the product. The confirmation message window is not blocked when you use this method.