Message Flow DIG in Microsoft Exchange 2000

1> Message Flow DIG in Microsoft Exchange 2000  - Find attach file for the same

2>Message Flow DIG in Microsoft Exchange 2007  - Find attach file for the same

 

3>Message Flow DIG in Microsoft Exchange 2003  :

 

 

Exchange Message Flow

To identify monitoring issues and proactively manage an Exchange 2003 network, you should understand message flow between Exchange components. Exchange message flow is shown in the following figure.

Message flow through an Exchange 2003 server

Message flow in Exchange 2003 is as follows:

1. An SMTP host connects to the SMTP transport engine on port 25, or an Outlook client places a message for sending in the database, or an inbound message is received from the MTA.
   
2. Regardless of the origin, the message is transferred to the advanced queuing engine. If the message comes from a remote SMTP host, the SMTP protocol engine transfers the message to the advanced queuing engine, whereas if the message comes from a MAPI client, such as Outlook, or from MTA, the store driver transfers it to the advanced queuing engine.
   
3. The advanced queuing engine then uses the categorizer to process received messages. The categorizer tries to resolve the originator, resolve recipients, and enforce message restrictions. Received messages are placed in one of two queues: a local queue with messages for recipients residing on the server, and an outbound pre-routing queue.
   
4. From the local queue, the message transfers to the store driver, which is part of the Microsoft Exchange Information Store service, and is placed in the destination mailbox.
   
5. To transfer messages from the pre-routing queue, the advanced queuing engine uses the routing engine to determine where the SMTP service should send the message. The routing module passes the message to the queue manager that finally places the message in a link queue to be sent through the SMTP service. The name of the link queue corresponds to the name of the destination domain. From the outbound queue, messages are sent to the next routing hop by the SMTP service.
   

 Verifying Server-to-Server Message Flow Manually by Reading Exchange Transport Events

The best way to test the message flow between servers and messaging systems is through small e-mail messages. The Exchange Management Pack includes scripts to test mail flow between servers. This is configured by using the Configuration Wizard, as described in Deploying Exchange Server 2003 Management Pack. These scripts periodically send e-mail messages and verify that the messages are received. Mail flow script configuration is discussed in the Exchange 2003 Management Pack Configuration Guide at http://go.microsoft.com/fwlink/?linkid=25436. The rules and dependencies of scripts are discussed in the topic, Exchange Management Pack Script Dependencies.

Additionally, you can verify the information that is related to message transfer in the event log entries. For example, suppose you are monitoring e-mail messages sent to non-local sites that do not reach the intended destination. You are not sure about the source of the problem and whether it is an error in the Exchange configuration or a mistake in recipient information by the sender. You can monitor the progress of message flow with event log entries in addition to the message-tracking feature in Exchange 2003.

As an example, consider the message that is sent is recognized as outbound and the advanced queuing engine uses the Routing service to query DNS and obtain information about the next routing hop to which the message should be sent. This information will be indicated in the routing engine event log query.

As an example of a delivery failure warning, consider that when DNS is queried, it returns data about the destination mail server of the domain from the mail exchange (MX) records to the routing engine. If there is a situation where the domain is fictitious and not a Fully Qualified Domain Name (FQDN), a warning is generated in the event log.

Finally, a non-delivery report event is logged that includes possible causes and remedies. You can filter the log list to display only relevant entries. In this case, sending to a nonexistent domain caused the error. Note that some of these events require that Transport logging be set to Maximum in Exchange System Manager.

 

Thanks and Regards,
Arun Sabale | L2 tech
Zenith Infotech Ltd.

READ MORE - Message Flow DIG in Microsoft Exchange 2000

How Exchange Link State Algorithm (LSA) Works?

Link State Algorithm (LSA)

Exchange Server 2003 determines the route that an e-mail must take based on the status and availability of connectors between different routing groups and to external messaging systems through an SMTP connector or other connectors.

Every exchange server stores its status information in a Link State Table (LST). The Link State Table is a small table which requires about 32 bytes per entry which is held in the Exchange Servers' RAM.

All information will be collected by the Routing Group Master (RGM) of the routing group. The Routing Group Master uses TCP Port 691 to talk with other exchange servers in the routing group and is responsible for generating / updating the LST and for the distribution of the LST to each exchange server in the routing group.

The updated LST is propagated to other routing groups through Bridgehead Servers. The Routing Group Master (RGM) then sends the updated information to the Bridgehead Server, and then the Bridgehead Server sends the information to Bridgehead Servers in other Routing Groups over TCP Port 25.

Figure 6: Link State Table

The Link State Table lists all connectors, and their status, in an Exchange Server 2003 organization. The following information is included in the LST:

Link status

There are only two states for any given link: up or down. For this reason, connection information, such as whether a link is active or in a retry state, is not propagated between servers running Exchange Server 2003, and it is only available on the server involved in the message transfer. Exchange Server 2003 only considers routing messages by using connectors with a link status of up.

Link cost

The Link State Table stores costs for each connector. Exchange Server 2003 uses the cost values stored in the link state table to select the least cost route for a message. Costs are configured on each connector, and Exchange Server 2003 records them in the Link State Table.

 

Exchange Link State Algorithm (LSA) :

 

To guarantee efficient and reliable message routing, Exchange servers must have up-to-date information in their link state table. This information must accurately reflect the state of all bridgehead servers and messaging connectors. To propagate link state information to all servers in an Exchange organization, a propagation protocol known as link state algorithm (LSA) is used.

Propagating link state information among all servers has the following advantages:

• Each Exchange server can select the optimum message route at the source instead of sending messages along a route on which a connector is unavailable.
  
• Messages no longer bounce back and forth between servers, because each Exchange server has current information about whether alternate or redundant routes are available.
  
• Message looping no longer occurs.
  

 Link State Algorithm

The propagation of link state information differs within and between routing groups. Within routing groups, reliable TCP/IP connectivity is assumed, and servers communicate with each other over direct TCP/IP connections. Across routing groups, however, direct TCP/IP connections might not be possible. Across routing groups, Exchange Server 2003 propagates link state information through SMTP or X.400.

Exchange Server 2003 propagates link state information as follows:

• Intra-routing group LSA   Within a routing group, the routing group master tracks link state information and propagates it to the remaining servers in the routing group. The remaining servers are also named member nodes or routing group members. When a member node is started and has initialized its routing table with information from Active Directory, it establishes a TCP/IP connection to port 691. It then authenticates with the routing group master and obtains most recent information about the state of all links in the routing topology. All intra-routing group connections require two-way authentication. The connection remains so that master and subordinate node can communicate with each other whenever link state changes occur.
  
  Master and subordinate in a routing group
  
  Within a routing group, Exchange Server 2003 updates link state information as follows:
  
  1. When the advanced queuing engine or the Exchange MTA determines a problem with a bridgehead or routing group connector, it informs the local routing engine, as explained in "Message Rerouting Based on Link State Information" in Exchange Server 2003 Message Routing.
     
  2. The local routing engine, acting as a caching proxy between the routing group master and the advanced queuing engine or Exchange MTA, forwards the link state information to the routing group master over the link state connection to TCP port 691.
     
  3. When the routing group master is informed of an update, it overwrites the link state table with the new information. Based on this new information, the routing group master creates a new MD5 hash, inserts it into the link state table, and then propagates the new information to all servers in the routing group. Again, communication takes place over TCP port 691.
     

     Note:
     An MD5 hash is a cryptographic block of data derived from a message by using a hashing algorithm that generates a 128-bit hash from a list of blocks with 512 bits. The same message always produces the same hash value when the message is passed through the same hashing algorithm. Messages that differ by even one character can produce very different hash values.

  4. The routing group master sends the whole link state table (that is, the OrgInfo packet) to each routing group member. Each routing group member compares the MD5 hash of the new OrgInfo packet with the MD5 hash in its own link state table and determines if the local server has the most up-to-date information.
     
  5. If the MD5 values are different, the routing group member processes the OrgInfo packet. After replacing the link state table in memory, the routing group member sends a short reply to the routing group master, now also referencing the new MD5 hash value.
     
  6. The routing group master processes this information, discovers that the routing group member is updated, and sends a short acknowledgment to the routing group member.
     
  7. Every five minutes thereafter, the routing group member polls the master to query for up-to-date routing information. Master and member node compare their MD5 hash values to determine if changes occurred.
     

  Note:
  All servers within a routing group must communicate with the routing group master through a reliable TCP/IP connection.

• Inter-routing group LSA   Link state information is communicated indirectly between routing groups, using bridgehead servers and routing group connectors. To send link state information to another routing group, the routing group master communicates the link state information in the form of an Orginfo packet, which it sends to the routing group's bridgehead server over TCP port 691. The bridgehead server then forwards this information to all the bridgehead servers in other routing groups to which it connects, using the various routing group connectors it hosts.
  If the communication between routing groups is SMTP-based (that is, Routing Group Connector or SMTP connector), link state information is exchanged before regular message transfer by using the extended SMTP command, X-LINK2STATE, as follows:
  
  1. The source bridgehead server establishes a TCP/IP connection to the destination bridgehead over TCP port 25.
     
  2. The bridgehead servers authenticate each other using the X-EXPS GSS API command.
     
  3. After connecting and authenticating, link state communication begins using the X-LINK2STATE command.
     
  4. First, the bridgehead servers compare their MD5 hashes to detect any changes to link state information. Then the local bridgehead server uses the DIGEST_QUERY verb to request the MD5 hash from the remote bridgehead server. The DIGEST_QUERY verb contains the GUID of the Exchange organization and the MD5 hash of the local bridgehead server.
     
  5. The remote bridgehead server now compares its MD5 hash to the MD5 hash received through the DIGEST_QUERY verb. If the hashes are the same, the remote bridgehead server sends a DONE_RESPONSE verb to indicate that the link state table does not require updating. Otherwise, the remote bridgehead server sends its entire OrgInfo packet.
     
  6. After receiving the OrgInfo packet, the remote and local bridgehead servers reverse roles and the local bridgehead server sends its own OrgInfo packet to the remote bridgehead server. Both bridgehead servers transfer the received OrgInfo packet to their routing group masters. The routing group master determines whether to update the link state table with the information from the OrgInfo packet. A higher version number indicates a more recent OrgInfo packet.
     

     Note:
     Routing group masters never accept information about their local routing group from a routing group master in a remote routing group.

  7. After the exchange of OrgInfo packets, the remote bridgehead server starts transferring e-mail messages, or issues a Quit command to end the SMTP connection.
     
  For details about SMTP communication between servers running Exchange Server 2003, see SMTP Transport Architecture.
  

Note:

When you link routing groups by means of an X.400 connector, link state information is exchanged between the MTAs as part of typical message transmission. A binary object, called the Orginfo packet, is sent in a system message to the receiving MTA before interpersonal messages are transferred. The receiving MTA then transfers the Orginfo packet to the local routing engine, which communicates the transfer to the routing group master.

 An LSA Example

The following figure illustrates how the link state algorithm works in an Exchange organization that contains multiple routing groups. The figure illustrates an environment that contains an unavailable bridgehead server in routing group E. Also, the bridgehead servers in the other routing groups have not received the information that there is a routing problem.

An organization with an unavailable bridgehead server, before link state changes

Exchange Server 2003 discovers the routing problem in the following way:

1. A user in routing group A sends a message to a recipient in routing group E.
   
2. The routing engine chooses the path shown in Figure 5.9. Therefore, the message is transferred to the bridgehead server in routing group B.
   
3. The bridgehead server in routing group B tries a direct transfer to the bridgehead server in routing group E. Because the remote bridgehead is unavailable, the try fails. After three consecutive connection tries, the routing group connector's local bridgehead server is marked as CONN_NOT_AVAIL. Because there are no more bridgeheads in the connector configuration, the connector is marked as STATE DOWN.
   
   First connector down
   
4. The bridgehead server in routing group B connects to its routing group master through TCP port 691 and transmits the new link state information. The master incorporates the information into the link state table and notifies all servers in the routing group about the change.
   
5. The link state change causes a rerouting event in routing group B. Exchange Server 2003 can select from two paths with the same cost values. In this example, the message is sent to routing group C, because the routing engine randomly chooses this transfer path.
   
6. Before the actual message is transferred, the bridgehead servers in routing group B and routing group C compare their MD5 hashes. Because the MD5 hashes do not match, the servers exchange link state information. The bridgehead server in routing group B informs its remaining adjacent remote bridgehead servers (routing groups A, C, and D) about the link state changes.
   
7. The bridgehead server in routing group C connects to its routing group master through TCP port 691 and transmits new link state information. The routing group master incorporates the information in the link state table and notifies all servers in the routing group about the change. All servers in routing group B and C now know that the routing group connector between routing group B and routing group E is unavailable.
   
8. The bridgehead server in routing group C tries a direct transfer to the bridgehead server in routing group E. Because the remote bridgehead is unavailable, the connection try fails. After three connection tries, the connector is marked as STATE DOWN.
   
   Second connector down
   
9. The bridgehead server in routing group C connects to its routing group master through TCP port 691 and transmits new link state information. The routing group master incorporates the information in the link state table and notifies all other servers in the routing group about the change.
   
10. The link state change causes a rerouting event in routing group C. The message is sent now to routing group D, because the routing engine still sees an available transfer path from routing group D to routing group E. The bridgehead server in routing group C informs its remaining adjacent remote bridgehead servers (routing groups A, B and D) about the link state changes.
    
11. The message is transferred to routing group D, but before the actual message transfer, the bridgehead servers in routing group B and C compare their MD5 hashes and exchange link state information.
    
12. The bridgehead server in routing group D connects to its routing group master through TCP port 691 and transmits new link state information. The routing group master incorporates the information into the link state table and notifies all servers in the routing group about the change. All servers in routing group D now know that the routing group connectors between routing groups B and E and routing groups C and E are unavailable.
    
13. The bridgehead server in routing group D tries a direct transfer to the bridgehead server in routing group E, but because the remote bridgehead is unavailable, the connection try fails. After three connection tries, the connector is marked as STATE DOWN.
    
    Third connector down
    
14. The bridgehead server in routing group D connects to its routing group master through TCP port 691 and transmits new link state information. The master incorporates the information into the link state table and notifies all servers in the routing group about the change.
    
15. The link state change causes a rerouting event in routing group D. Because no additional transfer paths are available to routing group E, the message remains in routing group D, until at least one transfer path is available. The message is transferred to routing group E as soon as the bridgehead server in routing group E is available.
    
16. The bridgehead server in routing group D informs its remaining adjacent remote bridgehead servers (routing groups B and C) about the link state changes. These routing groups then propagate the link state changes to routing group A.
    

 Link State Changes and Link State Propagation

The link state table contains version information for each routing group in the form of major, minor, and user version numbers. Major version changes have highest priority, followed by minor changes, and changes to user version numbers.

Exchange Server 2003 detects link state changes in the following way:

• Major version number   Major changes are actual physical changes in the routing topology. For example, you create a major change when you add a new connector to the routing group or change a connector configuration. To receive notification of major changes to its routing group in the routing topology, the routing group master registers with Active Directory for change notifications using DSAccess. The configuration domain controller sends these notifications to the Exchange server, according to the standard Lightweight Directory Access Protocol (LDAP) change notification process. When a routing group master receives an update to the routing topology from the configuration domain controller, it sends the updated information to all member servers in its routing group. It also notifies all bridgehead servers in remote routing groups, as explained earlier in the section "Link State Algorithm." For more information about the role of DSAccess and the configuration domain controller on Exchange 2003, see Exchange Server 2003 and Active Directory.
  
• Minor version number   Minor changes are changes in link state information, such as a connector changing from a STATE UP to STATE DOWN. Unreliable network connections, however, could lead to a situation in which connectors are frequently marked up and down, which causes extra link state updates across the Exchange organization. A substantial increase in processing overhead may occur, because of extra route resets and message rerouting. By default, Exchange Server 2003 mitigates oscillating connectors by delaying link state changes for a period of ten minutes. During this period, changes that occur are consolidated and then replicated across the organization in one batch. However, an oscillating connection can still generate link state traffic if changes occur for extended periods of time.
  You can increase or decrease the update window through the following registry parameter.
  

  Location	HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RESvc\Parameters\
  Value	StateChangeDelay
  Type	REG_DWORD
  Value Data	Interval in seconds between link state updates. Default is ten minutes. The maximum is seven days. Setting this parameter to 0 can be useful when troubleshooting connection failures. Failures are then immediately reflected on connector states.

  You can also prevent the routing group master from marking down its connectors by setting the following Registry key. This can be helpful, especially in hub-and-spoke routed scenarios, in which each destination can be reached only through a single connector. Message rerouting cannot occur if alternate connectors are not available.
  

  Location	HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RESvc\Parameters\
  Value	SuppressStateChanges
  Type	REG_DWORD
  Value Data	A value of 0x1 disables link state changes.

• User version number   User updates include minimal changes, such as when the routing group master changes, when services are started or stopped on an Exchange server, when another server is added to the routing group, or when a member server loses connectivity to the routing group master.
  

 Changing the Routing Group Master

The first server installed in the routing group is automatically designated as the routing group master. If this server fails or is taken offline, link state information is no longer propagated in the routing group. All servers in the routing group continue to operate on the earlier information. When the routing group master is available again, it reconstructs its link state information. The routing group master begins with all servers and connectors marked as unavailable. It then discovers any unavailable servers and updates members within the routing group.

If you shut down a routing group master for more than a brief time, you should nominate a different routing group master to avoid inefficient message routing. In Exchange System Manager, expand the desired routing group and select the Members container. In the details pane, right-click the server that you want to promote to the routing group master, and then select Set as Master.

Note:
Changing the routing group master represents a major link state change. In a link state change, link state information is propagated across the organization, and all Exchange servers must reroute their messages. Therefore, do not change the routing group master frequently.

 Conflicts Between Routing Group Masters

Only one server is recognized in a routing group as the routing group master. This configuration is enforced by an algorithm in which (N/2) +1 servers in the routing group must agree and acknowledge the master. N denotes the number of servers in the routing group. Therefore, the member nodes send link state ATTACH data to the master.

Sometimes, two or more servers mistake the wrong server as the routing group master. For example, if a routing group master is moved or deleted without choosing another routing group master, msExchRoutingMasterDN, the attribute in Active Directory that designates the routing group master, might point to a deleted server, because the attribute is not linked.

This situation can also occur when an old routing group master refuses to detach as master, or a rogue routing group master continues to send link state ATTACH information to an old routing group master. In Exchange Server 2003, if msExchRoutingMasterDN points to a deleted object, the routing group master relinquishes its role as master and initiates a shutdown of the master role.

Take the following steps to resolve this issue:

• Check for healthy link state propagation in the routing group on port 691. Verify that a firewall or SMTP filter is not blocking communication.
  
• Verify that no Exchange service is stopped.
  
• Check Active Directory for replication latencies, using the Active Directory Replication Monitor tool (Replmon.exe), which is included in Microsoft Windows Server 2003.
  
• Check for network problems and network communication latencies.
  
• Check for deleted routing group masters or servers that no longer exist. In these instances, a transport event 958 is logged in the application log of Event Viewer. This event states that a routing group master no longer exists. Verify this information by using a directory access tool, such as LDP (ldp.exe) or ADSI Edit (adsiEdit.msc). These applications are included in the Windows Server 2003 support tools.
  

 

 

 

Thanks and Regards,
Arun Sabale | L2 tech
+919821129229
Zenith Infotech Ltd.

READ MORE - How Exchange Link State Algorithm (LSA) Works?

Exchange Storage Internal Architecture

 

Exchange Storage Internal Architecture

 

Exchange servers store data in two files: an .edb file and an .stm file. Together, the .edb file and the .stm file form an Exchange store repository. For example, the default mailbox store on an Exchange server uses files named Priv1.edb and Priv1.stm. The default public folder store uses the files Pub1.edb and Pub1.stm. The .edb file contains many tables that hold metadata for all e-mail messages and other items in the Exchange store, in addition to the contents of MAPI messages. The .edb file is an ESE database, and because it is used primarily to store MAPI messages and attachments, it is also referred to as the MAPI-based database. The .stm file, in contrast, stores native Internet content. Because Internet content is written in native format, there is no need to convert messages and other items to Exchange format (as in Exchange 5.5 and earlier). The .stm file is also an ESE database, referred to as the streaming database. The .edb and .stm files function as a pair, and the database signature (a 32-bit random number combined with the time that the database was created) is stored as a header in both files. The internal schema for the .stm pages is stored in the .edb file.

Note:
You can rename the .edb and .stm databases and move them to different directories in Exchange System Manager. Because the .edb and .stm files together create a complete Exchange store repository, you should keep them together and assign them a common name with different extensions (that is, .edb and .stm).

Exchange Server 2003 uses transactions to control changes in storage groups. These transactions are recorded in a transaction log, similar to the way transactions are stored in traditional databases. Changes are committed or rolled back based on the success of the transaction. If there is a failure, you use transaction logs (together with the database files and, in some cases, the checkpoint file) to restore a database. The facility that manages transactions is the Microsoft Exchange Information Store service (Store.exe). Any uncommitted transaction log entries are also considered part of a current Exchange database, as illustrated in the following figure.

Current Exchange Server 2003 database

The following two types of databases are available in Exchange Server 2003:

• Private store databases   These databases store mailboxes and message queues for MAPI-based messaging connectors.
  
• Public store databases   These databases store public folder hierarchies and public folder contents.
  

The following figure illustrates the internal Exchange store architecture. The Microsoft Exchange Information Store service (Store.exe) uses Extensible Storage Engine (ESE) to access the database files in the file system, and provides access to the data through various interfaces, such as MAPIsvr, ExPOP, ExIMAP, ExSMTP, and ExOLEDB. Client application and application programming interfaces, such as Collaboration Data Objects for Exchange (CDOEX), can use these interfaces or communicate with the messaging database (MDB) module.

Exchange store architecture

 Storage Groups

Each storage group is made up of a set of log files and auxiliary files (internal temporary databases, the checkpoint file, and reserve logs) for all the databases (.edb files, .stm files) in the storage group. Exchange Server 2003 supports multiple storage groups and multiple databases in each storage group. In Exchange Server 2003, a single server supports up to four storage groups and a single storage group supports up to five databases. Support for multiple databases enables you to distribute numerous mailboxes and public folders across numerous, smaller databases, thus making database management easier. Exchange 2000 Server and Exchange Server 2003 can support up to 20 mailbox and public folder databases on a single server.

 Storage Group Architecture

As illustrated in the following figure, all storage groups are hosted from the same Store.exe process. Each storage group is represented by an ESE instance.

Storage group architecture

Within each storage group, each .edb and .stm database pair represents a mailbox store or a public folder store. As shown in Figure 10.3, all mailbox and public folder stores in a particular storage group share a common set of log files and other system files. These files enable transaction-oriented processing.

The log files and other system files in each storage group have the following purposes:

• <Log Prefix>xxx.chk   This is the checkpoint file (for example, E00.chk) that determines which transactions require processing to move them from the transaction log files to the databases. Checkpoint files are updated when ESE writes a particular transaction to a database file on a disk. This update always points the checkpoint file to the last transaction that was transferred successfully to the database. This update provides a fast recovery mechanism. However, checkpoint files are not required to commit transactions to databases. ESE has the ability to process transaction log files directly and to determine for itself which transactions have not yet been transferred. This process takes significantly more time than using checkpoints.
  

  Note:
  Extensible Storage Engine guarantees that transactions are not written to a database multiple times.

• Exx.log   This is the current transaction log file for the storage group. Transaction log files give ESE the ability to manage data storage with high speed efficiency. ESE stores new transactions, such as the delivery of a message, in a memory cache and in the transaction log concurrently. The data is written sequentially. New data is appended to existing data without the need for complex database operations. At a later time, the transactions are transferred in a group from the memory cache to the actual databases, which update them.
  By default, the default storage group, named First Storage Group, uses the prefix E00, which results in a transaction log file name of E00.log. The E00.log is used for all mailbox and public stores in this storage group. If you create additional storage groups, the prefix number is incremented to E01, E02, and E03.
  
• <Log Prefix>XXXXX.log   These are transaction log files that have no room remaining for further data. By default, transaction log files are always exactly 5.242.880 bytes (five megabytes) in size. It is theoretically possible to change the log file size, but this is not recommended. When a log is full, it is renamed to allow the creation of a new, empty transaction log file. Renamed transaction log files are named previous log files. The naming format of previous log files is <Log Prefix>XXXXX.log (such as E00XXXXX.log), where XXXXX represents a five-digit hexadecimal number from 00000 to FFFFF. Previous log files reside in the same directories as the current transaction log file.
  
• Res1.log and Res2.log   These are reserved transaction log files for the storage group. Reserved log files are an emergency repository for transactions. They provide enough disk space to write a transaction from memory to the hard disk, even if a server's disk is too full to admit new transactions to a log file. The reserved log files can be found in the transaction log directory. They are created automatically when the databases are initialized. They cannot be created later.
  ESE uses reserved transaction log files only to complete a current transaction process. It then sends an error notification to Store.exe to dismount the Exchange store safely. In the application event log, there is an entry that indicates the issue. In this situation, you should create additional free hard disk space (for example, add a new hard disk) before you mount the database again.
  
• Tmp.edb   This is a temporary workspace for processing transactions. Tmp.edb contains temporary information that is deleted when all stores in the storage group are dismounted or the Exchange Information Store service is stopped.
  

  Note:
  Tmp.edb is not included in online backups.

• <file name>.edb   These are the rich-text database files for individual private or public stores. The rich-text database file for the default private store is named Priv1.edb. The file for the default public store is named Pub1.edb.
  
• <file name>.stm   These are the streaming Internet content files for individual databases. The streaming database file for the default private store is named Priv1.stm. The file for the default public store is named Pub1.stm.
  

 Storage Group Attributes in Active Directory

You can determine the path to a storage group's transaction log file and the log file's name in Exchange System Manager. Right-click the desired storage group, select Properties, and from the General tab, look at the information in the Transaction Log Location and the Log File Prefix fields. Using the Browse buttons, you can move the transaction log and system files to a new location, such as a separate physical drive.

The configuration settings for a storage group are stored in Active Directory. If you want to use ADSI Edit to locate the directory object for a storage group, you must open the configuration naming contacts, expand the services node, then CN=Microsoft Exchange, and then expand the Exchange organization object, administrative group, and server container. Underneath it, you can find a container named CN=InformationStore, which contains the storage groups, such as CN=First Storage Group. The object class for storage group objects is msExchStorageGroup. If you plan to use custom scripts to manage Exchange store resources, you can access msExchStorageGroup objects by using Active Directory Service Interfaces (ADSI).

The following code example demonstrates how to access the default storage group on a server called SERVER01 in an Exchange organization called Contoso. It displays the current path to the transaction log files of that storage group.

strStorageGroupDN = "CN=First Storage Group," _
                  & "CN=InformationStore," _
                  & "CN=SERVER01,CN=Servers," _
                  & "CN=First Administrative Group," _
                  & "CN=Administrative Groups," _
                  & "CN=Contoso,CN=Microsoft Exchange," _
                  & "CN=Services,CN=Configuration," _
                  & "DC=Contoso,DC=com"
Set oStorageGroup = GetObject("LDAP://" & strStorageGroupDN)
MsgBox oStorageGroup.Get("msExchESEParamLogFilePath")

The following are important Exchange attributes of msExchStorageGroup objects that you can use in custom scripts based on ADSI:

• msExchESEParamCircularLog   This is a Boolean flag that determines whether circular logging is enabled or disabled. A value of 0 indicates that circular logging is disabled; a value of 1 indicates that circular logging is enabled.
  Circular logging causes ESE to discard transactions when the committed changes are transmitted to the database file on disk. The checkpoint file indicates which log files and transaction entries are successfully committed to the database. Any existing previous logs are deleted, while transactions in the current transaction log file are marked as obsolete. New transactions eventually overwrite the obsolete entries in the current transaction log before a new log file is created.
  

  Note:

  Through purging of transactions, circular logging reduces consumption of disk space. However, circular logging is not compatible with sophisticated fault-tolerant configurations and several online backup types that rely on the existence of transaction logs. When circular logging is enabled, you can only perform full backups. You cannot perform backups that rely on transaction log files, such as differential or incremental backups. When you recover data, you cannot replay transaction log files, thus you cannot restore data beyond the most recent backup. In contrast, if transactions are not automatically deleted through circular logging, you might be able to recover beyond the most recent backup by replaying transactions that still exist on a hard disk. Although circular logging is enabled by default in Exchange Server 5.5, it is disabled by default in Exchange 2000 Server and Exchange Server 2003.

• msExchESEParamEventSource   This is a language-independent process descriptor string that points to the Microsoft Exchange Information Store service key (MsExchangeIS) in the registry under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services.
  
• msExchESEParamLogFilePath   This attribute determines the path to a storage group's transaction log files, such as C:\Program Files\Exchsrvr\mdbdata.
  
• msExchESEParamLogFileSize   This attribute specifies the log file size in kilobytes (KB). The default value is 5120.This value should never be changed.
  
• msExchESEParamSystemPath   This attribute specifies the path to the check point file, such as C:\Program Files\Exchsrvr\mdbdata, in addition to the path to any temporary databases that might be present.
  
• msExchESEParamZeroDatabaseDuringBackup   This is a Boolean flag that determines whether deleted records and long values are overwritten with zeros during backup operations. A value of 0 indicates that records are not overwritten. A value of 1 indicates that databases are overwritten with zeros.
  
• msExchESEParamEnableOnlineDefrag   This is a Boolean flag that determines whether the Microsoft Exchange Information Store service should perform online defragmentation of databases. A value of 0 indicates no online defragmentation should be performed. A value of 1 indicates online defragmentation should be performed during scheduled maintenance cycles.
  

  Note:
  Online defragmentation frees space in the databases but does not reduce the size of the database files. Database inconsistencies are corrected during every start and shutdown of the server in a process referred to as soft recovery.

• msExchESEParamEnableIndexChecking   This is a Boolean flag that determines whether the operating system version is checked for Unicode indexes. A value of 0 indicates that index checking is not performed. A value of 1 indicates that index checking is performed. This parameter detects changes in the operating system that result from upgrading to a newer version or from applying a service pack. This flag determines whether the sort order for Unicode has changed. Whenever the operating system is changed in this manner, re-indexing occurs automatically.
  
• msExchESEParamBaseName   This attribute specifies the base name for the log files in this storage group. For example, a base name of E00 results in a transaction log file name of E00.log.
  
• msExchESEParamDbExtensionSize   This attribute specifies the database extension size, in pages. The default value is 2 megabytes (MB).
  
• msExchESEParamPageTempDBMin   This attribute specifies the minimum size of the temporary database, in pages. The default value is 0.
  
• msExchESEParamCheckpointDepthMax   This attribute specifies the preferred (not hard) maximum checkpoint depth, in bytes.
  

 Storage Group Minimum Disk Space Requirements

Each storage group consumes about 50 MB of free disk space. The files listed above that are required by the storage group use a minimum of 11 MB of disk space. The minimum disk space for private and public stores is 5 MB and 8 MB, respectively. Although the total disk space used is about 24 MB, extra disk space is also needed for the actual creation of the storage group and for read and write operations.

When working with storage groups, remember the following:

• A server running Exchange Server 2003 can have up to five storage groups. Because one of the storage groups is reserved for database recovery operations, only four storage groups can be used to hold databases that are accessible by clients. Attempts to create more than four storage groups result in an error message.
  
• You can create only five databases in a storage group. Attempts to create more databases result in an error message.
  

 Exchange Store Databases

Exchange Server uses ESE as an embedded database engine that determines the structure of the databases and manages memory. The database engine caches the databases in memory by transferring four-kilobyte chunks of data (pages) in and out of memory. It updates the pages in memory and writes new or updated pages back to the disk. When requests come to the system, the database engine can buffer data in memory, so that it does not have to access the disk constantly. This makes the system more efficient, because writing to memory is approximately 200,000 times faster than writing to disk. When users make requests, the database engine starts loading the requests to memory and marks the pages as dirty. A dirty page is a page in memory that contains data. These dirty pages are later written to the Microsoft Exchange Information Store service databases on disk.

Although caching data in memory is the fastest and most efficient way to process data, it means that while Exchange is running, the information on disk is never completely up-to-date. The latest version of the database is in memory, and because many changes in memory are not on disk yet, the database and memory are not synchronized. If there are any dirty pages in memory that have not been transferred and written to disk, the databases are flagged as inconsistent. Exchange databases are synchronized only when all dirty pages in memory are transferred to disk. This happens when you properly shut down the Microsoft Exchange Information Store service. During the shutdown process, the Microsoft Exchange Information Store service flushes all pages to disk.

 MAPI Database File

The Exchange Server 2003 MAPI database file contains the tables that hold the metadata for all e-mail messages, other objects in the database, and the contents of MAPI messages. Every folder displayed in Microsoft Office Outlook is a separate database table in the Exchange store. Every sort order used to view these folders is represented by a separate index on that table. The Store.exe process manages these sort orders.

Messages from MAPI clients, such as Outlook, are stored in the MAPI database, just as they were stored in previous versions of Exchange Server. MAPI-based clients can then access these messages without conversion. However, if an Internet protocol-based client attempts to read a message in this database, the message is converted to the requested format.

The traditional .edb file and its accompanying .stm file are a single unit. One of these files is of little use without the other file. It is important to understand that a single database in the Microsoft Exchange Server Information Store service contains two files, the .edb file and the .stm file.

A record in the .edb file contains a column (of data type JET_coltypSLV) that references a list of pages in the streaming file that contains the raw data. Space usage (maximum of four kilobytes of page numbers) and checksum data for the data in the streaming file is stored in the .edb file.

 Streaming Database File

Exchange Server 5.5 and earlier store messages in message database encapsulated format (MDBEF). This is the native format for Outlook clients. When a non-MAPI client requests a message, the Microsoft Exchange Information Store service converts the contents from MDBEF to the appropriate format, based on what the client requests. This conversion consumes processor bandwidth and slows server performance.

Later versions of ESE enable Internet messaging clients to store raw data in native format. The repository for this raw data is referred to as the streaming database, or simply the streaming file. The streaming file has no balanced tree (B-tree) overhead. Instead, it contains two four-kilobyte pages of header information and then raw data in four-kilobyte pages. This flat data structure is designed for binary large objects (BLOBs) of data that are unlikely to need content conversion and that can be received and transmitted very quickly.

 Property Promotion

Property promotion determines where data is stored in an ESE database and is therefore an important concept to understand. The Microsoft Exchange Information Store service supports the property promotion of data held in the .stm file to the .edb file. Property promotion enables folder views and indexes to be maintained efficiently. For example, a message streamed to the .stm file has its properties, such as sender, subject, and date sent and received, promoted to the records representing the message in the .edb file.

When a MAPI client, such as Microsoft Outlook, submits a message to the Microsoft Exchange Information Store service, the contents of that message are stored in the .edb file. If a non-MAPI client opens the message, the Microsoft Exchange Information Store service does an immediate conversion of the MAPI content to Internet format by performing some of the conversion and calling IMAIL, which in turn calls RTFHTML, to complete the conversion. None of this conversion is persistent, meaning that data is not moved out of the .edb file and written to the .stm file.

If an Internet client submits a message to the Microsoft Exchange Information Store service, the contents of that message are stored in the .stm file. Certain headers from the Internet message are duplicated to the .edb file, so the Microsoft Exchange Information Store service can find the message. This is referred to as a state 0 conversion.

If any client asks for a property, such as PR_Subject, or one of its many aliases, then the Microsoft Exchange Information Store service promotes all of the Internet message's header information to Properties. This is referred to as a state 1 conversion.

If any client asks for attachment information, then the Microsoft Exchange Information Store service creates a near duplicate (in MAPI form) of the Internet message. At first, the message is still in the .stm file. However, much of the data needed for MAPI access is in the .edb file. If a client alters the message in a way that changes the Multipurpose Internet Mail Extensions (MIME), then the .stm file version of the message is discarded and the .edb file of the message is preserved. This is referred to as a state 2 conversion.

Regardless of how a message is submitted to the Microsoft Exchange Information Store service, if Exchange Server receives Internet content that includes Application/ms-tnef content, the message initially goes to the .stm file, but it is then immediately decoded and moved to the .edb file. The same applies to messages with a winmail.dat attachment, encoded using UUEncode. Transport neutral encapsulation format (TNEF) and Winmail.dat are encapsulation methods for MAPI messages to preserve MAPI properties on transports that do not support MAPI. Therefore, the general principal that MAPI messages reside in the .edb file and Internet messages reside in the .stm file is correct. The current functionality has the TNEF decoded before any one of the MAPI properties are read.

 

 

Thanks and Regards,
Arun Sabale | L2 tech
+919821129229
Zenith Infotech Ltd.

READ MORE - Exchange Storage Internal Architecture

Find courses detail after SSC , HSC, BA, Bcom, B sc , Be, Bed, Ded, m tech, b tech, Msc, m com, Ma, LLB, MBA, MCA, CA , Also Entrance Exams Detail and schools colleges offering the courses

A.D.P.M.

General

A.M.Ae.S.I

Aeronautical Engineering

A.M.I.E

Chemical Engineering	Civil Engineering
Electrical Engineering	General Branch of Engineering Subjects	Mechanical Engineering	Section A

A.M.I.E.T.E

Computer Science & Engineering

Electronics & Tele Communication Engineering

Information Technology

AMFI Advisor Module

AMFI

B. Pharm

Anatomy, Psyology, Pharm.Engg.BasicComputer,Maths

B.A

General	Audiology and Speech Language Pathology	Arabic
Bengali	Computer Science	Drawing & Painting	Economics
English	English Special	Environmental Studies	General Forestry
Geography	Gujarati	Hindi	History
Home Science	Indian Heritage and Culture	International Hospitality Administration	Journalism
LL.B	Malayalam	Mass Communication and Video Production	Music
Optional English	Optional Kannada	Pali	Performance arts
Philosophy	Political Science	Population Studies	Psychology
Public Administration	Sanskrit	Social Science	Social Work
Sociology	Tamil	Tourism Studies

B.B.A

General
IT	LL.B

B.B.M

General

B.C.A

General

B.Com

General	Computer Science	Corporate Secretaryship	English & Business Communication

B.Des

Communication Design	Fashion Communication	Fashion Design	Product Design

B.E

General	Printing Technology	Aeronautical Engineering	Automobile
Biomedical engineering	Chemical	Civil	Civil and Structural
Computer Science	Digital Electronics	Electrical and Electronics	Electronic Instrumentation and Control
Electronics and Communication	Electronics and Microprocessors	Engineering Chemistry	Engineering Graphics.
Engineering Physics	Environmental Engineering	Geo Informatics	Industrial Bio Technolgy
Industrial Production	Information Science	Information Technology	Instrumentation and control engineering
Manufacturing Processes and Automation Engineering	Marine engineering	Mechanical	Mechatronics
Metallurgy	Mining	Production Engineering	Tele Communication
Textile Technology

B.Ed

General	English	Hearing & Impaired
Tamil	Yoga

B.Sc

Agriculture	Appropriate Technology
Bio-Chemistry	Bio-Technology	Botany	Chemical Technology
Chemistry	Computer hardware	Computer Science	Computer Technology
Digital Art, Classical animation - 3D	Economics	Electronic Media	Electronic Science
Electronics Equipment Maintenance	Engineering	Fashion Design	Food Science & Management
General	Genetics	Geology	Home Science
Hotel Management & Tourism	Industrial Chemistry	Industrial Microbiology	Information Technology
Interior Design	Mathematics	Microbiology	Nautical Science
Nursing	Nutrition and diet	Physics	Physiology
Polymer Chemistry	Psychology	Statistics	Textile Design
Visual Communication	Zoology

B.Tech

General	Aeronautical
Agricultural Engineering	Applied Electronics and Instrumentation	Architecture	Automobile Engineering
Bio Informatics	Bio medial instrumentation	Bio-Engineering	Biotechnology
Ceramic Technology	Chemical engineering	Civil Engineering	Computer Science & Engineering
ECM	Ecommerce	Electrical and Electronics Engineering	Electrical Engineering
Electronics	Electronics & Communications Engineering	Electronics & computers	Electronics and Biomedical Engineering
Electronics and Tele-Communication Engineering	Food and Process	Genetic Engineering	Industrial and Production
Industrial BioTechnology	Industrial Engineering	Industrial Production Engineering	Information Technology
Leather Techonology	Marine Engineering	Mechanical Engineering	Mechatronics
Metallurgy & Material Technology	Operating Systems	Petroleum Technology	Plastic and Polymer
Production	Regular	Safety and Fire Engineering	Textile Engineering
Thermal	Water Resources

BCT&CA

Catering Technology & Culinary Arts

Biology

General

C.A

General

Accounts

Certification

Microsoft Certified Professional Developer	Soil Ecology, Earthworms
: Indian . Chinese , Tandoor , Continental , Pastr	Actuarial Science	Advance Company Law and Practice	Automobile Technology
C.L.I.S.	CCP	Certified Financial Planner	CIC
Cisco Certified Network Associate	Computer Engieering	Computer Science	Computer Technology
Computing	Craft Programme in Front Office Management	CWA/ICWA	English
Finance	Fitter	Food & Nutrition	Forex
Foundation Programme (E.M. and T.M.)	HIV and Family Education	Human resource management	Industrial design , Communication Design
Master of Library and Information Science	Mewati language	Microsoft Certified Application Developers	Microsoft Certified Architect Program
Microsoft Certified Database Administrators	Microsoft Certified Learning Consultant	Microsoft Certified Solution Developers	Nursery Teacher Training
Office Management	Offset Machine Printing	Pre nursery	SELF HELP GROUP MANAGEMENT
Soil Ecology, Earthworms	Subtile Energy	TES	TML
Vascular and Inverventional Neuroradiology	VLSI Design	Womens Empowerment and Development

Diploma

General
Cruise Galley Operations	Embedded System and VLSI	Accounting & Finance	Acting
Actuary	ADITM	Advanced Diploma in Business Administration	Advanced Level Course In Computer Science
Agri Business Management	Anaesthetics	Animation	Apparel Mfg Tech
Application Oriented Course	Applied Electronics	Aquaculture Management	Architectural Assistantship
Architectural Engineering	Art for Drawing Teachers	Automobile Engineering	Banking & Financial Management
Bio-informatics	Bio-Medical Engineering	Bio-technology	Biopesticides Tech & Biofertilizer Tech
Business Administration	Business Management	Ceramic Technology	Chemical Engineering
Chemical Process Instrumentation and Control	Civil Engineering	Commercial Floriculture	Commercial Practice
Computer Applications	Computer Engineering	Concrete Technology & Design of Concret	Construction Management
Corrosion	CRAFT PROGRAMME	Craft Programme in Front Office Management	Craft Programme in House Keeping
Criminology and Forensic Science	Critical Care Nursing	Damage Assessment, Repair & Rehabilitation	DGO
Diabetes Patient Education	Diploma in Early Childhood Care and Education	Diploma in English	Diploma in Hindi
DMRD	Drives and Control	E.N.T	Electrical and Electronics
Electronics & Video Engineering	Electronics and Communication	Embedded Systems and Applications	Energy Engineering
Engineering Technician	English Journalism	English Language Teaching	Entrepreneurship
Environmental Management	Fabrication Engineering	Fashion Design	Financial Management
Food & Beverages Production	Food & Nutrition	Food Preservation Technology	Footwear Technology
Foreign Trade	Front Office Management	Garment Fabrication Technology	General Nursing
graphic and multimedia	Guidance and Counselling	Health Science in Accident & Emerge	Health Science in Acupuncture
Health Science in Diabetology	Health Science in Echo-Cardiography	Health Science in Family Medicine	Health Science in Medical Cosmetolo
Health Science in Medical Law	Health Science in Public Health	Health Science in Tobacco Control	Health Science in Ultrasonography
HIV and Family Education	Home science	Horticultural Nursery Management	Hospital Management
Hotel Management	House Keeping	Human Resource Mgt	Industrial Bio-technology
Industrial Electronics	Industrial Hygiene	Industrial Safety	Information Technology
Instrumentation & Control Engineering	Insurance Management	International Business	International English Language Testing System
Isaikalaimani	Jewellery manufacturing	Journalism & Mass Communication	Knitware Mfg & Mgt
law of taxes	Leather Technology	Library Automation & Networking	Livestock Products Technology
Management Executive	Marine Electrical	Marine Engineering	Marine Mechanical
Marine Microbial Technology	Marketing Management	Mass Communication	Material Management
Mechanical Engineering	Medical Electronics	Medical Laboratory Technology	Metallurgical Engineering
Mgt. Accounting	Mineral Exploration and Mining	Mining Engineering	Modern Office Management
N.G.O. Management	Natural Language Processing	Natural Resources	Nautical Science
Nutrition and Health Education	Operation Theatre Techniques	Operations Management	Ophthalmology
Orthopaedics	Packing Technology	Pathology	Pediatrics
Petroleum Exploration	Petroleum Refining	Pharmacy	Plant Protection
Plastic Engineering/Technology	Printing Technology	Production Engineering	Production Management
Production Technology	Programming	Promoting Rational Drug Use	Public Administration
Public Relations	Quality Management	Quantity Surveying and Valuation	Radio Diagnosis
Rural development	Security Management	Skin	Sociology of Health
Software Based Statistical Analysis	Software Marketing	Sugar Technology	Textile Design
Textile Technology	Tools & Die Making	Tourism Management	Value Added Products from Fruits
VLSI Design	Waste Management	Welding Engineering & Technology	Yoga
Youth & Dev. Wor

DOEACC

General	A Level	B Level
C Level	O Level

Entrance Exams

Gate Entrance Exam	IIT Entrance Exams
International General Certificate of Secondary	Management Aptitude Test (MAT)	Other Entrance Exams

IAS

Mains

Preliminary

LL.M

General	Constitutional & Administrative Law	Corporate & Securities Law
Labour Laws	LL.B	LL.D	Torts & Crimes

M.A

General	Audiology and Speech Language Pathology	International Relations	Philosophy and Religion
Advertisement and Public Relations	Applied Psychology	Arabic	Broadcast Communication
CC and E	Criminal justice	Economics	English
Gandhian Thought	Hindi	History	History and Tourism Management
Hospital Administration	Indian Economy	Linguistics	M.W.S.(Women's Studies)
Malayalam	Mass Communication and Journalism	Media Management	Mewati
Music	Philosophy	Police Administration	Political Science
Population Studies	Psychology	Public Policy	Quantitative Analysis & Comp Applications
Rural Development	Sanskrit	Social Work	Sociology
Tamil	Tourism Management	Vedanta

M.B.A

General
Business Administration	Business Policy and Strategic Management	Chemical Sales & Marketing Management (CSMM)	Commonwealth Executive Programme
Executive	FINANCE, HUMAN RESOURCES, MARKETING, BANKING	Financial Management	Human Resource Management
International Business	International Management	Investment Management	Management of Information Systems
Managerial Economics	Marketing Management	Operations Management	Research methodology for Management Decisions
Software Enterprise Management(SEM)

M.B.B.S

General

Medicine

M.C.A

General
c++, Java, HTML,soft. Engg., Graph theory, As/400,	Computer	Computer Aplications

M.Com

Accounting and Finance
Banking	Commerce	Finance and Control	Insurance Management
Marketing

M.D

General	Anesthesiology	Bio-Chemistry
Community Medicine	ForensicMedicine	GENERAL	General Medicine
Micro-Biology	O.B.G	Ophthalmology	Pathology
Pediatric Medicine	Pharmacology	Physiology	Psychiatry
Radio Diagnosis	Radio Therapy

M.E

General	Power Electronics and Drives
Communication System	Computer Aided Design	Computer Integrated Manufacturing	Computer Science
Computer science and Engineering	Construction Engineering and Management	Electrical & Electronics	Electronics and Control Engineering
Electronics and Telecommunications	Engineering Design	Environmental Engineering	Information Technology
Manufacturing Enginnering	Mechanical Engineering	Optical Communication	Power System Engineering
Structural Engineering	Thermal Engineering

M.Ed

Education

M.F.N

Financial Management

M.Phil

General	PSYCHOLOGY	Bio Technology	Botony
Commerce	Computer Science	Corporate Secretaryship	Economics
Education	English	Entrepreneurship	Gandhian Thought
History	International Business	Kannada	Library and Information Science
Management	Mathematics	Physical Education	Police Administration
Political Science	Public Administration	Research Methodology	Sanskrit
Satistics	Social Work	Sociology	Tourism
Zoology

M.Sc

Applied Electronics	Applied Psychology	Bio Chemistry
Bio Informatics	BioTechnology	Botony	Business Economics
Chemistry	Computer Science	Costume Design and Fashion	Diatetics
Electronic Science	Environmental Science	Food Chemistry	Genetical science
Geo-Informatics	Hotel Management	Information Science	Information Technology
Mathematics	Microbiology	Pharmacology	Physics
Physiology	Psychology	Software Engineering	Statistics
Total Quality Management	Tourism	Zoology

M.Tech

Aerospace Engineering
Applied Electronics and Instrumentation	Building Automation	chemical engineering	Civil
Computer Aided Structural Engineering	Computer Science	Control Systems	Digital Communications
DIGITAL ELECTRONICS	Electrical machines	Electronics and Communication Eng	Embedded Systems
Environmental Engineering	Geotechnical	Guidance and Navigation Controll	Hydraulics Engineering
Industrial Engineering	Information Systems	Machine Design	Mechanical
Mechatronics	Microwave and TV	Mineral Processing	Power Systems
Process Control	Production & Industrial Engineering (Mechanical)	Propulsion Engineering	Signal Processing
Structural Engineering	Thermal Power Engineering	Thermal Science	Traffic and Transportation
VLSI system design

MS

Aerospace Engineering	Anatomy	E.N.T
Education Management	Electronics and Communication Engineering	General Surgery	Ophthalmology
Orthopedic	Software Engineering

Other Bachelor's Degree

General	General
General	B.R.Sc.Rehabilitation Science	B Level Computer Application	B Level Computer Science
B.A.L	B.A.M.S	B.Arch	B.B.L
B.L.I.Sc.	B.Pharm	B.S.M.S	Bachelor of Dance
Bachelor of Dental Surgery	Bachelor of Developer Information Technology	Bachelor of Hotel Management and Catering	Bachelor of Information Technology
Bachelor of Physiotherapy	Civil services	ICSI

Other Master's Degree

M.B.M
M.C.S.	M.DS	M.H.R.M.	M.I.M
M.L.I.S	M.Pharm	Master In Computer Management - M.C.M	Master in Marketing Management
Master in Personnel Management	Master of Arts in Distance Education	Master of Finance and Control Programme	Master of Hospital Administration
Master of Labour Management	Master of mass communication	Master of Social Work (M.S.W)	Masters in Tourism Management
Microsoft Certified Trainers	MWS Women Studies

P.U.C

Economics	English
History	Physics, Chemistry, Maths & Biology	Political Science	Sociology

Ph.D

General	Aerospace Engineering	Bio-Technology	Botany
Chemical Engineering	Civil Engineering	Clinical Neurosciences	Commerce
Computer Science Engineering	Electrical and Electronics Engineering	Electronics and Communication Engineering	Energy Systems
Mechanical Engineering	Mental Health and Social Psycology	Metallurgy	NeuroPhysiology
Pharmaceutical sciences	Planning and Architecture	Polymer Science & Technology	Power Electronics
Social Science	Speech Pathology and Audiology

Physics

General

Post Graduate Diploma

General
Computer Aided Design of Concrete structures	Accounting Software	Advertising and Public Relation	Audio Programme Production
Bakery science and technology	Bank management	Broadcast Mangement and Journalism	Broadcasting and Journalism
Business Administration	Business Management	Community Cardiology	Computer Application
Computer Science & Management	Criminology and Forensic Science	Dairy Technology	Digital Instruments
Disaster Management	Electrical Energy Management and Energy Audit	Electrical Safety and Safety Management	Electronics and Instrumentation
English Literature	Environment Management	Financial Management	Financial Reporting & Control
Fire Protection & Industrial Safety Enginering	GERIATRIC MEDICINE	Ground Water Exploration	Guidance and Counselling
Health Science in Accident and Emergency Care	Health Science in Acupuncture	Health Science in Adolescent Health Care	Health Science in Diabetology
Health Science in Echo-Cardiography	Health Science in Family Medicine	Health Science in Maternity and Neonatal Care	Health Science in Medical Cosmetology
Health Science in Medical Law and Ethics	Health Science in Public Health	Health Science in Tobacco Control	Health Science in Ultrasonography
Hospital Management	Hotel Management	HR Management	Information Technology
Insurance Management	Journalism & Mass Communication	Library Automation and Networking	Management
Marketing Management	Material Management	Material Science	Maternal & Child Health
Media management & TV production	Mineral Exploration and Mining	NATURAL LANGUAGE PROCESSING	Natural Resources
NGO Management	Personnel Management Amd	Pharmacy Practice and Drug Store Management	Piping Design & Engineering
Power Plant Instrumentation and Control	Promoting Rational Drug Use	Public Relations	Quantity Surveying and Valuation
Retail Marketing	Sports Management	Supply chain & operations management	Technology Management
Tourism Management	Transport management	VLSI Design	Yoga

School Level Courses

Bachelor of General Law

Biology

English

School Level Courses

First Year Junior College (F.Y.J.C)

School Level Courses

H.Sc	Intermediate of Arts	Intermediate of Science	Maths
Matric	Physics	Pre-degree Maths/Physics/Chemistry

READ MORE - Find courses detail after SSC , HSC, BA, Bcom, B sc , Be, Bed, Ded, m tech, b tech, Msc, m com, Ma, LLB, MBA, MCA, CA , Also Entrance Exams Detail and schools colleges offering the courses