Autodeploy

Supported Clients

This option is valid for AIX®, HP-UX, Linux, Mac, Solaris, and Windows clients.

Options File

You can set this option by including it in your client options file. You can also set in using the Java GUI by clicking Edit > Client Preferences and selecting the appropriate option on the General tab.

Syntax

               .-Yes------.   
>>-AUTODEPLOY--+----------+------------------------------------><
               +-No-------+   
               '-NOReboot-'   

Parameters

Yes

Specifies that the client is automatically deployed from the server. Yes is the default.

Important:

• When you set autodeploy to yes, if a restart of the client workstation is required to complete the deployment, you cannot disable the restart. The client workstation will be restarted. If it is important that the workstation is not automatically restarted, set autodeploy to noreboot. The deployment will be canceled if a restart is required. The current client is not affected.
• If a restart is required, the deployment manager initiates a restart for the client computer and exits. However, it is possible that you cancel or interrupt the restart. Since the deployment manager is already terminated, a message is not sent to the server to indicate the failure of the restart. The deployment result is still successful. You must restart the computer so that the new client deployment completes.

No

Specifies that the client is not automatically deployed from the server.

NOReboot

Specifies that the deployment manager never automatically restarts the client computer, even if a restart is required. If a restart is required, allowing automatic deployment to many machines with the NOReboot parameter can result in only a partial update of, potentially, many clients.

To alleviate this problem, the deployment manager tries to detect if a restart is required. If a restart is required, the deployment manager cancels the deployment before the new client installation. This guarantees that the client computer still has a working backup-archive client, and the new client deployment can be rescheduled.

There are rare cases where the deployment manager cannot detect the restart; for example, if client processes are started from a script. In these cases, the new client installation will continue, but a manual restart of the client computer is required.

Syntax

               .-Yes-.   
>>-AUTODEPLOY--+-----+-----------------------------------------><
               '-No--'   

Parameters

Yes

Specifies that the client is automatically deployed from the server. Yes is the default.

No

Specifies that the client is not automatically deployed from the server.