The Agent Rollout wizard 11 - Scheduling the rollout

Now that the rollout and the members were defined, it must be scheduled to execute at a specific time. By default it is scheduled to execute once and immediately. If this is your choice you do not need to make any modifications in this window. To schedule the rollout for a specific moment proceed as follows:

1. On the Schedule window, click Advanced to select the connection mode for rollout targets that are Windows devices.
   1. Select the rollout mode. 
      1. Universal Connection Mode: The default rollout mode. BMC recommends using this mode to rollout agents as it does not require domain credentials to authenticate the agent on the rollout server.
      2. Domain Oriented Connection Mode: As the BCM agent runs as a LocalSystem, it cannot access remote or windows remote services. To access BCM agent binaries on the rollout server, BCM needs local credentials. Similarly, to connect to the target device, BCM needs remote credentials. During the rollout of the agent in this mode, BCM ensures that limitations of the agent running as a LocalSystem are overcome by impersonation of credentials on the rollout server and the target device. When the rollout is complete, BCM reverts back the agent to run only as LocalSystem.
      3. Workgroup Oriented Connection Mode:  In this connection mode, the rollout program of BCM can connect to remote devices but needs to impersonate a local account (NMAPUser) to connect to the rollout server. The rollout program impersonates from LocalSystem to a NMAPUser to extract and roll out the agent on the server. When the rollout is complete, BCM reverts back the agent to run only as LocalSystem.
   2. Check the Available on Rollout Server box, if the rollout is to be made available on the Rollout server (that is, if you have target devices that cannot be reached directly by the rollout).
   3. Check the Allow 32 bit Agent Installations on 64 bit Architecture box if a 32 bit agent is allowed to be installed on a 64 bit Windows system.
2. In the Assignment Date box select at what moment the assignment to the target devices is to be launched. The assignment in this case means that the link between the rollout and the target is established and the rollout package will be sent.
3. Select the Validity tab.
4. Define in the Execution Date box at what moment the rollout is to be launched for the first time.
5. Define in the Termination box defines when the rollout is to be run for the last time.
6. Select the Frequency tab. Here you can define the exact day, time or frequency at which the rollout is to be launched on the target. To run the rollout more than once only makes sense, if you expect that some rollout execution tentatives might not succeed at the first try due to specific reasons.
7. If you have specified to create a task , click Next to continue or click Finish to confirm all settings, create the rollout as defined and launch its execution.