Setting up Exchange Server 2010

Anyone know of a thread that shows a good way to setup exchange 2010 to work well internally and externally?

Hi,
I recommend you install Exchange 2010 SP3 directly.
What's more, before you install Microsoft Exchange Server 2010 in your organization, you should prepare Active Directory and domains at first.
Here are some helpful articles for your reference.
Prepare Active Directory and Domains
http://technet.microsoft.com/en-us/library/bb125224(v=exchg.141).aspx
Install Exchange 2010 Using the Custom Installation Type
http://technet.microsoft.com/en-us/library/bb125143(v=exchg.141).aspx
Hope it helps.
Best regards,
Amy
Amy Wang
TechNet Community Support

Similar Messages

SBS 2003 to 2011 Migration - Exchange Server 2010 cannot be installed

Hello,
We have a Small Business Server 2003 server that we are trying to migrate to SBS 2011 using the out of the box migration process. After the install, the SBS console showed a couple installation issues - the big one turned out to be "Exchange Server
2010 cannot be installed".
Here is the end of 'ExchangeSetup.log' showing various error messages:
[11/29/2014 23:00:07.0489] [2] Active Directory session settings for 'Get-ExchangeServer' are: View Entire Forest: 'True', Configuration Domain Controller: 'MB-MAINSERVER04.Contoso.local', Preferred Global Catalog: 'MB-MAINSERVER04.Contoso.local', Preferred Domain Controllers: '{ MB-MAINSERVER04.Contoso.local }'
[11/29/2014 23:00:07.0490] [2] Beginning processing get-exchangeserver -Identity:'MB-MAINSERVER04' -DomainController:'MB-MAINSERVER04.Contoso.local' -ErrorAction:'SilentlyContinue'
[11/29/2014 23:00:07.0506] [2] Searching objects "MB-MAINSERVER04" of type "Server" under the root "$null".
[11/29/2014 23:00:07.0518] [2] Previous operation run on domain controller 'MB-MAINSERVER04.Contoso.local'.
[11/29/2014 23:00:07.0518] [2] Previous operation run on domain controller 'MB-MAINSERVER04.Contoso.local'.
[11/29/2014 23:00:07.0518] [2] Preparing to output objects. The maximum size of the result set is "unlimited".
[11/29/2014 23:00:07.0522] [2] Unexpected Error
[11/29/2014 23:00:07.0522] [2] The operation couldn't be performed because object 'MB-MAINSERVER04' couldn't be found on 'MB-MAINSERVER04.Contoso.local'.
[11/29/2014 23:00:07.0523] [2] Ending processing get-exchangeserver
[11/29/2014 23:00:07.0523] [1] Executing:
if ($server -eq $null)
new-exchangeserver -DomainController $RoleDomainController -Name $RoleNetBIOSName
[11/29/2014 23:00:07.0545] [2] Active Directory session settings for 'New-ExchangeServer' are: View Entire Forest: 'True', Configuration Domain Controller: 'MB-MAINSERVER04.Contoso.local', Preferred Global Catalog: 'MB-MAINSERVER04.Contoso.local', Preferred Domain Controllers: '{ MB-MAINSERVER04.Contoso.local }'
[11/29/2014 23:00:07.0545] [2] Beginning processing new-exchangeserver -DomainController:'MB-MAINSERVER04.Contoso.local' -Name:'MB-MAINSERVER04'
[11/29/2014 23:00:07.0599] [2] [ERROR] Could not find the default Administrative Group 'Exchange Administrative Group (FYDIBOHF23SPDLT)'.
[11/29/2014 23:00:07.0600] [2] Ending processing new-exchangeserver
[11/29/2014 23:00:07.0607] [1] The following 1 error(s) occurred during task execution:
[11/29/2014 23:00:07.0607] [1] 0. ErrorRecord: Could not find the default Administrative Group 'Exchange Administrative Group (FYDIBOHF23SPDLT)'.
[11/29/2014 23:00:07.0607] [1] 0. ErrorRecord: Microsoft.Exchange.Data.Directory.SystemConfiguration.DefaultAdministrativeGroupNotFoundException: Could not find the default Administrative Group 'Exchange Administrative Group (FYDIBOHF23SPDLT)'.
at Microsoft.Exchange.Data.Directory.SystemConfiguration.ADSystemConfigurationSession.GetAdministrativeGroup()
at Microsoft.Exchange.Data.Directory.SystemConfiguration.ADSystemConfigurationSession.GetAdministrativeGroupId()
at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeServer.PrepareDataObject()
at Microsoft.Exchange.Configuration.Tasks.SetTaskBase`1.InternalValidate()
at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
[11/29/2014 23:00:07.0609] [1] [ERROR] The following error was generated when "$error.Clear();
if ($server -eq $null)
new-exchangeserver -DomainController $RoleDomainController -Name $RoleNetBIOSName
" was run: "Could not find the default Administrative Group 'Exchange Administrative Group (FYDIBOHF23SPDLT)'.".
[11/29/2014 23:00:07.0609] [1] [ERROR] Could not find the default Administrative Group 'Exchange Administrative Group (FYDIBOHF23SPDLT)'.
[11/29/2014 23:00:07.0609] [1] [ERROR-REFERENCE] Id=ProvisionServerComponent___84489810458648f5ac6e47811394a284 Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[11/29/2014 23:00:07.0610] [1] Setup is stopping now because of one or more critical errors.
[11/29/2014 23:00:07.0610] [1] Finished executing component tasks.
[11/29/2014 23:00:07.0618] [1] Ending processing Install-BridgeheadRole
[11/29/2014 23:00:07.0626] [0] The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
[11/29/2014 23:00:07.0633] [0] End of Setup
[11/29/2014 23:00:07.0633] [0] **********************************************
[11/29/2014 23:39:03.0429] [0] **********************************************
[11/29/2014 23:39:03.0435] [0] Starting Microsoft Exchange Server 2010 Setup
[11/29/2014 23:39:03.0435] [0] **********************************************
[11/29/2014 23:39:03.0456] [0] Local Time Zone: (UTC-08:00) Pacific Time (US & Canada).
[11/29/2014 23:39:03.0457] [0] Operating System version: Microsoft Windows NT 6.1.7600.0.
[11/29/2014 23:39:03.0469] [0] Setup version: 14.1.438.0.
[11/29/2014 23:39:03.0473] [0] Logged on user: Contoso2K3\Administrator.
[11/29/2014 23:39:06.0763] [0] Command Line Parameter Name='mode', Value='Install'.
[11/29/2014 23:39:06.0776] [0] ExSetupUI was started with the following command: '-mode:install'.
[11/29/2014 23:39:07.0413] [0] Setup is choosing the domain controller to use
[11/29/2014 23:39:07.0730] [0] Setup is choosing a local domain controller...
[11/29/2014 23:39:08.0459] [0] Setup has chosen the local domain controller MB-MAINSERVER04.Contoso.local for initial queries
[11/29/2014 23:39:08.0747] [0] PrepareAD has been run, and has replicated to this domain controller; so setup will use MB-MAINSERVER04.Contoso.local
[11/29/2014 23:39:08.0748] [0] Setup is choosing a global catalog...
[11/29/2014 23:39:08.0758] [0] Setup has chosen the global catalog server MB-MAINSERVER04.Contoso.local.
[11/29/2014 23:39:08.0819] [0] Setup will use the domain controller 'MB-MAINSERVER04.Contoso.local'.
[11/29/2014 23:39:08.0820] [0] Setup will use the global catalog 'MB-MAINSERVER04.Contoso.local'.
[11/29/2014 23:39:08.0823] [0] Exchange configuration container for the organization is 'CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Contoso,DC=local'.
[11/29/2014 23:39:08.0830] [0] Exchange organization container for the organization is 'CN=Contoso2K3,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Contoso,DC=local'.
[11/29/2014 23:39:08.0867] [0] Setup will search for an Exchange Server object for the local machine with name 'MB-MAINSERVER04'.
[11/29/2014 23:39:08.0914] [0] No Exchange Server with identity 'MB-MAINSERVER04' was found.
[11/29/2014 23:39:09.0061] [0] The following roles have been unpacked: BridgeheadRole ClientAccessRole MailboxRole AdminToolsRole
[11/29/2014 23:39:09.0062] [0] The following datacenter roles are unpacked:
[11/29/2014 23:39:09.0064] [0] The following roles are installed: AdminToolsRole
[11/29/2014 23:39:09.0066] [0] The local server has some Exchange files installed.
[11/29/2014 23:39:09.0320] [0] Setup will use the path 'C:\Program Files\Windows Small Business Server\Bin\CMPNENTS\EXCHANGE14_SP1' for installing Exchange.
[11/29/2014 23:39:09.0332] [0] The installation mode is set to: 'Install'.
[11/29/2014 23:39:13.0558] [0] An Exchange organization with name 'Contoso2K3' was found in this forest.
[11/29/2014 23:39:13.0560] [0] Active Directory Initialization status : 'True'.
[11/29/2014 23:39:13.0561] [0] Schema Update Required Status : 'False'.
[11/29/2014 23:39:13.0562] [0] Organization Configuration Update Required Status : 'False'.
[11/29/2014 23:39:13.0563] [0] Domain Configuration Update Required Status : 'False'.
[11/29/2014 23:39:13.0564] [0] The locally installed version is 14.1.218.15.
[11/29/2014 23:39:13.0565] [0] Exchange Installation Directory : 'C:\Program Files\Microsoft\Exchange Server\V14'.
[11/29/2014 23:39:13.0920] [0] Applying default role selection state
[11/29/2014 23:39:13.0961] [0] Setup is determining what organization-level operations to perform.
[11/29/2014 23:39:13.0962] [0] Because the value was specified, setup is setting the argument OrganizationName to the value Contoso2K3.
[11/29/2014 23:39:13.0963] [0] Setup will run from path 'C:\Program Files\Microsoft\Exchange Server\V14\'.
[11/29/2014 23:39:13.0972] [0] InstallModeDataHandler has 0 DataHandlers
[11/29/2014 23:39:13.0972] [0] RootDataHandler has 1 DataHandlers
[11/29/2014 23:39:15.0491] [0] Setup encountered an exception when trying to access the setup state file: Could not find file 'C:\ExchangeSetupLogs\exchangeInstallState.xml'.
[11/29/2014 23:39:26.0117] [0] End of Setup
[11/29/2014 23:39:26.0117] [0] **********************************************
I should add that the source server's AD configuration might not be perfect due to this being the second attempt at a SBS 2011 migration install.
I'd be grateful for any help I can get on this as SBS migration has been plauged with multiple setbacks already. I really need to get this done! ;)
Thanks,
Voon

Thank you Larry and Al for your replies.
I used the 'official' migration
guide plus this page (http://www.techieshelp.com/step-by-step-guide-to-migrating-to-sbs-2011/)
as my migration references. The SBS migration prep tool gave no errors on the source server when I ran it.
I have a full system drive image plus a a system state backup from before migration. Though I am very loathed to rollback the migration and attempt a new one - again. I will do some searching to see if I can resolve the Exchange server problem and continue
the migration/installation. If not, then its a system state restore for me. One of Al's links had a resource for doing a thorough check of AD - which something I'd run if I have to another migration attempt.
I am also really tempted to open up a paid MS support ticket for them to help me fix this problem. :)

How to install Exchange Server 2010 with the name of my existing Domain Controller.

I have my Primary domain Controller as abc.com in 2008 r2 standard. abc.com is registered. I want to set up Fresh Exchange Server 2010 sp2 with the name of the same
abc.com domain name. Please guide me the steps how to do that. Waiting for your kind response. :)

Hi,
From you description, you want to install an Exchange server 2010 in the abc.com. When you set up your Exchange, Exchange need to join in a domain. You just need to specify the domain to abc.com.
What's more, here is a helpful blog about Exchange 2010 installation for your reference.
HOWTO Install Exchange 2010 - Step by Step
http://blogs.technet.com/b/ferris/archive/2010/03/05/howto-install-exchange-2010-step-by-step.aspx
Hope it helps.
Best regards,
Amy
Amy Wang
TechNet Community Support

Need help with Outlook 2013 connecting to Exchange server(2010)

Hi
I need help with Outlook 2013 and with my exchange server(2010) email account
After setting up account initially emails come in and than after an hour or two stop. My OWA is working fine with no issues. I have even created a forward rule in OWA to my GMAIL account whch works fine
However Outlook 2013 is not syncing messages, have difficulty in sending emails sometimes as it takes too long. In fact the connection also is intermittent. Even if the task bar shows connected to exchange, it seems that is not the case since new emails
and any emails I compose dont work. I have trouble shot the issue with my ISP and email service provide, but they havent resolved the issue I have also done a TraceRoute and that shows no drops or problems to he exchange server.
Can someone please help me resolve this matter so I can continue to use Outlook 2013( running Windows 8.1) in both my computers which have the identical problem
Look forward to a solution soon
Thanks

Hi Angela
Thanks for your message
To answer your questions, please note the following
a) My account is set up in Cache Mode( not online mode)
b) I am the only other user on the account
c) When the connection to the exchange server is broken, I see upon clicking connection tab that there is no information in the box, and when I press reconnect it starts showing "connecting"
d) When the connection to the server is there, it shows connection as "established"
e) Sorry I dont understand th meaning of CAS array in your environment? Can you pls explain
Since yday I have been using Outlook 2010 on desktop and Outlook 2013 on my laptop using Exchange 2013 account. So far all emails are syncing, and I can send emails from both computers. However, I am concerned that the connection can break-off anytime,
as it has done that in the past on both outlook versions. The max time it has worked without any problem is 48 hrs and than after that the same issue of not connection, not syncing and unable to send emails happens
My ISP has checked and there is no network connectivity issues. My email service provider has trouble shot the issue many times, but to no positive results. I have also changed the profile a few times, but the intermittent connectivity problem hasn't
been resolved.
Can you identify the possible causes and more importantly a working permanent solution please
Thanks
Mahesh

Exchange server 2010 mail limitation

Hi,
We have exchange server 2010 cashub1 and cashub2
and also we have edge1 and edge2.
my requirement is, i want all the exchange user to set limit of internal and external as 10 MB, except just 5 to 10 user we need to set limit as 50MB.
Can you please assist and provide the step by step configuration to setup the requirements.
Thanks in advance.

Does that 50MB limit apply to messages to and from the internet as well?
If so, then here is an example of one way to do this:
I would set all the limits to 50MB including the organizational limits.
Then create a hub transport rule that rejects any message with an attachment over 10MB with a rejection message and code of your choosing except when to and from a Group that you create that contains those 5-10 users who need to send messages as large as
50MB.
and, as always, test this very well before implementing!
More info:
http://technet.microsoft.com/en-us/library/bb124345(v=exchg.141).aspx
Understanding Message Size Limits
Twitter!:
Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Exchange Server 2010 Backup and Restore

Hai,
I have Exchange server 2010 stand alone server combined with mailbox, hub and cas role. i dont have backup application program. I want to take my exchange database backup to my SAN storage automatically everyday...
Using windows server backup i can take full backup only and i can schedule it to happen daily.. Is it possible can i take incremental backup??????????for exchange 2010 database.
Thanks Chandru CT. MCITP

You have two basic options to backup Exchange 2010, VSS snapshots and "native backup" (meaning a Lag copy). As far as VSS backups go, there are three components; the VSS Writer, the VSS Provider, and the VSS Requestor. The Writer is built into
Exchange. In fact in Exchange 2010 there are two - the Exchange VSS Writer and the Exchange VSS Replica Writer. The provider can be a software VSS provider such as the Microsoft Shadow Copy provider or a hardware provider (usually supplied by your
SAN vendor. The requestor is what you would tend to think of as the backup application; it coordinates activities between the Writer and the Provider.
As far as the Exchange 2010 plugin for Windows backup goes, it a very minimal requestor. It only supports the Exchange 2010 VSS Writer, not the Replica Writer. This means you can only take backups of the Active copy of a database. The requirement
to backup the entire "volume" in the windows sense, or partition to the rest of us is a function of the way VSS works and is no real surprise. In fact, another limitation of VSS is that the logs and database need to be on seperate volumes: see
http://technet.microsoft.com/en-us/library/ee832794.aspx.
That it only takes full backups makes sense as well. Shadow copies, like many software providers and many hardware providers out there are copy on write. Initially, after the first one that is, they take up minimal space for some metadata.
As data is writen to the volume while the the snapshot is in place, the original blocks are evacuated to a "difference area" and the write is then written to the newly evacul\ated spot. You can generally put the difference area on the same volume or
somewhere else. The downside is to write a block while a copy on write snapshot is in place means a read and two writes for every write. This gets ugly on RAID 5 which already has a write penalty of 4; that turns into 9 IOs for every write while
the copy on write snapshot is in place. Since you can't do the snapshots on the replica because the replica writer isn't supported, that IO hit is on the active copy. When using copy on write snapshots, you generally want as few around as possible
for as short a time as possible; usually just long enough to export or copy the snapshot to another set of spindles. I really wouldn't want to use WSB plugin for Exchange 2010 in anything but the smallest deployments.
What about native backup? Well then you take a 100% space hit for every lag copy. In addition, restoring a LAG is a one shot deal. As you strive with the LAG to match what you could achieve with even daily or weekly copy on write snapshots,
the number of database copies, and Exchange mailbox servers, poliferates. You may want to consider a "Happy medium" that combines a LAG for fault tolerance/protection against logical corruption with copy on write snapshots (replicated or copied
to seperate storage) for HA. Perhaps DPM would be worth a look in your situation.
You did mention that you have a SAN. Most SAN vendors offer hardware VSS Providers. Many are copy on write, and you shift that set of problems to the, albeit likey a bit more performant SAN, Some vendors use other stratagies. The vendor
I work for uses allocate on write, so it avoids the 3 IOs per write copy on write penalty while a snapshot is in place. This means you can snapshot frequently and keep many of them around without penalty shortening your RPO and RTO. They optionally
archive truncated logs allowing for "up to the minute" restore of older snapshots, not just the last one. They also provide a proprietery version of RAID 6, called RAID DP that outperforms RAID 1. Combine that with all the storage efficiency features
like dedupe of primary storage, thin provisioning, compression, etc., that can all be combined and it starts to get compelling as the size of your deployment increases. Although I might be a bit biased when it comes to SAN vendors, if your SAN is someone
other than NetApp I still encourage you to talk with your SAN vendor and see what features/functionality they offer that can help you address your backup needs for Exchange 2010. I think you'll find much to like; it really comes down to scale and a cost/benefit
analysis.
If you decide that hardware VSS providers are not you thing and want to stay with a software vss provider, I encorage you to talk to the usual backup software vendors as well. Many can integrate with DAS and/or SAN, and have their own software
VSS providers often including support for the Exchange 2010 replica writer. This at a minimum allows you to snapshot passive copies. Features like replication (to get the changed blocks to other storage or off site), tape support (to roll backups
off to tape potentially to store off site) and catalogs come to mind as very useful things to have.
I'd take a look around at what's available and see if any of the things offered meet your business needs at a price you can afford to pay. The WSB Plug-in is a bare bones sort of thing, and it only gets better from there.
J

Exchange Server 2010 automatic reply once per day or once per week?

Hello,
can some tell me how often the automatic reply is send in Exchange Server 2010.
Is it once per day for each sender or once per week for each sender?
In the web some tell per week, some tell per day.
Is it possible to change the time shedule, so that each day a automatic reply is send?
Thanks,
Eduard

Hello,
after some googling and consolidating the different examples on the Internet I came up with this powershell script which is executed by the windows task scheduler once a day. The script first gathers all the mailboxes for which the out of office mechanism
is activated. Then it disables the autorepliers for these mailboxes, waits for 10 seconds (this seems to be necessary to let exchange do some housekeeping) and then reenables the autorepliers.
Warning: I have learned that this script resets the time interval of the autoreplier. Any ideas how to preserve the time settings?
Add-PSSnapin Microsoft.Exchange.Management.PowerShell.E2010
$objUsers = get-mailbox | Get-MailboxAutoReplyConfiguration | Where-Object {$_.AutoReplyState -eq "scheduled" }
$objUsers | %{ Set-MailboxAutoReplyConfiguration -Identity $_.identity -AutoReplyState disabled}
Start-Sleep -s 10
$objUsers | %{ Set-MailboxAutoReplyConfiguration -Identity $_.identity -AutoReplyState scheduled}
Remember to use -AutoReplyState scheduled instead of -AutoReplyState enabled to reenable. -AutoReplyState enable should only be used for permanent autorepliers and not for "out of office" messages.
Cheers,
Florian

Exchange Server 2010 - Receive Connector for Client Computers

I have one customer with a SBS 2011 with Exchange Server 2010 - a pretty standard setup except for some customisation with Receive Connectors in order to cater for an application which is installed on a number of computers that requires to use an SMTP Server
to send notifications. In order to accomplish this (allow to be sent using Exchange Server) we added the IP Address of client computer (which we also set as a DHCP reservation) to a pre-configured Receive Connector (Anonymous setup for Printer/Scanner).
This worked fine, but we now find that there are other applications that require the same function to use SMTP to send.
How should/could this be better configured so an application can send if they authenticate?

Hi
For this you need to create a seperate receive connector to be used for Relay in your organizations.
Follow the below steps
1) Create a dedicated Relay Receive Connector
2) Add only the Ip addresses of the applications which needs to relay on Exchange servers
3) You can use either anonymous or authenticated relay according to your relay config
You can follow the below link as well
http://exchangequery.com/2013/12/02/steps-to-configure-anonymous-and-authenticated-relay-in-exchange-2013/
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com Thanks Sathish
(MVP)

Exchange Server 2010 SP3 test environment - email flow to/from internet

Today I set up test environment for Exchange Server 2010 SP3 - domain controller running Windows Server 2008 R2 SP1, Exchange Server 2010 SP3 on Windows Server 2008 R2 SP1 and client computer running Windows 7 Pro SP1 x64 with Outlook Pro 2010 x64. These
machines are VMs on vSphere 5.0 cluster made of 4 esxi 5.0 hosts.
I have three years of experience in working with Exchange Server 2010 in my production environment but until recently I have not had enough resources to build a test environment. Does "testing" Exchange Server 2010 infrastructure have
a real life purpose considering the fact that only internal email flow is possible since authoritative SMTP accepted domain is not hosted anywhere thus not visible to outside world. This limited email flow combined with absence of possibility to test
ActiveSync, Outlook Anywhere, OWA from WAN, . . . really hurt and make Exchange Server rare technology that can not be tested completely before introducing something new into the production. Services that are not possible to test from the outside world are
useless and whole point of Exchange-like technologies is availability from anywhere and from whatever device.

I set up Internet Send Connector (by default this type of send connector uses DNS MX records to route email automatically). Having sent an email to my gmail account I did not receive it and in transport logs I saw that mx record was found successfully
but there is the following line:
2014-08-05T20:39:51.942Z,Internet Connector,08D17F000FE36010,1,,2a00:1450:4013:c01::1b:25,*,,"Failed to connect. Error Code: 10051, Error Message: A socket operation was attempted to an unreachable network 2a00:1450:4013:c01::1b:25"
I tried also to send an email to my production email address (we have Symantec Messaging Gateway which is used as a smart host (antispam,antimalware,content filter appliance)) but then error is:
2014-08-05T20:50:08.395Z,Internet Connector,08D17F000FE36019,1,,91.238.7.10:25,*,,"Failed to connect. Error Code: 10061, Error Message: No connection could be made because the target machine actively refused it 91.238.7.10:25"
Telnet from test exchange to 91.238.7.10 on port 25 also is not working.

Exchange Server 2010 Outlook Client Stops Responding

Greetings- This issue is with Exchange Server 2010 sp2 using Outlook 2013 clients in AD environment. Single server, single database (80GB) , 60+ users, Windows 8/8.1 workstations.
All of a sudden our users started experiencing issues yesterday. One or two at first, then more.
The issue where Outlook stops responding. This is most noticeable when you try to send and receive. The recipient will get the email before outlook clears it from pending submissions in the outbox.
1. SMTP is fully operational
2. Push clients functions normally
3. Exchange is fully updated and current
4. The mailbox databases are verified and healthy
5. Network traffic to and from the server appears normal according to wire shark
6. Setting Outlook to use no cache connection mitigates the issue partially
7. The issue is global on all deployed OS's
As this is happening on many, maybe all, workstations, my thought is that is has to do with Exchange, not the client.
Thanx
You should never, never doubt what nobody is sure about. -Willy Wonka

Does this happen all day, or at specific times? I'll add that your server appears to be light on CPU, but without knowing its CPU profile (when idle and when under a load), I can't say for sure this is your issue. One additional thing I can
ask - do you have hyperthreading enabled? This can be a bad thing in an Exchange server. See the following:
https://technet.microsoft.com/en-us/library/dd346699%28v=exchg.141%29.aspx?f=255&MSPPError=-2147217396#Hyper and the following:
http://blogs.technet.com/b/exchange/archive/2013/05/06/ask-the-perf-guy-sizing-exchange-2013-deployments.aspx Note that this second note is about Exchange 2013, but it goes into more details on some of the issues that may be adversely affecting your
Exchange 2010 servers.

Email language wise forwarder in specific DL on Exchange Server 2010

Dear All,
Can we set email language wise forwarder in specific
DL on Exchange Server 2010.
Below is the scenario :
I have 4 users who sent mail to DL(DL-IT) in different languages like Dutch, German, English, now I want to set email forwarder on DL-IT like if someone send email in Dutch language then Dutch language
email should be forward to another DL (DL_DUTCH) and same for other language.
Thank you in advance.
Pradip Sisodiya

Hi Pradip,
afaik there is no solution based on a DL object. While saying that, if you had to handle only organization internal senders you may try like that:
1. please set the language property for all your mailboxes ; I guess you can do that based on the OU / Location the user objects lives in.
2. now in Exchange 2013 and Exchange 2010 there will be a Header for the language like that
Content-Language: en-US
Accepted-Language: en-US
(the language, en-US in my example, at the RHS will Change if you changed the Languages property of that Mailbox.)
3. finally you can add Transport rules to forward based on the Content-Language or Accepted-Language
a. Setting in
mail flow -> rules -> create a new rule (choose no template) -> more Options -> add condition --> apply this rule if ... -> a message Header --> enter text (= Content-Language) & enter text patters "language", as en-US
plus (=add condition) the recipient is your DL
b. do the following : Redirect the message to --> your recipient
c. save that rule.
if you ran the get-transportrule cmdlet, it Looked like that:
(you better create it once for initial testing and afterwards you can Export / Change that rule and use new-transportrule to apply the other languages / recipients)
If that Content-Language Header is present on the message, that rule will work as you expected.
Please remember to add the language property to your Mailbox. if you ran
$mymailbox = get-mailbox
$mymailbox.language
it really Needs to have the value you expected on the RHS of your Header condition.
Regards,
Martin

Exchange Server 2010: Convert Mailbox to MailUser

Dear All,
I plan to cutover migration exchange on-premises to exchange online with single-sign-on.
http://community.office365.com/en-us/w/exchange/835.cutover-exchange-migration-and-single-sign-on.aspx
In Step 2: It need to Convert on-premises mailboxes to mail-enabled users. it has only instruction guide for exchange server 2003 and 2007. it didn't have for exchange server 2010 or 2013.
Could you guide what is the best solution to convert mailbox in exchange server 2010?
BR,
Khemarin
[email protected]

Hi Khemarin,
You can use the following cmdlet to convert a mailbox to a MailUser:
$DomainController = (Get-ADServerSettings).DefaultConfigurationDomainController.domain
$MailboxList= Get-Mailbox
foreach ($Mailbox in $MailboxList) {
    Disable-Mailbox -Id $mailbox.Identity -Confirm:$False -DomainController $DomainController
    Enable-MailUser -Id $mailbox.Identity -ExternalEmailAddress ($mailbox.alias +"@domain.com") -DomainController $DomainController
    Set-MailUser -Id $mailbox.Identity `
     -DomainController $DomainController `
     -CustomAttribute1 $Mailbox.CustomAttribute1
For more information, here is an article for your reference.
Converting a Mailbox to a MailUser
http://mikecrowley.wordpress.com/2010/12/09/converting-a-mailbox-to-a-mailuser-and-not-loosing-attributes/
Note: Microsoft is providing this information as a convenience to you. The site is not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any information found there. Please make sure that
you completely understand the risk before retrieving any suggestions from the above link.
Hope this can be helpful to you.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

Migrate from Exchange Server 2010 sp3 to 2013 sp1

I have one Exchange Server 2010 SP3 server (300 mailboxes) installed on Windows Server 2008 R2 SP1 with three major roles on it (CAS, MB and HT) - typical installation. Edge Transport server is not installed thus for controlling of mail flow
Symantec Messaging Gateway Virtual Appliance is used as Smart Host. UM server is not installed either. I set up test domain environment where I installed one domain controller (Windows Server 2008 R2 SP1) and one Exchange Server 2010 SP3 (Windows
Server 2008 R2 SP1) at first place and yesterday I did everything necessary to install Exchange Server 2013 SP1 on new test virtual server running Windows Server 2012 R2 which I successfully did.
Now in test domain I have two Exchange Servers (2010 SP3 and 2013 SP1). Is there any 100% reliable documentation with all actions that had to be taken in order to successfully migrate Exchange Server 2010 SP3 to 2013 SP1? I would want to know what
needs to be done not only for my scenario but also for other scenarios (DAG, CAS array, Edge, UM, multiple HT servers . . .) since I am interested in digging deep into Exchange Server 2013.

Hi BoxiKG,
In addition to the above mentioned, and this for your reference:
Upgrade from Exchange 2010 to Exchange 2013
http://technet.microsoft.com/en-us/library/jj898583(v=exchg.150).aspx
Best regards,
Eric

Windows Exchange Server 2010

After installation of Windows 2010 server.
can any one tell me...what are the next steps to work with Exchange Server 2010 ?
[email protected]

Hello friend,
first of all there is no version on windows server named "windows 2010 server"!!!!!
To install exchange server 2010, you can either install windows server 2008 standard/enterprise SP2 or windows server 2008 standard/enterprise R2 (actually its better to install w2k8 standard/enterprise R2 release to make the installation of exchange server
2010 easier). The server on which exchange will be installed should be part of a domain because exchange server works along with active directory
Here are the steps to follow for a successful exchange server 2010 installation:
Hardware requirements
-x64 architecture (Intel or AMD64)
-Quad core processor (minimum)
-8 GB RAM (minimum) if you want to combine the roles on one server
-2 GB HDD minimum
Software requirements
-w2k8 enterprise/standard R2 or w2k8 enterprise/standard service pack 2
-exchange server 2010 software
*Prerequisites for server 2008 standard/enterprise SP2
-Install the Microsoft.NET framework 3.5 SP1
-Install the .NET Framework 3.5 Family Update
-Install Windows Remote Management 2.0
-Install Powershell v2
-On Hub Transport & Mail Box servers install the Microsoft Filter Pack
-On Unified messaging server install server manager desktop experience
*Prerequisites for server 2008 standard/enterprise R2
-Install the Microsoft Filter Pack on Hub Transport and Mail Box server
-From PowerShell, type "Import-Module ServerManager"
-Use the Add-WindowsFeature cmdlet to type:
    Add-WindowsFeature NET-Framework, RSAT-ADDS, Web-Server, Web-Basic-Auth,
    Web-Windows-Auth, Web-Metabase, Web-Net-Ext, Web-Lgcy-Mgmt-Console, WAS-Process-Model,
    RSAT-Web-Server, Web-ISAPI-Ext, Web-Digest-Auth, Web-Dyn-Compression, NET-HTTP-Activation,
RPC-Over-HTTP-Proxy, Desktop-Experience-Restart
Note: If you are not using the Unified Messaging role you can remove Desktop Experience
After restarting, configure the TCP Port service to start automatically using: "Set-Service NetTcpPortSharing-StartupType Automatic".
Put the user account from which you performed the installation in the "Organization Management" group

Event logs fails to start on Exchange Server 2010

My Exchange server 2010 R2 SP1 Enterprise single server is down. All exchange services fail to start. It appears like the Microsoft Exchange Active Directory Topology service isn't starting which is a dependency for all other services.
The error I get when trying to start this service is:
Windows could not start the Microsoft Exchange Active Directory Topology on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code
-2147024882
To make matters worse, the event viewer is not starting either.
When trying to start the Windows Event Log, I get the error:
Windows could not start the Windows Event Log service on Local Computer. Displays Error code 5
This is running on a Windows Server 2008 R2 SP1 Standard box.
Any assistance is appreciated.

When trying to start the Windows Event Log, I get the error:
Windows could not start the Windows Event Log service on Local Computer. Displays Error code 5
Hi,
Based on this error, this problem happens if any of the following conditions are true:
The built-in security group EventLog does not have permissions on the folder %SystemRoot%\System32\winevt\Logs
The Local Service account does not have default permissions on the following registry key: HKLM\Software\Microsoft\Windows\CurrentVersion\Reliability
To solve this problem, we need to restore the default permissions in the list below on %SystemRoot%\System32\winevt\logs.
Authenticated user - List folder/read data, Read attributes, Read Extended attributes, Read permissions
Administrators - Full control
SYSTEM - Full control
EventLog - Full control
Please try the following methods:
Method 1
To restore the default permissions on folder %SystemRoot%\System32\winevt\logs, follow these steps.
Right-click on %SystemRoot%\System32\winevt\logs and select Properties.
Select the Security tab.
Click Edit button and click the Add button in the permissions dialog box.
In Select users, computers, or Groups dialog box ensure that under object types Built in Security Principals and the location as local computer name is selected.
Enter the object name as "NT SERVICE\EventLog" without quotes. And click OK. This group should have full control on the folder.
Once EventLog group is added add the rest of the groups with above mentioned permissions.
Method 2
Identify a Windows Server 2008 machine with default permissions.
Click Start, and then type cmd in the Start Search box.
In the search results list, right-click Command Prompt, and then click Run as Administrator.
When you are prompted by User Account Control, click Continue.
Type the command CD %SystemRoot%\SYSTEM32.
Once the working directory is changed to %SystemRoot%\SYSTEM32 type the command icacls winevt\* /save acl /T.
This will save a file named ACL in %SystemRoot%\SYSTEM32. Copy this file to the C: drive on the problem computer.
On the problem computer, open command prompt with administrator privileges (refer to previous steps 1-3).
Change the working directory to %SystemRoot%\SYSTEM32.
Execute the command icacls winevt\ /restore acl.
Default permissions on the registry key HKLM\Software\Microsoft\Windows\CurrentVersion\Reliability should be:
CREATOR OWNER - Full control
SYSTEM - Full control
LOCAL SERVICE - Query Value, Set Value, Create Subkey, Notify and Delete
Administrators - Full control
Users - Read
To set the permission on this registry key:
Click the Start menu, select Run and type Regedit.
Go to the location HKLM\Software\Microsoft\Windows\CurrentVersion\Reliability.
From the Edit menu click Permissions.
Add the permissions for the accounts as listed above.
In addition, Exchange 2010 SP1 and SP2 are end of support.
https://support.microsoft.com/en-us/lifecycle/search/default.aspx?alpha=exchange%20server%202010&Filter=FilterNO
Best Regards.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Lynn-Li
TechNet Community Support

Setting up Exchange Server 2010

Similar Messages

Maybe you are looking for