Question
It may be necessary to forcibly remove a user registration to trigger the Print Scout to request the user to login again. This is most often used for testing purposes but could also be used in the rare event that the Print Scout needs to “forget” existing users.
Information
- Delete the UserIdentities.dat file located within
Versions less than 7.20:
C:\ProgramData\Pharos\PrintScout\SpoolerService\Registration
Versions 7.20 and greater:
C:\Users\{username}\AppData\Roaming\PrintScout - Restart the Pharos Print Scout Spooler Service.
- The user will be prompted to login again upon the next use of Secure Queue.