ibm deployment pack for configuration manager...
TRANSCRIPT
IBM System x
IBM Deployment Pack forMicrosoft System Center Configuration Manager 2007Release NotesVersion 1.4
���
IBM System x
IBM Deployment Pack forMicrosoft System Center Configuration Manager 2007Release NotesVersion 1.4
���
NoteBefore using this information and the product it supports, read the information in “Notices” onpage 21.
Second Edition (July, 2010)
This edition applies to version 1.4 of IBM Deployment Pack for Microsoft Configuration Manager 2007 and to allsubsequent releases and modifications until otherwise indicated in new editions.
© Copyright IBM Corporation 2010.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.
Contents
About this publication . . . . . . . . vConventions and terminology . . . . . . . . v
Information resources . . . . . . . . viiPDF files . . . . . . . . . . . . . . . viiWorld Wide Web resources . . . . . . . . . vii
Chapter 1. Known limitations, problems,and workarounds. . . . . . . . . . . 1Limitations . . . . . . . . . . . . . . . 1
Known problems and workarounds . . . . . . 5
Chapter 2. Capturing and deployingWindows 2008 R2 . . . . . . . . . . 13Capturing the WS08 R2 image . . . . . . . . 13Deploying the WS08 R2 image . . . . . . . . 14
Notices . . . . . . . . . . . . . . 21Trademarks . . . . . . . . . . . . . . 22Important notes . . . . . . . . . . . . . 22
© Copyright IBM Corp. 2010 iii
iv IBM Deployment Pack for Configuration Manager 2007, v1.4 Release Notes
About this publication
This book provides instructions for installing IBM Deployment Pack for MicrosoftSystem Center Configuration Manager 2007, v1.4 and using the integrated featuresto deploy operating systems to IBM® servers in your environment.
Conventions and terminologyParagraphs that start with a bold Note, Important, or Attention are notices withspecific meanings that highlight key information.
Note: These notices provide important tips, guidance, or advice.
Important: These notices provide information or advice that might help you avoidinconvenient or difficult situations.
Attention: These notices indicate possible damage to programs, devices, or data.An attention notice appears before the instruction or situation in which damagecan occur.
© Copyright IBM Corp. 2010 v
vi IBM Deployment Pack for Configuration Manager 2007, v1.4 Release Notes
Information resources
You can find additional information about IBM Deployment Pack for MicrosoftSystem Center Configuration Manager 2007, v1.4 in the product documentationand on the World Wide Web.
PDF filesView or print documentation that is available in Portable Document Format (PDF).
Downloading Adobe Acrobat Reader
You need Adobe Acrobat Reader to view or print these PDF files. You candownload a copy from the Adobe Reader Web site.
Viewing and printing PDF files
You can view or print any of the PDF files in the following list. The most currentversion of each document is available online in the information center and on theproduct download page. Go to the Microsoft Systems Management Solutions forIBM Servers to sign in and locate the download links for the publications, or clickany title in the following list to open the version of each book that is in theinformation center for the IBM System x® and BladeCenter® Tools Center:
Release Notes®
v IBM Deployment Pack for Microsoft System Center Configuration Manager2007 Release Notes, v1.4
Installation and User's Guide
v IBM Deployment Pack for Microsoft System Center Configuration Manager2007 Installation and User's Guide, v1.4
World Wide Web resourcesThe following Web pages provide resources for understanding, using, andtroubleshooting IBM System x, BladeCenter blade servers, andsystems-management and systems-deployment tools.
IBM Systems Technical support site
Support for IBM Systems and servers
Locate support for IBM hardware and systems-management andsystems-deployment software.
IBM Web site for Microsoft Systems Management Solutions forIBM Servers
Microsoft Systems Management Solutions for IBM Servers
Download IBM systems-management and systems-deployment software.
© Copyright IBM Corp. 2010 vii
IBM Systems Management page
IBM Systems Management
Obtain an overview of IBM systems deployment using IBM tools and the IBMDeployment Pack for Microsoft Configuration Manager 2007.
IBM ServerProven® page
IBM ServerProven
Obtain information about hardware compatibility with IBM System x, IBMBladeCenter, and IBM IntelliStation® hardware.
Microsoft System Center Configuration Manager 2007 page
Microsoft TechNet: System Center Configuration Manager
Obtain information about Microsoft System Center Configuration Manager fromthe home page for the product.
Microsoft TechNet: Configuration Manager Documentation Library
Obtain information about Microsoft System Center Configuration Manager from itslibrary of documentation.
TechNet Blog: Inside ConfigMgr 07 Operating System Deployment
Obtain information about the Operating System Deployment feature of MicrosoftSystem Center Configuration Manager from a Microsoft sponsored blog thatprovides an inside look at the Operating System Deployment feature.
Microsoft TechNet Forum: Configuration Manager – Operating System Deployment
Discuss the Operating System Deployment feature forMicrosoft System CenterConfiguration Manager with Microsoft developers and other users.
viii IBM Deployment Pack for Configuration Manager 2007, v1.4 Release Notes
Chapter 1. Known limitations, problems, and workarounds
The following limitations, problems, and workarounds are applicable to the IBMDeployment Pack for Microsoft System Center Configuration Manager 2007, v1.4.
LimitationsThe following limitations are applicable to the IBM Deployment Pack.
Version 1.4
Limitations in the installation programThe 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 isavailable on the installation disk. The following message isdisplayed:Installation Failed
The wizard was interrupted before IBM Deployment Packfor Microsoft System Center Configuration Manger 2007could 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 spacebefore beginning the installation. If you have less than the requiredfree space on the disk where you are installing the DeploymentPack, the installation fails.
Action: Verify that you have 1 gigabyte of free space on theinstallation disk before you begin the installation. See the User'sGuide for more information about installation requirements.
Limitations in a context menu function for an advertised task sequenceThe following symptom has been reported when disabling anadvertisement.
Selecting "No" to disable an advertised task sequence might cause theAdministrative console to hang.
Symptom: This defect might occur when you perform thefollowing 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 controlwithin a reasonable amount of time.
© Copyright IBM Corp. 2010 1
Description: This problem is under investigation.
Action: If you run into this problem, manually stop the consolesession and restart the console.
Limitations in the IBM Advanced Settings Utility (ASU)The following ASU limitations might affect the behavior or result of ASUcommands issued during operating system deployment.
The ASU loaddefault cannot load all attributes to the default value onthe baseboard management controller (BMC) and on the RSA.
Symptom: The value of some attributes is not reset to the originalvalue, because there is no default value.
Description: This is working as designed. Not all attributes inBMC and RSA have a DEFAULT value in the DEF file for eachsubsystem.
The ASU tool sets values by issuing IPMI & RSA commands (BMCand RSA respectively) to perform the settings changes. Part of theDEF file for each subsystem contains the DEFAULT value that ASUwould use in such a case.
Action: Do not plan to be able to reset default values for attributesthat 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* valueusing ASU, ASU reports an error that the target attribute cannot befound.
Description: Some blades no longer use the boot settingCMOS_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 modifiedon blades.
Symptom: You can change the value in ASU, but after rebootingthe blade, the management module changes the value back to theoriginal value.
Description: These attributes are controlled by the managementmodule on BladeCenter chassis units.
Action: Use the management module to change the value.
Some IMM values cannot be changed by the IBM Deployment Action“IMM Config (Set)”.
Symptom: Some IMM values are defined as “noreplicate”. Thesevalues cannot be changed by the IBM Deployment Action “IMMConfig (Set)”.
Description: The value list on 3650M2 and 3550M2 is similar to thefollowing list:IMM.LoginId.1=USERIDIMM.LoginId.10=IMM.LoginId.11=IMM.LoginId.12=IMM.LoginId.2=
2 IBM Deployment Pack for Configuration Manager 2007, v1.4 Release Notes
IMM.LoginId.3=IMM.LoginId.4=IMM.LoginId.5=IMM.LoginId.6=IMM.LoginId.7=IMM.LoginId.8=IMM.LoginId.9=IMM.AuthorityLevel.1=SupervisorIMM.UserAccountManagementPriv.1=NoIMM.RemoteConsolePriv.1=NoIMM.RemoteConsoleDiskPriv.1=NoIMM.RemotePowerPriv.1=NoIMM.ClearEventLogPriv.1=NoIMM.BasicAdapterConfigPriv.1=NoIMM.AdapterConfigNetworkSecurityPriv.1=NoIMM.AdvancedAdapterConfigPriv.1=NoIMM.HostName1=IMM-001A64E611FDIMM.HostIPAddress1=9.123.199.52IMM.HostIPSubnet1=255.255.255.0IMM.GatewayIPAddress1=-IMM.MACAddress1=00:00:00:00:00:00
For more details, see the IBM Advanced Settings Utility (ASU)support page.
Action: Do not plan to change these values. This is a limitation ofASU.
Setting default value for the BootOrder configuration might fail.
Symptom: Setting default value for the BootOrder configurationmight fail.
Description: If there is no default value assigned to BootOrder, thetask sequence for setting the default value for the BootOrderconfiguration will fail.
Action: Do not plan to set default value for BootOrderconfiguration if there is no default value assigned to BootOrder inthe subsystem.
Some ASU commands might fail on some servers.
Symptom: Some ASU commands might fail on some servers.
Description: The operating system deployment (OSD) featureleverages IBM ASU to configure the hardware settings. Some ASUcommands might fail on some servers.
Action: If you get the error from the OSD configuration, check thelimitations of ASU, the driver, and the firmware.
The ASU sample file is only an example.
Symptom: If you use the sample parameters in your realconfiguration, they might not be successfully configured throughtask sequence.
Description: This is because the sample file is only an example.Different systems might use different parameters.
Action: For more information about parameters in differentsystems, refer to the manuals for your systems and the IBMAdvanced Settings Utility (ASU) support page.
Chapter 1. Known limitations, problems, and workarounds 3
|
|||
||
|||
Symptom: Reboot IMM action in the IBM Deployment Pack tasksequence fails on IBM System X3690 X5 server (MachineType 7148).Description: IBM Deployment Pack uses IBM Advanced SettingsUtility (ASU) to run configuration actions. However, reboot IMMwill fail on IBM System X3690 X5 server (MachineType 7148).Action: This is known issue of current ASU version. It can notsupport to reboot IMM on X3690 X5 (7148).
The Close button on the top-right of the installation window is not working.
Description: After the installation or uninstallation progress starts, clickingthe Close button on the top-right of the window opens a message box forconfirmation; but even if you click Yes, the installation or uninstallationwill not be cancelled.
Action: Do not plan to cancel the installation or uninstallation progressafter it starts.
The installation might fail if UAC is turned on.
Description: If you are using a non-built-in administrator account to installIBM Deployment Pack, UAC must be turned off or the installation will fail.
Action: Turn off UAC.
The IBM Deployment Pack cannot work together with Microsoft System CenterConfiguration Manager on an x64 server if the SCCM installation directory ismodified to “Program Files”.
Description: By default, Microsoft System Center Configuration Manager isinstalled into the “Program Files (x86)” directory on an x64 server. If youchange the directory to “Program Files”, the IBM Deployment Pack cannotwork together with SCCM.
Action: Install Microsoft System Center Configuration Manager to thedefault installation directory or to some directory other than “ProgramFiles”.
IBM Deployment Pack does not work on the Microsoft System CenterConfiguration Manager console only server if IBM Deployment Pack is notinstalled on the Microsoft System Center Configuration Manager site server.
Description: IBM Deployment Pack can be installed on a server that onlyhas the Microsoft System Center Configuration Manager administrationconsole, but the functions cannot work until the IBM Deployment Pack isalso installed on the Microsoft System Center Configuration Manager siteserver.
Action: Install IBM Deployment Pack on the Microsoft System CenterConfiguration Manager site server at first; and then install it on theMicrosoft System Center Configuration Manager administration console.
Uninstalling IBM Deployment Pack from the Microsoft System CenterConfiguration Manager site server does not remove it from the Microsoft SystemCenter Configuration Manager console only server.
Description: IBM Deployment Pack is not automatically uninstalled fromthe Microsoft System Center Configuration Manager console only serverwhen it is uninstalled from the Microsoft System Center ConfigurationManager site server.
Action: Manually uninstall IBM Deployment Pack from the MicrosoftSystem Center Configuration Manager console only server.
4 IBM Deployment Pack for Configuration Manager 2007, v1.4 Release Notes
|||||||
|||
||||
|||
Users are not alerted if IBM Deployment Pack have different versions on theMicrosoft System Center Configuration Manager administration console and onthe Microsoft System Center Configuration Manager site server.
Description: Installing different versions of IBM Deployment Pack on theMicrosoft System Center Configuration Manager administration consoleand on the Microsoft System Center Configuration Manager site serverrespectively will cause IBM Deployment Pack not working normally on theadministration console. But even if you install different versions, you willnot get any alert.
Action: If you want to install IBM Deployment Pack on a separateMicrosoft System Center Configuration Manager console, make sure thatthe version is same as the one on the Microsoft System CenterConfiguration Manager site server.
The Export XML button is disabled when the View XML button is enabled.
Description: On the IBM Deployment Pack page, if you create a tasksequence as “RAID Config (Wizard)” + “Set” + “<Create ConfigurationFile>”" and click Create, the Export XML button is displayed as disabledon the Array Builder page.
Action: Put the cursor in the Configuration Rule Name field, the ExportXML button is enabled.
The “Import Configuration File” action does not save RAID XML after youimport it in the Array Build page.
Description: On the IBM Deployment Pack page, if you create a tasksequence as “RAID Config (Wizard)” + “Set” + "<Import ConfigurationFile>", click Import to select a predefined XML, and click OK on theArray Builder page to finish the configuration, there is still a warning flagand no configuration file has been imported.
Action: This is a known limitation.
IBM ServerGuide Scripting Toolkit PRAID limitationThe following PRAID limitations might affect the behavior or result ofPRAID commands issued during operating system deployment. OtherRAID controllers are skipped if the first one does not match policy.Description: When running multiple RAID controllers, if the first oneapplies to a mismatched policy file, the remaining ones will be skippedand the PRAID will exit the directory.Action: This is a known limitation.
Selecting controller according to machine type does not workDescription: The policy file defined to select controller by machine typedoes not work as expected.Action: This is a known limitation.
Known problems and workaroundsThe following known problems and workarounds are applicable to the IBMDeployment Pack.
Version 1.4
An error message that falsely indicates that packages are not updated should notbe displayed at all. The message occurs when drivers are attempted to beremoved from driver packages that actually do not include the drivers, when
Chapter 1. Known limitations, problems, and workarounds 5
using the “Add or remove drivers to a driver package” function to removemultiple drivers from one or more packages.
You might see the following message after removing drivers with the Addor remove drivers to a driver package function:Some packages cannot be updated.Please see the log file for more information.
You can ignore this message. The message does not correctly indicate thesuccess of either a driver removal from a package or a driver addition to apackage.
During the same operation that removes drivers, if you also add drivers toone or more packages by checking one or more packages, or by leavinggrayed-out packages checked, the success of the addition of the drivers tothe packages is not indicated by the message. In fact, the message occursonly if you attempt to remove a driver from a package that does not containthe driver.
Because this message is caused by the removal of drivers, the message hasnothing to do with the addition of drivers. For instance, if you attemptonly to add drivers (no driver removal) to a package that already containsone but not all of the drivers (the package is grayed-out and checked), youdo not see this message.
You might see the message when you perform the following removalprocedure. Whether you are also adding drivers is irrelevant.1. Click System Center Configuration Manager → Site Database →
Computer Management → Operating System Deployment → Driverspackages → IBM Server Drivers.
2. Select multiple drivers; then right-click a selected driver and click Addor remove driver to packages.Driver packages that have one but not all drivers are displayed withgrayed out, selected checkboxes.
3. Clear the checkbox for a grayed-out driver package in the Add orremove drivers to a driver package page, or click Clear All to clear allcheckboxes, including grayed-out packages, to remove the selecteddrivers from the packages.
4. Click OK.If any packages were grayed out, meaning that they included one, butnot all selected drivers, the error message is displayed.
5. Click OK → Cancel to exit the Add or remove drivers to a driverpackage page.The error message does not affect the removal of the drivers from thedriver packages. The message actually indicates that because somepackages did not contain a selected driver, the driver was already notincluded in a package and therefore could not be removed from thepackage. The message should not be displayed at all because allpackages were, in fact, updated correctly.
IBM Deployment Pack does not check the IBM Advanced Settings Utility (ASU)command syntax.
IBM Deployment Pack uses ASU to do some configuration. However, IBMDeployment Pack does not check the ASU command syntax. If you input awrong ASU command syntax, IBM Deployment Pack will pass it to thetarget machine and the OSD sequence will fail.
6 IBM Deployment Pack for Configuration Manager 2007, v1.4 Release Notes
Workaround: Make sure that the ASU command syntax is correct. Formore details about ASU commands, refer to the IBM Advanced SettingsUtility (ASU) support page.
The menu item “Advertise” is missing from the Task Sequence Editor afteruninstallation or reinstallation.
Two reasons might cause the Advertise menu item to be missing from theTask Sequence Editor:v There is no boot image assigned to the task sequence.v The package ID of the boot image in the task sequence was changed
during the uninstallation or reinstallation.
Workaround:
v If there is no boot image assigned to the task sequence, assign a bootimage to it.
v If there is already an assigned boot image, edit the task sequence andsave it, and then right-click the task sequence and select the refreshaction.
The pre-existing task sequence does not work after the reinstallation of IBMDeployment Pack.
After reinstallation, the pre-existing task sequence does not work on theclient machine. Some error messages are displayed, such as “Failed toresolve the source for SMS package_ID...”.
The reason is that the package ID has been changed after the reinstallation.Therefore, the package ID that is referenced in the pre-existing tasksequence should be refreshed.
Workaround:
1. Open the task sequence in edit mode.2. Do some modification to the task sequence, for example, add a white
space in the description filed.3. Click Apply. The package ID in the task sequence is refreshed.
The “Diskpart clean” and “Apply Driver Package” tasks need to be reassignedafter you uninstall or reinstall the IBM Deployment Pack.
For pre-existing task sequences that were created through the TaskSequence wizard, the Diskpart clean and Apply Driver Package tasksneed to be reassigned after the uninstallation or reinstallation.
This is a normal behavior of OSD.
Workaround: After reinstallation or uninstallation, open the Task SequenceEditor to reconfigure the Diskpart clean and Apply Driver Package tasksby clearing the red flags.
Uninstallation of IBM Deployment Pack fails if the Microsoft System CenterConfiguration Manager server has already been uninstalled.
If you uninstall the Microsoft System Center Configuration Manager serverbefore uninstalling the IBM Deployment Pack, the uninstallation of IBMDeployment Pack will fail.
Workaround: Uninstall the IBM Deployment Pack before uninstalling theMicrosoft System Center Configuration Manager server.
The account and password settings in task sequence do not take effect onWindows 2003 operating systems.
When you create an IBM bare metal task sequence to deploy a Windows
Chapter 1. Known limitations, problems, and workarounds 7
2003 OS image, you can set the account and password in the ApplyWindows Setting panel. However, the account and password will not takeeffect after the OS deployment.
An error message is displayed on the client machine indicating that theaccount and password cannot be changed during the OS deploymentprocess.
Workaround: When capturing a Windows 2003 image from a referencecomputer, you must change the local administrator password to blank.
If you run Sysprep manually, configure the administrator password toblank as well.
For more information, see How to Capture an Image from a ReferenceComputer by Using Capture Media at http://technet.microsoft.com/en-us/library/bb694129.aspx.
The log file might not be created to trace the installation or uninstallation.After the installation or uninstallation of the IBM Deployment Pack, the logfile msixxxx.log might not be created.
Workaround:
v To create the installation log file, run the exe file from the command linewith this parameter: /v"/l install.log"
v To create the uninstallation log file, run the exe file from command linewith this parameter: /v"/l uninstall.log"
When you use the “Get” action for “RAID Config (ini file)”, the checkboxgroup“Use these additional command line parameters” might be unnecessary foryou.
When you create a task sequence to get the RAID from a server, thischeckbox group is displayed. It is likely that you do not need it. However,the users who want to get the error codes in the smsts.log file can use thischeckbox group.
You can select one of the following three parameters:
/e2 Returns an error code of 2 if no supported RAID controllers arefound in the system. By default, PRAID does not return errors ifno controllers are found in the system.
/e3 Returns an error code of 3 if at least one controller is found to bewithout any drives attached. By default, PRAID does not returnerrors if no drives are attached to a RAID controller.
/v:n Sets the verbosity level, where n is:
0 - quiet
3 - default
5 - maximum
Workaround: If you do not need these action parameters, just ignore thischeckbox group. For more information about PRAID parameters, refer tothe IBM ServerGuide Scripting Toolkit, Windows Edition (User's Reference).
The Configuration File Editor window loses focus when you save contents toanother file.
When you change the settings in the editor and save the changed settingsto a file, the editor window loses focus.
8 IBM Deployment Pack for Configuration Manager 2007, v1.4 Release Notes
|||
|
||
||
Workaround: This is a known limitation of OSD. No workaround isavailable currently.
Password cannot be saved when you use the “Retain network folder settings”function.
If you select the Retain network folder settings check box, the passwordcannot be saved. Therefore the task sequence might not correctly connectto the Microsoft System Center Configuration Manager server.
This is a known limitation of OSD.
Workaround: Manually input Path, Account, and Password instead ofselecting the Retain network folder settings check box.
PXE boot fails on the client machine after you restart the Microsoft SystemCenter Configuration Manager server.
After you restart the Microsoft System Center Configuration Managerserver, PXE boot will fail on the client machine. The error message is:“TFTP Error, File not found.”
The reason is that the PXE boot files on the Microsoft System CenterConfiguration Manager server are erased after the restarting.
Workaround: After you restart the Microsoft System Center ConfigurationManager server, perform the following steps :1. Stop the Windows Deployment Services (WDS).2. Delete or rename the windows\Temp folder and create a new
windows\Temp folder.3. Restart the WDS.
For more information, refer to this article in the Microsoft TechNet Forum:Configuration Manager – Operating System Deployment :http://social.technet.microsoft.com/forums/en-US/configmgrosd/thread/90308be3-81bc-462b-a014-a10e48452354/
Error messages might be displayed when you create an IBM bare metal tasksequence.
When you create an IBM bare metal task sequence, an error message mightbe displayed: CreateTaskSequenceTemplate: Unable to add the tasksequence 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 Managerserver and try creating the task sequence again.
A task sequence automatically picks up the OS when customer selects “Do notselect now” during the task sequence creation.
If you select Do not select now for the OS image selection when creating atask sequence, the task sequence picks up some available OS by defaultafter it is created. And if you apply the task sequence, an error message isdisplayed indicating “invalid values in some fields”.
Workaround: This problem is due to default OS selection mechanism. Toresolve the problem, select the default OS again, click OK, and clickApply.
During the task sequence editing, the sub-items need to be validated even if thegroup is disabled.
When you edit a task sequence, even if you disable a group, you still needto validate the sub-items of that group.
Chapter 1. Known limitations, problems, and workarounds 9
Workaround: Select the proper values of the sub-items to validate themaccording to the error icons, and apply the task sequence.
The Logs/Return Files tab displays errors although all the fields contain validvalues.
When you try to configure a get action in IBM task sequence, even if allthe fields contain valid values, there is still an error icon on theLogs/Return Files tab. In this case, you cannot save the configuration byclicking Apply or OK.
Workaround: The error icon will disappear if you click another field onthis tab, for example, a text box. You can then save the configuationsettings.
A task sequence can be saved although some fields are missing and display rederror icons.
When you generate a new task sequence that contains errors in somefields, this task sequence can be launched and closed and does not promptmessages. This task does not check errors before closing the task editor.
Workaround: The error icon will disappear if you click another field onthis tab, for example, a text box or a check box. You can then save theconfiguation settings.
The disk should be in active or unconfig good state before you can perform theSet RAID Config task in IBM Deployment Pack.
The Set RAID Config task will fail if the disk state is not active or unconfiggood. You can check the disk state from the WEBBIOS/RAID configurationpage.
Workaround: Reboot and set the disk to active state in WEBBIOS/RAIDconfiguration.
Windows 2003 OS cannot be deployed to a target computer if you did not selectdriver in Apply Driver Package of the Task Sequence.
If you did not select the specific driver in Apply Driver Package of theTask Sequence, the Windows 2003 OS deployment might fail with a bluescreen.
Workaround: If the target computer has a RAID card, select the correctRAID driver in Apply Driver Package of the Task Sequence. If the targetcomputer does not have a RAID card, deploy a OS image, which iscaptured from a target computer that has the same hardware options butdoes not have any RAID drivers. Then disable Apply Driver Package anddeploy Windows 2003 with the OS image.
The uninstall operation does not remove all components if the account does nothave SCCM administrator authority.
If you try to uninstall IBM Deployment Pack without the SCCMadministrator authority, the uninstallation does not remove all components.IBM Deployment Pack can be removed from the Add/Remove programlist, but you can still find the packages, drivers, or driver package items inthe Microsoft SCCM console. If you want to uninstall OSD, ensure that theaccount is in the system administrator group and SCCM administratorgroup.
Workaround: Remove IBM Deployment Pack with the systemadministrator and SCCM administrator authority.
10 IBM Deployment Pack for Configuration Manager 2007, v1.4 Release Notes
After upgrading OSD from 1.0 to 1.3, there is no IBM task sequence templateoption in the SCCM actions.
After upgrading OSD from 1.0 to 1.3, the task sequence menu Bare MetalDeployment is not shown in the SCCM console.
Workaround: Remove OSD 1.0 before OSD 1.3 is installed.
Windows Server 2008 (R2) OS failed to be deployed to a target computer if youapply drivers in step "Apply Driver Package" of the Task Sequence.
There is no need to apply drivers when you deploy Windows Server 2008and Windows Server 2008 R2.
Workaround: Disable the "Apply Driver Package" step in the TaskSequence.
IBM Deployment Pack can be installed when the import wizard is running.Users are not alerted that the import wizard is running and notified toclose the import wizard before starting the installation.
Workaround: This is a known issue. Please manually close the importwizard before IBM Deployment Pack installation.
Chapter 1. Known limitations, problems, and workarounds 11
||||
||
|||
||
12 IBM Deployment Pack for Configuration Manager 2007, v1.4 Release Notes
Chapter 2. Capturing and deploying Windows 2008 R2
When you install Windows 2008 R2, the system sometimes creates one morereserved partition based on your installation settings. You need to configure bothpartitions for OS deployment. If you only see one partition, you can skip steps inthe following topics and follow the common steps to capture and deploy OS.
You can see the two partitions (the reserved and C:) as shown in the followingscreen capture:
Capturing the WS08 R2 imageBefore capturing the WS08 R2 image, follow these steps to change the value of theOSDTargetSystemRoot property.1. Open SCCM Configuration Manager Console.2. Expand Computer Management → Collections.3. Click custom collection, right-click the target computer of capture, and click
Properties.4. Select Variables and add the OSDTargetSystemRoot property whose value is
[SystemDisk]:\Windows. (The D disk is the system disk in this example.)
Figure 1. Two partitions
© Copyright IBM Corp. 2010 13
5. Follow the common steps to capture the WS08 R2 image.
Deploying the WS08 R2 imageAfter capturing the OS image, you can import the WIM file to the SCCM server.
About this task
After you import the WIM file, you will see two volumes in the image list asshown in the following screen capture.
Figure 2. OSDTargetSystemRoot property
14 IBM Deployment Pack for Configuration Manager 2007, v1.4 Release Notes
The first volume (1-1) contains the 100 MB partition, and the second one (2-2)contains the OS image. Follow these steps to create a task sequence fordeployment:1. Create the IBM Server Deployment Task Sequence using the IBM Task Sequence
template.2. Edit the task sequence.3. Click Format and Partition Disk under Step 3 as shown in the following screen
capture.
Figure 3. Image list
Chapter 2. Capturing and deploying Windows 2008 R2 15
4. Double-click the first item in Volume. The Partition Properties menu isdisplayed.
5. Select the Mark this the boot partition option, select Quick Format, and enterBOOTPART in the Variable field. Click OK.
Figure 4. Format and Partition Disk
16 IBM Deployment Pack for Configuration Manager 2007, v1.4 Release Notes
6. Open Partition Properties to add a second volume. Set the following options asshown in the screen capture. Submit the changes by clicking OK:a. In the Partition options, select Use a percentage of remaining free space.b. Set Size(%) to 100.c. Select Quick Format and input OSPART in the Variable field:
Figure 5. Partition Properties
Chapter 2. Capturing and deploying Windows 2008 R2 17
The following screen is displayed after you submit the changes.
Figure 6. Partition Properties for the second volume
18 IBM Deployment Pack for Configuration Manager 2007, v1.4 Release Notes
7. Select Apply Operating System Image and change the Image to 2-2 in thedropdown list. As shown in the following screen capture, select Logical driveletter stored in a variable for Destination and input OSPART in the Variablefield. Click OK to submit the changes.
Figure 7. Task sequence
Chapter 2. Capturing and deploying Windows 2008 R2 19
8. Follow the common steps to deploy the WS08 R2 image.
Figure 8. Deploy Windows 2008 R2
20 IBM Deployment Pack for Configuration Manager 2007, v1.4 Release Notes
Notices
This information was developed for products and services offered in the U.S.A.IBM may not offer the products, services, or features discussed in this document inother countries.
Consult your local IBM representative for information on the products and servicescurrently available in your area. Any reference to an IBM product, program, orservice is not intended to state or imply that only that IBM product, program, orservice may be used. Any functionally equivalent product, program, or service thatdoes not infringe any IBM intellectual property right may be used instead.However, it is the user's responsibility to evaluate and verify the operation of anynon-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not grant youany license to these patents. You can send license inquiries, in writing, to:
IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A.
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express orimplied warranties in certain transactions, therefore, this statement may not applyto you.
This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.
Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct, and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.
© Copyright IBM Corp. 2010 21
TrademarksIBM, the IBM logo, and ibm.com® are trademarks or registered trademarks ofInternational Business Machines Corporation in the United States, other countries,or both. If these and other IBM trademarked terms are marked on their firstoccurrence in this information with a trademark symbol (® or ™), these symbolsindicate U.S. registered or common law trademarks owned by IBM at the time thisinformation was published.
Such trademarks may also be registered or common law trademarks in othercountries. A current list of IBM trademarks is available on the Web at Copyrightand trademark information at http://www.ibm.com/legal/copytrade.shtml.
Adobe and PostScript are either registered trademarks or trademarks of AdobeSystems Incorporated in the United States, other countries, or both.
Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc., inthe United States, other countries, or both and is used under license therefrom.
Intel, Intel Xeon, Itanium, and Pentium are trademarks or registered trademarks ofIntel Corporation or its subsidiaries in the United States and other countries.
Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc., inthe United States, other countries, or both.
Linux is a registered trademark of Linus Torvalds in the United States, othercountries, or both.
Microsoft, Windows, and Windows NT are trademarks of Microsoft Corporation inthe United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and othercountries.
Other company, product, or service names may be trademarks or service marks ofothers.
Important notesView important assumptions about terminology and claims.
Processor speed indicates the internal clock speed of the microprocessor; otherfactors also affect application performance.
CD or DVD drive speed is the variable read rate. Actual speeds vary and are oftenless than the possible maximum.
When referring to processor storage, real and virtual storage, or channel volume,KB stands for 1024 bytes, MB stands for 1v048v576 bytes, and GB stands for1v073v741v824 bytes.
When referring to hard disk drive capacity or communications volume, MB standsfor 1v000v000 bytes, and GB stands for 1v000v000v000 bytes. Total user-accessiblecapacity can vary depending on operating environments.
22 IBM Deployment Pack for Configuration Manager 2007, v1.4 Release Notes
Maximum internal hard disk drive capacities assume the replacement of anystandard hard disk drives and population of all hard disk drive bays with thelargest currently supported drives that are available from IBM.
Maximum memory might require replacement of the standard memory with anoptional memory module.
IBM makes no representation or warranties regarding non-IBM products andservices that are ServerProven, including but not limited to the implied warrantiesof merchantability and fitness for a particular purpose. These products are offeredand warranted solely by third parties.
IBM makes no representations or warranties with respect to non-IBM products.Support (if any) for the non-IBM products is provided by the third party, not IBM.
Some software might differ from its retail version (if available) and might notinclude user manuals or all program functionality.
Notices 23
24 IBM Deployment Pack for Configuration Manager 2007, v1.4 Release Notes
Readers’ Comments — We'd Like to Hear from You
IBM System xIBM Deployment Pack forMicrosoft System Center Configuration Manager 2007Release NotesVersion 1.4
We appreciate your comments about this publication. Please comment on specific errors or omissions, accuracy,organization, subject matter, or completeness of this book. The comments you send should pertain to only theinformation in this manual or product and the way in which the information is presented.
For technical questions and information about products and prices, please contact your IBM branch office, yourIBM business partner, or your authorized remarketer.
When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute your comments in anyway it believes appropriate without incurring any obligation to you. IBM or any other organizations will only usethe personal information that you supply to contact you about the issues that you state on this form.
Comments:
Thank you for your support.
Send your comments to the address on the reverse side of this form.
If you would like a response from IBM, please fill in the following information:
Name Address
Company or Organization
Phone No. Email address
Readers’ Comments — We'd Like to Hear from You����
Cut or FoldAlong Line
Cut or FoldAlong Line
Fold and Tape Please do not staple Fold and Tape
Fold and Tape Please do not staple Fold and Tape
NO POSTAGENECESSARYIF MAILED IN THEUNITED STATES
BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO. 40 ARMONK, NEW YORK
POSTAGE WILL BE PAID BY ADDRESSEE
International Business Machines CorporationPO Box 12195Research Triangle ParkNCU.S.A. 27709-9990
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
__
_
����
Printed in USA