IT & Services / capability
Deployment, Migration and Technology Refresh
The refresh that gets complaints is rarely the slow one. It is the one where the default printer changed. Ten users piloted with the real rollout script.
The refresh is not the hard part. The user's data, their printers and their saved passwords are.
Swapping the hardware is a scheduled event. What generates the complaints is everything that was configured over four years and never written down: the mapped drive, the local file nobody backed up, the certificate on the old machine. A refresh is judged on those, more than on the specification of the new device.
Where SECCOM stops. Application compatibility is signed off by the application owner. SECCOM runs the pilot and produces the evidence. The owner accepts it.
Next step