Abstract: An intake interface receives a package with files of content from a submitter and places a job with the package in a jobs database. An automated dispatcher retrieves the job, identifies each file of the content of the package of the job, and groups the identified files into one or more tasks. Each task has a particular type and represents a particular propagation event that can be submitted to one or more particular tools. The automated dispatcher, for each task, calls to a propagation system with the files of the task and the particular type of the task. The propagation system calls to one or more particular tools thereof to in fact perform one or more respective propagating events based on the files and type of such task to propagate the content of the job to the network.

Abstract: Automated system setup includes automated configuration of an operating system on a computing device(s), automated configuration of custom software on a computing device(s), and/or automated configuration of a network switch(es). The various information used for the automated configuration(s) can also optionally be maintained for asset tracking purposes.

Abstract: Content access management allows a content request to be received from a device. In response to the content request, both an identifier of a source of the content and one or more keys that allow the device to decrypt the content are sent to the device. The device is then able to retrieve, as it desires, the content from the source and decrypt and use the content.

Abstract: Automated system setup includes automated configuration of an operating system on a computing device(s), automated configuration of custom software on a computing device(s), and/or automated configuration of a network switch(es). The various information used for the automated configuration(s) can also optionally be maintained for asset tracking purposes.