Service
name
|
Service
short name
|
Security
context
|
Description
and dependencies
|
Default
startup type
|
Server
roles
|
Required
(R) or optional (O)
|
|
Microsoft Exchange Active
Directory Topology
|
MSExchangeADTopology
|
Local System
|
Provides Active Directory topology
information to Exchange services. If this service is stopped, most Exchange
services are unable to start. This service has no dependencies.
|
Automatic
|
Mailbox, Hub Transport, Client
Access, Unified Messaging
|
R
|
|
Microsoft Exchange ADAM
|
ADAM_MSExchange
|
Network Service
|
Stores configuration data and
recipient data on the Edge Transport server. This service represents the
named instance of Active Directory Lightweight Directory Service (AD LDS)
that's automatically created by Setup during Edge Transport server installation.
This service is dependent upon the COM+ Event System service.
|
Automatic
|
Edge Transport
|
R
|
|
Microsoft Exchange Address Book
|
MSExchangeAB
|
Local System
|
Manages client address book
connections. This service is dependent upon the Microsoft Exchange Active
Directory Topology service.
|
Automatic
|
Client Access
|
R
|
|
Microsoft Exchange Anti-spam
Update
|
MSExchangeAntispamUpdate
|
Local System
|
Provides the Microsoft Forefront
Protection 2010 for Exchange Server anti-spam update service. On Hub
Transport servers, this service is dependent upon the Microsoft
Exchange Active Directory Topology service. On Edge Transport servers,
this service is dependent upon the Microsoft Exchange ADAM service.
|
Automatic
|
Hub Transport, Edge Transport
|
O
|
|
Microsoft Exchange Credential
Service
|
MSExchangeEdgeCredential
|
Local System
|
Monitors credential changes in AD
LDS and installs the changes on the Edge Transport server. This service is
dependent upon the Microsoft Exchange ADAM service.
|
Automatic
|
Edge Transport
|
R
|
|
Microsoft Exchange EdgeSync
|
MSExchangeEdgeSync
|
Local System
|
Connects to an AD LDS instance on
subscribed Edge Transport servers over a secure LDAP channel to synchronize
data between a Hub Transport server and an Edge Transport server. This
service is dependent upon the Microsoft Exchange Active Directory Topology
service. If Edge Subscription isn't configured, this service can be disabled.
|
Automatic
|
Hub Transport
|
O
|
|
Microsoft Exchange File
Distribution
|
MSExchangeFDS
|
Local System
|
Distributes offline address book
(OAB) and custom Unified Messaging prompts. This service is dependent upon
the Microsoft Exchange Active Directory Topology and Workstation
services.
|
Automatic
|
Client Access, Unified Messaging
|
R
|
|
Microsoft Exchange Forms-Based
Authentication
|
MSExchangeFBA
|
Local System
|
Provides forms-based authentication
to Microsoft Office Outlook Web App and the Exchange Control Panel. If
this service is stopped, Outlook Web App and the Exchange Control Panel won't
authenticate users. This service has no dependencies.
|
Automatic
|
Client Access
|
R
|
|
Microsoft Exchange IMAP4
|
MSExchangeIMAP4
|
Network Service
|
Provides IMAP4 service to clients.
If this service is stopped, clients won't be able to connect to this computer
using the IMAP4 protocol. This service is dependent upon the Microsoft
Exchange Active Directory Topology service.
|
Manual
|
Client Access
|
O
|
|
Microsoft Exchange Information
Store
|
MSExchangeIS
|
Local System
|
Manages the Exchange Information
Store. This includes mailbox databases and public folder databases. If this
service is stopped, mailbox databases and public folder databases on this
computer are unavailable. If this service is disabled, any services that
explicitly depend on it will fail to start. This service is dependent on the
RPC, Server, Windows Event Log, and Workstation services.
|
Automatic
|
Mailbox
|
R
|
|
Microsoft Exchange Mail Submission
Service
|
MSExchangeMailSubmission
|
Local System
|
Submits messages from the Mailbox
server to Exchange 2010 Hub Transport servers. This service is dependent upon
the Microsoft Exchange Active Directory Topology service.
|
Automatic
|
Mailbox
|
R
|
|
Microsoft Exchange Mailbox
Assistants
|
MSExchangeMailboxAssistants
|
Local System
|
Performs background processing of
mailboxes in the Exchange store. This service is dependent upon the Microsoft
Exchange Active Directory Topology service.
|
Automatic
|
Mailbox
|
R
|
|
Microsoft Exchange Mailbox
Replication Service
|
MSExchangeMailboxReplication
|
Local System
|
Processes mailbox moves and move
requests. This service is dependent upon the Microsoft Exchange Active
Directory Topology and Net.Tcp Port Sharing service.
|
Automatic
|
Client Access
|
O
|
|
Microsoft Exchange Monitoring
|
MSExchangeMonitoring
|
Local System
|
Allows applications to call the
Exchange diagnostic cmdlets. This service has no dependencies.
|
Manual
|
All
|
O
|
|
Microsoft Exchange POP3
|
MSExchangePOP3
|
Network Service
|
Provides POP3 service to clients.
If this service is stopped, clients can't connect to this computer using the
POP3 protocol. This service is dependent upon the Microsoft
Exchange Active Directory Topology service.
|
Manual
|
Client Access
|
O
|
|
Microsoft Exchange Protected
Service Host
|
MSExchangeProtectedServiceHost
|
Local System
|
Provides a host for several
Exchange services that must be protected from other services. This service is
dependent upon the Microsoft Exchange Active Directory Topology service.
|
Automatic
|
Hub Transport, Client Access
|
R
|
|
Microsoft Exchange Replication
Service
|
MSExchangeRepl
|
Local System
|
Provides replication functionality
for mailbox databases on Mailbox servers in a database availability group
(DAG) and database mount functionality for all Mailbox servers. This service
is dependent upon the Microsoft Exchange Active Directory Topology service.
|
Automatic
|
Mailbox
|
R
|
|
Microsoft Exchange RPC Client
Access
|
MSExchangeRPC
|
Network Service
|
Manages client RPC connections for
Exchange. This service is dependent upon the Microsoft Exchange Active
Directory Topology service.
|
Automatic
|
Mailbox, Client Access
|
O (Mailbox), R (Client Access)
|
|
Microsoft Exchange Search Indexer
|
MSExchangeSearch
|
Local System
|
Drives indexing of mailbox
content, which improves the performance of content search. This service is
dependent upon the Microsoft Exchange Active Directory Topology and
Microsoft Search (Exchange Server) services.
|
Automatic
|
Mailbox
|
O
|
|
Microsoft Exchange Server
Extension for Windows Server Backup
|
WSBExchange
|
Local System
|
Enables Windows Server Backup
users to back up and recover application data for Microsoft Exchange. This
service has no dependencies.
|
Manual
|
Mailbox
|
O
|
|
Microsoft Exchange Service Host
|
MSExchangeServiceHost
|
Local System
|
|
Provides a host for several
Exchange services. On internal server roles, this service is dependent upon
the Microsoft Exchange Active Directory Topology service. On Edge
Transport servers, this service is dependent upon the Microsoft Exchange ADAM
service.
|
Automatic
|
All
|
R
|
Microsoft Exchange Speech Engine
|
MSSpeechService
|
Network Service
|
Provides speech processing
services for Unified Messaging. This service is dependent upon the Windows
Management Instrumentation (WMI) service.
|
Automatic
|
Unified Messaging
|
R
|
|
Microsoft Exchange System
Attendant
|
MSExchangeSA
|
Local System
|
Forwards directory lookups to a
global catalog server for legacy Outlook clients, generates e-mail addresses
and OABs, updates free/busy information for legacy clients, and maintains
permissions and group memberships for the server. If this service is
disabled, any services that explicitly depend on it will fail to start. This
service is dependent on the RPC, Server, Windows Event Log, and Workstation
services.
|
Automatic
|
Mailbox
|
R
|
|
Microsoft Exchange Throttling
|
MSExchangeThrottling
|
Network Service
|
Limits the rate of user
operations. This service is dependent upon the Microsoft Exchange Active
Directory Topology service.
|
Automatic
|
Mailbox
|
R
|
|
Microsoft Exchange Transport
|
MSExchangeTransport
|
Network
|
Provides SMTP server and transport
stack. On Hub Transport servers, this service is dependent upon the Microsoft
Exchange Active Directory Topology service. On Edge Transport servers,
this service is dependent upon the Microsoft Exchange ADAM service.
|
Automatic
|
Hub Transport, Edge Transport
|
R
|
|
Microsoft Exchange Transport Log
Search
|
MSExchangeTransportLogSearch
|
Local
|
Provides remote search capability
for Microsoft Exchange Transport log files. On Hub Transport servers, this
service is dependent upon the Microsoft Exchange Active Directory
Topology service. On Edge Transport servers, this service is dependent upon
the Microsoft Exchange ADAM service.
|
Automatic
|
Hub Transport, Mailbox, Edge
Transport
|
O
|
|
Microsoft Exchange Unified
Messaging
|
MSExchangeUM
|
Local
|
Enables Microsoft Exchange Unified
Messaging features. This allows voice and fax messages to be stored in
Exchange and gives users telephone access to e-mail, voice mail, calendar,
contacts, or an auto attendant. If this service is stopped, Unified Messaging
isn't available. This service is dependent upon the Microsoft
Exchange Active Directory Topology and the Microsoft Exchange Speech
Engine service.
|
Automatic
|
Unified Messaging
|
R
|
|
Microsoft Search (Exchange Server)
|
msftesql-Exchange
|
Local
|
This is a Microsoft
Exchange-customized version of Microsoft Search. This service is dependent on
the RPC service.
|
Manual
|
Hub Transport, Mailbox
|
Tuesday, November 11, 2014
Exchange 2010 Services and defintion
Wednesday, November 5, 2014
While initiating EMS received error :The user load quota of 2147483647 requests per 60 seconds has been exceeded
Issue : While initiating EMS received error
"Connecting to remote server failed with the following error message : The WS-Management service cannot process the request. The user load quota of 2147483647 requests per 60 seconds has been exceeded. Send future requests at a slower rate or raise the quota for this user. The next request from this user will not be approved for at least 2137494400 milliseconds. For more information, see the about_Remote_Troubleshooting Help topic."
Resolution : Reset IIS or from IIS Manager > Server > Application Pools > Recycle "MsExchangePowerShellAppPool"
Resolution : Reset IIS or from IIS Manager > Server > Application Pools > Recycle "MsExchangePowerShellAppPool"
Friday, October 17, 2014
Exchange 2010 Sp3 Ru7 OWA search is not working
Issue : OWA search is not working for all of the users, No issues with Outlook users on Exchange 2010 SP3 RU7 on SBS server
Troubleshooting steps performed
1. Last time When Index catalog has been built : Recently
2. How many users are facing this issue : All
3. How many nodes of Exchange server : Single
4. What if Mailbox moved to another Server/ Database : Not possible (SBS)
5. Since when Users are facing this issue : After installing Windows Update
6. Is Search is working for outlook Client : Yes
7. On newly Created Test user, Search is working : Not working
9. Test-MailboxDatabase –MailboxDatabase <DB> : Error "Time out for test thread"
10. Test-ExchangeSearch : The MSExchangeSearch service isn't running.
11. “Microsoft.Exchange.Search.ExSearch.exe” from Task Manager and check the processor : Normal , between 6% to 12%
12. Please check Search on Different Internet Browser like Chrome or Firefox : Same issue,Not Working
13. Download SymLink from Repair-ExchangeSearchSymlinks.ps1 and run the command (this script repairs symbolic links) : Still Search is not working
14. .\ResetSearchIndex.ps1 [-force] <dbname> [<dbname>]...
You will receive an Event ID 109 when the rebuilding of the index starts for each database and an Event ID 110 for each database when the index rebuild has completed : Still Search is not working
15. After receiving Event ID 110 for each database, test to make sure search functions correctly with both OWA and Outlook operating in Online Mode : Still Search is not working
16. From Exchange SP3 media, Goto Setup.Exe folder and from Command Prompt with "Run as administrator" First run setup /PrepareAD and then run setup /PrepareSchema and after that reboot he box and make sure “Microsoft Exchange Search Indexer Service” and “Microsoft Information Store” service is started and checked the issue
Now, issue is resolved
Troubleshooting steps performed
1. Last time When Index catalog has been built : Recently
2. How many users are facing this issue : All
3. How many nodes of Exchange server : Single
4. What if Mailbox moved to another Server/ Database : Not possible (SBS)
5. Since when Users are facing this issue : After installing Windows Update
6. Is Search is working for outlook Client : Yes
7. On newly Created Test user, Search is working : Not working
9. Test-MailboxDatabase –MailboxDatabase <DB> : Error "Time out for test thread"
10. Test-ExchangeSearch : The MSExchangeSearch service isn't running.
11. “Microsoft.Exchange.Search.ExSearch.exe” from Task Manager and check the processor : Normal , between 6% to 12%
12. Please check Search on Different Internet Browser like Chrome or Firefox : Same issue,Not Working
13. Download SymLink from Repair-ExchangeSearchSymlinks.ps1 and run the command (this script repairs symbolic links) : Still Search is not working
14. .\ResetSearchIndex.ps1 [-force] <dbname> [<dbname>]...
You will receive an Event ID 109 when the rebuilding of the index starts for each database and an Event ID 110 for each database when the index rebuild has completed : Still Search is not working
15. After receiving Event ID 110 for each database, test to make sure search functions correctly with both OWA and Outlook operating in Online Mode : Still Search is not working
16. From Exchange SP3 media, Goto Setup.Exe folder and from Command Prompt with "Run as administrator" First run setup /PrepareAD and then run setup /PrepareSchema and after that reboot he box and make sure “Microsoft Exchange Search Indexer Service” and “Microsoft Information Store” service is started and checked the issue
Now, issue is resolved
Thursday, September 4, 2014
“Your mailbox can't be accessed using the address you entered, please obtain the correct address, please contact your helpdesk”
“Your mailbox can't be accessed using the address you entered, please obtain the correct address, please contact your helpdesk”
Method1:
To proceed to the control panel you can access the EAC by adding the Exchange version to the URL. For example, to access the EAC whose virtual directory is hosted on the Client Access server locally, use the following URL:https://localhost/ecp?ExchClientVer=15
.
Same way applies if you want to access the Exchange 2010 ECP and your mailbox hosted on an Exchange 2013 Mailbox server, use the following URL:https://localhost/ecp?ExchClientVer=14
Method2:
Through PowerShell create a new mailbox on Exchange 2013 and give it the necessary administrative permissions.
refered from: http://blogs.technet.com/b/meamcs/archive/2013/05/04/exchange-2013-coexistence-ecp-your-mailbox-can-t-be-accessed-using-the-address-you-entered-please-obtain-the-correct-address.aspx
Friday, August 22, 2014
Troubleshooting Steps : The Proxy address "MBX:0" is already being used by org/users/username
Issue : Error received when for few user tried to change the "Set as Reply"
The Proxy address "MBX:0" is already being used by "org/users/username". Please choose another proxy address
Resolution : From the ADSIEdit.msc, remove the Problematic address from the Attribute "ProxyAddress"
Users had been migrated from Exchange 2003 to Exchange 2010, while moving mailbox Exchange stamps mailbox for processing with MBX:0 and MBX:1 likewise
The Proxy address "MBX:0" is already being used by "org/users/username". Please choose another proxy address
Resolution : From the ADSIEdit.msc, remove the Problematic address from the Attribute "ProxyAddress"
Users had been migrated from Exchange 2003 to Exchange 2010, while moving mailbox Exchange stamps mailbox for processing with MBX:0 and MBX:1 likewise
Tuesday, August 5, 2014
Cross Forest Migration
Tools
1. Microsoft Identity Lifecycle Manager (ILM) 2007 Feature Pack 1 (FP1)
2. MIIS
3. FIM, other 3rd party dirsync tool, etc
2. Scripts
(a) This example configures the Availability service to retrieve per-user free/busy information on a Mailbox server in the target forest.
1. Microsoft Identity Lifecycle Manager (ILM) 2007 Feature Pack 1 (FP1)
2. MIIS
3. FIM, other 3rd party dirsync tool, etc
2. Scripts
(a) This example configures the Availability service to retrieve per-user free/busy information on a Mailbox server in the target forest.
Get-MailboxServer | Add-ADPermission -Accessrights Extendedright -Extendedrights "ms-Exch- EPI-Token-Serialization" -User "<Remote Forest Domain>\Mailbox servers"
Add-AvailabilityAddressSpace -Forestname ContosoForest.com -AccessMethod PerUserFB -UseServiceAccount:$true(b) To configure bidirectional cross-forest availability, repeat these steps in the target forest.
If you choose to configure cross-forest availability with trust, and also choose to use a service account (instead of specifying organization-wide or per-user credentials), you must extend permissions as shown in the example in the "Use the Shell to configure trusted cross-forest availability with a service account" section. Performing that procedure in the target forest gives Mailbox servers in the source forest permission to serialize the original user context.
(c) This example configures trusted cross-forest availability with a service account.
Get-MailboxServer| Add-ADPermission -Accessrights Extendedright -Extendedright "ms-Exch-EPI-Token-Serialization" -User "<Remote Forest Domain>\Exchange servers"This example sets the organization-wide account on the availability configuration object to configure the access level for free/busy information in the target forest
Set-AvailabilityConfig -OrgWideAccount "Contoso.com\User"This example adds the Availability address space configuration object for the source forest.
$a = Get-Credential (Enter the credentials for organization-wide user in Contoso.com domain) Add-AvailabilityAddressspace -Forestname Contoso.com -Accessmethod OrgWideFB -Credential:$aFrom Microsoft Technet : http://technet.microsoft.com/en-us/library/bb125182(v=exchg.150).aspxfrom Blog :http://blogs.technet.com/b/ucedsg/archive/2010/04/22/how-does-federated-calendar-sharing-work-in-exchange-2010.aspxFour things needed to get you started:1) Obtain a X.509 certificate from a Trusted Root CA (GoDaddy, Entrust, etc) for use with Microsoft Federation Gateway (MFG) for signing and encrypting delegation tokens. (more here). Here is a list of Trusted Root CAs that MFG is aware of here.2) Create a Federation Trust using cmdlet with the MFG (more here):New-FederationTrust3) Provide domain ownership by creating a DNS TXT record similar to (more here):Contoso.com IN TXT AppId = 1C24) Add your SMTP domains (other Exchange Orgs) and add Federated domains to trust calendar information with (other org must accept) using cmdlet (more here):Set-FederatedOrganizationIdentifier - to enable your SMTP domains for federation sharing with the MFGAdd-FederatedDomain – to add other External Orgs to share calendar information with
Subscribe to:
Posts (Atom)