G
Guest
First off, I want to acknowledge the WG keepers. I appreciate the work
they've/you've done to make the XPe process more-accessible for integrators.
Next, I am relatively sure that the following issue is a slam-dunk, but I've
been unable to locate the answer:
I plan to deploy several hundred POS-type devices running a citrix client.
Each ships with the same printer model (HP1020) and will be configured with
the respective driver set. The problem comes when another HP1020 (read: one
physically different from the original one used to configure the runtime
post-fba) is connected to the XPe system.
Of course, the system installs the "new" printer and it doesn't become the
default queue.
I wish for each system to auto-configure its respective printer and have it
become the default queue without user intervention, if possible. I anticipate
that the fix will be something akin to the following:
The systems will ship without a printer / print queue pre-configured. I'll
set the build to auto-configure the HP printers without user intervention, so
each system's respective printer will install itself on boot and, being the
only printer available, become the default printer. I suspect that this
should be accompanied by a login script that uninstalls any existing printers
and then initiates the search for plug-and-play printers, or something alike
(so the queue will be new each time, in case the RAM Reg EWF gets updated
with the printer configured and another printer is added to the system
later).
Yes, RAM Reg EWF is also enabled on these systems. Any advice would be most
appreciated. Thankyou in advance.
they've/you've done to make the XPe process more-accessible for integrators.
Next, I am relatively sure that the following issue is a slam-dunk, but I've
been unable to locate the answer:
I plan to deploy several hundred POS-type devices running a citrix client.
Each ships with the same printer model (HP1020) and will be configured with
the respective driver set. The problem comes when another HP1020 (read: one
physically different from the original one used to configure the runtime
post-fba) is connected to the XPe system.
Of course, the system installs the "new" printer and it doesn't become the
default queue.
I wish for each system to auto-configure its respective printer and have it
become the default queue without user intervention, if possible. I anticipate
that the fix will be something akin to the following:
The systems will ship without a printer / print queue pre-configured. I'll
set the build to auto-configure the HP printers without user intervention, so
each system's respective printer will install itself on boot and, being the
only printer available, become the default printer. I suspect that this
should be accompanied by a login script that uninstalls any existing printers
and then initiates the search for plug-and-play printers, or something alike
(so the queue will be new each time, in case the RAM Reg EWF gets updated
with the printer configured and another printer is added to the system
later).
Yes, RAM Reg EWF is also enabled on these systems. Any advice would be most
appreciated. Thankyou in advance.