As you may be aware, Endpoint Encryption for PC version 5.2.11 was recently released. One of the larger PER's in that release was support for the WACOM USB driver. What this essentially means is that specific tablet devices which use either the WACOM Serial (older style) or USB (newer style) devices can now be supported in the EEPC Pre-boot. McAfee has tested this support on a specific set of devices and can atest to those devices working as expected.
Similar to the Reader Support, McAfee is taking a stance where we claim support for specific devices which have been explicitly tested by the EEPC QA Team. Other devices may work as expected, however McAfee has not officially tested those devices inhouse. Should a customer find a device which is not working as expected, it should be logged as a Product Enhancement Request (PER) that can be appropriately assessed and scheduled by Product Management.
An administrator just needs to enable the On-screen keyboard support and the necessary WACOM support. Then the end user can use their finger(nail) or the digital stylus to enter the relevant information in pre-boot.
This type of support can be useful for companies in the Healthcare industry, Utilities (Energy, Oil, etc) or any industry where employees may be out on the road and want to use a touch interface.
Senior Product Manager
Endpoint Encryption for PCon 22/11/11 20:26:17 CET
What is the current time delay after a PER is submitted that one can expect before the product enhancement makes its way into a beta release or is made a KB article with workaround/solution?
Specifically, is there still a method that one could use to set custom information for the WACOM Serial devices (i.e. port,base,irq information)?
the old Serial driver is still there, and still works the same way.
As for PER's - there's no guarantee they will ever make it into the product, it's a request after all - it's dependent on many other things, other customer requests, development timescale's, effort etc.
If you MUST have a feature, then you need to do more than a PER - you'd need to reach out to your McAfee representative and discuss putting something in writing and getting commitments etc - perhaps even a professional services / custom development engagement.
We try and deliver PER's when we can, but as you can appreciate, we get lots of them and it's not possible for every one to make it into a product, especially if they are not generally interesting to every customer, or if they affect current behavior which others are relying on.
Is there a KB article that assists us in making the custom configuration file?
I understand that for my tablet, the com, base, and irq are at 0, 238, 5 (the exact range is 238-23f), what steps should I follow to get EEPC 5.2.11 to pick up the WACOM pen digitizer in this case?
Additionally, I haven't tested the 6.1.x release, would that perform similiar to 5.2.11 when it comes to the preboot environment? For the record, I am working on a Motion Computing J3500 i3 tablet.
I am still unable to get the tablet's digitizer and pen to function.
I tried the information that Motion Computing provided 0,238,5 and the information that others stated worked 0,238,3; unfortunately neither worked in my case. It must be a newer digitizer & pen combo from WACOM?
I do notice during some boots, EEPC hangs (>25minutes) at the blue loading bar. If I power off and restart, then the tablet boots as expected.
If you have any other tips or guidance I will take it, but I am conceding that I may have to wait until this makes its way through the PER process.
EEPC6 does not support pen digitizers I'm afraid. Only EEPC5.Message was edited by: SafeBoot - Seems I was mistaken about the above, and EEPC6 does support digitizers now! my bad. on 1/5/12 8:23:25 AM EST
Thanks for the reply. We have got the pen digitizer working with EEPC6 on a Motion Computing C5 Tablet pc on pre-boot using the sylus to log into EPO/Safeboot. We just cant get it working on a HP Elitebook 2730p Tablet pc ?