Package printer client for use in the card office

Package the printer client for use in the card office - this should allow as little interaction with the print team as possible.

The printer client currently requires specific dependencies, including a specific build version of Java (boo), which adds pain to this process.

Ideally the print team have a solution where they flip a switch and any cards which are pending for printing immediately are printed - with no interaction directly with the printer client.

added to epic uis/devops/iam&34 (closed)

changed milestone to %DevOps Sprint 142

assigned to @av603

added priority1 High teamIdentity workflowNeeds Refinement labels

changed the description

added University Card + 1 deleted label

mentioned in issue #9 (closed)

Discussed at planning:

We need to investigate:

• How to package the requirements into a docker container and get this talking to the printer?
• What access do we need to the Dell micro PC - can we get this re-imaged with a basic windows 10 image?

As a first-pass we shouldn't worry about distributing this across the University, but just getting the PC updated

A bit of clarifying for this:

• The Dell Micro PCs need to be managed by the Desktop Services team. They will image them and keep the OS patched and up to date and be responsible for its maintenance. We are not going to maintain the PCs as we are not in that "business".
• Based on the previous point, the same team prepare the packages (I think is based on Intune now), so they will ask us what they need from us for the packaging and distribution. But what they need from us is definitely not going to be a docker container.

changed time estimate to 2d

added spike workflowSprint Ready labels and removed workflowNeeds Refinement label

set weight to 2

Discussed at planning:

• MVP, we deploy on the existing PCs with a 'run me' script to kick off the printer client, with instructions given to the printing team about making sure that this works as expected,
• Follow-up work on deploying to the micro-PC can be split off to a separate ticket,

Notes from a brief call with Mark Neal (arranged by Katya):

• Desktops team are happy to manage the physical box (Micro-PC or desktop) via Blue/Azure with the app deployed using Microsoft Intune
• We can re-use the existing Micro-PCs (re imaged by desktops team). Any additional Micro-PCs would need an accompanying purchase order and expect a lengthy lead time.
• The specific Java build requirement will likely be flagged by Snow (may need to follow up with security team).
• Microsoft Intune expects compiled binaries, so need to work out how/if this can work with our app...

Sounds good.

Any additional Micro-PCs would need an accompanying purchase order and expect a lengthy lead time.

We have plenty in stock for Lecture Capture that we are replacing by new managed appliances, so I don't expect to have to purchase any.

mentioned in issue #12 (closed)

marked this issue as related to #12 (closed)

mentioned in merge request !11 (merged)

Closed by MR: !11 (merged) allowing client to be installed locally and triggered from a .bat file. This approach - where the application is installed locally and settings passed in as environmental variables - lays the groundwork for remote management via Microsoft Intune.

Emergent work to deploy the printer client via Microsoft Intune captured under #12 (closed)

added workflowReview Required label and removed workflowSprint Ready label

added workflowRework label and removed workflowReview Required label

mentioned in commit b8eca6b8

closed with merge request !11 (merged)