We are running a Nice system with a CLS version 8.9 with free seating.
We currently have 2 loggers, servicing a different network each. Nice has been successfully set up so that the silentlogin application is talking across from the second network to the CLS, and attempting to log in the user via windows username. However the system is not correctly mapping the required user to the channel that they are stationed at. On our main network there is no problem. The only difference I can see is that on our original network the Windows username was setup as surnameinitial, such as bloggsj, while on the new network it is firstname.surname, ie joe.bloggs
Is it possible that Nice cannot read a windows username with a . in the middle. If so, is there any work around we could use without needing to change all the usernames on Windows
Any ideas????
Riddler
The man in black fled across the desert, and the Gunslinger followed
We currently have 2 loggers, servicing a different network each. Nice has been successfully set up so that the silentlogin application is talking across from the second network to the CLS, and attempting to log in the user via windows username. However the system is not correctly mapping the required user to the channel that they are stationed at. On our main network there is no problem. The only difference I can see is that on our original network the Windows username was setup as surnameinitial, such as bloggsj, while on the new network it is firstname.surname, ie joe.bloggs
Is it possible that Nice cannot read a windows username with a . in the middle. If so, is there any work around we could use without needing to change all the usernames on Windows
Any ideas????
Riddler
The man in black fled across the desert, and the Gunslinger followed