Moving Exchange 2010 Mailbox replicated databases path in DAG environments.

Hi there,
I’m trying to get some feedback on the topic of moving Exchange 2010 Mailbox replicated databases path in DAG environments.
Here is the situation: I currently have a 3-Node DAG (Node 1 and Node 2 are in my main datacenter, and Node 3 in my Disaster Recovery (DR) site in a remote location.
I have DB copies in Node 2 and Node 3. The thing is that the DB copies in Node 2 are in an older storage box and since we got a new storage box, I need to move the DBs and related logs of Node 2 to the new storage box
I have found some information about how to deal with this (below I’m listing a KB link) but I would like to reconfirm a couple of things to make sure I’m understanding this correctly
Move the Mailbox Database Path for a Mailbox Database Copy:
https://technet.microsoft.com/en-us/library/dd979782%28v=exchg.141%29.aspx
According to the KB: “If the mailbox database being moved is replicated to one or more mailbox database copies, you must follow the procedure in this topic to move the mailbox
database path”
Would this apply to my case even when I’m moving the BDs copies and Logs on Node 2 as opposed to Node 1 where the source DBs are?
On step #3 in the procedure, you are supposed to “Remove all mailbox database copies for the database being moved. After all copies are removed, preserve the database and transaction log files from each server from which the database copy is being removed
by moving them to another location. These files are being preserved so the database copies do not require re-seeding after they have been re-added.”
Then in Step # 7, you are supposed to “Add all of the database copies that were removed in Step #3”
As far as I know, when you add a copy of a database, Exchange creates the copy DB and starts to seed the replica servers with an up to date copy of the DB and all the current transaction logs at that point…according to the instructions
above, you are supposed to re-add the DB copied we preserved...does it mean that we need to wait for the DBs seed process to finish after “adding the DB copy” and then replace the new DBs copies and logs created by the “Add database copy” function with the
DB and logs preserved in Step #3?
Thanks in advance for your feedback!
FT
FT

Hi there,
What the article is stating is that once you have removed the copies you can keep the existing transaction log files and database edb file to allow you not to have to do a full seed. You can do this by using the -seedingpostponed parameter in
Add-MailboxDatabaseCopy
However, and quite honestly, if your database isn't that big and your are not worried about performing a full copy of the database again to the other DAG members once you have moved your database to its preferred new location, just add the copy in the normal
way and remove the legacy files afterwards.
Oliver Moazzezi | Exchange MVP, MCSA:M, MCITP:Exchange 2010,Exchange 2013, BA (Hons) Anim | http://www.exchange2010.com | http://www.cobweb.com | http://twitter.com/OliverMoazzezi

Similar Messages

Restore exchange 2010 mailbox from database and restore the mailbox to pst file

Hello,
I'm running exchange 2010Sp2 rollup5 ver2, the mailbox database in question is in a DAG. The databases are being backed up by commvault.
So, I received a request to restore a couple mailboxes from 10 days ago and export the mailbox to PST file for archiving.
How would you go about the restore. I'm thinking the database needs to be offline, so I don't mistakenly overwrite my production databases.
Where should backup guy restore the database/log file (completely separate server from my mailbox servers?)
Once database/logs are restored, what is the procedure to make the mailboxes visible
Once the mailboxes are visible, what is best way to restore one to a PST file?
thanks in advance for all your help.

Hi
For DB Restores with commvault you have to reed the product documantation.
The Database must not be offline.
I would recommend to try the following steps:
1. Create Recovery DB on Exchange
http://terenceluk.blogspot.ch/2013/06/restoring-mailbox-from-exchange-2010.html
2. Restore to this Recvovery DB from Commvault
(Commvault Administration Guide)
http://documentation.commvault.com/hds/release_9_0_0/books_online_1/english_us/pdf/exchange_db_admin.pdf
3. Restore to a temporary Mailbox and take a PST
Restore Mailbox from Recovery Database
http://technet.microsoft.com/en-us/library/bb125218(v=exchg.141).aspx
Create the PST with Outlook or Exchange Powershell Export Requests
http://technet.microsoft.com/en-us/library/ee633479(v=exchg.141).aspx
Georg

Error in moving exchange 2010 mailboxes to Exchange 2013 SP1 during migration

Dear All,
We were running Exchange 2010 SP3 with MBX/HT/CAS role in single server. Now we are migrating our exchange 2010 to Exchange 2013 SP1. After configuring co-existence and during the mailbox move from Exchange 2010 to Exchange 2013 SP1, we are facing below
error. Please help to troubleshot. As per our search on net, people were suggesting that it can be due to not able to resolve NetBIOS name. We checked same and we are able to ping both servers by NetBIOS and FQDN names.
[PS] C:\Windows\system32>New-MoveRequest -Identity
'[email protected]' -TargetDatabase "CI-DB01"
MapiExceptionNetworkError: Unable to make connection to the server. (hr=0x80004005, ec=2423)
Diagnostic context:
    Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 1722
    Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 323
    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0
    Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 0
    Lid: 62184
    Lid: 16280   dwParam: 0x0 Msg: EEInfo: ComputerName: n/a
    Lid: 8600    dwParam: 0x0 Msg: EEInfo: ProcessID: 6004
    Lid: 12696   dwParam: 0x0 Msg: EEInfo: Generation Time: 0414-08-21T09:10:43.8970000Z
    Lid: 10648   dwParam: 0x0 Msg: EEInfo: Generating component: 18
    Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 1237
    Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 313
    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0
    Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 0
    Lid: 62184
    Lid: 16280   dwParam: 0x0 Msg: EEInfo: ComputerName: n/a
    Lid: 8600    dwParam: 0x0 Msg: EEInfo: ProcessID: 6004
    Lid: 12696   dwParam: 0x0 Msg: EEInfo: Generation Time: 0414-08-21T09:10:43.8970000Z
    Lid: 10648   dwParam: 0x0 Msg: EEInfo: Generating component: 18
    Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 10060
    Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 311
    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0
    Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 3
    Lid: 12952   dwParam: 0x0 Msg: EEInfo: prm[0]: Long val: 22964
    Lid: 15000   dwParam: 0x0 Msg: EEInfo: prm[1]: Pointer val: 0x0
    Lid: 15000   dwParam: 0x0 Msg: EEInfo: prm[2]: Pointer val: 0xFE01A8C000000000
    Lid: 62184
    Lid: 16280   dwParam: 0x0 Msg: EEInfo: ComputerName: n/a
    Lid: 8600    dwParam: 0x0 Msg: EEInfo: ProcessID: 6004
    Lid: 12696   dwParam: 0x0 Msg: EEInfo: Generation Time: 0414-08-21T09:10:43.8970000Z
    Lid: 10648   dwParam: 0x0 Msg: EEInfo: Generating component: 18
    Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 10060
    Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 318
    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0
    Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 0
    Lid: 53361   StoreEc: 0x977
    Lid: 51859
    Lid: 33649   StoreEc: 0x977
    Lid: 43315
    Lid: 58225   StoreEc: 0x977
    Lid: 39912   StoreEc: 0x977
    Lid: 54129   StoreEc: 0x977
    Lid: 50519
    Lid: 59735   StoreEc: 0x977
    Lid: 59199
    Lid: 27356   StoreEc: 0x977
    Lid: 65279
    Lid: 52465   StoreEc: 0x977
    Lid: 60065
    Lid: 33777   StoreEc: 0x977
    Lid: 59805
    Lid: 52487   StoreEc: 0x977
    Lid: 19778
    Lid: 27970   StoreEc: 0x977
    Lid: 17730
    Lid: 25922   StoreEc: 0x977
    + CategoryInfo          : NotSpecified: (:) [New-MoveRequest], RemoteTransientException
    + FullyQualifiedErrorId : [Server=Exch01,RequestId=f6886977-92f1-4148-991b-aa76b449aff5,TimeStamp=8/21/2014 9:1
   0:43 AM] [FailureCategory=Cmdlet-RemoteTransientException] 7FCC37,Microsoft.Exchange.Management.RecipientTasks.New
MoveRequest
+ PSComputerName        : Exch01.domain.local
Please help as we are stuck here!!
Thanks in advance!!

Can yo ping server by name not by FQDN? e.g. ping server1.
Make sure firewall/antivirus not blocking communication. Disable antivirus and try
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.

Exchange 2010 - Dismount Mail Database on a DAG

Hi All,
I'm experiencing an issue in which 2 Mail Databases out of 3 within a DAG are not truncating the log files after a full backup, so for those 2 I currently have Circular Logging turned on.
I spoke with an outside Exchange source that recommended trying to dismount the Mail Databases and bounce the Information Store on both Mailbox Servers. To give it a "fresh start."
Here's what was recommended:
Get-MailboxDatabase -Server mbx* | dismount-Database
get-service -computername mbx1 msexchangeIS | restart-service
get-service -computername mbx2 msexchangeIS | restart-service
Get-MailboxDatabase -Server mbx* | mount-Database
I have to be honest. I've never really had to dismount the Mail Databases in a DAG before. Has anyone else - if so, does the above seem okay to you?
Thanks,
Mr Mister

Hi,
Agree with Andy. You can dismount a database in a mailbox server, a member of a DAG, which is similar as what you do for a mailbox server that is not a DAG member.
Full and Incremental backups will truncate the transaction log files, please make sure your backup is one of these two types.
If a server hosting the data being backed up is a member of a DAG, and this server hosts both active and passive database copies, we must disable the Microsoft Exchange Replication service VSS writer.
So, please check if you have disabled the Exchange Replication VSS writer.
Besides, to narrow down the issue that the transaction log files were not truncated after backup, I recommend you check the application log to see if there is any related events.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

I can't either mount for remove Exchange 2010 mailbox database file

Yesterday I proceeded with moving Exchange 2010 database file to a newly installed hard drive because my "C" drive was running out of space. After dismouting both the mailbox database and the public folder database, I used EMC's "move
data path" wizard to move both the mailbox database and public folder database to "mailbox" folder in "D" drive. The move was successful without an error, but when I opened "mailbox" folder in "D" drive, both
the database file and public folder database files weren't there. All the other files were moved, but the mailbox database file was gone.
Luckily I manually copied entire mailbox folder to another folder in "D" drive. So I manually copied mailbox database file (it is about 20GB) to "d:\mailbox". When I try to mount, I received the following error message.
Microsoft Exchange Error
Failed to mount database 'Mailbox Database 1658107303'.
Mailbox Database 1658107303
Failed
Error:
Couldn't mount the database that you specified. Specified database: Mailbox Database 1658107303; Error code: An Active Manager operation failed. Error The Microsoft Exchange Replication service may not be running on server bigrock.BKSERVER.LOCAL. Specific RPC
error message: Error 0x6d9 (There are no more endpoints available from the endpoint mapper) from cli_MountDatabase3..
An Active Manager operation failed. Error The Microsoft Exchange Replication service may not be running on server bigrock.BKSERVER.LOCAL. Specific RPC error message: Error 0x6d9 (There are no more endpoints available from the endpoint mapper) from cli_MountDatabase3.
Error 0x6d9 (There are no more endpoints available from the endpoint mapper) from cli_MountDatabase3
When I try to move the database path back to the original path, I received the following error message.
Mailbox Database 1658107303
Failed
Error:
There are no source files under the path:d:\emailbox\Mailbox Database 1658107303. Use the command Move-DatabasePath -ConfigurationOnly in the Exchange Management Shell to set the new path in Active Directory only.
Exchange Management Shell command attempted:
move-DatabasePath -Identity 'Mailbox Database 1658107303' -EdbFilePath 'c:\progam files\microsoft\exchange server\v14\mailbox\mailbox database 1658107303\Mailbox Database 1658107303.edb' -LogFolderPath 'c:\progam files\microsoft\exchange server\v14\mailbox\mailbox
database 1658107303'
EMC would not even delete the database file.
I need help. I need to mount my mailbox database file. Please help.

If the database was fine pre move I doubt it needs a repair, however if you want to validate do an eseutil /mh ReplaceWithYourDatabaseName.edb and post the results here
did you move the logs as well or are they still in same location
I have seen this before if everything is where its supposed to bea restart fixed it so I would recommend that you put the DB back into the NEW D path and do a restart to see if that resolves the issue
Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline Exchange Mailbox and Public Folder EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003
--> 2007 --> 2010 --> 2013 with Lucid8's
DigiScope

Moving Exchange 2010 Transaction Log

Hi. Running a single instance of SBS2011 with Exchange 2010. We only have one mailbox.
Earlier today I moved our main exchange database (.edb) file to a different hard drive. Used EMC, went through smoothly, no issues.
I then started moving the transaction logs. Same process:
Exchange Management Console > Organization Configuration > Mailbox > Move
Database Paths
This appeared to be going fine but after 40 mins came up with an error along the lines of "WinRM cannot process the request in the time specified"
Now I cant access any mailboxes. OWA giving the error - Your mailbox appears to be unavailable. Try to access it again in 10 seconds. If you see this
error again, contact your helpdesk
I have checked in EMC and the mailbox is successfully mounted. I have restarted all exchange services.
I also now have 8.5GB of log files in the "new" location. Not if these are just copies or exchange is actually using this drive.

Hi:
I think you may be over complicating this. SBS includes a wizard in the SBS Console to move most/all of the user impacted data stores, including Exchange, SharePoint, WSUS and Redirected folders. The transaction logs are limited in size if you
use either the SBS backup or a third party backup that is "Exchange Aware" to backup the server or the Exchange subsystem, so there is really no need to move the logs, assuming you are making good backups.
Larry Struckmeyer[MVP] If your question is answered please mark the response as the answer so that others can benefit.

Exchange 2010 mailbox moves get stalled

I am Experiencing an issue with Exchange 2010 SP3 UR2 two node DAG environment (server01 and server02). While moving mailboxes from old Exchange 2007 environment I get following errors.
Move for mailbox xxxxxxxxxxxx is stalled because DataMoveReplicationConstraint is not satisfied for the database 'MDB01' (agent MailboxDatabaseReplication). Failure Reason: Database does not satisfy constraint SecondCopy. Throttling completion as database copies
are falling behind.
Get-MailboxDatabaseCopyStatus informs me that server02 Copy and ReplayQueue length on the passive copy are getting big (from 10-500) while moving and the throttling will always pause the move for a while and then start again until it stops again because the
second copy is falling behind. This only happens when I move mailboxes to databases that have active copy of the database on my server01 and passive on server 02. If the active copy is moved to server02 and server01 is the passive copy this does not happen.
So this leads to a conclusion that there is something wrong with server02 replication from server01.
I've traced the replication network and there are no issues. What could be the reason that only the second node suffers from falling back during moves? I would not like to se the datamovereplicationconstraint value to none since this is the only Exhchange
2010 DAG environment where I am facing this issue and the replication should keep up while mailbox moves.

Hello,
" I would not like to see the datamovereplicationconstraint value to none". Do you mean you set
DataMoveReplicationConstraint to SecondCopy? If so, I recommend you use test-replicationhealth cmdlet to check all aspects of the replication and replay status.
Please check if you
configure a lagged database copy.
Please check if there is a witness server, and whether the witness is online.
If not, please set DataMoveReplicationConstraint to SecondCopy.
Besides, please check if there is any error in application log.
Here are some articles for your reference.
http://technet.microsoft.com/en-us/library/dd335158(v=exchg.150).aspx
http://blogs.technet.com/b/exchange/archive/2011/05/06/exchange-2010-mailbox-moves-and-mailbox-resiliency.aspx
If you have any feedback on our support, please click
here
Cara Chen
TechNet Community Support

How to monitor particular individual Exchange 2010 mailbox

Hi
Is it possible to monitor a particular individual Exchange 2010 mailbox? If so please send me the script or steps to to accomplish this
Donald D'souza (http://donald-scom.blogspot.com/)

The Exchange 2010 MP has had some issues of late and is once again unavailable. Hopefully this should be rectified soon. Keep an eye on the Management Pack forum and someone should post there once it is back.
I appreciate the Exchange team are looking for ways to get extra monitoring from SCOM and I'm certainly not saying you can't do mailbox monitoring with SCOM. I'm just saying be careful. I have seen one enterprise write a discovery to discover the
mailboxes they wanted to monitor. The discovery captured data that changed every iteration that the discovery ran. They then wondered why SCOM stopped working, ignoring the fact that they had discovered thousands of objects whose properties changed every
time discovery ran, causing huge numbers of state change events and massive database growth.
If you are looking for in-depth exchange mailbox monitoring then SCOM is not the tool for it. Quest and Sirana do dedicated enterprise tools. If you take a look at the links and say that is what your team want then I'd suggest evaluating those
products. Developing SCOM to deliver that would not be cost efficient.
Hope you don't mind but I'll ask again - what specifically do you want to monitor? Mailbox Size? Number of emails sent \ received? size of message sent? destination? number of attachments? size of attachments? blocked messages? If you need deep detail
along the lines of the following then you really need to evaluate the following:
http://www.sirana.com/exchange/reporting
If you end up writing scripts to do all the above then you will likely severely impact performance of either SCOM or your Exchange server or possibly both.
Sadly (for budgeting) SCOM doesn't necessarily replace specialist tools - it just complements them. Likewise, if you want deep dive SQL then you'll still need Quest or Idera based tools. Probably fewer licenses and better targetted at servers with known
issues.
Cheers
Graham
Regards Graham New System Center 2012 Blog! -
http://www.systemcentersolutions.co.uk
View OpsMgr tips and tricks at
http://systemcentersolutions.wordpress.com/

Unable to remove orpahned Exchange 2010 mailbox databse server permantely offline

Greetings,
I am having great problems removing and Exchange 2010 mailbox Database, the server that the database resided upon is permanently offline and gone,
Under Organization Configuration / mailbox
The orphaned database is listed there however I cannot delete it under Database Copies a copy of the orphaned database is listed as offline.
How can I remove this database if the server is offline?

run ADSIEDIT.msc
Select Configuration well-known naming configuration -> CN=Configuration -> CN=Services -> CN=Microsoft Exchange -> CN=<YourExchOrgName> -> CN=Administrative Group -> CN=Exchange Administrative
Group (FYDIBOHF23SPDLT) -> CN=Servers > CN=Databases -> Select Exchange 2010 database name and delete
MCP, MCSE 2000 , MCSA 2000 ,MCSA 2003 , MCITP , MCTS , MCT

Auto-Mapping Exchange 2013 Mailboxs in an Exchange 2010 Mailbox

We're in the middle of migrating mailboxes from Exchange 2010 to Exchange 2013. Many of our users have Auto-Mapped mailboxes as well. In my testing, I've found that I cannot Auto-Map a mailbox that's on Exchange 2013 in a Exchange 2010 mailbox. I can manually
add it and it works fine. Is this by design with this type of coexistence or is there a fix for it? Our current Exchange 2010 environment is at SP3 with UR2.
Orange County District Attorney

This issues is fixed in UR5 so suggest you to upgrade Exchange 2010 to SP3 UR5.
Reference Thread: http://social.technet.microsoft.com/Forums/exchange/en-US/a2aa4163-f74b-401f-aec5-13324e6b29c8/exchange-2010-mailbox-not-able-to-access-automapped-exchange-2013-cu3-mailbox?forum=exchangesvradmin
Blog |
Get Your Exchange Powershell Tip of the Day from here

Exchange 2013 / 2010 co-existence - Outlook won't connect to Exchange 2010 mailboxes

Greetings! I have a lab set up at home where I have been testing co-existence of Exchange 2013 and 2010 for a future corporate upgrade project.
I am running into some odd behavior. Any mailbox that has been migrated to Exchange 2013 works just fine, however, when I try to set up Outlook for a mailbox still on Exchange 2010 I receive errors. OWA works just fine for these Exchange
2010 mailboxes, it is just Outlook that has the problem. This is what I am running into:
1. Outlook uses autodiscover to locate server settings. It fails at the 'logging on to mail server' step saying that Exchange isn't available; Outlook must be connected, etc.
2. It then gives me the settings box for Exchange server and Mailbox. This is auto populated with one of the Exchange 2013 servers (there are 3 of them, all have both MBX and CAS role). If I then change the server to the Exchange 2010 CAS server,
and hit 'check names', it underlines the very same entries (like it found them this time) that were there initially and goes on to finish the configuration.
3. When I launch Outlook with this Exchange 2010 user, it fails to open with the error message that the set of folders couldn't be opened.
I've been doing as much research on this as I can. I've tried disabling IPv6 to no avail. It seems as if perhaps the issue is with Exchange 2013 proxying the request back to the Exchange 2010 servers but I am not sure what to check in that regards.
Any suggestions? Thanks in advance!

Hi,
Don´t disable IPV6 on an Exchange Server, it is, in my opinion not necessary - also applies for AD.
You can use your original SSL Cert for your new Ex 2013 environment.
In dns you want two host A records: mail.domain.com and autodiscover.domain.com
On your 2013 set your internal and external virtual directories to mail.domain.com
leave autodiscover and Powershell alone.
Also set the autodiscover URI to your Certificate name ie. mail.domain.com
Set-ClientAccessServer -Identity "YourCASServer" -AutoDiscoverServiceInternalUri "https://mail.domain.com/autodiscover/autodiscover.xml"
Thanks. I wanted to give some additional info before I run any commands. I currently have an A record for autodiscover and it is pointed to the Exchange 2013 DAG/cluster IP. I have a 3 entries for mail.domain, for DNS round robin; basically
it is listed 3 times for the IP of each of my Exchange 2013 servers. Does any of this sound problematic?

Exchange 2010 mailbox prompts for authentication to Exchange 2013 mailbox

I am in the process of a 2010 to 2013 migration. The only issue I can't seem to manage is an authentication issue with Outlook 2010. My Outlook profile consists of my Exchange 2013 mailbox and a shared mailbox on Exchange 2010. Initially, Outlook was prompting
for authentication to the Exchange 2010 mailbox. Regardless of whether I entered the correct credentials or simply cancelled the prompt, I still had full access to both mailboxes (including Public Folders on 2010). The authentication prompt was removed with
the following command:
Get-OutlookAnywhere -Server my2013exchserver | Set-OutlookAnywhere -InternalClientsRequireSsl $true
The second issue I now have is the reverse of the above: an Exchange 2010 user is prompted for authentication to an Exchange 2013 mailbox. How do I begin to troubleshoot this problem - should I run the same command (above) on 2010? I don't quite understand
how Outlook communicates with Exchange but I am thinking there is an incorrect setting on one of the Virtual Directories(?).
Many thanks.

Hi Dennis,
Please open Outlook - press CTRL key - right click on the Outlook icon from right bottom corner taskbar –Connection Status to check the connection for your Exchange 2010 mailbox with shared 2013 mailbox. The following example in my test results:
Please check your connection authentication. We can run the following command to set your Outlook Anywhere for Exchange 2013:
Set-OutlookAnywhere -Identity "E15-01\Rpc (Default Web Site)" -InternalClientAuthenticationMethod Ntlm -ExternalClientAuthenticationMethod Basic -ExternalClientsRequireSsl $True -InternalClientsRequireSsl $true
In Outlook side, please ensure the following settings in Account Settings:
In Security tab, make sure Always prompt for logon credentials is unchecked and Logon network security is set to Negotiate Authentication.
Regards,
Winnie Liang
TechNet Community Support

Outlook 2007 Clients Cannot Access Free/Busy Calendar info. for Exchange 2010 Mailbox

Hi:
I have Outlook 2007 clients that cannot access Free/Busy Calendar info. for Exchange 2010 mailboxes. They receive error like "...you do not have appropriate permissions..."
If those same users logon to a machine running Outlook 2010 then they can view the free/busy info. of the other user's mailbox, so I believe the permissions are set correctly on the mailbox to allow the viewing.
Any insights are greatly appreciated!
Thank you!
Bob Herman IT Tropolis

Hi Herman,
As you said, it seems users have proper permissions on mailbox.
Please make sure users has Reviewer permission on Outlook 2007.
Please try to run Outlook 2007 under safe mode or re-create profile.
Also try to turn Outlook 2007 to Exchange Online mode from Cached mode.
Thanks
Mavis Huang
TechNet Community Support

Exchange 2010 Mailbox automapping issues after updated to Rollup 5 for Exchange Server 2010 SP3

Hi,
i have problem with Outlook Uses who have Full Access on other mailbox.
An authentication window pop up very time a user start Outlook.
If i remove the access everything is ok.
if i insert manual the mailbox everything is ok
The System was for 3 days ago updated to Rollup 5 for Exchange Server 2010 SP3
Before the update, was no issue.
i will appreciated any help
Thanks

Same issue here. Ever since we installed Update Rollup 5 for SP3 Exchange 2010 mailboxes that were auto mapped are not accessible. They all get the same error.
Cannot expand the folder. The set of folders cannot be opened. The attempt to log on to the Microsoft Exchange has failed.
What I have been doing is removing the users permission, then adding them back using the noautomap switch in Powershell. After doing that, the user manually adds the mailbox and all is well.
Just a note here, I suspect it may have something to do with the version of Outlook 2010. We are running an older version here. I think only SP1 with no other incremental updates. Office is up to SP2. Also, one of the users I was working with could not access
the mailbox no matter what we tried but she can walk over to another workstation and open Outlook and access the very same mailbox so that pretty much proves its software related particularly with Outlook.
I cannot reproduce the problem on a workstation (XP) with a newer version of Outlook.
This has been wearing me out and I suspected the Update Rollup all long. Now I am confident as others are having the same problem. If you find out anything on how to fix this other than the steps above, let me know.

Is it possible to monitor a particular Exchange 2010 mailbox via SCOM if 30 or more emails trigger in 30 minutes in the inbox and alert should be generated

Is it possible to monitor a particular Exchange 2010 mailbox via SCOM if 30 or more emails trigger in 30 minutes in the inbox and alert should be generated for that.
If this is not possible in SCOM. Is there another way we can do it via power shell or any thing.
Gautam.75801

Hi,
We may need to create script based rule using PowerShell or VBScript.
Please go through the below links for command get-mailboxstatistics:
Exchange 2010 : http://community.spiceworks.com/topic/122241-scripting-to-count-all-of-the-messages-in-a-mailbox
Regards, Yan Li

Moving Exchange 2010 Mailbox replicated databases path in DAG environments.

Similar Messages

Maybe you are looking for