There is no support for $msi macro expansion. Hence, you cannot use job container order files to create MSI administrative installations or network installations based on administrative installations (using the $msi macro). There is no support for added procedures. Only procedures created before the software package was sealed are possible to execute with job container order files.
There is no support for scheduling of containers or for renewing them. Only one Job Container Order File (COF) can be executed at any given time. If an order is placed during the execution of another order, a queuing of the second sd_acmd takes place.
The sd_acmd execution fails with an exit code indicating the error, if Job Check is currently running. On the other hand, Job Check cannot be run while sd_acmd is executing. The software delivery (SD) functionality handles this synchronization lockout internally.
There is no support for Prompt user functionality or for expanding $cl macros to scalability server time; these macros expand to local agent time. There is no support for NOS-less configuration or for NFS protocol connection to the SD manager.
In a Windows NT Technology environment, the COF Executor only supports execution in the System context. This implies the need to provide a user account and password when accessing a network share, which is not a NULL-session share (the account should be one with the necessary access rights to the share).
|
Copyright © 2013 CA.
All rights reserved.
|
|