David_PCN

Print Credits for students can be updated automatically or manually based on a per user, group or OU basis. Most solutions have multiple payment methods - over the counter, wall mounted payment station, card payment, web based payments.... It very much depends on when you want to make them pay: For all Jobs? For anything over a set cost per week? For colour jobs only? For copying only? For example, you could give them a free quote of £1 per week, which at 5p per mono side allows 20 sheets a week. This free quota did not then apply to copying or colour devices which use a real balance for which they've paid for and does not get automatically updated. If they use all 20 sheets of mono, they can then use the real balance for mono jobs also.

What level of education are you involved in? Secondary/College/Uni? Visitors or part time courses?

There are alot of options!, I've got alot of experience with Pcounter so happy to help any time, pm me if easier.

No Problem! In the Dacc's web page, goto settings - theres an option the under client code/department (can't remember exact wording) which needs to be ticked for use associated code only. I would update to Pcounter 2.60 if possible, especially with dacc's 3.xxx

It's included in the latest release under a folder called client.... Also, It's used to require the Pro version, now it's included as standard.

As does PCounter, OSX uses a local client which is FOC.

Port 8080 is used - check communication over this. More than likely a VLAN rule.

Yes, the user authenticates in some way on the copier screen itself (AD username/password, PIN, Card, Fingerprint). These are handled via a remote "gateway" on your Pcounter server, The view is consistent within the same manufacturer - development and inclusion of functionality is managed subject to the copier firmware but it's our aim to keep the logging in and job release as simple as possible, while keeping the copy/scan screens as the manufacturer intended. Pcounter is modular but the core packaqe covers any number of devices or users, AD/E-Dir integration, quota's on a user/group/ou basis, rules and full reporting. It also includes departmental accountability, Mac support, user balance notifications and much more! It's priced per print server, with the cost dependant on type of student

RM now supplies Pcounter for advanced print control - not sure if CC4 has the original "print Credits" option still though!

Why not use client codes, then charge back the staff members department?

Hows Pcounter working out?

The Pcounter Biostore terminal can use the fingerprint from the child/staff member or a card giving you the option where parents are unsure. This all then ties into the Biostore databases, so is shared with door access, cashless catering and any other solution also linked. We have other options, including our own development if you only need print and copy though!

Nice to see good feedback from Pcounter users! Pcounter is non device specific, with embedded support for Sharp, Toshiba, Xerox, HP, Kyocera, KM and more!!!! For printer support, it covers nearly all devices, new and old! Different embedded (i.e. authentication/control on main touch panel) is cost effective if you are in a longer term contract, and is simple to manage - you then get the rules and quota's allowing very specific control of the work being done. All the embedded solutions are diffent in some way, but the core requirement and functionality remains. This is all very well, but you do need to decide on a pricing structure and the limits per staff/student and enforce them (thus management buy-in required) Reducing the device count and bringing in MFD's with pull printing (print to 1 queue, release from any device) can be a huge saving (Lower cost per click, green credentials, less support time - single queue to be used, user confirms if job required for a second time...) but failing that, moving high cost jobs to more capable/lower cost devices and instigating student quota's can still lead to large savings.

Yes, but this has been simplified, and these are more for communication so registry based. The port monitor setup is simpler, with all monitors merged together. There is now unofficial support for GDI devices with generally good success. SNMP support is better, and you can use a mass migration tool to change ports for TCP/IP or LPR onto Pcounter ports. There is a rollback option, and it's only on rare occasions there will be an output queue required. Happy to help with any questions, or niggles that people may have.

Pcounter now has a native mac installer for local tools if required, but otherwise simple to use and lots of options.