Changing object attributes in a BLPackage
A common task when editing a BLPackage is to change the attributes of an object in the package.
To change object attributes in a BLPackage
- In the hierarchy view, select the object that you want to modify.
On the right you see the attributes associated with that object.
- For Action, use the drop-down menu in the Value column to select an action.
For most assets, you can select an action of Add, Delete, or Modify.
If the selected asset is a custom configuration object, it may give you an option to select other custom actions. If you select a custom action, a message warns you that the package will be converted to use the custom action for the selected asset. If you agree to proceed, the package cannot be converted back so it uses the standard Add, Delete, or Modify actions. In addition, if you select a custom action, asset attributes that are not applicable to the custom action are no longer displayed.
- Click in the Value column and enter new values for the attributes of the selected object.
If you are using parameters in a path, enter them here or click Select Property . For more information about tool, see Inserting a parameter.
When changing attributes of objects in BLPackages, be aware of the following:
- Some attributes provide a drop-down list from which you can choose a value.
- Attributes listed in italics are not editable.
- When specifying a parameter, ensure that the defined value for the property that you reference does not contain special characters. Inclusion of special characters in a property can cause the Deploy Job to fail due to the failure of an external command.
- Actions for some custom configuration objects may require parameters that only apply to a target server that satisfies a particular condition. The required condition is enclosed in a parenthesis.
- The values of attributes that require long text strings can be scrolled horizontally, and text fields can be resized vertically to improve readability.
- When editing a password field for a Windows object, the Password Required dialog box opens. Use it to change the password, as described in Providing password information in a BLPackage.
For most asset types, if you select Add in the Action field when the asset already exists at the target, the existing asset is modified according to the asset in the BLPackage.
- When editing a Windows local user, be aware that the Action field has the following effects:
- Add — Adds a new local user account. An existing user account is not modified.
- Modify — Alters an existing local user account.
- Delete — Deletes an existing local user account.
Also, when editing a local user, the various Update fields (for example, UpdatePath or UpdateLoginScript) are only available when modifying a BLPackage (that is, the Action field must be set to Modify).
- The Permissions property of UNIX files lets you click Browse to display a dialog box where you can edit the file's permissions.
For additional information about changing attributes of objects in a BLPackage, see the following:
- Working with soft-linked objects
- Setting single-user mode for an object
- Setting a reboot for an object
- Setting action on failure
- Changing network-based software deploy options
- Changing file ownership attributes
- Windows multi-value registry entries in BLPackages
- Windows security settings in BLPackages
- Manipulating Windows user account properties through a BLPackage
For a discussion of the rules that apply when entering paths to server objects, see Rules for entering paths.