Provisioning Engine


The Art of Provisioning


Provisioning a PC is a task necessary to define how a PC will be deployed.

Good provisioning ensures that the device is set up properly, has all the correct configurations and desired applications, is ready for the employee to do their job, and allows for the device to be managed well by IT.

If a PC is provisioned poorly, the device may not have all the configurations and applications needed, could have security issues, and could be useable by the employee without additional IT support post deployment.  This scenario adds enormous costs to the deployment for both the employee (downtime) as well as IT (additional touches to the device).

The Swimage Provisioning Engine has three primary objectives:

  1. Ensure that the PC has all components it needs when complete
  2. Provide flexibilty to handle any provisioning scenario
  3. Simplify the provisioning process

Future State

Every managed PC is assigned a “Future State” by Swimage before a deployment can happen. The Future State defines exactly how the PC will be deployed. A valid Future State will have the minimal components necessary to complete a full deployment without any issues.

Components assigned to any given Future State can come from a number of sources. Multiple sources assigned to the same Future State will automatically be prioritized and added to give you the desired results.

Future State sources can be any combination of the following:

  1. Roles
  2. Templates
  3. Static Assignment
  4. Dynamic Assignment

 

Dynamic PC Configuration with Layering Templates

One Role is required for every Future State. A Role has all the base components needed to do a successful deployment at a minimal level.

Templates are optional and can be stacked to further define a PCs configuration. Templates are designed as layers to the Future State. Based on the scope of the template, some template settings can be set to override others. This is very similar to the way AD group policies work. Global defaults can be configured; but as more individualized templates are added, they can override the defaults, further specializing the build. There is no limit to the number of templates a single future state can have assigned.

As an example, you can have multiple templates assigned to a single Future State, such as a “Germany” template, a “Finance” template, and a “Remote Worker” template. The combined templates will ensure the PC is assigned the right language with all finance applications, and the proper security and VPN required for a remote worker. Any combination of roles and templates will allow for flexible configuration, while making assignments very easy to maintain.

Static assignments can be used as one-offs when a template does not quite address the requirements for a specific employee. For example, maybe an employee also needs “Project” installed out-of-band. A static assignment in the Future State will ensure this application is installed.

Dynamic assignments are based on pre-defined rules that are assigned at the time of deployment. This may include things such as PC naming conventions, OU assignments, and application installations. Dynamic assignments can be overruled with a static override whenever needed. The exception is that hardware driver assignment is always based on the targeted hardware model and device IDs, which makes hardware driver injection completely automated.

Deployment Provisioning Components

Swimage allows for all of the components that make up all PC configurations to be managed through a single, easy to use portal.

These deployment components include items such as:

  1. Operating Systems
  2. Custom Images
  3. PC Naming Rules
  4. Data Migration Rules
  5. Application Matching Rules
  6. Disk Formatting Rules
  7. Custom Scripts
  8. Registry Punches
  9. OEM Settings
  10. Security Policies
  11. Domains
  12. Organizational Units
  13. Device Hardware Drivers
  14. Patches
  15. Windows Features
  16. Applications