Unblocking an application migration through its launch workflow.

01 / THE CHALLENGE

Understanding the problem.

A legacy application had not yet migrated because a product bug made it incompatible with the proposed solution. A fix was available in an Office release channel, but the application also depended on data being present in the user's profile. Those requirements had to come together within the Citrix launch experience.

1. 01Compatibility blocker
2. 02Profile data + corrected Office release
3. 03Seamless application launch

02 / MY INVESTIGATION

Following the evidence.

I approached the blocker through the launch workflow. A wrapper could coordinate the supporting scripts and prepare the user's environment for the application.

The Office version was part of the compatibility problem. I used a user registry setting to select a release channel containing the Office bug fix, as part of moving the user to the required version.

The application also needed its data deployed to the user's profile. I brought that preparation into the same coordinated workflow so it could support seamless execution inside the Citrix session.

03 / IMPLEMENTATION

Putting the work into practice.

1. 01

   Developed a launch wrapper that interacted with supporting scripts to prepare the application environment.

2. 02

   Coordinated deployment of the required application data into the user's profile.

3. 03

   Set the user registry configuration to move Office onto a release channel containing the required fix, supporting the Office-version change needed for compatibility.

4. 04

   Integrated the preparation and launch workflow so the legacy application could execute as a seamless Citrix application.

04 / OUTCOME & EVIDENCE

What the work delivered.

The wrapper coordinated the workaround. The Office bug fix came from the corrected release; changing the registry setting selected the channel rather than repairing the Office code itself.