Skip to main content

How to re-certify Lotus Notes ID Manually?


If you see above alert box, understand that you need to re-certify the user’s lotus notes ID.
First export the user’s lotus notes ID as “SAFE.IDS” or get the expired  user’s lotus notes ID and save it on Removable Storage Drive or Shared Network Drive that can access from Domino Server.
Then log in to Domino Server and click Configuration Tab, Expand Certification and select Certify as shown below.
After that Click Certifier ID and choose cert.ID.

Type correct password for Certification ID and click OK.
Then Choose the SAFE.IDS or Expired User’s lotus notes ID that you saved at first step.
Type the current user’s lotus notes password and click log in.
Click Certify if you see prompt windows as shown below.
Click NO if you see prompt windows as shown below.
User ID re-certify task done from Domino Server Side.
Go to user’s PC/Notebook, open lotus notes and Click File>Security>User Security
Then you will see prompt windows that ask you to key in the password.
Key in the current user’s lotus notes password.
Expand Your Identity, Select Your Certificates and Click Get Certificates.
Then Select Import (Merge) Notes Certificates and choose the Re-certified ID from your Removable Storage Drive or Shared Network Drive.
Key in the password if prompt.
You’ve done the task of lotus notes client ID re-certification process.






Please see the below careful if you are not clear the above steps.
Administrator: Recertify user's ID
A user has a Notes ID that has an expired certificate. These steps are performed by the server administrator to correct the user's expired ID.
  1. After obtaining the user ID, you (as the administrator) launch the Lotus® Domino® Administration client.
  2. Open the Configuration tab, expand Certification (located on the right hand pane) and select Certify.
  3. Select the Certifier ID file.
  4. From the Choose Certifier ID dialog box, select the O or OU certifier that was originally used to certify the user ID.
  5. Enter the password for the certifier ID.
  6. From the Choose ID to Certify dialog box, select the user ID to be recertified.
  7. Enter the password for user ID to be recertified.
  8. [Optional] In the Certify ID dialog box, you may set or change the following:
    Registration server, expiration date of the certifier and password length.
  9. Click Certify.
    The Status window displays:
    Updating address book entry for username/org
    Successfully updated address book entry for username/org
    Username/org successfully certified
  10. Choose "No" when you receive the following dialog box:
    Would you like to certify another?
  11. Provide the newly-recertified ID file to the user.

User: Merge the new certificate
Once the administrator recertifies the safe.ID and returns the ID to the user, the user must perform the following steps:
  1. Select File -> Security -> User Security -> Your Identity -> Your Certificates -> Get certificates button -> Import (Merge) Notes Certificate.
  2. Enter password.
  3. The dialog box then prompts the user to choose the safe.ID that has been recertified and it is then merged into the original user ID.

Comments

Popular posts from this blog

Fortigate guide for Begineer - 6

I would like to explaine how to troubleshoot the Fortigate Unit configured by Transparent Mode in step by step this time. Let's assume, you have one Fortigate Unit that configured as Transparent Mode. But devices from Internal/Private Network unable to access Internet/Public Network through your Fortigate Unit. OK. Let's troubleshoot with following steps, 1) Check the physical network connections between the network and the FortiGate unit, and between the FortiGate unit and the Internet. 2) Check the router and ISP-supplied equipment to make sure it is operating correctly. 3) Verify that you can connect to the internal interface by connecting to the management IP address of the FortiGate unit from the Internal network. From the internal network, attempt to ping the management IP address. If you cannot connect to the internal interface, verify the IP configuration of the PC and make sure the cables are connected and all switches and other devices on the network are powered on a

Solving the "A general system error occured:Invalid fault" error in vSphere 4

Below error was come out when you try to migrate VM to other host for some reason. Below error was come out when you try to edit VM setting. Below error was come out when you power on the VM. How to solve those error? Here is how I resolve the error! Login to the Host that errored VM exist by using Terminal or Direct Console. Enter below command and press enter. services.sh restart Wait until all VMware Services are restarted. After that try to Power On/Edit Settings or Migrate the errored VM and you will see all you can do without any error pop-up. This kind of errors can occur if you shutdown/restart VM unproperly or shutdown/restart the Host unproperly that VM exist. You can check log file deeply if you willing to know precisely on this. May you all be happy. (Be knowledgeable, pass it on then)

Link Aggregating with Synology NAS and Cisco Switch

I’d like to share how to setup Link Aggregating between Synology NAS and Cisco Switch. I’ve got one Synology NAS with 4 Network Ports and I’m going to use 2 of them. Both Network Port to be as one Logical Link, Fault Tolerance and Load Balancing. To do that, I need to configure Link Aggregating on Synology NAS and EtherChannel with LACP on Cisco Switch. Below is brief steps to do to meet with my requirements. - Get connected Synology NAS and Cisco Switch as shown in picture. - Bonding two Network Ports of Synology NAS and assign IP Address - Configure EtherChannel with LACP in Cisco Switch and add two physical ports as Member. OK. Let’s begin from Synology NAS. - Login to the Synology and go to Control Panel>Network>Create>Create Bond - Select IEEE 802.3ad to get Fault Tolerance and Load Balancing Featureyou’re your switch not support 802.3ad you can only select Fault Tolerance only feature). After that click “Next”. - Choose the network port f