Issue
In the Padvish management console, in the section of Logs and Reports > Server Logs section, you see logs with MessageID=90 stating Duplicate login from client (%computerName%) rejected. The meaning of this message and the steps to deal with it are explained below.
The meaning of the message
To understand the message and conditions leading to its occurrence it’s necessary to be familiar with the concepts of registration and client connection.
Every client connecting to Padvish management server must be registered under specific conditions: This is done automatically under the following conditions:
Registration occurs during installation for remotely installed clients or those utilizing the rgc config file. For clients manually added through license management, registration happens during the first connection to the server.
Then, upon subsequent connections (for example, after restarting the system), it first introduces itself to the server according to the previous registration. If the client is registered on the server and is available in the server database, this connection is successful and the MessageID=8 with the content of Client %computerName% connected% will be registered. Normally, immediately after connection request from client, the server promptly updates the client’s status to Connected and informs the client accordingly.
However, if a client already connected attempts to reconnect, the server registers the DuplicateLogin message and does not respond to the second request.
Under normal conditions, such an event should not occur, and a connected client should not request another connection. Yet, certain problems may lead to this, such as:
- Failure to coordinate server resources with the number of clients.
- Installing Windows using a Restore Image from another system.
- Failure to execute the Convert_To_VDI_Template task for VDI systems.
- Applying registry changes related to orphaned clients.
- Other problems
How to deal with and Resolve the Message:
Several solutions have been outlined to deal with this message and should be examined in sequence:
1. Evaluate Server Resources
Review the Amanpardz server console installation requirements.
Assess if the server resources are adequate for the number of clients. Increase resources if necessary.
Check the status of tasks and avoid simultaneous heavy task execution.
Ensure the hard disk writing speed exceeds 100 MB per second.
Note that as the number of connected clients to the console increases, server resources should scale accordingly.
2. Image Installation Precautions:
If using another system’s image for Windows installation, ensure Padvish is not activated on the primary system.
Padvish activation creates a unique SystemSignature for each system. If activated on one system and the image is used on another, only one system will be allowed to connect to the console.
To resolve, unregister these systems once and reactivate them.
3. VDI Considerations:
In VDIs, where multiple systems introduce themselves with the same signature, the DuplicateLogin issue may arise.
Select one VDI and use the ConvertToVDITemplate option from the PerformTask menu.
The server will automatically detect these conditions.
4. Orphan Clients and Registry Changes:
Deal with orphan client problem by reverting registry changes that automatically activate unlicensed clients.
Revert changes to their original state within one week at most to avoid DuplicateLogin logs.
Study this page for additional guidance.
5. Expert Support:
Implementing these steps should help resolve the DuplicateLogin problem, but, in the case that problem is still persistant, it is necessary to check the system by Amnpardaz Support experts.