Exchange server 2007 BackEnd services functions

Exchange Services in Exchange 2007 and it’s functions
In this article you will see the description on Exchange 2007 Services which are responsible for Client Access Server, Hub Transport Server, Mailbox Server, Edge Server and Unified Messaging.
This article is purely published on the basis of event triggered from my virtual lab. Event id whatever you see in your production environment may vary compare to this however the function of each service will remain the same.
1) Microsoft Exchange Active Directory Topology : This service is responsible to provide the information of Active Directory Information to Exchange Server Components. This service need to be started on the client Access Server, Hub Transport Server, Mailbox Server and Unified Messaging Server. It doesn’t depend on dependency in order to start. However there are some other Exchange Services which are dependent on this service.
The following are the services which are dependent on this service are as follows:a. Microsoft Exchange Transport Log Search
b. Microsoft Exchange Transport
c. Microsoft Exchange Service Host
d. Microsoft Exchange Search Indexer
e. Microsoft Exchange Replication Service
f. Microsoft Exchange Mail Submission
g. Microsoft Exchange Mailbox Assistants
h. Microsoft Exchange File Distribution
i. Microsoft Exchange EdgeSync
j. Microsoft Exchange Anti-spam Update
Who is responsible to execute this service : "MSExchangeADTopologyService.exe"
Path from where it is executed : "C:\Program Files\Microsoft\Exchange Server\Bin\MSExchangeADTopologyService.exe"

Functions:
• It will help the Exchange Server component to get the list of domain controllers, global catalogs server & Configuration Domain Controllers which needs to be used.
• It will help the Exchange Server Component to discover the following server like the server name, their roles, reachability, synchronize status, GC capable, PDC, SACL Rights, Net-logon etc which are in the site and the servers which are out of site.
Event Id : 2080 & 2081
2) Microsoft Exchange Monitoring :
This service is installed on Exchange Server Role as part of installation. This service is optional and set to manual. This service will not depend on any other service.

Who is responsible to execute this service : “Microsoft.Exchange.Monitoring.exe"

Path from where it is executed : "C:\Program Files\Microsoft\Exchange Server\Bin\Microsoft.Exchange.Monitoring.exe"
Functions:
Provides a remote procedure call (RPC) server that can be used to invoke diagnostic cmdlets. This service does not have any dependencies.
Event ID : 700 & 701
3) Microsoft Exchange File Distribution Service :
This service is responsible for distribution offline address book and custom unified messaging prompts. This is a required service for client Access Server & Unified Messaging Server. It is dependent on Workstation & Microsoft Exchange Active Directory Topology Service.

Who is responsible to execute this service: MSExchangeFDS.exe

Path from where it is executed : "C:\Program Files\Microsoft\Exchange Server\Bin\MSExchangeFDS.exe"
Functions:This will help the client access server to give the synchronization status of OAB like it will give the details OAB is synchronized successfully or not. And the name of the OAB.
Event Id: 1008
4) Microsoft Exchange IMAP4 :
This service will get installed on Client Access Server Role. It is an optional which is set to manual. Service name for this service is MsExchangeIMAP4. This service is dependent on Microsoft Exchange Active Directory Service.

Who is responsible for this service : "Microsoft.Exchange.Imap4Service.exe"
Path from where it is executed : "C:\Program Files\Microsoft\Exchange Server\ClientAccess\PopImap\Microsoft.Exchange.Imap4Service.exe"

Functions:
It provides the IMAP4 access to IMAP4 Client.

Event Id: 2080 (First this service will information about GC DC, synchronize status, PDC, SACL Rights etc from Microsoft Exchange Active Directory Topology
Event Id: 1000 (This will provide the status of IMAP4 service whether it is getting start)
Event Id : 1001 (Final status of the IMAP4 Service)
5) Microsoft Exchange POP3 : This service will get installed on Client Access Server Role. It is an optional which is set to manual. Service name for this service is MsExchangePOP3. This service is dependent on Microsoft Exchange Active Directory Service.

Who is responsible for this service : "Microsoft.Exchange.Pop3Service.exe"

Path from where it is executed : "Server\ClientAccess\PopImap\Microsoft.Exchange.Pop3Service.exe"

Functions:
It provides the POP3 access to POP3 Client.

Event Id: 1000 (This will provide the status of POP3 service whether it is getting start)
Event Id : 1001 (Final status of the POP3 Service)
6) Microsoft Exchange Service Host : This service will get installed on Client Access Server & Mailbox Server. It is a required service which needs to be started and running all the time. This service is dependent upon “Microsoft Exchange Active Directory Topology Service”.

Who is responsible for this service : "Microsoft.Exchange.ServiceHost.exe"

Path from where it is executed : "C:\Program Files\Microsoft\Exchange Server\bin\Microsoft.Exchange.ServiceHost.exe"
Functions:This service will get the information about GC, DC and synchronization & online status of the AD Servers from Microsoft Exchange Active Directory Service
It will initially check the server role which is installed on the server where it is running like if you have installed MBX, CAS & HUB on the same server it will give the status of all the server role and if you have just installed CAS it will give only CAS Server role installed information.
If it is just a cas server role then it will load RPC over https autoconfig dll i.e Microsoft.Exchange.RPCOverHTTPAutoconfig.dll and for Mailbox Server : Microsoft.Exchange.SystemAttendantMailboxServicelet.dll

Event Id : 2080, 2003, 2014, 2016, 2018, 2001 & 2004
7) Microsoft Exchange EdgeSync :
This service is installed on the Hub Server. It is a required service which needs to be started and running all the time. It is dependent upon “Microsoft Exchange Active Directory Topology Service”.

Who is responsible for this service : " Microsoft.Exchange.EdgeSyncSvc.exe"
Path from where it is executed : "C:\Program Files\Microsoft\Exchange Server\Bin\Microsoft.Exchange.EdgeSyncSvc.exe"

Functions:
This service will help the hub server to get synchronized with Edge Server by connecting to ADAM instance on the Edge Server through LDAP.
Event ID : 1059
8) Microsoft Exchange Anti-spam Update : This service is installed on Hub Server & Edge Server. It is an optional service. In Hub Server, this service is dependent on “Microsoft Exchange Active Directory Topology Service” and in Edge Server, this service is dependent on “Microsoft Exchange ADAM".

Who is responsible for this service : "Microsoft.Exchange.AntispamUpdateSvc.exe"
Path from where it is executed : "C:\Program Files\Microsoft\Exchange Server\Bin\Microsoft.Exchange.AntispamUpdateSvc.exe"
Functions:
It is used to automatically download anti-spam filter updates from Microsoft Updates.
Before it initialize the service it will contact the AD topology service for getting the information of AD Servers if it is a hub server and if it is edge server it will contact ADAM for getting the access information.
Event ID : 1000
9) Microsoft Exchange Transport : This service is installed on Hub Transport Server and Edge Transport Server. This service is dependent on “Microsoft Exchange Active Directory Topology Service” for Hub Server & In Edge Server “Microsoft Exchange ADAM.

Who is responsible for this  service : " MSExchangeTransport.exe"

Path from where it is executed : "C:\Program Files\Microsoft\Exchange Server\Bin\MSExchangeTransport.exe"

Functions:It is responsible for mailflow.
It will give the SMTP Server information and transport stack.
This will even load the transport rule collection, configuration update for transport, content filter in another word Filtering components.
Event ID : 1000, 102, 16022, 4002, 7004, 1001, 2000, 300, 301, 302 & 17010
10) Microsoft Exchange Transport Log Search :
 This service is installed on the Hub Server, Edge Server and Mailbox Server Role. This is an optional service set to manual only on Edge Server. This service is dependent on “Microsoft Exchange Active Directory Topology Service” on Mailbox and Hub Server. For Edge Server it is dependent on “Microsoft Exchange ADAM”

Who is responsible to start this service : " MSExchangeTransportLogSearch.exe"
Path from where it is executed : "C:\Program Files\Microsoft\Exchange Server\Bin\MSExchangeTransportLogSearch.exe"
Functions:
Message Tracking logs are generated.
Transport logs searching.
Event id : 7001 & 7002
11) Microsoft Exchange Information Store :
This service is installed on Mailbox Server Role. It is a required service which needs to be running all the time. It is dependent upon eventlog, NT LM Security Support Provider, RPC, Server & Workstation.

Who is responsible for this service : "store.exe"

Path from where it is executed : "C:\Program Files\Microsoft\Exchange Server\bin\store.exe"
Functions:
It is main core for Mailbox server, it manage the exchange server database
It is responsible to initialize OLEDB
The Microsoft OLE DB Provider for Exchange exposes data stored in a Microsoft Exchange Web Store in tabular form. This data can be queried using an SQL-like language that is similar to the SQL subset supported by the OLE DB Provider for Microsoft Indexing Service
It is responsible to initialize calendaring agent
It is responsible to  mount the database
12) Microsoft Exchange Mail Submission Service :
This service is installed on Mailbox Server Role. It is a required service which needs to be running all the time. It is dependent upon “Microsoft Exchange Active Directory Service”

Who is responsible for this service: “MSExchangeMailSubmission.exe"
Path from where it is executed : "C:\Program Files\Microsoft\Exchange Server\Bin\MSExchangeMailSubmission.exe"
Functions:
When the message is sent by users, the mail will first move to outbox folder in outlook and then move to sent items, that means it is delivering the message. This is the service who is responsible to send mail from Mailbox Server to Hub Server.
Event Id : 1000
13) Microsoft Exchange Mailbox Assistants : This service is installed on Mailbox Server Role. It is a required service which needs to be running all the time. It is dependent upon “Microsoft Exchange Active Directory Service”

Who is responsible for this service : “MSExchangeMailboxAssistants.exe"
Path from where it is executed : "C:\Program Files\Microsoft\Exchange Server\Bin\MSExchangeMailboxAssistants.exe"

Functions:It is responsible to initiate the function for Resource Booking, Out of Office, Calendaring and Managed Folder Assistants.
Event Id : 1004 and 1001
14) Microsoft Exchange Replication Service : This service is installed on Mailbox Server Role. It is a required service which needs to be running all the time. It is dependent upon “Microsoft Exchange Active Directory Service”

Who is responsible for this service : “Microsoft.Exchange.Cluster.ReplayService.exe"
Path from where it is executed : "C:\Program Files\Microsoft\Exchange Server\bin\Microsoft.Exchange.Cluster.ReplayService.exe"

Functions:It is responsible for log shipping where the LCR and CCR is enabled
Event id: 2018, 2001 & 2133
15) Microsoft Exchange Search Indexer :
 This service is installed on the mailbox server. It is an optional service which is dependent upon “Microsoft Exchange Active Directory topology Service” and “Microsoft Search”

Who is responsible for this service : " Microsoft.Exchange.Search.ExSearch.exe"
Path from it is executed : "C:\Program Files\Microsoft\Exchange Server\Bin\Microsoft.Exchange.Search.ExSearch.exe"

Functions:It is responsible to provide the indexing information to “Microsoft Search (Exchange Server) service.
Event id: 0 & 1003
16) Microsoft Search (Exchange Server) :
 This service is installed on Mailbox Server role. It is an optional service which is dependent upon “Remote procedure call (RPC) service”.

Who is responsible for this service : msftesql.exe
Path from where it is executed : "C:\Program Files\Microsoft\Exchange Server\bin\msftesql.exe"
Functions: It create full-text indexes on content and properties of structured and semi-structured data to allow fast linguistic searches on the exchange data.
Event id: 1003
17) Microsoft Exchange System Attendant : This service is installed on Mailbox Server. It is a require service which needs to be running all the time. This service is dependent up on Event Log, NT LM Security Provider, Remote Procedure Call (RPC), Server and workstation

Who is responsible for this service : " mad.exe"
Path from where it is executed : "C:\Program Files\Microsoft\Exchange Server\bin\mad.exe"
Functions:
It is responsible to initialize the AD Server access detail i.e DSACCESS.dll
It is responsible to initialize the IIS access details i.e DSProxy.dll
It is responsible to initialize ABV_DG.Dll for generating OAB.
It is responsible to initialize madfb.dll for Free Busy Information and in the background it will start the Microsoft Exchange Free Busy Publishing Service
It will generate OAB, oabgen.dll
It manage NSPI Proxy listen port on transport Rpc/HTTP is being overridden by registry setting System\CurrentControlSet\Services\MSExchangeSA\Parameters\Rpc/HTTP NSPI Port. NSPI Proxy will listen on port 6004 on this transport.
Note : Many of the responsible of SA is almost same like we had in Exchange 2003. This service will perform all the above actions if you have public folder store and older outlook version i.e mixed environment. It is not necessary all the service will process the information but it will start the function on Mailbox Server for older version.
Event Id : 1000, 9007, 2068, 9006, 9008, 9013, 9012, 9242, 9410, 9411, 8192, 9316, 9014, 9091, 9070 & 9028
18) Microsoft Exchange ADAM :This service is installed on Edge Server. It is a required service which needs to be running all the time and it is dependent on Com+ Event System

Who is responsible for this service : dsamain.exe
Path from where it is executed : C:\WINDOWS\ADAM\dsamain.exe

Functions:
It will store the Configuration partition information of Active Directory.
It will also store the recipient mailbox data information.
Event id :100
19) Microsoft Exchange Credential Service :
This service is installed on Edge Server. It is required service which should be running all the time and it is dependent on Microsoft Exchange ADAM.

Who is responsible for this service : "EdgeCredentialSvc.exe"

Path from where it is executed : "C:\Program Files\Microsoft\Exchange Server\Bin\EdgeCredentialSvc.exe"

Functions:
It keeps the track of any credential changes on ADAM.
It will update the credential changes on Edge Transport.
20) Microsoft Exchange Speech Engine : This service is installed on Unified Messaging Server. This is a required service which needs to running all the time and the dependent for this service is  “Windows Management Instrumentation Service”.
Functions:
Provides speech processing services for Unified Messaging.
21) Microsoft Exchange Unified Messaging :
This service is installed on Unified Messaging Server. This is a required service which needs to running all the time and this service is dependent upon Microsoft Exchange Active Directory Topology service and the Microsoft Exchange Speech Engine service.”
Functions:
Provides Unified Messaging features, such as the storing of inbound faxes and voice mail messages in a user's mailbox, and access to that mailbox via Outlook Voice Access.

Exchange server 2007 interview Questions

1. Tell me a bit about the capabilities of Exchange Server.
2. What are the different Exchange 2003 versions?
3. What’s the main differences between Exchange 5.5 and Exchange 2000/2003?
4. What are the major network infrastructure for installing Exchange 2003?
5. What is the latest Exchange 2003 Service Pack? Name a few changes in functionality in that SP.
6. What are the disk considerations when installing Exchange (RAID types, locations and so on).
7. You got a new HP DL380 (2U) server, dual Xeon, 4GB of RAM, 7 SAS disks, 64-bit. What do you do next to install Exchange 2003? (you have AD in place)
8. Why not install Exchange on the same machine as a DC?
9. Are there any other installation considerations?
10. How would you prepare the AD Schema in advance before installing Exchange?
11. What type or permissions do you need in order to install the first Exchange server in a forest? In a domain?
12. How would you verify that the schema was in fact updated?
13. What type of memory optimization changes could you do for Exchange 2003?
14. How would you check your Exchange configuration settings to see if they’re right?
15. What are the Exchange management tools? How and where can you install them?
16. What types of permissions are configurable for Exchange?
17. How can you grant access for an administrator to access all mailboxes on a specific server?
18. What is the Send As permission?
19. What other management tools are used to manage and control Exchange 2003? Name the tools you’d use.
20. What are Exchange Recipient types? Name 5.
21. You created a mailbox for a user, yet the mailbox does not appear in ESM. Why?
22. You wanted to change mailbox access permissions for a mailbox, yet you see the SELF permission alone on the permissions list. Why?
23. What are Query Based Distribution groups?
24. What type of groups would you use when configuring distribution groups in a multiple domain forest?
25. Name a few configuration options for Exchange recipients.
26. What’s the difference between Exchange 2003 Std. and Ent. editions when related to storage options and size?
27. Name a few configuration options related to mailbox stores.
28. What are System Public Folders? Where would you find them?
29. How would you plan and configure Public Folder redundancy?
30. How can you immediately stop PF replication?
31. How can you prevent PF referral across slow WAN links?
32. What types of PF management tools might you use?
33. What are the differences between administrative permissions and client permissions in PF?
34. How can you configure PF replication from the command prompt in Exchange 2003?
35. What are the message hygiene options you can use natively in Exchange 2003?
36. What are the configuration options in IMF?
37. What are virtual servers? When would you use more than one?
38. Name some of the SMTP Virtual Server configuration options.
39. What is a Mail Relay? Name a few known mail relay software or hardware options.
40. What is a Smart Host? Where would you configure it?
41. What are Routing Groups? When would you use them?
42. What are the types of Connectors you can use in Exchange?
43. What is the cost option in Exchange connectors?
44. What is the Link State Table? How would you view it?
45. How would you configure mail transfer security between 2 routing groups?
46. What is the Routing Group Master? Who holds that role?
47. Explain the configuration steps required to allow Exchange 2003 to send and receive email from the Internet (consider a one-site multiple server scenario).
48. What is DS2MB?
49. What is Forms Based Authentication?
50. How would you configure OWA’s settings on an Exchange server?
51. What is DSACCESS?
52. What are Recipient Policies?
53. How would you work with multiple recipient policies?
54. What is the “issue” with trying to remove email addresses added by recipient policies? How would you fix that?
55. What is the RUS?
56. When would you need to manually create additional RUS?
57. What are Address Lists?
58. How would you modify the filter properties of one of the default address lists?
59. How can you create multiple GALs and allow the users to only see the one related to them?
60. What is a Front End server? In what scenarios would you use one?
61. What type of authentication is used on the front end servers?
62. When would you use NLB?
63. How would you achieve incoming mail redundancy?
64. What are the 4 types of Exchange backups?
65. What is the Dial-Tone server scenario?
66. When would you use offline backup?
67. How do you re-install Exchange on a server that has crashed but with AD intact?
68. What is the dumpster?
69. What are the e00xxxxx.log files?
70. What is the e00.chk file?
71. What is circular logging? When would you use it?
72. What’s the difference between online and offline defrag?
73. How would you know if it is time to perform an offline defrag of your Exchange stores?
74. How would you plan for, and perform the offline defrag?
75. What is the eseutil command?
76. What is the isinteg command?
77. How would you monitor Exchange’s services and performance? Name 2 or 3 options.
78. Name all the client connection options in Exchange 2003.
79. What is Direct Push? What are the requirements to run it?
80. How would you remote wipe a PPC?
81. What are the issues with connecting Outlook from a remote computer to your mailbox?
82. How would you solve those issues? Name 2 or 3 methods
83. What is RPC over HTTP? What are the requirements to run it?
84. What is Cached Mode in OL2003/2007?
85. What are the benefits and “issues” when using cached mode? How would you tackle those issues?
86. What is S/MIME? What are the usage scenarios for S/MIME?
87. What are the IPSec usage scenarios for Exchange 2003?
88. How do you enable SSL on OWA?
89. What are the considerations for obtaining a digital certificate for SSL on Exchange?
90. Name a few 3rd-party CAs.
91. What do you need to consider when using a client-type AV software on an Exchange server?
92. What are the different clustering options in Exchange 2003? Which one would you choose and
93. Distribution List?
94. GAL, Routing Group, Stm files, Eseutil & ininteg - what are they used for?
95. What is MIME & MAPI?
96. List the services of Exchange Server 2000?
97. How would you recover Exchange server when the log file is corrupted?
98. What is latest service pack Exchange 2003?
99. What is latest service pack Exchange 2000?
100. What is the name of Exchange Databases?
101. How many databases in Standard Exchange version
102. How many databases in Enterprise Exchange version
103. What is Storage Group?
104. What is mail store?
105. Explain Exchange transaction logs
106. What is default size for Transaction logs?
107. Why exchange is using transaction logs? Why not to write to data directly to the Exchange database?
108. How exchange database gets defragmented?
109. What is white space, and how can it be reclaimed?
110. What time online maintenance runs by default in Exchange?
111. What event log exchange logs after online defragmentation

How to manually remove virus which generates folder.exe

Step: 1

• Search for autorun.inf file. It is a read only file so you will have to change it to normal by right clicking the file, selecting the properties and un-check the read only option.
• Open the file in notepad and delete everything and save the file.
• Now change the file status back to read only mode so that the virus could not get access again.
• Click start->run and type msconfig and click ok
• Go to startup tab look for regsvr and uncheck the option click OK.
• Click on Exit without Restart, because there are still few things we need to do before      
• We can restart the PC.
• Now go to control panel -> scheduled tasks, and delete the At1 task listed there.

Step: 2

• Click on start -> run and type gpedit.msc and click Ok.
• If you are Windows XP Home Edition user you might not have gpedit.msc in that case
• download and install it from Windows XP Home Edition: gpedit.msc and then follow
• These steps.
• Go to users configuration->Administrative templates->system
• Find “prevent access to registry editing tools” and change the option to disable.
• Once you do this you have registry access back.

Step: 3

• Click on start->run and type regedit and click ok
• Go to edit->find and start the search for regsvr.exe,
• Delete all the occurrence of regsvr.exe; remember to take a backup before deleting.
• KEEP IN MIND regsvr32.exe is not to be deleted. Delete regsvr.exe occurrences only.
• At one or two places you will find it after explorer.exe in these cases only deletes the
• Regsvr.exe part and not the whole part. E.g. Shell=“Explorer.exe regsvr.exe” the just delete the regsvr.exe and leave the explorer.exe

Step: 4

• Click on start->search->for files and folders.
• Their click all files and folders
• Type “*.exe” as filename to search for
• Click on ‘when was it modified ‘ option and select the specify date option
• Type from date as 1/31/2008 and also type To date as 1/31/2008
• Now hit search and wait for all the exe’s to show up.
• Once search is over select all the exe files and shift+delete the files, caution must be taken so that you don’t delete the legitimate exe file that you have installed on 31^st January.
• Also selecting lot of files together might make your computer unresponsive so delete them in small bunches.
• Also find and delete regsvr.exe, svchost .exe( notice an extra space between the svchost and .exe)

Now do a cold reboot (i.e. press the reboot button instead) and you are done.

Run Windows XP on Windows 7

It’s been a long time since the release of Windows 7 but there are few individuals who are not impressed with Windows 7 and want to continue with XP.


Windows XP is so simple and easy to use that not everyone wants to come out of XP. So if you are using Windows 7 but also wants XP back then Windows 7 has something interesting for you.


The feature is called “XP mode on windows 7” and it can enable you to continue with XP while using Windows 7. This feature works with the feature called Windows Virtual PC. Other advantage of this feature is that while Windows 7 is compatible with most of the applications in XP, in case there is some application that runs only on XP then you can run it easily.


The only thing to note is that you must have Windows 7 Professional, Enterprise, or Ultimate to run Windows XP Mode. Download link for the same is given below:


http://www.microsoft.com/windows/virtual-pc/download.aspx


Note: This particular version of software would run only on the processor which has got the feature called Intel VT

Exchange server interview Q & A

Difference between Exchange 2003 And 2007

Exchange Server 2003

Exchange Server 2003 may be run on the Windows 2000 Server if the fourth service pack has already been installed. It may also be run on 32 bit Windows Server 2003. There is a new disaster recovery feature that is even better than before. It allows the server to experience less downtime. The Exchange Server 2003 received some features form Microsoft Mobile Information server as well. These include Outlook Mobile Access as well as ActiveSync. Improved versions of anti-spam and anti-virus were also included. Management tools for mailboxes and messages have been improved and Instant Messaging and Exchange Conferencing Server are now separate products. There are two versions available of Exchange Server 2003. These include the Enterprise edition and the Standard edition. There are many other features that are available on Exchange Server 2003.

Exchange Server 2007

When Exchange Server 2003 was released there were no immediate plans as to what would happen to the product. A 2005 edition was dropped and it was not until the end of 2006 that the new version was released. Some of the new features included integration of voicemail, improved filtering, Web service support, and Outlook Web Access interface. The new edition was run on a 64 bit x 64 version of Windows Server. This increases the performance significantly. There are quite a few improvements to Exchange Server 2007. These include better calendaring, improved web access, unified messages, and better mobility. From a system protection standpoint there is more clustering, antivirus, anti spam, and compliance included. The IT experience is improved overall with a 64-bit performance. Deployment is better; routing is simplified as well as the command line shell and GUI.

There have been many changes and improvements to the Exchange Server 2007 and it is better than ever. There are no definite plans as to what Microsoft has in store for Exchange Server but the next version will certainly be better than ever.

What is the Difference between Exchange 2003 and 2007?

Exchange 2003 and 2007 difference

· 2003 is 32 bit
· Single server base, No roles base
· Outlook Mobile Access (or OMA)
· Active sync
· Up-To-Date Notifications

Exchange 2003 with SP2

· Direct Push
· Global Address List lookup
· Mobile Admin

2007 exchange server Enhanced and Newly added features

· Has Power full command line Power shell for configuration
· Most of configuration is done through power shell
· Fast message retrieval
· Follow-up flags
· Meeting attendee information
· Enhanced Exchange Search
· Windows Share Point and file share document access
· Reset PIN/Password
· Enhanced PPC security
· Auto discover for over the air (OTA) provisioning
· Out of Office
· Support for HTML messages

Missing/ Removed features in 2007 RTM due to stability Issue but available in SP1

· Information Rights Management (IRM)
· Support for S/MIME

Completely Removed Feature

· Outlook Mobile Access (OMA)

Exchange 2007 has Role base Infrastructure. These are:

Mailbox Role

· Stores Mailboxes and Public folder
. Client Access Client request for mail are fetched by this Role
· Browser-based clients using either the full-featured Outlook Web Access (OWA) or a new OWA Light client
· Mobile devices via Exchange ActiveSync (EAS)
· Phone devices via Outlook by Phone
· POP3 or IMAP4 clients, such as Outlook Express and Eudora

Hub Transport
Responsible for all internal mail flow

Inbound mail are accepted by Edge Transport and passed on to Mailbox server and all outbound mail is relayed from the Hub Transport to the Edge Transport and out to the Internet.

Edge transport

Edge Transport server handles all Internet-facing mail flow, which provides Simple Mail Transfer Protocol (SMTP) relay and smart host services for the Exchange organization.

Unified Messaging

Unified Messaging combines email, voicemail and fax into the Exchange Server databases, and makes this data available to mailbox users via both telephone and computer.

Exchange 2007 System Requirements

PROCESSER

· x64 architecture-based computer with Intel processor that supports Intel 64 architecture
· AMD processor that supports the AMD64 platform
· Intel Itanium IA64 processors not supported
· Intel Pentium or compatible 800-megahertz (MHz) or faster 32-bit processor (for testing and training purposes only; not supported in production)

Memory

· Minimum: 2 gigabytes (GB) of RAM for Single Roles
· 5 GB of RAM. if Roles are installed on single server.
· 8 megabytes (MB) of RAM per mailbox
· Minimum based on number of storage groups

Disk space

· At least 2.5 GB on the drive on which you install Exchange
· An additional 500 MB of available disk space for each Unified Messaging (UM) language pack that you plan to install
· 200 MB of available disk space on the system drive
· In Exchange 2007 RTM, a hard disk drive that stores the message queue database on an Edge Transport server or Hub Transport server with at least 4 GB of free space
· In Exchange 2007 SP1, a hard disk drive that stores the message queue database on an Edge Transport server or Hub Transport server with at least 500 MB of free space
· Disk partitions formatted as NTFS file systems.

Upgrade Tip

· It is not supported to upgrade Exchange 2007 RTM to Exchange 2007 SP1, and then upgrade your operating system to Windows Server 2008.
· Complete Fresh Installation of Ex-2007-SP1 on 2008 is supported