fify"Lurkor" here! Kinda' Sorta' Heh!
A valid approach for Windows computers and 90% of printer problems.I have always followed a rule: Any issue, any update always get a 2-reboot sequence. I was able to reducer staffing on help desks in most cases over 50% when that is given as the first command on and intake call.
The first computer that sat on my desk that was not a terminal from mainframe or DEC was a Sun Workstation in early '85 when I got promoted to Project Mgr for Software Dev. My first Wondoze machine was in 1996 which was in terms of use like trying to unlearn how to ride a bicycle, what a convoluted, crude, archaic OS...A valid approach for Windows computers and 90% of printer problems.
Personally, I got so spoiled when my Officers first got computers and everything, from the laptops to the servers, was 100% Unix. That was about the time I moved from field Officer work to back-end support because I was a mediocre field officer and I thought computers were the future.
The full staff of server sysadmins, desktop/deskside support, and continuing training for a staff of 300 old-line, often computer-phobic field Officers was 2 people. We used to joke that we only had enough work for 1.5 people so there was never any problem for anyone taking vacation time; we could always cover for each other. We literally left the server room and went walkabout once a week, stopping into every group, asking every manager if they had any computer problems, anything we could make work better, any issues they'd like for us to explain in a presentation at their next group meeting.
My heart was filled with pity for the Windows-using side of the house.
Those were the days...Zilog terminals, a dual 8-inch floppy computer on my desk, (later) the copy of 2600 that was always in my drawer...you're bringing back memories.