When a VersaLink device is configured with Equitrac or Output Manager and AutoStore, and AutoStore is set for Windows authentication, do not restart the device at the identity screen. If you do, you cannot log on with a card swipe or the alternate keyboard.

Workaround: Restart DWS.

When the device is configured with Equitrac or Output Manager and AutoStore, and AutoStore is set for Windows authentication, a card swipe fails if the device times out at the identity screen.

Workaround: Log on with the alternate keypad and swipe the card again.

When you swipe the card at the identity screen, press the Home button, and press Reset to log off, you cannot log back in by swiping the card again. Manual logon also does not work. This occurs when the device is configured with Equitrac or Output Manager and AutoStore, and AutoStore is set for Windows authentication.

Before users can log on to the device again, DWS must be restarted. If users still cannot log on, the app must be uninstalled and reinstalled.

If the Output Manager DBM service is offline, AutoStore scan, native scan, and copy jobs are not tracked and do not appear on reports. These jobs should have been tracked by Output Manager even if the DBM service is offline. This occurs when Kofax Unified Client for Xerox is configured with Output Manager and Authentication set to On.

If you configure the billing code prompt at login in Equitrac or Output Manager and select a billing code when logging on, USB jobs are not tracked with those billing codes when released. In Equitrac or Output Manager reports, the USB jobs are tracked against the user (or the assigned department if Charge to Department is enabled), but not the billing codes.

While tracking scans from the native Xerox Email app, the Destination and Scan Destination Type in Equitrac reports are shown as Unknown for AltaLink devices.

When reinstalling the Kofax Unified Client for Xerox on AltaLink devices, the Please Wait screen appears. The problem is that the device has the previous user logged on and cannot be logged out automatically.

Workaround: Tap the Home button and log out. At the Convenience Authentication Login screen, log on again.

If a form field has a numeric field set to a range (such as 100–1000), if the device is set to a language that is not supported by the Kofax Unified Client for Xerox, entering a valid value generates an error.

For a list of languages supported by Kofax Unified Client for Xerox, see the ControlSuite help.

If you create a form in AutoStore with fields in long date format, you may encounter the following issues:

• When you attempt to select a date in Catalan or Turkish, "NaN" appears instead of the date.

• If you attempt to select a date again, Invalid Date appears in the date field, and the form hangs. Exit the form to return to the Launcher and go back into the form.

If you are using one Equitrac workflow configured for departmental access (not global access) and had added it to a department that has a user, the launcher screen is still empty if you log on with departmental credentials.

Workaround: Log on using the credentials of a user assigned to that workflow instead of departmental credentials.

When an Equitrac user name has special characters (such as á, Ě, ñ), a scan workflow in AutoStore fails.

Workaround: Do not use special characters in Equitrac user names.

If a Xerox device is not configured on the Output Manager server, Authentication is Off, and you are using a third-party authentication provider, launching the Kofax Unified Client for Xerox app causes the Please Wait screen to appear instead of an error.

In Output Manager, print transactions are not tracked correctly to users across domains. Reports based on JBA show "None" as the user name.

In the Output Manager Print Preferences window, only the title and Done button are localized, but not the options and settings in the window. This occurs with the following languages:

• Catalan

• Czech

• Hungarian

• Polish

• Russian

• Turkish

For all other languages, the window is fully localized.

If you unregister the Kofax Unified Client for Xerox when DWS 2 is down or invalid, the warnings are not indicated in the uninstall message. The message "Successfully completed" appears, but you have to click the + icon to view the warnings.

Workaround: Always check messages that include a + icon to view any warnings and additional messages.

After logging on and selecting Bypass at the AutoStore Identification screen and selecting a billing code, the AutoStore Identification screen appears again. If you click Cancel at this second screen, the Please Wait screen appears and remains on the screen until you press Home. This occurs only when the Kofax Unified Client for Xerox is installed with Authentication set to On with Equitrac or Output Manager as the print manager and AutoStore as the capture component.

Workaround: Press Home and select Kofax XeroxUC. The AutoStore Identification screen appears again, but you can bypass or log on.

On VersaLink devices when Authentication is set to On, if you attempt to change the default application to something other than the Kofax XeroxUC app, the Convenience Authentication Login screen displays the message, "You do not have permission to use this feature." Changing the default back to XeroxUC enables you to log on without the error message.

When using when using Kofax Business Connect with Output Manager, when you tap your phone to the device, an "Authentication Error" message appears instead of the expected "Please follow the prompts on your mobile device" message. This is because the Xerox device cannot display the type of popup messages used by Output Manager.

When you install and log on with an AltaLink device, a black strip randomly appears on the Launcher screen when you open the Kofax Unified Client for Xerox app. For subsequent logons, the black strip does not appear.

Function Access Control is not supported by the Kofax Unified Client for Xerox. If you enabled Function Access Control in Equitrac to deny access to native scan, copy, and fax features, it will not prevent access. This occurs when the device is configured with Output Manager.

When you remove the license for a third-party card reader, make sure it has been cleared from the cache so you remain in compliance with the card reader license agreement. The removed license should be cleared after 24 hours, but it could stay in the cache up to 7 days. If the license has not been cleared, delete the cache under C:\ProgramData\Nuance\Equitrac\CAS and restart CAS.

When the device is reset, the default domain is not populated automatically on the identification screen. This occurs when Windows authentication is used in an AutoStore only or AutoStore and Equitrac configuration when authentication is off.

During DWS failover, users should be logged out automatically. Instead, the Please Wait icon appears and remains on the device front panel.

Workaround: Users must log out manually whenever DWS failover occurs and when the secondary DWS becomes active.

If you are performing an AutoStore workflow and filling out text fields, tapping Scan does not start scanning immediately. You have to tap Scan again to beginning scanning.

When clicking in the Number of Copies field at the Follow-You Printing screen, the alphanumeric soft keyboard appears instead of the numeric keypad. You can switch to the numeric keypad, but if you type any non-numeric character, the number of copies is reset to 1. This occurs with AltaLink C8030 and VersaLink C505 devices.

The behavior of the Home button does not appear to change after logging on if you had pressed it before logging on. Pressing the Home button takes you to the device's Home screen instead of the Kofax Unified Client for Xerox launcher as expected for the logged on user. This occurs only on AltaLink devices when configured for centralized workflows and authentication on.

When you attempted to delete a job from the Print-to-Me screen, the following error appears:

Displayed document list may have expired. Refreshing list from server.

This error occurs even when a job is just added to the queue.

Workaround: This error occurs when WebDAV is installed on server roles. When WebDAV is uninstalled from server roles, jobs can be deleted successfully from the queue.