@gjacobse said in A Startdocprinter Call Was not Issued:
This is a recent issue I have had to work on. And while I do see there are some options to correct it, it seems that they are also as likely to not
fix the issue as it is likely to
fix it.
Google Search: A Startdocprinter Call was not issued.
Is this something that it's likely as easy to re-install Windows as it is to spend a few hours trying to correct?
First link looks like 5 minutes of things to try so why not?
But as @IRJ said, a lot of time isn't spent on troubleshooting unless it's absolutely necessary. I can't speak for the service desk because they are a different department than I've been, but it doesn't seem like they do.
We use modern device management technologies and practices so never have to worry about re-imaging in most cases, at least the last two places I've been at which are larger enterprises.
But if you're not using modern device management practices and your only option is to either spend days troubleshooting or days reimaging and setting up the device, then I dunno. Only you can answer that because I'm sure it depends on your unique situation/environment and the user.