on the client machine with the problem, open control panel and go to
admin tools - print management and expand print servers where you should
see the local machine
remove the drive for the problem printer from the local machine, then
remove the connection to the printer and readd it
i’ve had similar issues with printers not working on machine even with
iprint until I remove the driver from the local print server driver
store and reconnect to it
What type of licensing does that require? We are only going to have
Groupwise licensing eventually… :-([/color]
It requires iPrint licensing. You definitely don’t need to license OES
to use this. And if you don’t need mobile printing right now, which
the appliance offers, you can license just desktop printing in the
appliance.
Joseph Marton sounds like they ‘said’:
[color=blue]
It requires iPrint licensing. You definitely don’t need to license
OES to use this. And if you don’t need mobile printing right now,
which the appliance offers, you can license just desktop printing in
the appliance.[/color]
So my response to Joseph’s comment is…
Not sure I can talk my boss into adding licensing cost, that was the
big reason he wanted to move to ad, since we were told we needed m$
cals anyway for one application.
Both are windows 7 64 bit machines, only difference is the one that[color=blue]
works is physical, the ones that don’t are virtual.[/color]
That’s a pretty big difference actually and sounds like policy is
being enforced differently or ignored. Does the policy do checking
based on hardware?
That’s a pretty big difference actually and sounds like policy is
being enforced differently or ignored. Does the policy do checking
based on hardware?[/color]
So my response to GofBorg’s comment is…
Policy is set to deploy printers on the computer portion, no hardware
checking.