What are your Day-to-Day activities

Created Daily Admin Checklist, Server cpu performance, memory performance, network usage, disk space , Daily monitoring of Domino Servers using Domino Admin Client, Domino Domain Monitor, and statrep.nsf databases,Spam mail in IMSS (Internet message scan service), pending mail, lotus server n/w ping, 1: Which are the files created while installing Domino Server.

Ans :- Server id, Cert id, OU id, Admin id, Names.nsf, admin4.nsf, event4.nsf,notes.ini, log.nsf,certlog.nsf

2: What are Pending Mails and Held Mails and how are the resolved.

MAIL.BOX databases on the server may contain two types of undeliverable messages: dead messages, designated by a stop sign icon: INCLUDEPICTURE "http://www-12.lotus.com/ldd/doc/domino_notes/rnext/help6_admin.nsf/c1f2605b7be6a95985256b870069c0a8/d86d3e300e74a40385256c1d003959ab/Body/0.324?OpenElement&FieldElemFormat=gif" \* MERGEFORMATINET

; and held messages, designated by a red exclamation point: By default, when Domino cannot transfer or deliver a message -- for example, when the address is typed incorrectly -- the Router returns a delivery failure report to the sender. If the Router can neither deliver the message to its intended recipient (To, CC, or BCC) nor deliver the failure report to the sender -- for example, when the recipient's address is typed incorrectly and the sender's mail server is unavailable -- the Router changes the routing state of a message to Dead.By default, when you configure the Router to hold undeliverable mail, it does not mark messages as Dead. Only if the Router cannot deliver a held message or its delivery failure report after you release it for a final delivery attempt does the Router mark any message Dead.

For each held or dead message, the views in MAIL.BOX display information about when the server received the message, as well as the sender and recipient, message size, and the reason why the message failed. In addition, Dead messages display a Dead failure reason explaining why the message could not be returned to the sender.

To check MAIL.BOX for undelivered mail

Periodically examine MAIL.BOX for messages, especially if you configure MAIL.BOX to hold undeliverable messages. 1. From the Domino Administrator, select the server on which you want to resolve undelivered mail.

2. Click the Messaging - Mail tab.

3. Select the MAIL.BOX database you want to examine by clicking Servername Mailbox (mail.box). On servers with multiple mailboxes, a separate view is available for each mailbox.

4. Check Held and Dead messages. You can do one of three things with undeliverable messages:

Correct the addresses of the message recipients

Release the messages to their intended recipients

Delete the messagesTo edit and release held or dead messages Edit messages in MAIL.BOX to specify the destination address for resending the original message or resulting delivery failure report. You can also edit the Subject line to insert additional information about the message, such as the reason it was held or the name of the original recipient.

1. In the MAIL.BOX database, select the Held or Dead message for which you want to correct addresses and click Edit Message.

2. Edit the address in the Recipients field or Intended Recipient field as follows:

To edit the address of a held message:

To correct the destination address to which the Router resends an original message, edit the Recipient field. You can specify a Notes address or an Internet address.

When you release held messages, the Router ignores the entry in the Intended Recipient field.

To edit the address of a dead message:

To correct the destination address to which the Router resends the original message, edit the address in the Intended Recipient field, and click Release - Resend dead message to originally intended recipient. You can specify a Notes address or an Internet address. The Router ignores the entry in the Recipients field. The received message displays the original recipient address. To correct the destination address to which the Router resends the delivery failure report for a dead message, change the address in the Recipients field, and click Release - Return Non Delivery Report to sender. You can specify a Notes address or an Internet address.To release held and dead messages from MAIL.BOX

Depending on what caused a message to be retained in MAIL.BOX, you may be able to successfully resend it to its originally intended recipients or return a delivery failure report to the sender. For example, if messages were marked held or dead as a result of a temporary network failure, you may be able to release messages to their destinations after restoring network connections. Or, if a message failed to reach its destination because of a misspelled address, you can resend it by correcting the address and releasing the message. When deciding what to do with dead messages, always examine them carefully before taking action. Check the message origin and the list of intended recipients, and determine the failure reason. If the From or Recipients fields of a dead message are blank or contain invalid addresses, or if the failure reason indicates a null SMTP reverse path, consider deleting the message, rather than releasing it. 1. From the Domino Administrator, select the server on which you want to resolve undelivered mail.

2. Click the Messaging - Mail tab.

3. Click Servername Mailbox (mail.box) to select the MAIL.BOX database to examine. On servers with multiple mailboxes, the view displays each of the available mailboxes (mail1.box, mail2.box, and so forth).

4. Select the held or dead messages to release and click the Release button. Choose one of the following:

Release optionDescription

Resend all dead messages to originally intended recipientsThe Router attempts to resend each dead message in the current MAIL.BOX database to the originally intended recipient (To, CC, or BCC), listed in the Intended Recipient field. If the Router cannot deliver or transfer the message, it generates a delivery failure report to the sender. If the NDR is also undeliverable, the Router again marks the message Dead.

Note This action applies to all messages in the current MAIL.BOX database only. On servers with multiple MAIL.BOX databases, dead messages in other MAIL.BOX databases are not released.

Resend selected dead messages to originally intended recipientsThe Router attempts to resend the selected dead message to the originally intended recipient (To, CC, or BCC) listed in the Intended Recipient field. If the Router cannot deliver or transfer the message, it generates a delivery failure report to the sender. If the NDR is also undeliverable, the Router again marks the message Dead.

Return Non Delivery Report to sender of all selected dead messagesThe Router attempts to resend the delivery failure report for the selected dead messages to the message originator specified in the Recipients field. If the failure report is undeliverable, the Router again marks the message Dead.

Resend selected held messagesThe Router attempts to resend the selected held messages to the originally intended recipient (To, CC, or BCC) listed in the Recipients field. The Router ignores the entry in the Intended Recipient field.

If the Router cannot transfer or deliver a released message, it again marks the message Held.

Resend selected held messages for a final timeThe Router attempts to resend the selected held messages to the originally intended recipient (To, CC, or BCC) listed in the Recipients field. The Router ignores the entry in the Intended Recipient field.

If the Router cannot deliver the messages to the recipients, it sends a nondelivery failure report to the message originator and removes the message from MAIL.BOX. If the delivery failure report cannot be sent, the Router marks the message Dead.

When you finish processing undeliverable messages, close the MAIL.BOX database.

To delete messages from MAIL.BOX

The Router automatically deletes sent messages from MAIL.BOX. If you cannot resend a message or delivery failure report, or choose not to resend it, delete the message. 1. Select the Held or Dead to delete.

2. Click Delete Message. The messages are marked for deletion.

3. Press F9, and click Yes when prompted to delete the document. 3: What are the tasks running on domino server.Ans :- Running server tasks Server tasks perform complex administration procedures -- for example, compacting databases and updating indexes. You can run a server task manually, by loading the task at the server console or by using the Domino Administrator Task - Start tool, Server menu, or the Administrator console. Or you can run the task automatically when the server starts by adding the name of the task to the ServerTasks or ServerTasksAt settings in the NOTES.INI file. In addition, you can create a Program document in the Domino Directory to run a task at scheduled intervals.

From the local server console

Open the server console and enter the server task at the command prompt.

From the Domino Administrator server console

1. From the Domino Administrator, open the console for the server on which the program runs by clicking Console on the Server - Status tab.

2. In the Server console command field, type:

Load taskname

where taskname is the name of the server task that you want to run.

From the Domino Administrator Start - Task tool

1. From the Domino Administrator click the Server - Status tab.

2. Click Server Tasks.

3. Open the set of Task tools.

4. Click Start.

5. In the Start New Task box, select a server task from the list. Select advanced options to specify additional parameters.

6. Click Start Task.

In the NOTES.INI file

Many tasks run, by default, at specific times. You can schedule additional tasks to run by editing one of these settings in the NOTES.INI file:

ServerTasks starts tasks automatically every time the server starts up

ServerTasksAt starts tasks at a specified timeDomino server tasks

TaskCommand to run taskDescriptionDefault in NOTES.INI file

Activity Trends CollectortrendsRuns the Activity Trends Collector which performs historical and trended analysis on IBM Lotus Domino Activity data.None

Administration ProcessAdminPAutomates a variety of administrative tasks.ServerTasks

Agent managerAMgrRuns agents on one or more databases.ServerTasks

BillingBillingCollects all generated billing information.ServerTasks

Calendar ConnectorCalconnProcesses requests for free-time information from another server.ServerTasks

CA processcaAutomates a variety of server-based certificate authority tasks.ServerTasks

CatalogerCatalog Updates the database catalog. ServerTasksAt1

Change Managerrunjava ChangeManRuns the Change Manager addin task which manages large-scale changes within the domain.None

ChronosChronosUpdates full-text indexes that are marked to be updated hourly, daily, or weekly.None

Cluster Administration Process (R4/R5 only)CladminOversees the correct operation of all components of a cluster.None

Cluster Database Directory ManagerCldbdirUpdates the cluster database directory and manages databases with cluster-specific attributes.None

Cluster ReplicatorClreplPerforms database replication in a cluster.None

Database compactorCompactCompacts all databases on the server to free up disk space.None

Database fixupFixupLocates and fixes corrupted databases. None

DesignerDesignUpdates all databases to reflect changes to templates. ServerTasksAt1

DIIOPDIIOPAllows Java applets/applications to access Domino data remotely using CORBA.ServerTasks

Directory CatalogerDircatPopulates directory catalogs and keeps the catalogs up-to-date.None

Domain IndexerDomidxCreates a central, full-text index for all specified databases and file systems in a domain. Runs only on Domain Catalog servers.None

Event MonitorEvent Monitors events on a server.None

HTTP ServerHTTPEnables a Domino server to act as a Web server so browser clients can access databases on the server.None

IMAP ServerIMAPEnables a Domino server to act as a maildrop for IMAP clients.None

Indexer UpdallUpdates all changed views and/or full-text indexes for all databases. ServerTasksAt2

Internet Cluster Manager (ICM)ICMProvides failover and workload balancing for HTTP clients (Internet browsers) that access Domino Web servers.None

ISpyRunJava ISpySends server and mail probes and stores the statistics.ServerTasks

LDAP ServerLDAPEnables a Domino server to provide LDAP directory services to LDAP clients.ServerTasks on administration server for the Domino Directory; None on other servers

MTCMTCReads log files produced by the router and writes summary data about message traffic to a database for message tracking purposes.ServerTasks

Object store manager

POP3 ServerPOP3Enables a Domino server to act as a maildrop for POP3 clients.None

ReplicatorReplicaReplicates databases with other servers. ServerTasks

ReporterReport Reports statistics for a server.None

RouterRouter Routes mail to other servers. ServerTasks

RunjavaRunjavaRuns Java server add-in tasks such as the Change Manager and ISpy.None; used only with the name of another add-in task, never appears by itself

Rooms & Resource ManagerRnRMgrProcesses all Rooms and Resources activities, such as meeting invitations, reschedules or cancellations, and updates the Busytime database accordingly.ServerTasks

Schedule managerSchedProcesses all user calendar activities and updates the Busytime database accordingly.ServerTasks

SMTP listenerSMTPListens for incoming SMTP connections, enabling Domino to receive mail from other SMTP hosts.None

SNMP

QuerySet

InterceptorQurySet

IntrcptAllows Domino to respond to Simple Network Management Protocol (SNMP) requests. Prerequisite: Domino SNMP Agent (LNSNMP).

Allows Domino to issue SNMP traps for Domino events. Prerequisite: Domino SNMP Agent (LNSNMP).None

None

Statistic CollectorCollectCollects statistics for multiple servers.None

StatisticsStatlogRecords database activity in the log file.ServerTasksAt5

StatsStatsGenerates statistics for a remote server on demand.ServerTasks

Web RetrieverWebImplements the HTTP protocol to retrieve Web pages and convert them into IBM Lotus Notes documents.None

4: What command consoles are u familiar with.

Ans :- Lotus notes admin console, Server > status> server console5: Can we create password for server id.

Ans :- No one assign in primary domino server(Main domino server). you can assign password in additional Domino server id,

6: What is Archiving and how it is done.

Q. What is archiving?

A. Archiving frees up space and improves performance of any database by storing documents in another database when they are old or not in use anymore. After specifying which documents you want stored, you can have Notes archive automatically on a schedule, or you can archive manually. This saves server storage space and cuts down on the time it takes to open your mail and folders.

Q. What actually happens when you archive?

A. Archiving takes older mail messages off of the Notes servers and places a database copy on your local computer. These messages are easily accessible by your Notes client. You can archive manually or set a schedule to archive daily or weekly.

7: Default Path for archiving.

Ans :- C:\Program Files\Lotus\Notes\Data\Archive\a_yourname.nsf

8: If a user is not able to replicate local mail file what is the issue and how will u resolve.

Ans:- N/W related prob, trace route, server down, server max connection. 9: What is route* and is user for.

Ans :- Route * --- Sends mail to all pending destinations

1. From the Domino Administrator, click the Server - Status tab.

2. If necessary, click Tools to display the tool bar, and then click Server - Route Mail.

3. Under "Route mail with server," enter the name of the server you want to route mail to, or select the name of the server from the list.

4. Click Route.

10: Difference between Lotus Client 7 and Lotus Client 8.5.2

Ans :-

V 7.0xV 8.0xV 8.5x

password when forgotten through ID vaultY

Date / Time email was deleted column in trash folderYY

Vertical preview pane for emailYY

Email RecallYY

Out of office notification with both hours n dateYY

Automatic disable to out of office notification upon returnYY

11: What does compact means and what does -B indicates and how to use compact command.Ans :- Reorganizes the disk usage by each database in order to free up unused space.load compact [database] -b

Compacts databases in place. Can be used only if the database internal format is not being changed due to a change in one if the advanced database properties. It recovers unused space within the database, but does not reduce the file size of the database. load compact [database] -bCompacts databases in place. Can be used only if the database internal format is not being changed due to a change in one if the advanced database properties. It recovers unused space within the database, but does not reduce the file size of the database

load compact [database] -BCompacts databases in place. It recovers unused space within the database, and does reduce the file size of the database.

load compact [database] -cUses copy-style compaction of the database, rather than in-place compaction

12: IF a user adds a address, where it is cached and if does not require that particular address how it is removed

????

13: What are the templates size and ODS versions.

V3 :- 17

V4 :- 20

V5:- 41V6, V7:-43 > Database Size17 MBV8:-51 > Database Size 11 MB14: If a users mails views are changed sunddenly to unread, how will u resolve.

Ans :- ????

15: I require to change my username, OU and email ID how it is done.

Ans :- Go to lotus domino admin client > people and group > select user name(Person Doc) > tools> rename > common name> changes user names or ou

16: If user sends a mail, then where can we find the logs if there is some problem to the mailIn domino admin client > go to server tab > analysis > log > date or time

17: Any knowledge on AIX platform. ????