[00:00] Agent tasks have the ability to send projects and project resources from a controller to an agent. So let's see how to send some projects to an agent. With my enterprise administration setup, I have two active gateways. On the screen here is my controller gateway named controller. Within it, I have two projects named project one and project two. The goal here is to send over these projects and or their resources to my agent gateway using a send project agent task. If I pull up my agent gateway here named agent, you'll see in the projects section that this gateway currently doesn't have any projects. So to give the agent some projects, I'll navigate back to my controller. Since we'll be utilizing an agent task, I'll scroll down to my config section here to enterprise administration. Then I will click on agent task.

[01:04] There are no tasks defined, so I'll need to create one by clicking on the create new gateway task link. Within this list of all the agent task, we will utilize the task, send project, and send project resources. The send project task distributes the entire project and the send project resources task distributes individual resources of a project like windows and templates. I'll select the send project task first. Then I'll click next for the task schedule. I'll leave it to execute the task immediately. Once this create task configuration wizard is complete, I'll continue by clicking next. On this screen, we'll select where the project is going. You can select either the individual gateways or groups you'd like to send the project to. I'll go ahead and check off my agent. Additionally, on this screen, we could choose to select the controller as a target. I'll click on next again to continue.

[02:02] Now we have a selection to choose a source gateway from where the project is coming from. Since I am pulling them from the controller, which is hosted locally, I'll choose this local system option. I'll click on Next. Now we can choose which controller project to send over. If you don't see your desired project, you can pass in its name using this other option. I'll go ahead and select project two. We also have an option to send over inherited project resources. I'll leave this unchecked for now. Continuing on, I'll click next again. Now we have a task setting relevant to the send project task. Max concurrent agents allows you to set a number greater than zero to limit the number of agents that will be concurrently contacted, while the task runs. So if you have an enterprise administration set up with many agents, this would be a good resource to help better maintain system performance when sending many projects. I'll leave this as zero, providing no limit as it doesn't matter as much when I only have one agent configured.

[03:09] I'll click on next one more time here. On the final configuration screen, we have this task summary showing us all the task configurations we made. If you needed to go back and change anything, you could tab backwards through the prompts using this previous button. I think everything looks good here, so I'll click on finish. If you have a sharp eye, you'll notice my task will run fairly quick here as it was scheduled to execute immediately. Let's check on the agent gateway to make sure the project came over. I'll pull it up here and if I refresh, we can clearly see project two is here now, so we know the send project task executed. Let's take a look at sending over project resources. Now I'll minimize my agent here to go back to the controller again. I'll create a new task with the create new gateway task link. On the task selection I'm picking send project resources and I'll click Next.

[04:05] I'll keep the task execution as immediate and click. Next, I'll select my only agent available to send to and continue to the next prompt. On this page, I'm choosing the local system to set my controller as the source gateway and clicking next. We see our available source project selection options again. This time I'll choose project one and click next. Now is where we see something different. With this select resources screen, you can see all of the resources inside of project one. I can use this all button on my vision resources to select all of them. The none button will clear out all my selections for that section. Finally, I can select individual resources by checking them off. I'll grab a couple of windows and this transaction group. With all of the desired resources selected, I'll click on next. This select Target project allows you to send the resources to an existing project on my target agent.

[05:05] Project two is an option because we just sent that project over to our target agent with the send project task. Again, we have the other option here to pass in the name of a project. Something cool about this field is if a project doesn't exist with the name, a new one will be created. I'll select other to show that off and I'll give it the name project three. I'll click on next. Again, max concurrent request is also available for us to configure on the send project resources task. I'll leave this as zero providing no limit, and click on next one more time. And I'll click on finish to execute the task. Now that the task has been executed, let's go confirm project three was created on my agent. I'll pull up my agent gateway here and on the project page we see Project three now exist on the agent. So with enterprise administration, we can easily send projects and or their resources to many connected agents.

[06:03] This provides a fantastic opportunity to manage and distribute projects from one source.