If automation is important to your infrastructure — in particular, speeding up your Citrix ADC deployments — Citrix Application Delivery Management (ADM) can play an important role in eliminating repetitive provisioning tasks. I work with customers who are implementing pooled capacity licensing within their Citrix ADC hybrid infrastructure, which is made up of physical and virtual appliances. Recently provisioned Citrix ADCs require individual instance actions to configure the appliance’s licensing to “remote licensing,” while also setting the throughput allocations. This can be a laborious task if you’re faced with multiple Citrix ADC appliances to configure before you can provision with broader configuration aspects

Configurations jobs can be created in Citrix ADM to automate the configuration of selected individual (or groups of) Citrix ADC instances

In this blog post, I’ll cover an example of how I have used Citrix ADM configuration jobs to achieve this for a pooled capacity environment. I used configuration jobs to push out license server configuration and throughput allocation. I also included virtual server configuration as an example of generic configuration I wanted pushed out to instances; you may wish to create separate “jobs” for separate config.

Lets see how it works!

Within my newly provisioned Azure-based Citrix ADC, I need to manually apply the remote licensing via GUI or CLI.

Doing this individually, for multiple instances, takes time and can be prone to error. This is where we can leverage Citrix ADM configuration jobs.

Within Citrix ADM, access the “Configuration Jobs” function and “Create Job.”

Create a new job and add your configuration. A sample configuration is shown below. Click the image to view larger.

The pooled capacity configuration I used was the following below. (Note, as I use ADM service, I added the relevant ADM Agent IP as the IP address)

#ADM AGENT LICENSE SERVER & BANDWIDTH ALLOCATION

add ns licenseserver <ADM_Agent_IP> -port 27000

set capacity -bandwidth 1 unit Gbps -edition enterprise

reboot -w -f

Please note, all Citrix ADCs require a reboot command with license changes.

Then select the targeted instances. In my example, I have one instance available in Citrix ADM.

Complete the steps shown above, and you’re done. It’s a simple as that!

Learn more about Citrix ADC and how configuration jobs can help you.