Skip to main content

 
Professional certification
 alt="" height="6"
  >  
Certifications

  >  
Test information

Test 879: IBM Tivoli Provisioning Manager Express V4.1 for Software Distribution


Overview Objectives alt="" height="1" width="30" Test Preparation

Section 1 - Planning

  1. Given the customer’s environment, document the required network resources, access and machines by location, distribution mechanism, evaluate customer bandwidth, end user access rights and security policies, validate the IBM Tivoli Provisioning Manager Express V4.1 Software Distribution (TPMx) Server hardware against specifications determined in technical TPMx manuals and ensure sufficient hardware resources are available, so that the TPMx infrastructure requirements are known and the architectural design document is created. With emphasis on performing the following steps:
    1. Determine number of locations.
    2. Determine if proxy servers are in place.
    3. Determine number of subnets.
    4. Determine network utilization.
    5. Determine network link speeds(10Mbit, 100 Mbit, etc.).
    6. Determine any firwall(client or network) restrictions(i.e., Zonelabs, etc.).
    7. Determine number of machines per location.
    8. Evaluate list of distribution mechanisms, to choose the method for agent deployment.
    9. Evaluate customer bandwidth, end user access rights and security policies to determine best type of packages for deployment.
    10. Review TPMx technical docs for appropriate TPMx server hardware and resources.

  2. Given the access to an IT Administrator or focal point, interview the IT administrator or focal point to determine how the current client server environment is configured, TPMx technical specification of hardware to be utilized, so that the client server environment is understood. With emphasis on performing the following steps:
    1. Determine if Active Directory/LDAP integration is required.
    2. Determine if fileshare utilization is needed.
    3. Determine user access rights on machines.
    4. Determine if there is another software delivery mechanism in place.
    5. Obtain projected size of packages.
    6. What is the size of the change window for package deployment?

      7. termine the manufacturers for machines that are currently in use.
    7. Determine the custom software that is in use.

      8.  +#Given the architectural design document, determine the appropriate TPMx Server installation parameters to be used during the installation of the TPMx server, so that the TPMx server installation parameters are determined and added to the architectural design document. With emphasis on performing the following steps:
    8. Review TPMx installation documentation.
    9. Review the architectural document.

  3. Given the architectural design document, determine the appropriate TPMx Server hardware and software prerequisites, so that the TPMx server hardware and software can be defined. With emphasis on performing the following steps:
    1. Review architectural design document.
    2. Review pre-requisite software for TPMx.
    3. Determine if any additional hardware needs to be obtained.

Section 2 - Installing

  1. Given the Tivoli Provisioning Manager Express for Software Distribution (TPMx) media, installation guide and architecture design documents, run the TPMx setup program so that TPMx is installed on the server. With emphasis on performing the following steps:
    1. Click Install TPMx (server).
    2. Click “Click here to install IBM TPMx Server”.
    3. Click Next.
    4. Accept IBM and non-IBM usage Terms by clicking on appropiate radio buttom and click next.
    5. Select Quick and choose and installation path click next.
    6. Enter the servername, server port, server context and the administrators’ email address as documented in the architecture design documents. Click next.
    7. Review installation path and click next.
    8. Click Finish.

  2. Given the TPMx media, installation guide and architecture design documents, run the TPMx Advanced Setup program so that TPMx is installed on the server. With emphasis on performing the following steps:
    1. Click Install TPMx (server).
    2. Click “Click here to install IBM TPMx Server”.
    3. Click Next.
    4. Accept IBM and non-IBM usage Terms by clicking on appropiate radio buttom and click next.
    5. Select Custom and choose an installation path click next.
    6. Select Enable e-mail functions and fill appropiate e-mail settings according to architecture desing documents. @Click next
    7. Enter the servername, server port, server context and the administrators’ email address as documented in the architecture design documents. Click next.
    8. Select the appropiate authority and roles for each task according the the architecture desing documents.
    9. Select the appropiate settings for client agent scheduling and server task scheduling according the architecture desing documents.
    10. Select the appropiate settings for password control and password creation rules according the architecture designing documents.
    11. Select one or more fields that will be required in order for an asset to be succefully added to the TPMx database.
    12. Select the security settings that will be monitored by TPMx on the client workstation.
    13. Review installation path and click Next.
    14. Click Finish.

  3. Given a recently installed TPMx, verify TPMx web interface and TPMx Engine so that the TPMx server installation can be verified. With emphasis on performing the following steps:
    1. Launch the Windows Services Control Panel applet.
    2. Verify the “IBM Websphere Application Server v6 – Tivoli Provisioning Manager” service is in a started state.
    3. Click Start --> Programs --> IBM Tivoli Provisioning Manager Express--> Shortcut to Tivoli. Provisioning Manager Express to Launch TPMx Home page.
    4. Click Manage Assets.
    5. Enter Admin user name and password.
    6. Update the Admin password and optionally update the details of the default admin account and click submit.
    7. Select Admin --> View Application Log and verify there are no errors listed.

  4. Given a verified TPMx Server or the media CD, run the TPMx client setup, so that the TPMx client can be installed. With emphasis on performing the following steps:
    1. From a client workstation use the browser to open up http://tpmxserver.company.com/tpmx/ or launch media drive:\ TPMXSWDA\tpmxsd_setup.exe.
    2. Select “Click Here” to download the client setup. Select Run.
    3. Click Next.
    4. Select Typical, click next.
    5. Enter the TPMx Server hostname or IP. Click next.
    6. Click Install.
    7. Click Finish.

  5. Given a verified TPMx Server or the media CD, run the Advanced TPMx Client setup, so that the TPMx client can be installed. With emphasis on performing the following steps:
    1. From a client workstation use the browser to open up http://tpmxserver.company.com/tpmx/ or launch media drive:\ TPMXSWDA\tpmxsd_setup.exe.
    2. Select “Click Here” to download the client setup. Select Run.
    3. Click Next.
    4. Select Advanced, click next.
    5. Select the TPMx Client install directory. Click Next.
    6. Enter the TPMx Server hostname or IP, communications port and server context. Click Next.
    7. Enter the proxy information if required. Click Next.
    8. Select the time window during which the agent can contact the TPMx Server. Click Next.
    9. Click Install.
    10. Click Finish.

  6. Given a verified TPMx Server or the media CD and the Redbook “Deployment Guide Series IBM Tivoli Provisioning Manager V4.1 for Software Distribution”,deploy the TPMx client agent unattended, so that the TPMx client agent can be deployed to multiple machines. With emphasis on performing the following steps:
    1. Review unattended command line agent installation in the TPMx Redbook.
    2. Select apropiate properties.
    3. Build the apropiate command line string using the properties selected ; for example

      4. tpmxsd_setup.exe /s /v"/qn SERVER_HOSTNAME=http://TPMXSERVER SERVER_PORT=80"
    4. Execute the command using the preferred delivery mechanism.

  7. Given a TPMx server and agent are installed, verify a successful registration to the server so that the communication between TPMx agent and server is verified. With emphasis on performing the following steps:
    1. Click Start -->Programs -->IBM Tivoli Provisioning Manager Express Shortcut to TPMx to Launch TPMx Home page.
    2. Click Manage Assets.
    3. Enter Admin user name and password.
    4. Click on Dists -->All Machines.
    5. Verify that the Agent is listed and the timestamp is not older than 24 hours.
    6. Explore Agent installation path (i.e. C:\Program Files\IBM\Tivoli\TPMX\Agent\logs).
    7. Open the sdcagent.log, scroll down to the last lines.
    8. Check for presence of “INFO : Autoregistered : ……”
      1. Given a TPMx server Installed, uninstall the TPMx server so that TPMx is removed from the system. With emphasis on performing the following steps:
    9. Click Start -->Control Panel --> Add or Remove Programs.
    10. Search for IBM Tivoli Provisioning Manager Express for Software Distribution.
    11. Click on Change/Remove.
    12. Select Remove --> click Next.
    13. Click OK if you want to remove the server.
    14. Click OK.
    15. Click on Finish.

  8. Given a TPMx agent Installed, uninstall the TPMx agent so that TPMx agent is removed from the system. With emphasis on performing the following steps:
    1. Click Start --> Control Panel --> Add or Remove Programs.
    2. Search for IBM Tivoli Provisioning Manager Express for Software Distribution – Agent.
    3. Click on Remove.
    4. Select Remove --> click Yes.

Section 3 - Configuring

  1. Given a IBM Tivoli Provisioning Manager Express V4.1 Software Distribution (TPMx) server installed and verified, define the purpose the TPMx properties files so that purpose of the files are understood. With emphasis on performing the following steps:
    1. common.properties: This file is used to control database connection settings and user demographics compliance.
    2. ldap.properties: This file is used to control TPMx authentication to LDAP, user authentication via LDAP and importation of groups from LDAP.
    3. log4j.properties: This file is used to control logging parameters.
    4. sdc.properties: This file is used to control software distribution default values, purchase order management, ftp parameters.

  2. Given a TPMx server installed and verified, update/define the TPMx isic.properties file so that the file has been updated. With emphasis on performing the following steps:
    1. Update SMTP – email configuration settings.
    2. Update Action Authority configuration settings.
    3. Update Scheduling configuration settings.
    4. Update Password configuration settings.
    5. Update User Form configuration settings.
    6. Update Security Settings configuration settings.
    7. Perform additional configuration for upload.
    8. Perform additional configuration for Queries.
    9. Perform additional configuration for Queue Management.
    10. Perform additional configuration for the DBCleaner.

  3. Given a default installation of the TPMx Agent, architectural design documents, use local or server configuration files so that the TPMx Agent configuration can be updated. With emphasis on performing the following steps:
    1. Explore to the agent installation path (ex. C:\Program Files\IBM\Tivoli\TPMX\Agent).
    2. Open the sdc.conf file.
    3. Modify the necessary parameters as defined in the architecture documents.
    4. OR
    5. Open the sample config files located in c:\program files\IBM\Tivoli\TPMx\Server\TPMXAPP.ear\tpmx.war\apps\sdc-client\*
    6. Modify the necessary parameters as defined in the architecture documents.
    7. Copy the updated files to c:\program files\IBM\Tivoli\TPMx\Server\TPMXAPP.ear\tpmx.war\apps\ .

  4. Given a TPMx server is installed and verified, create the TPMx folder structure so that the folder structure has been created to assist with managing packages. With emphasis on performing the following steps:
    1. Explore to the document root (ie C:\Program files\IBM\Tivoli\TPMX\SERVER\TPMXAPP.ear\tpmx.war).
    2. It is beneficial to use the \PACKAGES folder under the document root to help you organize the files associated with your packages. Under the \PACKAGES folder, it is possible to organize your packages by operating system, type of application, or any other characteristic that meets the requirements. It is a good idea to plan for long-term organizational needs before designing.

  5. Given a verified Tivoli Provisioning Manager for Software Distribution Server (TPMx) and the Redbook “Deployment Guide Series IBM Tivoli Provisioning Manager V4.1 for Software Distribution”, prepare a shared folder for installations using LogicalDrive(Secure) on a windows file share so that LogicalDrive(Secure) packages can be used. With emphasis on performing the following steps:
    1. Open the registry key

      2. \HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet
      \Services\lanmanserver\parameters.
    2. Double-click NullSessionShare and add the sharename to the value data.
    3. Open the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa.
    4. Ensure that restrictanonymous: REG_DWORD : 0 is defined. If not defined add a new DWORD. Value and ensure value data is set to 0.
    5. Ensure that everyoneincludesanonymous: REG_DWORD : 1 is defined. If not defined add a new DWORD Value and ensure value data is set to 1.
    6. Set Share Permissions to include Read Permissions for Everyone.
    7. Add Groups or User name ANONYMOUS LOGON.
    8. Set Share Permissions to only include Read Permissions for
    9. ANONYMOUS LOGON.
    10. Close all the windows.
    11. Reboot the server.

Section 4 - Troubleshooting

  1. Given a TPMx server problem, locate and review the TPMx server logs, enable debugging and if necessary restart the TPMx Service so that the problem can be resolved. With emphasis on performing the following steps:
    1. Go to the \Program Files\IBM\Tivoli\TPMX\SERVER\PROFILES\TPMXPROFILE\logs\TPMX\SERVER folder on the TPMX server to display the SystemErr.log
    2. Go to the \Program Files\IBM\Tivoli\TPMX\SERVER\PROFILES\TPMXPROFILE\logs\TPMXSERVER folder on the TPMX server to display the SystemOut.log
    3. Review the contents of the logs for error messages.
    4. On the TPMx server go to the: \Program Files\IBM\Tivoli\TPMX\SERVER\TPMXAPP.ear\tpmx.war\WEB-INF\classes\log4j.properti es file
    5. Change the Default Log Level line to:ALL to obtain the maximum level of logging. Note: there are 7 levels of logging available (ALL, DEBUG, INFO, WARN, ERROR, FATAL, OFF) Increased event logging to the tpmx.log file
    6. If troubleshooting an LDAP issue, go to: \Program Files\IBM\Tivoli\TPMX\SERVER\TPMXAPP.ear\tpmx.war\WEB-INF\classes\ldap.propertie s file

  2. Given a TPMx client agent problem, locate and review the TPMx client agent log, so that the log has been located and reviewed. With emphasis on performing the following steps:
    1. Go to the \Program Files\IBM\

      2. Tivoli\TPMX\Agent\logs folder on the client workstation to display the sdcagent.log.
    2. Review the contents of the logs for error messages.

  3. Given that a client workstation cannot connect to the TPMx server, locate and view the TPMx client agent log and client configuration file, so that the problem can be determined.

    4. With emphasis on performing the following steps:
    1. On the local machine go to: \Program Files\IBM\
    2. Tivoli\TPMX\Agent\logs\sdcagent.log.
    3. View the ERROR : Server return with error message: Operation timed out: connect:could be due to invalid address.
    4. Go to the \Program Files\IBM\Tivoli\TPMX\Agent\sdc.conf file and confirm that the line: com.ibm.sdc.server.host is correct.

  4. Given that client machines are having problems, modify the client debug setting, so that the number of events logged is increased. With emphasis on performing the following steps:
    1. On the local machine go to: \Program Files\IBM\Tivoli\TPMX\Agent\sdc.conf.
    2. Add the line: com.ibm.sdc.agent.debug=true , in order to increase the number of events logged.

  5. Given that a software package is not completing successfully on a client machine, review the distribution event logs, so that the TPMx return codes are found and identified.

    6. With emphasis on performing the following steps:
    1. In the TPMx server admin console: Select Reports --> Distribution Reports --> View Logs to display the distribution results for a software package.
    2. Review the TPMx Server return code in the log to determine the failure.
    3. Select the Tool Tip next to the return code to display the type of failure.

  6. Given that the customer workstation requires a secure WinZip 9.0 package and the defined installation file is not available on the server, a warning message is displayed indicating that the system could not locate the defined installation file, manually create a digital certificate for software packages of type Logical Drive (secure), so that the digital certificate file is available. With emphasis on performing the following steps:
    1. Manually create a digital certificate for the WinZip 9.0 software package of type Logical Drive.
    2. Open a command prompt window and Change to the \signatures folder located under (default) - \Program files\IBM\Tivoli\TPMX\Server\TPMXAPP.ear\tpmx.war.
    3. Run the command: java -jar ..\..\apps\sdcsigner.jar.\..\packages\win32\winzip90\WinZip90M.exe

Section 5 - Administering

  1. Given a request for adding a new default user id to TPMx, fill in the default mandatory fields, so that the requested User ID has been created and verified. With emphasis on performing the following steps:
    1. Logon to TPMx Administrative console with an ID that had administrative access.
    2. Within the admin console, select Users -> Users -> New.
    3. In the Add User form, enter in the following default mandatory fields: User ID, E-Mail Address, First Name, and Last Name.
    4. In the Add User form, select default authority from the drop-down menu.
    5. In the Add User form, select the group or groups of which the user will be a member of.
    6. In the Add User form, Click Submit.
    7. Within the admin console, select Users -> Users -> All Users.
    8. In the All User list verify that the new user ID has been created.

  2. Given a request to delete a User ID from TPMx, delete the User ID using the Administrative console, so that the requested User ID has been removed and verified.

    3. With emphasis on performing the following steps:
    1. Logon to TPMx Administrative console with an ID that had administrative access.
    2. Within the admin console, select Users -> Users -> All Users.
    3. On the All Users list, Select the check boxes next to the user names you want to delete.
    4. On the All Users list Click Delete from the Actions box.
    5. On the Process Transfer Page enter in your reason and select Yes to approve the transaction.
    6. On the Process Transfer Page Click Submit.
    7. Within the admin console, select Users -> Users -> All Users.
    8. In the All User list verify that the User ID has been deleted.

  3. Given a request to create a group within TPMx, create a group using the Administrative console, so that the requested group has been created and verified. With emphasis on performing the following steps:
    1. Log on to TPMx Administrative console with an ID that had administrative access.
    2. Within the admin console select Users -> Software Catalog Groups -> New Group to display the Add Group form.
    3. On the Add Group page, enter the name in the Name field and the description in the Description field for the group.
    4. On the Add Group page Click Add, you will get a new page about the creation of the group.
    5. Within the admin console, select Users -> Software Catalog Groups -> All Groups.
    6. In the All Groups list verify that the new group has been created.

  4. Given a request to delete a Group from TPMx, delete a group using the Administrative Console, so that the requested Group has been removed and verified. With emphasis on performing the following steps:
    1. Logon to TPMx Administrative console with an ID that had administrative access.
    2. Within the admin console select Users -> Software Catalog Groups -> All groups.
    3. On the All Groups list, From the List Groups table, select the check box next to the group name you want to delete.
    4. On the All Groups list Click Delete.
    5. In the conformation dialog box, click OK to delete the group.
    6. Within the admin console, select Users -> Software Catalog Groups -> All groups.
    7. In the All User list verify that the Group has been deleted.

  5. Given a request to add a User ID to a group in TPMx, add a User ID to a group using the Administrative Console, so that the requested User ID has been add to the group.

    6. With emphasis on performing the following steps:
    1. Logon to TPMx Administrative console with an ID that had administrative access.
    2. Within the admin console select Users -> Software Catalog Groups -> All Groups.
    3. On the All Groups list, from the List Groups table select the group name.
    4. From the Update Group area, select the Users tab.
    5. Click the user name from the User List for a specific group.
    6. Make the changes to the user information in the Update User area.
    7. On the Update User portion, click update.

  6. Given that a request to add a software package in TPMx, add a software package to TPMx using the Administrative Console, so that the software package is added to TPMx .

    7. With emphasis on performing the following steps:
    1. Logon to TPMx Administrative console with an ID that had administrative access.
    2. Within the admin console select Software -> Packages -> New Package
    3. Select the General Tab of the Package Management Page
    4. On the General Tab enter the name of the package and the version in the respective fields.
    5. On the General Tab enter the document root path to the details file in the details field.
    6. On the General Tab enter the document root path to the icon.gif in the Icon Path field.
    7. On the General Tab enter the maximum install time in minutes for the software package to complete the install on a client machine.
    8. Other options that are avaliable on the General Tab:
    9. Select Silent for the software package so that it installs unattended.
    10. Select Package Reboot so that the software package initiates the reboot of the machine.
    11. Select Client Reboot so that the Tivoli Provisioning Manager Agent initiates the reboot of the machine.
    12. Select Mandatory so that the software package is essential and installs immediately upon startup of the Software Distribution Catalog.
    13. Select Enable Deferral option so that the end user can choose to defer the mandatory package installation.
    14. Select the Deferral Number to indicate the number of times the end user can choose to defer the mandatory package installation.
    15. Select the Deferral Duration to indicate the interval until the next mandatory package installation attempt.
    16. On the General Tab Click Next to get to the Install Tab.
    17. On the Install Tab select the Package Type of the software package: Download, Logical Drive, or Directory Download.
    18. On the Install Tab select Secure if the package requires administrator rights to install.
    19. Based on the Download package type selected, the next fields are defined as follows:
    20. In the Installation File field type the document root path to the installation file.
    21. In the Installation Parameters field type the installation parameters to be passed to the executable if required.
    22. Based on the Logical Drive package type selected, the next fields are defined as follows:
    23. In the Installation File field type the drive designation and path relative to the shared drive to be mapped to the client.
    24. In the Installation Parameters field type the installation parameters to be passed to the executable if required.
    25. Based on the Download Directory package type selected, the next fields are defined as follows:
    26. In the Installation Directory field type the document root path to the installation directory.
    27. In the Installation Command field type the installation command to be run after the delivery of the source directory.
    28. To remove the source directory from the client machine after executing the install command, select Remove Directory After InstallSelect Include MST / ISS File to activate the text field. Type the document root path to the MST file or ISS response file.
    29. Click Show Command to display a pop-up window containing the installation command syntax that will be executed on the client machine.
    30. You can Select Enable Process Tracking to track subprocesses of a software package.
    31. Type in the Windows registry key or stamp file in their respective fields.
    32. Select the stamp file mode.
    33. Type the stamp file date if using the Dated option from the Stamp Mode field.
    34. If using Purchase Orders to enable software package installation, select this option to enable require purchase orders and then type the part number.
    35. Click Next to get to the Target Tab.
    36. In the Temp. Space Required field type the temporary space required in megabytes.
    37. In the Target Space Required type the target space required in megabytes.
    38. In the Target Directory type the target directory.
    39. In the Prerequired Program type the document root path to the prerequired program.
    40. In the Preinstall Program type the document root path to the preinstall program.
    41. In the Postinstall Program type the document root path to the post-install program.
    42. Select Enable Network Speed Detection to require a minimum network speed for the package installation.
    43. Select the Network Speed Allowed to specify the minimum network speed requirement for the package installation.
    44. Click Next to ge tto the Platform Tab.
    45. On the Platform tab, choose the target platforms that the package is designed for.
    46. Click Next to get to the Upload Tab.
    47. Click Browse or type the local path to the download package installation file or ZIP file of the directory download source tree to be uploaded to the server and placed in the installation file location.
    48. Click Browse or type the local path to the package details file to be uploaded to the server and placed in the details file location.
    49. Click Browse or type local path to the package icon .gif file to be uploaded to the server and placed in the details file location.
    50. Click Browse or type local path to the package MST/ISS file to be uploaded to the server and placed in the MST/ISS file location.
    51. Select Add to submit the Pakcage entry to the TPMx for processing.

  7. Given a request to export a package definition in TPMx, export a package and/or bundle definition in to XML format using the Administrative Console, so that a file containing the package and/or bundle definitions in XML format. With emphasis on performing the following steps:
    1. Logon to TPMx Administrative Console with an ID that had administrative access.
    2. Within the admin console select Select Software -> Export/Import -> New Export.
    3. In the Add Export area, enter the name in the Name field and the description in the Description field for the export and then Click Next.
    4. Select the packages to add to the export list by selecting the check box next to the package names and then @Click Next.
    5. Select the bundles to add to the export list and Click OK to save the export list.
    6. You will get a message that says "Export_list_name has been added successfully".
    7. Select Software -> Export/Import -> All Exports to display the export table.
    8. From the List Exports table, select the export name.
    9. From the Edit Export table, click OutputXML.
    10. Click Open to display the XML output in a browser.
    11. Click Save to save the XML output.

  8. Given a request to import a package and/or bundle definition in TPMx, import the package and/or bundle defintion using the Administrative Console, so that a package and/or bundle is added to TPMx. With emphasis on performing the following steps:
    1. Logon to TPMx Administrative console with an ID that had administrative access.
    2. Within the admin console select Select Software -> Export/Import -> Import XML.
    3. Select the XML File for Import area, in the File Name field, enter the XML source file name or click Browse to select the XML output file. Click OK.
    4. In the Import Package area, click OK to accept each package. Click Skip to bypass any package you do not want to import. After all the packages and bundles contained in the output XML have been added, you will be prompted to add the export definition used to create the export output XML file.
    5. Click OK to finish importing the XML output file.

  9. Given a request to add a purchase order in TPMx, add a purchase order using the Administrative Console, so that the purchase order is available for use in the system. With emphasis on performing the following steps:
    1. Logon to TPMx Administrative console with an ID that had administrative access.
    2. Select Software -> Purchase -> New Purchase Order to display the Add Purchase Order Form.
    3. Enter the Purchase Order Number, the Part Number for the associated package, the Employee ID of the end user, and any associated Description and Click OK.
    4. You get a message that says "Purchase_order_number has been added successfully.

  10. Given a request to update a purchase order in TPMx, update the puchase order using the Administrative Console, so that the purchase order is updated in TPMx.

    11. With emphasis on performing the following steps:
    1. Logon to TPMx Administrative console with an ID that had administrative access.
    2. Select Software -> Purchase -> All Purchase Orders.
    3. From the List Purchase Orders table, click the purchase order number you wish to modify.
    4. Make changes to the purchase order information and Click OK.

  11. Given a request to delete a purchase order in TPMx, delete the purchase order using an Administrative Console, so that the purchase order is deleted from TPMx. With emphasis on performing the following steps:
    1. Logon to TPMx Administrative console with an ID that had administrative access.
    2. Select Software -> Purchase -> All Purchase Orders.
    3. Select the check box next to the purchase order number you want to delete and Click Delete.
    4. Click OK on the confirmation message that pops up to delete the purchase order.

  12. Given a request to Create a Software Bundle in TPMx, create a software bundle using the Administrative Console, so that there is a software bundle to install from the TPMx. With emphasis on performing the following steps:
    1. Logon to TPMx Administrative console with an ID that had administrative access.
    2. Select Software -> Bundles -> New Bundle.
    3. In the Add Bundle table Enter the name, description, and stamp file values.
    4. Select the Selectable option to define the bundle as optional and allow individual packages to be removed by the end-user or fail an installation without affecting the remaining packages in the bundle, and select the supported operating system for the bundle. Click Add.
    5. On the Update Bundle panel, click Next.
    6. On the Packages tab, select the packages to add to the bundle definition and Select Update.
    7. From the Adjust Package Order area, adjust the package installation sequence in the bundle definition and @Click OK.
    8. The Add Bundle area, you will get a message that says "Bundle_name has been added successfully".

  13. Given a request to update a Software Bundle in TPMx, update the software bundle using the Administrative Console, so that you have completed the modification of the software bundle in TPMx. With emphasis on performing the following steps:
    1. Logon to TPMx Administrative console with an ID that had administrative access.
    2. Select Software -> Bundles -> All Bundles.
    3. Click the software bundle name and the Update Bundle window opens.
    4. Make the changes to the software bundle definition information.
    5. Click Next or Packages to display the list of available packages.
    6. Select the check box next to the software package name you want to add to the bundle.
    7. After selecting all the packages to add to the bundle, click Update.
    8. You will be prompted to select the order of installation for the packages in the bundle.
    9. Select a software package name, and click Up or Down to move the packages into the desired order.
    10. Click OK to update the bundle.

  14. Given a customer has requested a list of all the TPMx Software Packages designed for the Windows XP OS, create a search to list only the Windows XP packages, so that only Windows XP packages are displayed. With emphasis on performing the following steps:
    1. Logon to TPMx Administrative console with an ID that had administrative access.
    2. Select Software--> Packages --> All Packages.
    3. Select the Search tab.
    4. In the “OS:” Drop down window, select Windows XP and press Search.

  15. Given that a customer has informed the administrator that a software package now requires a registry entry update program patch.exe to be executed after the software package has been installed, update the original software package, so that the registry is updated when the install completes. With emphasis on performing the following steps:
    1. Log on to TPMx Administrative console with an ID that had administrative access.
    2. Copy the customer supplied patch to the package repository on the TPMx server: /tpmx/packages/win32/
    3. Select Software--> Packages --> All Packages.
    4. Find and then Select the Software package.
    5. Select the Target Tab.
    6. In the Postinstall Program field, Enter: /tpmx/packages/win32//patch.exe.
    7. Press the Update button.

  16. Given the customer has requested that all the Windows XP machines have the latest Microsoft Security patch applied, generate a list of machines that have Windows XP installed, so that the Security patch can be applied to all of the Windows XP machines. With emphasis on performing the following steps:
    1. Log on to TPMx Administrative console with an ID that had administrative access.
    2. Select Dists--> Distribution Lists --> New Distribution List.
    3. In the Name: field, Enter a name for the new Distribution List.
    4. In the Description: field, , Enter a description for the new Distribution List.
    5. Press the Selectable Search tab.
    6. In the “OS:” Drop down window, Select Windows XP and press Search.
    7. Select the check box next to the “Name” column to select all the machines, then press Update.

  17. Given a request to distribute a package to a subset of end-users, create a new evaluation using the Administrative Console, so that the evaluation is created. With emphasis on performing the following steps:
    1. Logon to TPMx Administrative console with an ID that had administrative access.
    2. Within the admin console select Dists --> Evaluations --> New Evaluation.
    3. Select the General Tab of the Evaluation Management Page.
    4. On the General Tab enter the name of the evaluation and the description in the respective fields.
    5. Select Case Sensitive if the user want to define if the condition will use case sensitive to find data and select SD to define if the condition wil use only SD machine data tables.
    6. Switch to the Conditions tab and add your evaluation conditions.
    7. Click OK when finished.

  18. Given a request to distribute a package to a subset of end-users, create an evaluation from a query using the Administrative Console so that the evaluation is created. With emphasis on performing the following steps:
    1. Logon to TPMx Administrative console with an ID that had administrative access.
    2. Within the admin console select Assets --> All Assets
    3. Select an Asset.
    4. Click on button create Evaluation directly.
    5. Select the General Tab of the Evaluation Management Page.
    6. On the General Tab enter the name of the evaluation and the description in the respective fields.
    7. Select Case Sensitive if the user want to define if the condition will use case sensitive to find data.
    8. Click OK to Finish.
    9. OR
    10. Select an action to be performed on selected asset that required data (ie. Software Summary by selected OS).
    11. Select a Software or a field you want to perform an evaluation on the right panel (ie. Acrobat Reader 5.0).
    12. Click an action you want to have data for on the left panel (ie. Models with selected software).
    13. Click on Edit SQL.
    14. On the panel Edit Report click on Edit SQL.
    15. Modify SQL for custom reports and click Update.
    16. Click Create Evaluation.
    17. Select the General Tab of the Evaluation Management Page.
    18. On the General Tab enter the name of the evaluation and the description in the respective fields.
    19. Select Case Sensitive if the user want to define if the condition will use case sensitive to find data.
    20. Click OK to create the evaluation.

  19. Given a request to edit an evaluation to distribute a package to a subset of end-users, edit the evaluation using the Administrative Console so that the evaluation is modified.

    20. With emphasis on performing the following steps:
    1. Logon to TPMx Administrative Console with an ID that had administrative access.
    2. Within the Administrator Console select Dists --> Evaluations --> All Evaluation click on the Evaluation Name to edit it.
    3. Change the description if needed.
    4. Change Case Sensitive option if the user want to define if the condition will use case sensitive to find data and SD option to define if the condition wil use only SD machine data tables.
    5. Click on the Conditions tab.
    6. Modify the conditions as required.
    7. Click OK to finish.

  20. Given that a request to Create a portable Software Catalog be distributed from CD or DVD, create a portable software catalog using the Administrative Console, so that the catalog can be distributed using portable media. With emphasis on performing the following steps:
    1. Logon to TPMx Administrative console with an ID that had administrative access.
    2. Select Software, Export Import, New Export.
    3. In the Add Export area, enter the name in the Name field and the description in the Description field for the export Click Next .
    4. Select the packages to add to the export list by selecting the check box next to the package names.
    5. Click Next Select the bundles to add to the export list.
    6. Click OK to save the export list.
    7. Click Apply if the Add Purchase Order page message says "Export_list_name has been added successfully”.
    8. Select Software, Export, Import, CD Catalog Exporter.
    9. Click Start In the Security Warning dialog box.
    10. In the CD Catalog Exporter window select an export group previously created from the Export Group field.
    11. In the Image Location field, type the file name or click Browse to select the folder where the portable catalog files and folders are to be stored.
    12. Select Reversibly Corrupt to indicate that the individual packages should be encoded with the Reversibly Corrupt process.
    13. Select Delete Image After Install.
    14. Click Preview to take note of space per package, verify list of packages, the total space required, and the names of any missing files.
    15. Click Export to initiate the process of creating the directory structure with the specified packages from the export list.
    16. Verify process is complete, the bottom of the CD Catalog Exporter window will display “Done”.
    17. Obtained locally CD/DVD recording software of your choice to copy the portable catalog files and folders to the CD or DVD.

  21. Given a request to Schedule a distribution,create a schedule for a distribution using the Administrative Console, so that the distribution can be scheduled. With emphasis on performing the following steps:
    1. Logon to TPMx Administrative console with an ID that had administrative access.
    2. Select Dists, Schedule, New Schedule, to display the Add Schedule table. In the Add Schedule table.
    3. Enter the name of the schedule and add any add-itional description information.
    4. Select Enable to activate the schedule for distribution.
    5. Select the distribution list from the drop-down menu to define the list of target machines to be included in the scheduled distribution.
    6. Select Enable Deferral Option.
    7. Select 3 for the number of times the installation can be deferred.
    8. Select the duration between deferrals.
    9. Set the daily start time and daily end time and set the start date and the end date for the distribution.
    10. Click Next to display the package/bundle search.
    11. Entering the search criteria based on name, package type, and operating system
    12. Select package, Click Add.
    13. Verify the Add Schedule page has a message that says "Schedule_name has been added successfully".

  22. Given a request for a software distribution report that is currently available in TPMx, create the report using the Administrative Console, so that a standard report is produced.

    23. With emphasis on performing the following steps:
    1. Determine which report needs to be produced.
    2. Logon to the TPMx with an Admin ID.
    3. Go to the report menu and select the distribution reports.
    4. Select one of the reports needed.
    5. Submit to produce the report.

  23. Given a request for a standard inventory report that is currently available in TPMx, create the report using the Administrative Console, so that a standard inventory report is produced. With emphasis on performing the following steps:
    1. Determine which report needs to be produced.
    2. Logon to the TPMx with appropriate ID.
    3. Go to the report menu and select the All Assets.
    4. Select one of the reports needed under All Assets
    5. Submitt to produce the report.

  24. Given a request for a custom inventory report that is not currently available in TPMx, create and run the report using the Administrative Console, so that a custom inventory report is produced. With emphasis on performing the following steps:
    1. Determine what needs to be in the report.
    2. Logon to the TPMx with an appropriate ID.
    3. Go to the report menu and select the All Reports.
    4. Select an existing report from the All Report menu.
    5. Edit the selceted report by selecting edit this row and add additional column.
    6. Submit to produce the report.

  25. Given the need to list all machines running software from a specific vendor, create a custom query using the TPMx GUI to list all machines having the specific vendor’s software, so that the all machines running the software are displayed. With emphasis on performing the following steps:
    1. Login to TPMx.
    2. Select Assets from TPMx GUI.
    3. Select All Assets.
    4. Select the All checkbox.
    5. Select Show Software Summary for Selected Assets.
    6. Select Edit SQL.
    7. Select Modify Conditions.
    8. Click on the Add button.
    9. Scroll down and select Software.Vendor.
    10. Set value equal to desired vendor name.
    11. Click Add.
    12. Click Submit.
    13. Click Reports.
    14. Click Save Custom Query.
    15. Enter Query Name.
    16. Enter Description.
    17. Enter Menu Name.
    18. Click Selected checkbox.
    19. Click Submit.

  26. Given the need to identify and explain the four functions of the TPMx Client, define eGather2, callHome2, Software Distribution Agent & Software Distribution C atalog so that the functions are understood. With emphasis on performing the following steps:
    1. eGather2: Workstation Scanning Engine that will return all hardware and software attributes.
    2. callHome2:Service used to call egather2 and upload the scanned data to the TPMx Server.
    3. Software Distribution Agent: Service used to complete scheduled distributions. Additionally receives calls from the SD Catalog to complete secure package installations.
    4. Software Distribution Catalog: End-user interface used to install applications using a “pull”.

Section 6 - Maintaining

  1. Given a new TPMx Patch has been released, apply the TPMx patch, so that TPMx server infrastructure has the updated TPMx code. With emphasis on performing the following steps:
    1. Determine if the TPMx patch needs to be applied.
    2. Apply patch to the TPMx test server.
    3. Verify functionality of the TPMx test server after the patch has been applied.
    4. Determine an install schedule time.
    5. At the install scheduled time ensure no distributions are in the Queue.
    6. Apply the TPMx patch to the production server.
    7. Verify the TPMx patch is applied and the server is working.

  2. Given a new TPMx upgrade that has been released, apply the TPMx upgrade, so that TPMx server infrastructure has the TPMx code upgrade. With emphasis on performing the following steps:
    1. Determine if the TPMx upgrade needs to be applied.
    2. Apply upgrade to the TPMx test server.
    3. Verify functionality of the TPMx test server after the upgrade has been applied.
    4. Determine an install schedule time.
    5. At the install scheduled time ensure no distributions are in the Queue.
    6. Apply the TPMx upgrade to the production server.
    7. Verify the TPMx upgrade is applied to the production server and the server is working properly.
Test registration

Authorized Prometric test centers (worldwide testing)