Tivoli Provisioning Manager for Images System x Edition Version 7.1.1 Fix Pack 13, Readme

Product readme


Abstract

This readme file provides important information about Fix Pack 13 for Tivoli Provisioning Manager for Images System x Edition Version 7.1.1.

Content

IBM Tivoli Provisioning Manager for Images System x Edition Version 7.1.1 Fix Pack 13 Readme

IBM Tivoli Provisioning Manager for Images System x Edition Version 7.1.1 Fix Pack 13 Readme

Version 7.1.1 Fix Pack 13

© Copyright International Business Machines Corporation 2013. All rights reserved. US Government Users Restricted Rights - Use, duplication, or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

About this fix pack

This readme file provides important information about Fix Pack 13 for Tivoli® Provisioning Manager for Images System x Edition Version 7.1.1.

What’s New in this fix pack

Fix Pack 13 of Tivoli Provisioning Manager for Images System x Edition Version 7.1.1 contains the following enhancements:

  • The UEFI support is now extended to Linux for unattended deployments only.
  • When creating deployment schemes, you can select to use the Linux Deployment engine to deploy Linux cloned 64-bit profiles PXE, for driver injection purposes.
  • The IBM Global Security Kit Version 8 (GsKit) now supports the FIPS 140-2 compliance.

Fixes in this fix pack

Fix Pack 13 of Tivoli Provisioning Manager for Images System x Edition Version 7.1.1 contains the following fixes:

Software problems fixed:

  • APAR IV38026: Attempting to delete multiple drivers from a software package crashes the service.
  • APAR IV38619: An HTTP deployment failure occurs when using advanced TCP/IP settings.
  • APAR IV38625: The Linux cloning profile captured on HS22 fails when deployed on HS23.
  • APAR IV41201: The deployment fails due to TCP connection timeout.
  • APAR IV41956: A RHEL 6.4 profile deployment failure occurs after importing a profile multiple times.
  • APAR IV42060: The "Update" button to update a system profile with security updates (such as Windows hot fixes) does not work.
  • APAR IV43433: During the image deployment, an error is raised by GETPARTITIONSSTATUTEX.
  • APAR IV44240: Error raised by CmdWinVistaAction_DoIt in depl_vista.rbc, line 5756, when deploying a Windows 7 cloned image.
  • APAR IV44306: The Rembo service crashes when creating a software module consisting of an installation script and a 450 MB tar file using the Software Module Wizard.
  • APAR IV44416: The computer host name cannot be longer than 15 characters during the deployment.
  • APAR IV45078: Doing a preload redeployment the task does not start with an Oracle database.
  • APAR IV45133: With a target configured to use Advanced IP Setting - Static IP - manual, some DNS settings are not picked up by the ESXi server.
  • APAR IV45134: Unable to deploy ESXi to multiple targets simultaneously. Only the first target is installed successfully.

Documentation problems fixed:

  • APAR IV44309: A Windows image deployment fails with the error netfs-open: file is too large.

Fixes in previous fix packs

Fix Pack 12 of Tivoli Provisioning Manager for Images System x Edition Version 7.1.1 contains the following fixes:

Software problems fixed:

  • APAR IV32303: Linux deployment dual disk configuration might fail to correctly write the MBR on the primary disk.
  • APAR IV33039: Linux deployment to a Dell Precision 690 hangs on reboot.
  • APAR IV33499: Windows 7 deployment stops asking the product key.
  • APAR IV33503: Using the target option "Boot on OS if idle", the boot is not performed and the system hangs after a VMWare ESXi 5 deployment.
  • APAR IV34061: You cannot specify the VLAN ID on VMWare ESXi platforms.
  • APAR IV35683: After the deployment of a Windows XP unattended profile against Dell latitude E5530, the deployment stops and the RBO-Cache is not deleted.
  • APAR IV35796: Fix Pack 11 upgrade does not manage the WinPE deployment engine correctly.
  • APAR IV36023: During the deployment the RBO-cache mapping occupies the D: drive letter.
  • APAR IV36028: Web Interface extension installation fails because the Web Interface extension does not communicate with the OS Deployment server.
  • APAR IV36134: OS configuration using cluster NIC configuration might cause replication synchronization errors.
  • APAR IV36295: Operating system file transfer is always using unicast even if multicast file transfer was configured.
  • APAR IV36713: During the profile deployment a DISK://0:5/ deployment failure occurs when managing the temporary disk location on the target.
  • APAR IV36775: Windows 2008 R2 64-bit deployment fails on an IBM 3550 M4 due to the RAID controller driver embedded.
  • APAR IV37137: Scheduled jobs run twice.
  • APAR IV37449: VMWare ESXi deployment fails because the boot option of the ESXi installer does not include the VLAN ID.
  • APAR IV39196: The Server OS field exceeds the database length. String or binary are truncated.
  • APAR IV39371: Interface name is not maintained during the Red Hat cloned profile deployment.
  • APAR IV39797: The autologon might fail during the Windows XP deployment using the join domain option.

Fix Pack 11 of Tivoli Provisioning Manager for Images System x Edition Version 7.1.1 contains the following fixes:

Software problems fixed:

  • APAR IV25222: When using HTTP mode, it is not possible to define a partition as a % of the remaining disk.
  • APAR IV24918: Deployment wizard failure: an error is raised by GETSYSTEMARCH.
  • APAR IV29882: Improve multicast efficiency for fast network and large profiles.
  • APAR IV30711: ARP error during the network boot of an HP ELITEBOOK 8470P.
  • APAR IV30387: Edit engine driver binding grid takes 10 minutes to load because the MSSQL 2005 cross join is running slowly.
  • APAR IV31313: Large product logs cause problems to the PXE BOOT and Web UI log on.
  • APAR IV27940: The option: "When deployment is done: boot the operating system" causes the redeployment failure.

Documentation problems fixed:

  • APAR IV25177: A new procedure is now available on how to deploy a Windows retail media profile using Windows.
  • APAR IV28788: A new procedure is now available on how to deploy a DELL POWEREDGE family when configured to boot from SD card.
  • APAR IV29451: A reboot is needed between a capture of a Linux profile and a deployment of the same profile on the same machine.
  • APAR IV29727: Improvements in the GSKIT usage for FIPS compliance.

Fix Pack 10 of Tivoli Provisioning Manager for Images System x Edition Version 7.1.1 contains the following fixes:

Software problems fixed:

  • APAR IV12864: The operating system cannot be restored when the target boots with a network boot CD.
  • APAR IV17671: The model binding with DB2® does not work properly.
  • APAR IV18336: The VMWare ESX 3.5 deployment Fails with Tivoli Provisioning Manager for Images System x Edition 7.1.1.8
  • APAR IV19951: The hardware configuration fails on a UEFI enabled HS22 target if multiple NICs are present on the same subnet.
  • APAR IV21118: The option of importing all parameters from DHCP server does not work in kernel free mode.
  • APAR IV21387: Microsoft Windows 7 clone: the Windows reserved partition gets a drive letter after cloning.
  • APAR IV21484: In Windows 2008 Enterprise Server Japanese Edition - System Reserved, the partition has a label in Japanese.
  • APAR IV22094: Insufficient timeout in agent-server communication.
  • APAR IV22705: The RHEL 6.X unattended profile fails due to missing JAVA-1.6.0-OPENJDK-JAVADOC-1.6.0.0-1.41.1.10.4.EL6.X86_64.RPM
  • APAR IV22797: Windows 7 cloned with system locale different from English (for example, Japanese) cannot be deployed.
  • APAR IV22803: The deployment of a RHEL 6.2 unattended profile with every software group selected within the profile wizard fails.
  • APAR IV22808: When all the software groups are selected within the profile wizard to create an unattended profile, many RPMs are missing from the profile.
  • APAR IV23087: The editing of a volume label in Japanese environment for Windows operating systems through a system profile is not reflected in the deployed target.
  • APAR IV24398: The HP G7 blades cannot be deployed as there is not enough free memory available.
  • APAR IV24605: The deployment to HP G7 blades hangs at 73% due to the incorrect drive letter discovery on the operating system.
  • APAR IV24759: Unable to find hardware configuration image error when deploying multiple hardware configurations in one task in kernel free.
  • APAR IV24762: Procedure to keep command lines confidential does not work in hardware configuration tasks.
  • APAR IV24910: The automatic inventory of PCI and DMI devices does not complete successfully during the UEFI switcher.
  • APAR IV24979: The web interface extension RAD-UNREGISTERHOST command fails when only the MAC address is used.
  • APAR IV25175: Windows 2008 deployment fails with custom UNATTEND.XML.
  • APAR IV25454: Windows Server 2008 SP2 64-BIT fails when deploying on UEFI a profile captured on BIOS.
  • APAR IV25570: The system profile creation of VMware vSphere Hypervisor (ESXi) with IBM® Customization version 5 fails.
  • APAR IV25577: The disk label is assigned incorrectly if no mount point is provided.
  • APAR IV24931: The Tivoli Provisioning Manager for Images System x Edition install of 2008 R2 with extended partition fails while partitioning.
  • APAR IV28688: Multicast efficiency incorrectly calculated with large profiles.

Documentation problems fixed:

  • APAR IV18054: Clearer instructions are now available for configuring Tivoli Provisioning Manager for Images System x Edition to use a Microsoft Domain Controller for Tivoli Provisioning Manager for Images System x Edition web user interface authentication.
  • APAR IV19008: A new procedure is now available on how to use PAM for local user authentication.
  • APAR IV19027: The procedure for FIPS enablement with GSKIT has been improved.
  • APAR IV19651: Improve documentation about dynamic searches in target grouping.
  • APAR IV20815: The documentation about WinPE update has been improved.
  • APAR IV22046: Clarifications have been added to the documentation on when the dbgw needs to be installed on a Tivoli Provisioning Manager for Images System x Edition parent-child server.
  • APAR IV23078: The documentation has been updated about UEFI using FAT32 partitions.

Fix Pack 9 of Tivoli Provisioning Manager for Images System x Edition Version 7.1.1 contains the following fixes:

Software problems fixed:

  • APAR IV11706: Tivoli Provisioning Manager for OS Deployment fails when deploying a single ESX task to multiple targets.
  • APAR IV12373: The RHEL 5.6 setup deployment with multipath SAN disks fails during Linux setup Anaconda action.
  • APAR IV13912: The redeployment with multiple operating systems is now fixed.
  • APAR IV14253: On HP7800DC the USB port, mouse and keyboard are not functional when the operating system is booted from REMBO kernel.
  • APAR IV15082: During a Windows XP deployment, after joining the domain the AUTOADMINLOGON incorrectly uses a domain account.
  • APAR IV15550: During a Windows 7 deployment, after joining the domain the AUTOADMINLOGON incorrectly uses a domain account.
  • APAR IV15868: The operating system fails if a join domain is set and a reserved partition is present.
  • APAR IV16056: If legal notices are updated during the installation with a software module, the original value is restored on the deployed machine.

Fix Pack 8 of Tivoli Provisioning Manager for Images System x Edition Version 7.1.1 contains the following fixes:

Software problems fixed:

  • APAR IV06901: Hosts are not replicated in a multiserver environment. The registered targets on the parent server are not created on the child server. Likewise, with the two-way target sync option enabled, the targets on the child server are not created on the parent.
  • APAR IV07030: Hosts are not deleted in a multiserver configuration. When a target is deleted from the parent server it is not automatically removed from the child server . Likewise, with two-way target replication enabled, deleting a target from the child server does not remove it from the parent server.
  • APAR IV09143: It is now possible to customize the timeout duration while cloning from a reference Windows image file.
  • APAR IV09762: The deployment of a Windows 7 profile cloned from a Spanish OS fails.
  • APAR IV09997: The network share does not work when deploying Windows 2008.
  • APAR IV10219: The server does not take into account the value set for the BootReplyLimit parameter.
  • APAR IV10551: Improved string management in the INF file.
  • APAR IV11038: Kernel crashes on DELL 790/990 when the mouse or the keyboard are connected to the USB switch.
  • APAR IV11047: When redeploying to systems with a dedicated video card, the Linux Deployment Engine hangs on systems that have ATI video cards.
  • APAR IV11205: The OS detection fails when you try to capture a Windows XP reference machine with the ipv6 protocol installed and the ipv6 service not enabled.
  • APAR IV11737: Windows 2008 unattended deployment fails on targets containing either an IBM ServeRAID M1015 Disk Device controller or an IBM ServeRAID M5015 SCSI Disk Device controller.

Documentation problems fixed:

  • APAR IV09286: A new procedure is now available on how to deploy on a Windows target while keeping the existing partition.
  • APAR IV11064: Importing WIM images from Microsoft DVD is not supported.
  • APAR IV11276: A new procedure is now available on how to perform the redeploy of partition D with the BitLocker feature enabled.

Fix Pack 7 of Tivoli Provisioning Manager for Images System x Edition Version 7.1.1 contains the following fixes:

Software problems fixed:

  • APAR IV02842: When a generated ISO image is used to perform an offline deployment of Windows 2008 Standard 64-bit, the following error occurs: Invalid Argument.dcache: read past end of device. Before you create the CD\DVD you must rebuild the WinPE deployment engine.
  • APAR IV04046: Missing support of USB 2.0 devices from the console.
  • APAR IV04741: When editing a software module, the caption for the path field is not clear.
  • APAR IV06183: The Tivoli Provisioning Manager workflow named "TPMfOSd_Capture_GoldenMasterImage" fails when using a multiserver environment and Kernel-Free mode.
  • APAR IV06660: While creating a cloning profile of Windows Server 2008, the vm.log file shows the following error: Error raised by DbRbcExecEx in dbdb.rbc.
  • APAR IV06831: A problem occurs when restoring a Windows 7 SP1 captured image.
  • APAR IV06832: The injected drivers section is no longer visible after upgrading to Fix Pack 6.
  • APAR IV06939: You cannot deploy HP G6/G7 blades when the target is registered using the serial number.
  • APAR IV07306: The diagnostic partition cannot be deployed.
  • APAR IV07659: The profile deployment fails when the target uses SAN storage.
  • APAR IV07673: A failure occurs when cloning a Linux HP server with HP Smart Array controller installed.
  • APAR IV08594: A crash dump occurs, from Rembo 7.1.1.6 150.87, if more than 32 partitions are present on the server.

Documentation problems fixed:

  • APAR IV02218: When deploying a system profile against a Sony model, the last digit of the serial number is not reported in the Target Monitor. The serial number gets truncated to 15 characters.
  • APAR IV03981: The software module wizard does not resolve the .lnk files contained in the folder.
  • APAR IV04081: The Boot on OS function is not able to understand if you deployed a multi-boot system.
  • APAR IV07611: You cannot capture or deploy a cloning mode profile of the reference server using uEFI.
  • APAR IV07675: The deployment menu on the target is not available if the target is started in kernel-free mode.
  • APAR IV08838: The Oracle user must be created using the following roles and privileges:
    Table 1. Oracle user roles
    Role Admin option Default
    CONNECT N Y
    RESOURCE N Y
    Table 2. Oracle user privileges
    System privilege Admin option
    UNLIMITED TABLESPACE N
  • APAR IV08861: The following statement must be removed from the Web interface section of the infocenter:
    With the provisioning server and browser on the same computer, type 
    http://127.0.0.1:8080 in your browser to open the web interface login screen.

Fix Pack 6 of Tivoli Provisioning Manager for Images System x Edition Version 7.1.1 contains the following fixes:

Software problems fixed:

  • APAR IZ96552: After a deployment, the administrator account remains enabled on the target
  • APAR IZ97905: fixshare option procedure of rembo command terminated abnormally while removing duplicated entries
  • APAR IZ98628: ipv6 settings on windows donor machine not imported into cloned profile
  • APAR IZ98769: media creation wizard points to incorrect system type
  • APAR IZ99007: Windows 7 deployment fails in tpmfosd v.5.1.1.0 ee
  • APAR IZ99232: Receiving the message "error raised by cloningadddrivers in depl_xp2k
  • APAR IZ99557: Windows 2008 Japanese image deployment fails due to wrong language settings in the unattend.xml file
  • APAR IZ99708: Failure in creating Hardware Abstract Layer (HAL) injection for the Windows 2008 platform
  • APAR IZ99711: Missing some Intel NIC drivers in the Linux deployment engine package released with 7.1.1 Fix Pack 5
  • APAR IV00139: Software groups do not select software modules that are in different subdirectories
  • APAR IV00265: NIC driver not injected correctly into the operating system causes a network failure in WinPE
  • APAR IV00294: Setting the installation stage on a software group does not affect the behavior of the software modules
  • APAR IV01107: Static IP address is not correctly set in Windows offline deployments.
  • APAR IV01191: During a Windows clone profile deployment, the boot of WinPE stops due to a memory reservation in the kernel.
  • APAR IV01442: Reorder software module panel hangs when there are software modules of type "Group".
  • APAR IV01445: When exporting targets to a .csv file, the rembo service crashes and must be restarted manually.
  • APAR IV01473: Incorrect architecture error when trying to install Windows6.1-KB958830-x64-RefreshPkg.msu.
  • APAR IV02144: Boot on OS does not work on IBM X3850 and X3950 hardware after installing Linux or VMWare ESX operating systems.

Documentation problems fixed:

  • APAR IZ96962: The product assigns a drive letter to a bitlocker partition created using the bdehdcfg command.
  • APAR IV01087: The default location for the data folder, also known as data directory, is C:\TPMfOS Files\. To have the data directory on a network driver disk use the OS deployment server silent installation command line because it allows you to specify the UNC path of the data folder.

Fix Pack 5 of Tivoli Provisioning Manager for Images System x Edition Version 7.1.1 contains the following fixes:

Software problems fixed:

  • APAR IZ90884: When deploying a Windows XP profile to a target, the join domain on-site operation fails.
  • APAR IZ91067: Remove the error messages No deployment engine data found from the traces.
  • APAR IZ91072: When setting the Pacific timezone, the Baja timezone is applied instead.
  • APAR IZ92034: If deploying Windows 7 with the network share module feature configured, the deployment fails
  • APAR IZ92748: Unattended setup of Windows 2008 Server Standard with Volume License sets the deployed systems to Retail license.
  • APAR IZ93257: The Bootmgr file is locked during a direct migration.
  • APAR IZ91363: When the Java™ API is used to add network interfaces to a target, they appear in random order.
  • APAR IZ92802: When the agent running in rad-refreshhypervisor mode (needed for VM discovery on a hypervisor), the reboot is not run automatically.
  • APAR IZ92056: When creating software modules, some of the listed options are not supported.
  • APAR IZ92145: Update the message Unable to boot Linux Deployment Engine from agent for informing that a target PXE boot is needed.
  • APAR IZ94256: Errors might occur during the deployment of Windows 7/2008/Vista with software modules containing commands to run.
  • APAR IZ95754: Failure in creating differential Windows 7 rad
  • APAR IZ95746: If you set target hostname to star, a warning message is displayed.
  • APAR IZ96125: The product does not get the default gateway during Linux deployment if you set TCP/IP to Static, import from DHCP server.
  • APAR IZ96135: During deployment of a Windows clone profile, the following error is displayed on the target: Last action (Install Operating System files) caused an exception" errno = 0 in CltSynchronize (act_common.rbc line 292).
    Note:
    To run the fix open the /global/radconf/*.ini file related to the customer profile and add the following line to the end of the [Configuration] section:
    LegacyFormat="true"
  • APAR IZ97085: Memory reservation was added to prevent conflicts.
  • APAR IZ97102: During profile capture from a 64-bit Windows 2008 R2 HS22 blade, an error occurs and the Web Interface hangs.
  • APAR IZ97364: The network card does not receive packets in PXE on HP BL460C G7.
  • APAR IZ97983: The software module binding rule Windows (setup only) (windows%setup) does not work when the DB2 database is used
  • APAR IZ97905: The fixshared option of the rembo command ends with errors while removing duplicated entries
  • APAR IZ98600: The bounded drivers are not installed during the deployment of Windows 7

Documentation problems fixed:

  • APAR IZ92050: You can create a snapshot only if the Web Interface Extension does not run on the target or the target is stopped.
  • APAR IZ92340: The product does not need to have a dedicated partition to make the BitLocker tool work.
  • APAR IZ91267: You cannot deploy a machine if the bootable partition is not on C:
  • APAR IZ94803: In Linux deployments, unallocated space is left on the target.
  • APAR IZ95176: CD boot fails on LVM partitions.
  • APAR IZ96522: WinPE 3.0 deployment engine installation failure

Fix Pack 4 of Tivoli Provisioning Manager for Images System x Edition, Version 7.1.1 contains the following fixes:

  • APAR IZ86320: Tivoli Provisioning Manager and Tivoli Provisioning Manager for Images System x Edition automatic synchronization/replication failure
  • APAR IZ86603: Tivoli Provisioning Manager for Images System x Edition unable to use multiple system profiles
  • APAR IZ86865: SLES 10 SP3 deployment fails if "pseudo" loopback address is written in /etc/hosts file
  • APAR IZ87116: SELINUX is incorrectly set to "enforcing" if deployment is done via HTTP
  • APAR IZ87346: Offline deployment fails if disk cluster size is not 4KB
  • APAR IZ87262: Operation not permitted (invalid runtime environment, current is kernel_native but "Agent_winstall" was expected)
  • APAR IZ88198: Windows 7 failing on non-English locales with 0XC0000098
  • APAR IZ88201: Hostname always set to localhost when deploying VMWare ESX 4.0
  • APAR IZ88280: There is no disk in drive using WinPE
  • APAR IZ88480: Join domain on-site does not work in FP3 for Windows Vista/2008/7
  • APAR IZ88662: Error when deploying Windows 7/2008 R2
  • APAR IZ89558: Keyboard not found error when deploying a RHEL clone profile
  • APAR IZ89684: Hostname is not set correctly after deploying SLES 11 SP1
  • APAR IZ89573: System profile can be corrupted by deleting file
  • APAR IZ90143: Network boot CD/DVD for RHEL 5.5 hangs with a blank screen
  • APAR IZ90541: Software module failure when HTTP option is set to no

Documentation problems fixed:

  • APAR IZ86709: Error when deploying Windows XP with a "Boot Sector 52"
  • APAR IZ86771: In a parent/child environment, a deployment fails if started from one OS deployment server and the PXE target boots from another
  • APAR IZ87093: WIM cloning is supported only for Windows Vista/2008/7
  • APAR IZ88197: Windows Administrator password has a 15-character limitation
  • APAR IZ88887: Child web interface unusable during object replication
  • APAR IZ89542: Redeployment by deployment media is not supported
  • APAR IZ89963: Cannot deploy multiple targets simultaneously in HTTP mode
  • APAR IZ89975: Multicast ports need to be open in both directions

Fix Pack 3 of Tivoli Provisioning Manager for Images System x Edition, Version 7.1.1 contains the following fixes:

Software problems fixed:

  • APAR IZ68559: The deletion of the / partition in Linux profiles makes the system profile unusable because VPD are lost
  • APAR IZ70575: Error of the sequence for reboot where PXE is not the first device in boot sequence, during Linux deployment
  • APAR IZ72327: Unable to have actions other than "display a green banner" in the redeployment template
  • APAR IZ74372: Symlink is not correctly handled during Linux deployment
  • APAR IZ75029: Multicast feature has not been working from 7.1.1 GA version
  • APAR IZ75341: The creation of a SW profile from a WIM image of Windows 7 leaves EditionID empty
  • APAR IZ75561: Tivoli Provisioning Manager for Images System x Edition does not handle a ks.cfg file containing the percent char '%'
  • APAR IZ75849: Error when attaching two software modules during a Linux deploy task
  • APAR IZ75868: RAID configuration not possible with HP Start Smart toolkit, due to a too short DB column
  • APAR IZ76045: Tivoli Provisioning Manager for Images System x Edition 7.1.1.1 HPBL460C G6 unable to boot into Linux deployment engine
  • APAR IZ76074: Tivoli Provisioning Manager for Images System x Edition is unable to reconnect a child server to the DB if it gets error code 99999
  • APAR IZ76362: The Linux deployment engine does not contain the driver for the Fujitsu Siemens ESPRIMO P9900 hardware
  • APAR IZ76553: Unable to create a net boot CD if you save the .iso in a path with blank spaces
  • APAR IZ76688: Kernel panic when deploying RHEL 5.2 64bit clone profile with / on LVM partition
  • APAR IZ76736: Problem with "disk geometry" when using WINPE2, blank screen appears.
  • APAR IZ76751: Tivoli Provisioning Manager for Images System x Edition does not handle HP machine with SMART ARRAY controller when deploying Linux
  • APAR IZ76977: When deploying a clone profile to a target having the same type as the donor, some drivers are not injected correctly
  • APAR IZ76989: The deployed /etc/fstab on a cloned system does not reflect the same file on the donor system
  • APAR IZ77239: The LV names in a deployed Linux clone profiles are different from the donor names
  • APAR IZ77348: The new UEFI BIOS update tool iflash.exe is not recognized by Tivoli Provisioning Manager for Images System x Edition
  • APAR IZ77434: After a successful deployment of Windows 2008, the boot on OS of the x3850 M2 fails
  • APAR IZ77522: The OS restore task creates and leaves on the deployed machine the RBO-CACHE partition
  • APAR IZ77633: Non-PCI device drivers are wrongly processed
  • APAR IZ77852: LVM Linux partitions are not counted correctly as primary partitions when creating a clone profile.
  • APAR IZ77860: Tivoli Provisioning Manager for Images System x Edition 7.1.1.2 fails when deploying SLES clone profile with LVM partitioning
  • APAR IZ77923: Linux deployment over IBM System x3650 M2 fails due to a wrong driver in Linux deployment engine.
  • APAR IZ78133: Rembokernel hang when starting netboot CD on HP model with ILO card
  • APAR IZ78148: If importing a targets list (csv) with the fixed ip value set, the option in the common networking information is not set to static IP.
  • APAR IZ78388: ISO images in OSD are for Intel machines only. Therefore, ISO images downloaded directly from big-endian (non-Intel) servers are useless. They are valid, instead, if downloaded using rbagent running on an Intel-based machine different from the server.
  • APAR IZ78474: Tivoli Provisioning Manager for Images System x Edition 7.1.1.1 does not correctly capture and detect multi-path SAN disks. It also creates multiple disks in the image profile based on each copy of the same disk.
  • APAR IZ80501: A deleted Windows setup partition leads to the deployment of an empty partition.
  • APAR IZ80503: User builds a Windows 2003 64-bit OS image. When User deploys the image on an HP system, the rembokernel hangs on the first boot.
  • APAR IZ80605: If creating an unattended profile from the Tivoli Provisioning Manager WEBUI on a Japanese machine, as soon as you click the option a failure occurs.
  • APAR IZ81460: Deploying a cloning image of Windows 2003 server 64bit to a HP DL380 G6 server fails
  • APAR IZ81877: In Linux /UNIX unattended installations, if a password is provided that is made up of hexadecimal characters only, it is not interpreted correctly as an encrypted password, causing the installation to fail.
  • APAR IZ83218: Management of DB2 connection code loss was missing from dbgw.jar
  • APAR IZ83526: The rbagent hangs at startup when launched with debug level 5 or 6 on Linux platforms
  • APAR IZ84719: If deploying a Windows Server 2008 SP2 Enterprise 64-bit clone profile and adding the admin password to the profile configuration, the deployment stops with the password value to be entered by the user on the target machine. This problem occurs whether or not an administrator name is entered.
  • APAR IZ84854: The NIC card initialization does not complete when requesting the DHCP address in WinPE

Documentation problems fixed:

  • APAR IZ73167: Tivoli Provisioning Manager for Images System x Edition is unable to deploy SLES 11 when partition schema include more than two logical partitions
  • APAR IZ76612: It is not possible to run a hardware capture when a target boots from a net boot CD.
  • APAR IZ77441: Documentation lacks steps to be performed to make a child server a standalone server.
  • APAR IZ77666: Instructions to create RAID configuration task are not sufficiently documented
  • APAR IZ83005: The generation of a boot CD leads to a core dump

Fix Pack 2 of Tivoli Provisioning Manager for Images System x Edition, Version 7.1.1 contains the following fixes:

Software problems fixed:

  • APAR IZ65150: Unmounted partition when using the do not deploy option
  • APAR IZ68390: Missing packages for the Japanese distribution
  • APAR IZ68580: Mount point is null when deploying Linux profiles created in 5.1.1 or 7.1.1
  • APAR IZ68900: IBM Systems x3850 and x3950 generates an error when PXE boots with an external NIC
  • APAR IZ69078: deployment problems with more than 1 nic connected to Tivoli Provisioning Manager for Images System x Edition
  • APAR IZ69202: No password required to login to the Tivoli Provisioning Manager for Images System x Edition web user interface
  • APAR IZ69594: Wrong offline mbr with FAT32 partition
  • APAR IZ70318: Header in autoinst.xml causes a deployment failure
  • APAR IZ70838: offlineMBR not set during Windows GUI setup when target has bootable disks not discovered as first
  • APAR IZ70889: After the deployment of Windows 7 user administrator remains logged on
  • APAR IZ71026: can not run host inventory when OS is installed
  • APAR IZ71181: offlineMBR code hung when starting "reading ldr" last line appearing on the screen
  • APAR IZ72900: Windows 2000, Windows 2008 deployment: popup appears at first boot on operating system when offline SAN disks are attached
  • APAR IZ73008: Operating system configuration parameter [dhcpname] does not work
  • APAR IZ73127: 'mount point' information in the "hint /tooltip" for Linux operating system
  • APAR IZ73234: Added 10 second delay to let WAIK inject drivers into WinPE ramdisk for Window 2008 x64bit
  • APAR IZ73419: Failure in deploying SUSE Linux Enterprise Server 10 SP2 over a 2 disk machine
  • APAR IZ73428: Unable to capture the profile of a Dell PowerEdge 840 running Windows 2003 or Windows 2008
  • APAR IZ73763: WinPE assigns labels to SAN disk partitions
  • APAR IZ73842: When using a custom partition scheme, the ESX 3.5 deployment fails
  • APAR IZ74327: Missing deployment progress in target monitor
  • APAR IZ74454: Windows 2008 deployment fails on IBM System x3850 enterprise server.
  • APAR IZ74524: Labels are set wrongly for LVM partitions
  • APAR IZ74558: Unable to provision computers with SATA drives
  • APAR IZ74766: Offline PXE OSD deployment boot disk failure

Documentation problems fixed:

  • APAR IZ68790: Partitioning in autoinst.xlm is not used
  • APAR IZ70752: Limitation to 16 MB for the file upload option when editing software modules and browsing partition files.
  • APAR IZ70746: There is no check on rpm dependencies when rpms are added through autoyast.xml file
  • APAR IZ72555: When cloning Linux you can have 3 primary partitions only
  • APAR IZ72907: Only unattended AIX® setup is supported. Cloning is not supported.

Fix Pack 1 of Tivoli Provisioning Manager for Images System x Edition, Version 7.1.1 contains the following fixes:

Software problems fixed:

  • APAR IZ60585: Redeployment feature does not work on 7.1.1
  • APAR IZ60805: Second partition automatically sets to E: when deploying Windows 2000 or Windows 2008 operating systems
  • APAR IZ61279: Tivoli Provisioning Manager for Images System x Edition 7.1.1 deployment to a Dell 760 computer hangs during disk partitioning
  • APAR IZ62814: Network boot via cd fails if a static IP address is selected
  • APAR IZ62602: PXE emulation via cd or usb fails
  • APAR IZ62518: After Red Hat Linux 5.3 deployment, the user cannot be switched (su)
  • APAR IZ63339: Red Hat Linux 5.3 directories permissions are changed with clone profiles
  • APAR IZ63955: Diskpart failing when a drive different from the drive C is not empty
  • APAR IZ63961: Unallocated space left on the deployed machine
  • APAR IZ64803: Bad binary rbagent for rebranded version
  • APAR IZ64855: On some Lenovo notebooks, Windows XP operating system cannot be provisioned with Tivoli Provisioning Manager for Images System x Edition 7.1.1
  • APAR IZ65300: Duplication problem when cloning Linux Box with multiple disks
  • APAR IZ64805: Operating system installation of German Windows Server 2008 and Windows Vista operating systems fails
  • APAR IZ65377: No deployment engine data found because of a letter assignment problem
  • APAR IZ65258: Parent-child replication does not work in Tivoli Provisioning Manager for Images System x Edition 7.1.1
  • APAR IZ65981: The network boot CD with static IP address can switch to DHCP if more than one NIC is detected
  • APAR IZ67024: IBM eserver 3550 bare metal disk not found

Documentation problems fixed:

  • APAR IZ59903: Support of Red Hat Linux 5.3 missing in the operating system table.
  • APAR IZ64414: Requirement of using the English WAIK version
  • APAR IZ64940: Partitions are aligned on megabytes rather than on cylinders
  • APAR IZ66354: Broadcom NetXtreme II drivers can be injected, by packaging the drivers in the special RIS package.
  • APAR IZ67064: During deployment of a Linux Red Hat using an unattended install setup, the non-silent installation starts.

Known problems in Fix Pack 13

Fix Pack 13 of Tivoli Provisioning Manager for Images System x Edition Version 7.1.1 contains the following known issues:

  • When upgrading from Tivoli Provisioning Manager for Images System x Edition 7.1.1.8 or earlier, WinPE 3.1 must be uploaded to the OSD server as a new deployment engine in order to support UEFI targets. To use the WAIK files and the associated procedure go to http://www.microsoft.com/en-us/download/details.aspx?id=5188 and http://technet.microsoft.com/en-us/library/dd349350(v=ws.10).aspx#Win7SP1. To successfully add the WinPE 3.1 deployment engine, the web interface extension on the WAIK endpoint used for WinPE 3.1 deployment engine generation must be uninstalled at the deprecated level and then reinstalled at the current level.
  • The redeployment preload is supported for Linux operating systems only if the file systems in the profile are ext2 or ext3 with 128-byte inode size. To determine if the file system has a 128-byte inode size, run the following command:
    tune2fs -l /dev/sda2 | grep "Inode size"
    where:
    /dev/sda2
    Is the file system where the operating system is installed.
  • The deployment of a Linux system profile with an LVM partition that is less than or equal to 10% of disk fails.
  • The direct migration of Windows XP Professional SP2 from HP Desktop machine (300 GB HDD) to IBM ThinkPad T410 (500 GB HDD) fails due to driver injection problems

    Workaround: Provide the following package to the Windows XP installer during its initialization by pressing F6: 32-bit Intel RST Driver Files for F6 Install

    This driver includes the inf files that describe the supported PCI devices and the txtsetup.oem file needed to inject the driver.

  • During Linux deployments in non-HTTP mode, unallocated space is left on the target disk equal in size to the rembo cache used by the deployment. This space is not added to the partition defined as the 100% of the remaining disk space. To solve the problem, run Linux deployments in the HTTP mode.
  • In a multiserver environment with a centralized database, if you change the OS deployment server hierarchy using the web interface, the OS deployment server roles are updated only after a server restart.
  • The OS deployment server might be unable to boot a Linux deployment engine environment on some recent HP BIOS targets and on a Lenovo ThinkCentre M90.
  • When a target is deleted from either a parent or child OS deployment server, it might still appear as part of the environment.
  • Deployment fails on the following hardware:
    Table 3. Deployment failure on hardware
    Software Deployment Hardware
    RHEL 5u5 32bit and 64bit HP DL580 G4, HP DL785 G6
    SLES10 SP3 32bit HP DL580 G2 HP DL580 G5, HP DL785 G6
    SLES11 SP1 32bit HP DL580 G4
    VMware ESX 4.0 U2 HP DL785 G6
    VMware ESX 4.1 HP DL585 G2, HP DL580 G4, IBM System x3850
    VMware ESX 4.2 IBM System x3850
  • Network deployment of SUSE Linux Enterprise Server (SLES) version 11, GA version, fails because SLES11 does not contain NIC drivers for Lenovo ThinkPad T510.
  • When deploying the Enterprise and Datacenter editions of Windows Server 2008 or Windows Server 2008 R2 on a server that contains more than one disk, either local or remote (such as SAN or SAS disks), the additional disks are shown as offline.
  • If you create a system profile that contains EXT2 file system partitions, then after the deployment, all of the file system partitions are transformed into EXT3.
  • Deployment of RAID configurations is not supported on HP DL580 G2 hardware.
  • Even if the deployment of a Windows XP SP3 cloning-mode system profile on a target with two hard disks ends successfully, when the target reboots, it hangs.
  • If the WinPE deployment engine is not created automatically, try to create it by restarting the machine hosting the OS deployment server. If the WinPE deployment engine is still not created, verify the following to create it at the next reboot:
    1. Ensure that there is a loopback entry present in the C:\WINDOWS\system32\drivers\etc\hosts file.
    2. Ensure that the loopback entry in the C:\WINDOWS\system32\drivers\etc\hosts file is not commented.
    3. Reboot the system.
  • If you create an image of a machine having extended partitions, when you deploy it, the logical partitions might not be handled correctly.
  • When you use the driver bindings from the web interface to bind a software folder to a device, the binding does not work. To create the rule using the web interface, expand the folder and manually bind all the items contained in the folder.
  • During ESX 3.5 deployment on a blade machine, after copying the files, the machine hangs when rebooting. After manual reboot, deployment completes successfully.
  • The Windows 2003 EE R2 SP2 x64 setup deployment using a network boot CD on a blade target HS20 fails.
  • Keyboard mapping is incorrectly set up when redeploying a RH5.4 on Hyper-V virtual machine.
  • If the HTTP Linux is disabled, the deployment of a SLES11 setup profile with only one disk defined fails on blade targets with two hard disks.
  • In the Windows 2003 clone deployment with two NIC cards, the DNS search order of the second NIC card is not set on the target computer.
  • After Windows 2008 deployment with target advanced network settings, the DNS suffix related to the second network connection is not set.
  • Every time you run a task that involves loading the Linux deployment boot engine to deploy SLES 10 virtual images on HP pro 3090 MT or Dell Vostro 230 machines, after the Linux deployment boot engine is loaded, the agent crashes because of a missing Realtek NIC driver in Linux deployment engine. The following error message is displayed: Agent Crash.

Problems with network boot USB drives

There are several known issues when using a USB drive as a boot device. Some problems are not related to the product, but instead are related to specific hardware.

  • The rbagent running on Windows is required to prepare USB drives even if the server is installed on UNIX.
  • During the deployment, the target computer displays a black screen and a blinking cursor after the letters "F@.". This problem can occur intermittently.

    Workaround: Power® off the target and remove the USB device.

  • Target computer displays black screen and the letters "F@_". This problem has been observed on some types of hardware and there is no known workaround. A BIOS flash might resolve the problem.
  • Target computers with multiple USB ports fail to boot with the USB device connected to some of the ports, but not all.

    Workaround: Try connecting the USB device to a different port and retry the deployment.

  • Scenarios that require multiple boots must list the USB device before the hard drive in the boot sequence.
  • Some targets boot successfully on flash USB drives, as well as disk drives, but cannot boot on other disk drives.

    Workaround: Retry with another USB device or flash the BIOS if the target does not detect the USB drive.

  • The USB drive is larger than the size supported by the BIOS.

    Workaround: Modify the partitions on your USB drive to have the first partition on the drive smaller than the size seen by the BIOS and use this partition to create the bootable USB drive.

  • Launching Windows PE from a USB drive is very slow.

    Workaround: Reset default settings in the BIOS.

  • An error might occur when performing an unattended installation of the Windows operating system using offline deployment USB media. After disk partitioning, the target reboots and the following message is displayed: Unable to reach WPE environment from AGENT_WPE
  • Deployment using USB media is not supported on the following Lenovo models due to a BIOS problem:
    • Lenovo Thinkpad R400
    • Lenovo Thinkpad W540
    • Lenovo Thinkpad X200
    • Lenovo Intellistation S20
    • Lenovo ThinkCenter M55p
    • Lenovo ThinkCentre M58e
    • Lenovo Thinkpad T400
    • Lenovo ThinkCentre 7188W4P M58p
    • Lenovo ThinkCentre M57
    Regularly check the Lenovo support and downloads website for available BIOS updates and fixes that might resolve these problems.

Installation, upgrade, and configuration information

Tivoli Provisioning Manager for Images System x Edition Version 7.1.1.13, is a full image that replaces all binaries of Tivoli Provisioning Manager for Images System x Edition 7.1.1.

Tivoli Provisioning Manager for Images System x Edition Version 7.1.1.13, can also be uninstalled to reinstall the GA version of Tivoli Provisioning Manager for Images System x Edition Version 7.1.1.

Installation on Windows operating systems

Fix Pack 13 is provided as a full build. To install it, you must upgrade your OS deployment server. Before installing the fix pack, perform a partial uninstallation and then install the fix pack full build.

For details about how to install Fix Pack 13 for Tivoli Provisioning Manager for Images System x Edition Version 7.1.1 on computers with a Windows operating system, see Installing Tivoli Provisioning Manager for Images on Windows operating systems.

Installation on UNIX operating systems

Fix Pack 13 is provided as a full build. To install it, you must upgrade your OS deployment server. Before running a full build file replacement, stop the dbgw, rembo, and rbagent daemons.

For details about how to install Fix Pack 13 for Tivoli Provisioning Manager for Images System x Edition Version 7.1.1, on UNIX computers, see Installing Tivoli Provisioning Manager for Images on UNIX operating systems.

Uninstallation

On Windows operating systems, you can run a partial uninstallation that leaves the database and the disk images on your system.

On UNIX operating systems, you must run a full uninstallation.

Uninstallation on Windows operating systems

To uninstall Fix Pack 13 for Tivoli Provisioning Manager for Images System x Edition Version 7.1.1, from computers with a Windows operating system installed, see Uninstalling Tivoli Provisioning Manager for Images on Windows operating systems.

Uninstallation on UNIX operating systems

To uninstall Fix Pack 13 for Tivoli Provisioning Manager for Images System x Edition Version 7.1.1 from UNIX computers, see Uninstalling Tivoli Provisioning Manager for Images on UNIX operating systems.

Documentation updates

You can view the latest version of the Tivoli Provisioning Manager for Images System x Edition infocenter, at:

http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/index.jsp?topic=/com.ibm.tivoli.tpm.osdimg.doc/welcome/osdimgwelcome.html .

Appendix A. Contacting IBM software support

IBM Software Support provides assistance with product defects.

Before contacting IBM Software Support, your company must have an active IBM software maintenance contract, and you must be authorized to submit problems to IBM. The type of software maintenance contract that you need depends on the type of product you have:

  • For IBM distributed software products (including, but not limited to, Tivoli, Lotus®, and Rational® products, as well as DB2 and WebSphere® products that run on Windows or UNIX operating systems), enroll in IBM Passport Advantage® in one of the following ways:
    • Online: Go to the Passport Advantage web page (http://www.ibm.com/software/howtobuy/passportadvantage/) and click How to Enroll
    • By phone: For the phone number to call in your country, go to the IBM Software Support web site (http://techsupport.services.ibm.com/guides/contacts.html) and click the name of your geographic region.
  • For IBM eServer™ software products (including, but not limited to, DB2 and WebSphere products that run in IBM zSeries®, IBM pSeries, and IBM iSeries® environments), you can purchase a software maintenance agreement by working directly with an IBM sales representative or an IBM Business Partner. For more information about support for eServer software products, go to the IBM Technical Support Advantage web page (http://www.ibm.com/servers/eserver/techsupport.html).

If you are not sure what type of software maintenance contract you need, call 1-800-IBMSERV (1-800-426-7378) in the United States or, from other countries, go to the contacts page of the IBM Software Support Handbook on the web (http://techsupport.services.ibm.com/guides/contacts.html) and click the name of your geographic region for phone numbers of people who provide support for your location.

Appendix B. Notices and trademarks

The following section includes important information about this document and its use.

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 in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does 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 any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785 U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

Intellectual Property Licensing
Legal and Intellectual Property Law
IBM Japan, Ltd.
1623-14, Shimotsuruma, Yamato-shi
Kanagawa 242-8502 Japan

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement might not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM web sites are provided for convenience only and do not in any manner serve as an endorsement of those web sites. The materials at those web sites are not part of the materials for this IBM product 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 it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Corporation
2Z4A/101
11400 Burnet Road
Austin, TX  78758 U.S.A.

Such information may be available, subject to appropriate terms and conditions, including in some cases payment of a fee.

The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.

If you are viewing this information in softcopy form, the photographs and color illustrations might not be displayed.

Trademarks

IBM, the IBM logo, and ibm.com® are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.

Linux is a trademark of Linus Torvalds in the United States, other countries, or both.

Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Other company, product, and service names may be trademarks or service marks of others.

Rate this page:

(0 users)Average rating

Document information


More support for:

Tivoli Provisioning Manager for OS Deployment

Software version:

7.1.1

Operating system(s):

AIX, Linux, Solaris, Windows

Reference #:

7039046

Modified date:

2013-08-09

Translate my page

Machine Translation

Content navigation