Don't know about that - they came with a set of Zebra-specific drivers
(and I believe a barcode font, too), so can't say for sure without
digging more.

Kurt

On Thu, Aug 1, 2013 at 8:22 AM, Ziots, Edward <ezi...@lifespan.org> wrote:
> I believe the Zebra Printers use the plain text driver, which shouldn’t be 
> really taxing....
>
> Z
>
> Edward E. Ziots, CISSP, CISA, Security +, Network +
> Security Engineer
> Lifespan Organization
> ezi...@lifespan.org
> Work:401-255-2497
>
>
> This electronic message and any attachments may be privileged and 
> confidential and protected from disclosure. If you are reading this message, 
> but are not the intended recipient, nor an employee or agent responsible for 
> delivering this message to the intended recipient, you are hereby notified 
> that you are strictly prohibited from copying, printing, forwarding or 
> otherwise disseminating this communication. If you have received this 
> communication in error, please immediately notify the sender by replying to 
> the message. Then, delete the message from your computer. Thank you.
>
>
>
> -----Original Message-----
> From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] 
> On Behalf Of Kurt Buff
> Sent: Thursday, August 01, 2013 10:25 AM
> To: ntsysadm@lists.myitforum.com
> Subject: Re: [NTSysADM] Odd spooler issue
>
> And the HP driver(s) would also affect some, but not all, of our Zebra 
> printers?
>
> Kurt
>
> On Thu, Aug 1, 2013 at 1:26 AM, Ziots, Edward <ezi...@lifespan.org> wrote:
>> I would look for Bad HP drivers with the HPBPRO.exe and HPBOID.exe
>> running on the print server I have found in past travels that these
>> have been the root cause of some of our print server issues. Removing
>> the drivers with these additional HP software on them has addressed
>> the issue. But I also agree that using ADplus as recommended will get
>> you down to a driver issue and from there can work out which printers
>> are using that driver and maybe upgrade that driver or switch over to
>> universal print driver which works well enough for most cases but not
>> all :)
>>
>> Z
>>
>> Edward E. Ziots, CISSP, CISA, Security +, Network + Security Engineer
>> Lifespan Organization ezi...@lifespan.org
>> Work:401-255-2497
>>
>>
>> This electronic message and any attachments may be privileged and 
>> confidential and protected from disclosure. If you are reading this message, 
>> but are not the intended recipient, nor an employee or agent responsible for 
>> delivering this message to the intended recipient, you are hereby notified 
>> that you are strictly prohibited from copying, printing, forwarding or 
>> otherwise disseminating this communication. If you have received this 
>> communication in error, please immediately notify the sender by replying to 
>> the message. Then, delete the message from your computer. Thank you.
>>
>>
>>
>>
>> -----Original Message-----
>> From: listsad...@lists.myitforum.com
>> [mailto:listsad...@lists.myitforum.com] On Behalf Of Kurt Buff
>> Sent: Wednesday, July 31, 2013 8:18 PM
>> To: ntsysadm@lists.myitforum.com
>> Subject: Re: [NTSysADM] Odd spooler issue
>>
>> Per our offline conversation, this has been initiated.
>>
>> Many thanks for your help on this.
>>
>> Kurt
>>
>> On Fri, Jul 19, 2013 at 4:49 PM, Brian Desmond <br...@briandesmond.com> 
>> wrote:
>>> Get a full hang dump with adplus, zip it, and ping me.
>>>
>>> You can find adplus in the debugging tools for Windows installer which is 
>>> found in the WDK download.
>>>
>>> Thanks,
>>> Brian Desmond
>>> br...@briandesmond.com
>>>
>>> w – 312.625.1438 | c – 312.731.3132
>>>
>>> -----Original Message-----
>>> From: listsad...@lists.myitforum.com
>>> [mailto:listsad...@lists.myitforum.com] On Behalf Of Kurt Buff
>>> Sent: Friday, July 19, 2013 5:42 PM
>>> To: ntsysadm@lists.myitforum.com
>>> Subject: Re: [NTSysADM] Odd spooler issue
>>>
>>> I might well take you up on that offer next week.
>>>
>>> Currently am unable to reproduce, as the folks complaining about it are out 
>>> of the office.
>>>
>>> Plus, I spent a fascinating bit of time last night troubleshooting a 
>>> problem with our VNXe, which deserves an email all it's own.
>>>
>>> I'm going to set a reminder for this problem for next week, and see what I 
>>> can dig up.
>>>
>>> Kurt
>>>
>>> On Thu, Jul 18, 2013 at 3:23 PM, Brian Desmond <br...@briandesmond.com> 
>>> wrote:
>>>> So troubleshooting this without a dump of the spooler when the issue is 
>>>> occurring is going to be hard, IMO. I'm willing to look at the dump, but 
>>>> full disclosure it's been like five years so I can't promise I'll produce 
>>>> anything for you.
>>>>
>>>>
>>>>
>>>> Thanks,
>>>> Brian Desmond
>>>> br...@briandesmond.com
>>>>
>>>> w – 312.625.1438 | c – 312.731.3132
>>>>
>>>>> -----Original Message-----
>>>>> From: listsad...@lists.myitforum.com
>>>>> [mailto:listsad...@lists.myitforum.com]
>>>>> On Behalf Of Kurt Buff
>>>>> Sent: Wednesday, July 17, 2013 6:15 PM
>>>>> To: NTSysADM@lists.myitforum.com
>>>>> Subject: [NTSysADM] Odd spooler issue
>>>>>
>>>>> All,
>>>>>
>>>>> I've got a little head scratcher, and would appreciate any insight
>>>>> folks might have.
>>>>>
>>>>> Printer Server: Win2k8 R2, fully patched VM running on vSphere 5
>>>>> (recently gone from 5.0 to 5.1, the problem began on the earlier
>>>>> version.)
>>>>>
>>>>> Problem: Print jobs from our installation of Epicor Avante to
>>>>> various printers (an HP 2055 and several models of Zebra printer)
>>>>> hosted on the printer server, will intermittently hang in the print queue.
>>>>> Delay will range anywhere from 1.5 - 2 minutes, and they they'll
>>>>> print. I can see the jobs in queue, just sitting there (they have a
>>>>> status of 'printing', but do nothing.)
>>>>>
>>>>> I am seeing nothing in the event viewer for the printer server that
>>>>> looks relevant, and certainly no warnings or errors. Neither memory
>>>>> nor CPU spike
>>>>>
>>>>> The Avante server is running Win2k3 R2.
>>>>>
>>>>> The problem disappears and reappears a couple of times a week.
>>>>>
>>>>> Thoughts?
>>>>>
>>>>> Kurt
>>>>>
>>>>>
>>>>
>>>
>>>
>>>
>>
>>
>>
>
>
>


Reply via email to