…heavy work deserves a better moment
There’s a small rule in workspace management that can save a surprising amount of frustration:
Not every possible moment is a good moment to install software.
Technically, you can make a computer do all sorts of things while someone is working.
- Download a few gigabytes.
- Start an installer.
- Copy a mountain of files.
- Reconfigure half the machine.
The computer may even cooperate.
The user, however, may have opinions.
A refresh should feel like a refresh
In worXpace, the Workspace Refresh event has a very specific job. It keeps the user’s workspace current.
Think shortcuts. Network drives. Network printers. The useful little things that make sure someone sees the right resources and can get on with their day. That is exactly the sort of work a refresh should do: quick, predictable and almost invisible.
There is an important reason for keeping it that way. A Workspace Refresh does not only happen when somebody deliberately asks for one. It can also be triggered during an active session when worXpace receives updated data.
So imagine a user halfway through a meeting, editing a document or enthusiastically explaining why their spreadsheet is definitely the correct spreadsheet.
Then a refresh arrives…
If all it needs to do is update a shortcut or reconnect a resource, nobody notices.
Perfect.
If that same refresh decides it would now be an excellent time to install a very large application… well, the word refresh starts to feel a little optimistic.
Heavy work needs a predictable home
Large application installations are different from workspace housekeeping.
They can take time. They may need substantial downloads. They can consume CPU, disk and network resources. One installation may depend on another. And if something goes wrong, you want to know exactly where you are in the process.
That makes Computer Startup a much better fit.
worXpace supports provisioning and pre-installing applications during the Computer Startup event. This lets the work happen independently of the user and, ideally, before that user ever reaches the desktop.
That has a few lovely side effects.
The user is not competing with an installer. The deployment process is more predictable. Applications can be handled in a deliberate order. And IT gets a much cleaner place to deal with errors or changing conditions.
For especially large applications that belong on practically every machine, including them in the standard device build can also be worth considering. The exact deployment choice will depend on how your environment is managed, but the principle stays the same:
Do the heavy lifting before the user needs the computer whenever you can.
“But it works…”
Ah, some of the most dangerous words in IT.
Yes, something can work and still be in the wrong place.
Putting an application installation into Workspace Refresh may appear convenient. There is already an event. It already runs. Why create another flow?
Because timing is part of good workspace design.
Workspace Refresh can occur while the user is active. That makes large downloads, application installations, program launches and other heavy operations poor guests. They introduce work at a moment when worXpace is really trying to keep the workspace synchronized and consistent.
The effect can become even more noticeable in server-based computing environments, where one badly timed piece of heavy work may not inconvenience just one person.
A useful test is simple:
- Would I be happy if this action ran unexpectedly while the user was working?
If the answer is “please no,” Workspace Refresh is probably not its natural home.
Give every event one clear job
Good worXpace design becomes much easier when events have clear responsibilities.
- Workspace Refresh keeps the workspace tidy and current.
- Computer Startup handles machine-level work that benefits from running independent of user activity.
- Application Install handles the actual installation logic for an application.
Once you start thinking this way, configuration becomes easier to reason about. Troubleshooting gets simpler too. When something happens at the wrong time, you know where to look.
There is less magic.
And in IT, less magic is often rather magical.
A little extra care at startup pays off
When applications are pre-installed during computer startup, worXpace can check whether an application is already installed before calling its installation context. That prevents pointless repeat installations.
It is also useful to keep ‘Wait for completion’ enabled when installation order matters. That gives worXpace a chance to finish one step, inspect the situation and then continue.
The alternative may look faster because several requests can be handed off quickly, but it also makes the final installation order less predictable.
Fast is nice.
Predictably correct is nicer.
The best workspace maintenance is boring
Users should not have to understand your deployment architecture.
They should not need to know which event ran, which package was downloaded or which clever bit of automation just connected their printer.
They should open their workspace and find that everything they need is simply there.
That is the real goal.
So keep Workspace Refresh light. Let it maintain the things users expect to change smoothly during a session. Move large installs and other heavyweight work to a moment designed for them, such as computer provisioning or startup.
Your users probably won’t thank you.
They won’t notice.
And that may be the nicest compliment an IT system can get.