Transactions

For a conceptual discussion of groups, machines, and the machine set, see the following topics:

The following tasks contain information on performing common transaction operations:


Creating a Transaction

When you create a transaction, it is applied to the current machine set. You can also assign the transaction to machines or groups after it is created.

  1. On the Transactions list, click the Create New Transactions link.

  2. Specify a name for this transaction.

  3. Choose a start time and date for the transaction. The default value is the current time and date. The time you enter is interpreted as being in the same time zone the server is set to; it is then translated into UTC and stored that way. See Server Date Handling for details on the way that the server handles time.

  4. Some transactions may require the removal of software. If you are sure that you want to allow the transaction to remove software, click the Remove conflicting packages checkbox.

  5. Select the type of transaction you want to create:

    Transaction Type Description

    Once Only

    A basic transaction which happens once at the time you specify.

    Rollback

    Rollback transactions occur only once. When you select a rollback transaction, you also select the date to which you will revert all the software on the client machines.

    Recurring

    To have a transaction repeat, select this option and choose a repeat frequency.

    Pre-Position

    To have software downloaded in advance, choose this option and select a time and date for the downloads to begin. Pre-positioning allows you to time installations more exactly, without worrying about network traffic. The software will be downloaded at the time and date you specify as the pre-position time, and then installed at the transaction start time. Be sure to select a pre-position time that is before the start time.

    Dry Run

    Select this option to test the transaction without performing it. If you choose Server Side Dry Run, the server will simulate the transaction without involving the client. Client side dry runs download packages and resolve dependencies, but do not install or remove anything.

    In order for a server-side dry run to succeed, all packages included in your transaction must be in channels that are visible to the clients included in this transaction. If you encounter problems when performing a server-side dry run, make sure you have granted your target clients access to the necessary channels.

  6. Click Next. If you selected Rollback for your transaction type, you are finished. If you selected other transaction types, continue on to select software for the transaction.

  7. Select one or more channels for your transaction. You do not need to choose a channel if you prefer to work with individual packages.

    Update means that software is only be installed if an older version is already present on the client machine. Install means that the software is installed even if it is new to the machine.

    Neither updates nor installs occur if a newer version is already installed, or if the transaction would break a package set. This is not considered an error and will not trigger a failure report.

    When you are done selecting channels, click Next.

  8. Select one or more packages for your transaction. You do not need to choose a package if you prefer to work with whole channels instead.

    When you are done selecting packages, click Next.

  9. If necessary, select or upload pre-transaction and post-transaction scripts. Click Next.

  10. Select additional machines or groups for the transaction. The machines in the machine set are already be selected for you. When you are done, click Next.