| Step | Action | Click Image to Enlarge |
| 1 | Delete the existing terminal.
Note: The printer will be removed from all of the print groups.
| |
| 2 | Go to Pharos Systems Blueprint Administrator >Device Management >Devices, highlight the device, and then click on Create Associated Terminal. | |
| 3 | Choose the terminal type. See Application cannot be accessed message displays after pressing the release station icon to view terminal types.
Note:The Terminal name in Blueprint has to be the same as the printer's hostname. Mismatches usually happen when you create terminals manually on client computers, which is not recommended.
| |
| 4 | Go to Pharos Systems Blueprint Administrator > Secure Release Here > Print Groups > Managed Devices > Add Managed Devices > search for your printer, and then add it to the correct print group.
Note: By default, creating a terminal places the device into the default print group. Add the printer back into the specific print group where it was before deleting the terminal.
| |
| 5 | Restart the eDAS and RegisterMe apps via the printer’s Embedded Web Server (EWS) > Settings > Embedded Solutions or Device Solutions – Solutions (eSF) or Apps – Apps Management.
Note:Disable then enable the apps to restart.
See to view steps to access printer's EWS. | No Image |
| 6 | On the analyst server, go to the Pharos Systems Blueprint Administrator > Servers, and click on the Clear Replicated Data button. While on collector server, go to the Pharos Systems Blueprint Administrator > Replication, and then click on all three available buttons.
Note: This will populate the settings update to the collector server.
| No Image |
| 7 | Restart the printer and test again. | No Image |