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
notfix the issue as it is likelytofix 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?
-
@gjacobse said in 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?
I know in enterprises, not too much effort is spent on troubleshooting workstations on the Lan. Generally users save everything to one drive or similar and it is much faster (10 mins) to reimage workstations.
Remote users require a bit more troubleshooting, because reimaging is not as fast over WAN or especially VPN. @Obsolesce might be able to speak a bit more on this.
-
@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
notfix the issue as it is likelytofix 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.
-
@obsolesce said in A Startdocprinter Call Was not Issued:
either spend days troubleshooting or days reimaging and setting up the device,
Days troubleshooting, yes.
Days reimagine and setting up, fuck no.Even the shittiest place I have ever been was not days to do something like a reimage (once approved).
Even if you do like I do and reinstall from ISO instead of imaging, it is still only a couple of hours.
-
I can have a device reimaged in about 20-30 minutes... barring dealing with the user documents. they
shouldbe ONEDRIVE, but doesn't always happen...As we all well know, the user (tries to) make a case of how important this is over everything else and that this should be the only thing to be worked on. I want to find a solution, but as with anything, have to set limits.
I've since found out that the agency doesn't even OWN this printer. And a 'personal printer' isn't policy. and yet - here it is... oFFS!
-
@gjacobse said in A Startdocprinter Call Was not Issued:
they should be ONEDRIVE, but doesn't always happen...
Hopefully you find this out before re-imaging the machine...
-
@dafyre said in A Startdocprinter Call Was not Issued:
@gjacobse said in A Startdocprinter Call Was not Issued:
they should be ONEDRIVE, but doesn't always happen...
Hopefully you find this out before re-imaging the machine...
Not an IT problem.
-
@jaredbusch said in A Startdocprinter Call Was not Issued:
@dafyre said in A Startdocprinter Call Was not Issued:
@gjacobse said in A Startdocprinter Call Was not Issued:
they should be ONEDRIVE, but doesn't always happen...
Hopefully you find this out before re-imaging the machine...
Not an IT problem.
Chair to keyboard interface problem
-
@irj said in A Startdocprinter Call Was not Issued:
@jaredbusch said in A Startdocprinter Call Was not Issued:
@dafyre said in A Startdocprinter Call Was not Issued:
@gjacobse said in A Startdocprinter Call Was not Issued:
they should be ONEDRIVE, but doesn't always happen...
Hopefully you find this out before re-imaging the machine...
Not an IT problem.
Chair to keyboard interface problem
PEBKAC - Problem Exists Between Keyboard And Chair
