Exchange Server 2010 DAG requirement

Hi i am configuring Exchange server 2010 with DAG. i read that Enterprise level OS must have needed for MS-Exchange DAG
but i have 4 Windows Server 2012 standard. can i configure my DAG setup on it?
It will be like 4 hyperv
DAG Node 1 – Windows Server 2012 standard.(MS-Exchange 2010)
DAG Node 2 – Windows Server 2012 standard.(MS-Exchange 2010)
Domain Controller – Windows Server 2012 standard.
FSW Server – Windows Server 2012 standard.
Is it right environment setup for DAG?

Hello,
For Exchange 2010 DAG installation you need:
1. Windows 2012 Standard or Datacenter.
2. Windows 2008 R2 Enterprise or Datacenter.
Each node of DAG must have the same version of OS, both version and edition.
Your setup will be fully supported.
Hope it helps,
Adam
http://www.codetwo.com/?sts=3470 If this post helps resolve your issue, please click the 'Mark as Answer' or 'Helpful' button at the top of this message. By marking a post as Answered, or Helpful you help others find the answer faster.

Similar Messages

Exchange Server 2010 - DAG - Physical and Virtual

Hi All,
we are trying to configure Exchange Server 2010 SP1 DAG with TWO Servers, we are getting the error sector size on log file header was mismatch
1) Physical Server - when we check the sector size on log file - 512 bytes (RAID5)
2) Virtual Server - when we check the sector size on log file - 4096 bytes
is there any workaround to solve this issue or do i need to re-install the physical server with 4096 sector size..
When i check the Volume details on both machine
1)
Bytes Per Sector : 512
Bytes Per Physical Sector : <Not Supported>
Bytes Per Cluster : 4096
Bytes Per FileRecord Segment : 1024
2)
Bytes Per Sector : 512
Bytes Per Physical Sector : 4096
Bytes Per Cluster : 4096
Bytes Per FileRecord Segment : 1024
MCITP

Hi Jared,
I've got a question regarding your answer.
We have an existing Exchange 2010 DAG configuration with 3 mailbox servers in NL and 3 in the UK.
2 for normal databases at each site and 1 for Archive databases at each site.
The current Mailbox servers for the Archive databases are Hyper V 2008 R2 based VM's with a passthrough for storing the databases.
We now want add 1 new Mailbox server for storing archive databases at each site and add them to the DAG.
Can we use Windows 2012 Hyper-V hosts and create the new VM's with 4k sectorsize vhdx files for the new mailbox servers ?
Regards
Misha Verhoeven

Exchange server 2010 DAG configuration

Dear Boss,
I would like to configure Exchange server 2010 with DAG . I have test lab . i would like to tell my test LAB setup .
One domain controller win-2008 X 64 Ent
Two Exchange server 2010 ( Role - Client Access, Mailbox) Each Server Two Network Cards with Different Classes
IP 192.168.44.50 , 51
IP 10.0.0.10 , 20
One Exchange server 2010 ( Role - Hub Transport )
IP 192.168.44.53
Pls tell me how can i create DAG
Note:- i would like to test below steps
1. Exchange server1 may be down or network link down how server 2 to work automatically without any disturbance
2. Exchange server2 may be down or network link down down how server 1 to work automatically without any disturbance
3. Hub transport server maybe down how it can be work ?
Regards
Subash

Hi Suriya,
To create a DAG, simply use the below commands from Exchange Management Shell:
New-DatabaseAvailabilityGroup -Name "DAGNAME" -WitnessServer HUBSERVERNAME
Add-DatabaseAvailabilityGroupServer –Identity DAGNAME -MailboxServer ExchangeServer1
Add-DatabaseAvailabilityGroupServer –Identity DAGNAME -MailboxServer ExchangeServer2
New-MailboxDatabase -Name DB1 -Server
ExchangeServer1
Add-MailboxDatabaseCopy -Identity DB1 -MailboxServer
ExchangeServer2
You can run your tests now, by restarting any of the servers, and you should be able to see the DB1 will automatically failover & failback between the nodes with out any intervention.
for the HUB transport you must have another server to achieve high availability, so you can install the HUB role on a different server or add it to one of your existing servers.
Mohammad Saeed | MCSE 2003 | MCTS: Lync, OCS, Exchange

Exchange server 2010 DAG failover

Hi team ,
We have configured exchange server 2010 in DAG environment .
We have added 3 mailbox server in DAG . but my active mailbox copy failed the database are failover to another passive copy server & status is mounted . after failover emails service are not working.
Note : We have also configured NLB on CAS server .All exchange servers placed in single AD site
Please suggest

Hi
So are all your exchange servers the same? settings?
have you tried to fail the DB back to its original server? all services started on the other server?

Restoer exchange server 2010 DAG

hi
could you please let me know the prerequisite for restoration of exchange 2010 DAG which has broken one months ago.
Don't forget to mark helpful or answer connect me :- http://in.linkedin.com/in/satya11 http://facebook.com/satya.1000

Hi Satya,
If you are trying to recover a failed DAG member please check this
http://exchangeserverpro.com/exchange-recovery-failed-dag-member-exchange-server-2010/
If you are trying to recover Entire DAG Please check this
https://technet.microsoft.com/en-us/library/gg513521(v=exchg.141).aspx
Thanks, MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Moving the mailbox database copy from one exchange server to another exchange server 2010 DAG

Hello Team
is it possible to the move the passive copy of database and logs from one server to another exchange server in the same DAG with out removing and deleting the mailbox database copies in exchange 2010
normaly procedure is
Remove the mailbox database copies and manually delete the .edb files and logs from the physical location and re-add the mailbox database copy to the new server in the DAG.
is that any way to achieve to move the passive database copy to another exchange 2010 server in the same DAG ?

From your note, you appear to have a two-member DAG (with a server hosting your active database, and a second hosting the passive copy), and you want to move your passive database copy from the current passive server to another. Your note
about what "the normal procedure is" isn't 100% correct - there are many ways to handle this task, and all can be considered "normal". Why not just add the third server to the DAG and
add a database copy on that third server? Once it is fully seeded, you can remove the current passive copy. This way, you never lose your redundancy.
Yes i can add the third and fourth serve in DAG , but i cannot add the mailbox database copies to the 3rd and 4th mailbox server in DAG as am using RTM version of exchange 2010 which is allowing to have only 5 database inclding mailbox datbase copies
and also currently my lab setup is two member dag (with a server hosting your active database,
and a second hosting the passive copy) in the same site named SITE A
and recently i have created new SITE B and included the 3rd and 4th DAG members in the same DAG
i want the mailbox database copies from the mailbox server database in SITE A to
Mailbox server database in SITE B as passive copy
That is why i want to move the mailbox database without deleting / removing it manually
Hope you understand my situation!

Exchange Server 2010 get error HResult = -2147024891 when Accessing Virtual Directories on CAS

I've just installed a Exchange 2010 server in an Exchange 2007 server environment.
The 2007 enviroment include two exchange server "Server-A" and "Server-B"
and "Server B" has dead on hardware issue for half year.
When I go to Microsoft Exchange On-Premises -> ServerConfiguration -> Client Access and receive the following error message
An IIS directory entry couldn't be created. The error message is Access is denied. . HResult = -2147024891 It was running the command 'Get-OabVirtualDirectory'
I try run the “Get-OwaVirtualDirectory” in powershell and get following result
From the power Shell command prompt .. Run
[PS] C:\Windows\system32>Get-OwaVirtualDirectory
An IIS directory entry couldn’t be created. The error message is Access is denied.
. HResult = -2147024891
+ CategoryInfo : NotInstalled: (<Server-B\Exchange (Default Web Site):ADObjectId) [Get-OwaVirtualDirectory]
, IISGeneralCOMException
+ FullyQualifiedErrorId : 4B12EB5D,Microsoft.Exchange.Management.SystemConfigurationTasks.GetOwaVirtualDirectory
I've google that i need to add "Exchange Trusted Subsystem" as a member in local admin group in Exchange 2007
but my exchange 2007 "Server-B" already dead, how should i fix it?
Appreciate for any help!!

re-create the new virtual directories does not work for me.
still got the error
An IIS directory entry
couldn’t be created. The error message is Access is denied.
. HResult = -2147024891
+ CategoryInfo : NotInstalled: (<Server-B\Exchange (Default Web Site):ADObjectId) [Get-OwaVirtualDirectory]
, IISGeneralCOMException
+ FullyQualifiedErrorId : 4B12EB5D,Microsoft.Exchange.Management.SystemConfigurationTasks.GetOwaVirtualDirectory
I don't understand why change new exchange server 2010 setting require me to have permission to access
my dead exchange server 2007

DAG in exchange server 2010 across different sites

hello ;
I want to know the best way to implement DAG for exchange server 2010 across 2 sites in the same domain ,
I have 2 exchanger server in one site in DAG ,with 300 gb database size
but I want to implement exchange server 2010 in a new site within the same domain and this will be my 3rd exchange server and will be a member on my existing DAG in the head office
the new site is linked to my head office using ipvpn connection which is 6 mb , and ADC is there in the new site,
what is the best way to implement the new exchange server in the new site to join the existing DAG .
is there is any problem related to DAG in this scenario ?
what is the best way to implement this scenario ?
Thanks

Hi,
For each AD site, it is recommended to have at least there Exchange roles: CAS, HUB, and MBX roles.
Do you plan to have active users in this new site?
If there are active users in this new site, you can deploy a Three-Member DAG in two AD sites. However, it is recommended to deploy two DAGs in two AD sites and you should have at least two DAG members each AD site. This scenario, two witness servers in
separate site is necessary.
If the new site is only for DR purpose, you can install this new Exchange server and add it to DAG. After that, add database copy to this new server.
Besides that, here are two articles which may help you for your reference.
Database Availability Group Design Examples
http://technet.microsoft.com/en-us/library/dd979781(v=exchg.141).aspx
Understanding Database Availability Groups
http://technet.microsoft.com/en-us/library/dd979799(v=exchg.141).aspx
Hope this helps.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

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 configure Mailbox Read-Only access for Mailbox's owner on Exchange Server 2010?

I have to configure the Exchange Server 2010's mailbox to only grant Read-Only Access on the mailbox's owners. So they can only allowed to read their messages and cannot modify or remove them. Are there any references or methods to do?

Hi,alexchy8
We can make use of 2 PowerShell commands to achieve this goal.
Add-MailboxPermission and Add-MailboxFolderPermission.
Execute the Add-MailboxPermission command to delegate the read permission at mailbox level.
Execute the Add-MailboxFolderPermission command to delegate the required permissions on specific folders inside the mailbox.
You can read the following article as reference:
http://www.exchangedictionary.com/articles/assign-read-only-mailbox-permission-on-exchange-2010-2013-powershell
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety,
or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.
Best Regards.

When sending e-mail messages to a mail-enabled public folder that have been replicated from old Exchange Server 2000/2003/2007, Exchange Server 2010 environment mails are rejected with NDR.

Hi, I would like to share with you issue that I’ve solved regarding mail-enabled PF that migrated from Exchange 2000/2003/2007 to 2010, I’ve searched & contacted my MVP leader – there’s no official KB regarding this issue right
now, so I’m posting here in order to share this among others.
Note: There’s article(s) that talked about PF replication from Exch2000/2003/2007 to 2010 – this is the same issue as well.
Symptoms
E-mail messages that been sent to mail-enabled public folder in Exchange Server 2010 environment rejected with the following NDR:
“#< #5.2.0 smtp;554 5.2.0 STOREDRV.Deliver.Exception:ObjectNotFoundException; Failed to process message due to a permanent exception with message The Active Directory user wasn’t found. ObjectNotFoundException: The Active Directory
user wasn’t found.> #SMTP#”
Sometimes Exchange Server 2010 is documented as well Event ID 1020 on the Event Viewer with this information:
“Log Name: Application
Source: MSExchange Store Driver
Event ID: 1020
Level: Error
Description:
The store driver couldn’t deliver the public folder replication message "Hierarchy ([email protected])" because the following error occurred: The Active Directory user wasn't found.”
Cause
In an environment where Microsoft Exchange Server 2000 or Microsoft Exchange Server 2003 previously existed, and all those servers have been removed, there is a chance that an Administrative Group (First Administrative Group or another custom Administrative
Group) remains with a Servers container, but no servers inside it.
During replication, when the Exchange 2010 Store Driver sees the empty Servers container in Active Directory, it's expecting a System Attendant object inside the container and when it is not found the error occurs.
Resolution
To work around the issue, delete the empty Servers container. This can't be done through Exchange System Manager. Use the ADSI Edit tool to remove it using the following steps:
Warning If you use the ADSI Edit snap-in, the LDP utility, or any other LDAP version 3 client, and you incorrectly modify the attributes of Active Directory objects, you can cause serious problems. These problems may require you to reinstall Microsoft Windows
2003 Server, Microsoft Windows Server 2008, Microsoft Exchange 2010 Server or both Windows and Exchange. Microsoft cannot guarantee that problems that occur if you incorrectly modify Active Directory object attributes can be solved. Modify these attributes
at your own risk.
1.
Start the ADSI Edit MMC Snap-in. Click Start, then
Run, and type adsiedit.msc, and then click OK.
2.
Connect & Expand the Configuration Container [YourServer.DNSDomainName.com], and then expand
CN=Configuration,DC=DNSDomainName,DC=com.
3.
Expand CN=Services, and then CN=Microsoft Exchange, and then expand
CN=YourOrganizationName.
4.
You will see an empty Administrative Group. Expand the
CN=YourAdministrativeGroupName.
5.
Expand CN=Servers.
6.
Verify there are no server objects listed under the
CN=Servers container.
7.
Right click on the empty CN=Servers container and choose
Delete.
8.
Verify the modification, and try to send again the E-mail to the mail-enabled public folder.
Applies to
Exchange Server 2010, Standard Edition
Exchange Server 2010, Enterprise Edition
Netanel Ben-Shushan, MCSA/E, MCTS, MCITP, Windows Expert-IT Pro MVP. IT Consultant & Trainer | Website (Hebrew): http://www.ben-shushan.net | IT Services: http://www.ben-shushan.net/services | Weblog (Hebrew): http://blogs.microsoft.co.il/blogs/netanelb
| E-mail: [email protected]

Sounds like you are looking in the wrong Administrative Group container which is why you are seeing your Exchange 2010 servers in there.
When you install Exchange 2003 only you will see a container named by default as "CN=First Administrative Group" container. But this could be named anything if you changed the Organization Name on the installation when you installed the first
Exchange 2003 server into the domain/forest.
You will notice that when you install Exchange 2010 part of the AD setup is to create a new configuration container and is named by default "CN=First Administrative Group (FYDIBOHF23SPDLT)".
So it sounds like you are not looking in the right location within ADSIEdit.
You may find the following article also helpful for this issue which is the same resolution:
http://blogs.technet.com/b/sbs/archive/2012/05/17/empty-cn-servers-container-causing-issues-with-public-folders-on-small-business-server-2011.aspx
I recommend though that you ensure your Exchange 2003 servers are fully uninstalled or no longer present in your environment before you go deleting the Servers container though.. The following Microsoft article will help with this:
http://technet.microsoft.com/en-gb/library/gg576862(v=exchg.141).aspx

Send As, Send on Behalf and Full Access for Exchange server 2010/2013

[This FAQ contains 2 parts]
Testing and watching the behavior of Send As, Send On Behalf and Full Access permission.
Common issue and Troubleshooting on the three permission.
[Testing and Watching]
Based on following blog, I decide to test on my lab:
Full Mailbox Access Rights + Send On Behalf = Send As ?
http://blogs.technet.com/b/ehlro/archive/2012/04/06/full-mailbox-access-rights-send-on-behalf-send-as.aspx
Description on my lab and test:
Exchange 2010 + Outlook 2010
Exchange 2013 + Outlook 2013
Senders: A01, A02, … , A07, A08
Recipient: A09
A01 grand permission to other senders.
Two methods:
a. Use A0x’s credential configure A01’s profile, then send From both A01 and A0x via Outlook. Watching result in A09’s Inbox and Sent Items which has message copy left.
b. Use A0x’s credential configure A0x’s profile, then send From both A01 and A0x via Outlook. Watching result in A09’s Inbox and Sent Items which has message copy left.
Result as following forms:
1. Exchange 2010 + Outlook 2010 / Exchange 2013 + Outlook 2013
Using A0x’s credential configure A01’s mailbox, then send From both A01 and A0x
To A09.
2. Exchange 2010 + Outlook 2010 / Exchange 2013 + Outlook 2013
Using A0x’s credential configure A0x’s mailbox, then send From both A01 and A0x
To A09.
[Common Issue]
1. [Issue]
Exchange 2010 + Outlook 2010. A01 grand A03 Send As permission. However A03 can’t send as A01 to A09 and get NDR:
You can’t send a message on behalf of this user unless you have permission to do so. Please make sure you’re sending on behalf of the correct sender, or request the necessary permission. If the problem continues, please contact your helpdesk.
Details as following pic:
[Troubleshooting]
1) Based on the NDR, it seems a permission issue. Check Send As permission, however the Send As permission configured correctly. Pic as below:
2) ince the Send As permission configured correctly, it seems the permission hasn’t been replicated. Try to restart Microsoft Exchange Information Store service. It works.
Note: The Send As permission isn’t granted until after replication has occurred. Replication times depend on your Exchange and network configuration. To grant the permission immediately, stop and then restart the Microsoft Exchange Information
Store service.
2. [Issue]
Exchange 2013 + Outlook 2013. A01 grand A03 Send As permission. However A03 can’t send as A01 to A09 and get NDR:
Your message did not reach some or all of the intended recipients.
Subject: xxx
Sent: xx/xx/2014 8:20 AM
The following recipient(s) cannot be reached: A09
This message could not be sent. Try sending the message again later, or contact your network administrator. Error is [0x80070005-00000000-00000000].
Details as below:
[Troubleshooting]
1) Also check the Send As permission configuration first.
2) Then try to use A03 send as A01 to A09 via OWA. If OWA works well, it seems and issue on the Outlook client side.
3) This behavior may occur if the OAB in Outlook isn’t updated. Try to download OAB manually.
4) If doesn’t work, please close Outlook and try to delete all the OAB folder on your computer. The path of OAB folder in Win7, Win8 as below:
\Users\<UserName>\AppData\Local\Microsoft\Outlook\Offline Address Books
5) Restart Outlook.
Note: Be aware that you cannot send e-mail messages on behalf of a mailbox if the mailbox is hidden from address list. When sending a message, Exchange requires that e-mail address is resolved in the
From field.
3. [Issue]
Exchange 2010. A01 grant A0x “Send As” or “Send on Behalf” permission. A0x send as/ send on behalf of A01. The message is only copied to the Sent Items folder in A0x’s mailbox (same as the result of my test). Also cannot configure Exchange 2010 so that the
message is copied to the Sent Items folder of both A01 and A0x.
[Troubleshooting]
This issue occurs because Exchange server 2010 was designed to copy message to the Sent Items folder of the sender only. This issue can be solved by installing Exchange 2010 SP2 UR4. More details in the following KB:
Messages that are sent by using the "Send As" and "Send on behalf" permissions are copied only to the Sent Items folder of the sender in an Exchange Server 2010 environment
http://support.microsoft.com/kb/2632409/en-us
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Nice guide Mavis, I recently explored the same topic. Few things you might want to add is the type of connectivity (Cached vs Online will produce different results) and to expand further on the methods of adding the other mailbox in Outlook (additional mailbox
vs additional account defaults to different methods). Check the screenshot:
And please post this somewhere more visible, like blog/wiki page.

Exchange Server 2010 - OWA, ECP, EWS not working

Hello,
I am evaluating exchange server 2010. I was able to install it, but now the admin websites will not render in IIS. OWA, ECP, etc. I especially want Outlook Anywhere to work. I can admin through the windows admin interface so that's not a concern.
I want users to access their email through the web as well. I checked permissions but could have them wrong. Any help is appreciated.
Thanks
John Grace

There are about twenty different types of 403 error. To see which one is happening here, you'd need to look at the IIS log files, and get the status subcode, which is the number after the 403 in the logged line.
The most common, though, is 403.4, which means 'SSL Required'. What happens if you go to
https://servername (i.e. https instead of http).
Another one is 403.6, which means that IIS has been configured to only allow access to a certain range of IP address, and the one you're trying to access it from isn't one of them.
OWA For SmartPhone

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 DAG requirement

Similar Messages

Maybe you are looking for