BB Torch 9810 direct access mailbox Microsoft Exchange 2010

Hi,
Wanna check whether in anyway my BB could direct access mailbox Microsoft Exchange 2010 without BES (private and/or Company). Thanks
BR

Hi eddiesonka,
"Why" is truly a difficult question for us end users to truly know the answer to. Typically, I shy away from those since, well, not being an insider, I can only have my own personal theories. But, this topic is one that I'm OK presenting my theories on.
The basic answer is that different is different. Non-BB devices do things in their way, BBs do them in their way. Consequently, we all have choice, which is a good thing in a free market society, I think!
Unlike other devices (e.g., ActiveSync), BBs do not technically have a full on-device email client. Other devices, with a full on-device client, conduct all device to email server activities directly. BBs use the carrier/RIM hosted BIS service as an intermediary between the BB and the email server. The main benefit is one of data plan consumption. With non-BBs, the full on device email client must check the server for new email on a periodic basis (yes, I know that some services have more PUSH, but many are still PULL), generating traffic over the carrier data network even when there is no new email on the server. With BBs, that "check for new email" is done by BIS, completely independent of the BB...so no traffic to the BB is generated unless BIS finds something on the server that needs to come to the BB. For folks on limited data plans and limited WiFi access, this can become important.
So, it is up to the consumer to completely research the different choices available to them...and make their selection according to their own unique set of requirements and desires. RIM is advancing BIS...with GMail and Yahoo, there now are some calendar and contact OTA synchronization capabilities that did not exist in the past. With luck, they will continue to develop BIS and enable more and more OTA functions to BIS-level customers -- while, of course, at the same time, preserving their dominance in the mobile security world! And remember, for enterprises, RIM has made BES-X totally free...
Hope that helps!
Occam's Razor nearly always applies when troubleshooting technology issues!
If anyone has been helpful to you, please show your appreciation by clicking the button inside of their post. Please click here and read, along with the threads to which it links, for helpful information to guide you as you proceed. I always recommend that you treat your BlackBerry like any other computing device, including using a regular backup schedule...click here for an article with instructions.
Join our BBM Channels
BSCF General Channel
PIN: C0001B7B4 Display/Scan Bar Code
Knowledge Base Updates
PIN: C0005A9AA Display/Scan Bar Code

Similar Messages

Who has full access on all mailboxes in Exchange 2010 using Powershell ?

Greetings,
Could you please tell me how can i know Who has full access on all mailboxes in Exchange 2010 using Powershell ?
Thanks.
Redouane SARRA

This is going to depend greatly on WHICH inherited permissions you plan to delete - there are some that you can never delete if you want the system to function properly. Now, that being said, let's look at some example permissions. First, here
are some permissions on a standard mailbox:
Identity             User                 AccessRights
IsInherited Deny
users.corp.... USERS\btwatcher    {FullAccess}
False       False
users.corp.... USERS\svcactAdmin {FullAccess}
True        False
users.corp.... CORP\Domain Ad... {FullAccess}
True        True
users.corp.... CORP\Enterpris... {FullAccess}
True        True
users.corp.... CORP\Organizat... {FullAccess}
True        True
users.corp.... CORP\adminact    {FullAccess}
True        True
users.corp.... CORP\esswin       {FullAccess}
True        True
users.corp.... USERS\svcactEncase {FullAccess}
True        False
users.corp.... CORP\Exchange ... {FullAccess}
True        False
users.corp.... NT AUTHORITY\SYSTEM {FullAccess}
True        False
As you can see, the first is not inherited. All others are, and two are from service accounts (svcact...). Also, some are Exchange system permissions, some are denies, and some are just administrative accounts. Once you determine which
you wish to remove, the SIMPLEST way to set the permissions you want is to open the account properties in ADSIEdit, and go to the Security tab. Here, click the Advanced button and find the inherited permission you wish to remove. ADSIEdit will
show where the permission is inherited from - you will need to go to that container to remove the inherited permission. You can also grant inherited denies at the same level(s).
Now, something you will need to understand is that if you hope to remove permissions granted to domain administrators, the system will replace them - these permissions are required by the system and can't be modified permanently.

How to use Powershell to set delegate for user mailbox in Exchange 2010 and Office 365

Hello,
Can you please tell me if I can set delegate for user mailbox in Exchange 2010 or Office 365 using Powershell?
If I can, then how can I do that? (which Powershell commands for setting the delegate?)
Many thanks, and have a good day!

Hi,
If you wanted to add a delegate to possiblly a large number of users or you do this during mailbox provisioning. So the following script will use
impersonation to access another users mailbox and add a delegate.
$mbtoDelegate = "[email protected]"
$delegatetoAdd = "[email protected]"
$dllpath = "C:\Program Files\Microsoft\Exchange\Web Services\1.0\Microsoft.Exchange.WebServices.dll"
[void][Reflection.Assembly]::LoadFile($dllpath)
$service = new-object Microsoft.Exchange.WebServices.Data.ExchangeService([Microsoft.Exchange.WebServices.Data.ExchangeVersion]::Exchange2007_SP1)
$windowsIdentity = [System.Security.Principal.WindowsIdentity]::GetCurrent()
$sidbind = "LDAP://<SID=" + $windowsIdentity.user.Value.ToString() + ">"
$aceuser = [ADSI]$sidbind
$service.AutodiscoverUrl($aceuser.mail.ToString())
$service.ImpersonatedUserId = new-object Microsoft.Exchange.WebServices.Data.ImpersonatedUserId([Microsoft.Exchange.WebServices.Data.ConnectingIdType]::SmtpAddress,
$mbtoDelegate);
$mbMailbox = new-object Microsoft.Exchange.WebServices.Data.Mailbox($mbtoDelegate)
$dgUser = new-object Microsoft.Exchange.WebServices.Data.DelegateUser($delegatetoAdd)
$dgUser.ViewPrivateItems = $false
$dgUser.ReceiveCopiesOfMeetingMessages = $false
$dgUser.Permissions.CalendarFolderPermissionLevel = [Microsoft.Exchange.WebServices.Data.DelegateFolderPermissionLevel]::Editor
$dgUser.Permissions.InboxFolderPermissionLevel = [Microsoft.Exchange.WebServices.Data.DelegateFolderPermissionLevel]::Reviewer
$dgArray = new-object Microsoft.Exchange.WebServices.Data.DelegateUser[] 1
$dgArray[0] = $dgUser
$service.AddDelegates($mbMailbox, [Microsoft.Exchange.WebServices.Data.MeetingRequestsDeliveryScope]::DelegatesAndMe, $dgArray);
Hope this helps.

Can't move Exchange 2003 mailbox to Exchange 2010 Resource forest (Linked Mailbox)

Problem Description:
Can’t move Exchange 2003 mailbox to Exchange 2010 resource forest
Error message:
Failed to reconnect to Active Directory server SRVUMVMDC02.umfolozi.local. Make sure the server is available, and that you have used the correct credentials.
Source Environment Configuration:
Active Directory
FQDN: umfolozi.local
Domain name (pre-Windows 2000): UMFOLOZI
Domain Function Level: Windows Server 2003
Domain Controllers:
Hostname
OS
Operation Master
SRVUMVMDC01.umfolozi.local
Windows Server 2008 R2 Standard SP1
Schema Master, Domain Naming, RID, PDC
SRVUMVMDC01.umfolozi.local
Windows Server 2008 R2 Standard SP1
Infrastructure
Exchange
Version: Microsoft Exchange 2003 Standard SP2 Build 7638.2
Server Information:
Hostname
OS
TUSKUMFMAIL.umfolozi.local
Windows Server 2003 R2 SP2
DNS Zones
Zone Name
Zone Type
Domain Controllers
umfolozi.local
Active Directory-Integrated (Primary)
SRVUMVMDC01.umfolozi.local
SRVUMVMDC01.umfolozi.local
peermont.com
Secondary
SRVPGVMDC01.peermont.com
SRVPGVMDC02.peermont.com
Trusts
Domain Name
Trust Type
Transitive
Validated
peermont.com
Forest
Yes
Yes
Target Environment Configuration:
Active Directory
FQDN: peermont.com
Domain name (pre-Windows 2000): PG
Domain Functional Level: Windows Server 2008 R2
Domain Controllers:
Hostname
OS
Operation Master
SRVPGVMDC01.peermont.com
Windows Server 2008 R2 Std SP1
SRVPGVMDC02.peermont.com
Windows Server 2008 R2 Std SP1
Domain naming, RID, PDC, Infrastructure, Schema Master
Exchange
Resource Exchange Forest
Server Information:
Hostname
OS
Role
Version
Client Access Array
SRVPGVMEXCH01.peermont.com
Windows Server 2012 Std
HUB, CAS
Version 14.3 (Build 123.4)
exchange.peermont.com
SRVPGVMEXCH02.peermont.com
Windows Server 2012 Std
HUB, CAS
Version 14.3 (Build 123.4)
exchange.peermont.com
Hostname
OS
Role
Version
Database Availibility Group
SRVPGVMEXCH03.peermont.com
Windows Server 2012 Std
MBX
Version 14.3 (Build 123.4)
PeermontDAG
SRVPGVMEXCH04.peermont.com
Windows Server 2012 Std
MBX
Version 14.3 (Build 123.4)
PeermontDAG
DNS Zones
Zone Name
Zone Type
Domain Controllers
peermont.com
Active Directory-Integrated (Primary)
SRVPGVMDC01.peermont.com
SRVPGVMDC02.peermont.com
umfolozi.local
Secondary
SRVUMVMDC01.umfolozi.local
SRVUMVMDC01.umfolozi.local
Trusts
Domain Name
Trust Type
Transitive
Validated
umfolozi.local
Forest
Yes
Yes
Migration Process
Task
Description
Successful/Error
1
SYNC AD Domain account from source forest (umfolozi.local) to target forest (peermont.com) using BinaryTree SMART Directory Sync (ADMT can be used as alternative)
Successful
2
Create mailed enabled user
Successful
3
Run Prepare-MoveRepuest with –OverWriteLocalObject
Command Example:
.\Prepare-MoveRequest.ps1 -Identity [email protected] -RemoteForestDomainController SRVUMVMDC01.umfolozi.local
-RemoteForestCredential $RemoteCredentials -UseLocalObject -LocalForestDomainController SRVPGVMDC01.peermont.com -LocalForestCredential $LocalCredentials -OverWriteLocalObject
Successful
4
Submit mailbox request
Command Example:
New-MoveRequest -Identity "0fa7d17e-3637-4708-a51b-f14eaae17968" -BadItemLimit "50" -TargetDeliveryDomain
"internal.peermont.com" -TargetDatabase "{c5d6ea95-07b3-4a52-9868-e41e808a76fe}" -RemoteCredential (Get-Credential "umfolozi\svcmigration") -RemoteGlobalCatalog "SRVUMVMDC02.umfolozi.local" -RemoteLegacy:$True
Error
All the standard migration task works as expected until the mailbox migration move request is submitted. See move request verbose detail below:
[PS] C:\Windows\system32>New-MoveRequest -Identity "0fa7d17e-3637-4708-a51b-f14eaae17968" -BadItemLimit "50" -TargetDeli
veryDomain "internal.peermont.com" -TargetDatabase "{c5d6ea95-07b3-4a52-9868-e41e808a76fe}" -RemoteCredential (Get-Crede
ntial "umfolozi\svcmigration") -RemoteGlobalCatalog "SRVUMVMDC02.umfolozi.local" -RemoteLegacy:$True -Verbose
VERBOSE: [11:34:27.346 GMT] New-MoveRequest : Active Directory session settings for 'New-MoveRequest' are: View Entire
Forest: 'False', Default Scope: 'peermont.com', Configuration Domain Controller: 'SRVPGVMDC02.peermont.com', Preferred
Global Catalog: 'SRVPGVMDC02.peermont.com', Preferred Domain Controllers: '{ SRVPGVMDC02.peermont.com }'
VERBOSE: [11:34:27.362 GMT] New-MoveRequest : Runspace context: Executing user: peermont.com/Admin/Users/Admin
Accounts/Information Technology/SoarSoft/Johann Van Schalkwyk, Executing user organization: , Current organization: ,
RBAC-enabled: Enabled.
VERBOSE: [11:34:27.362 GMT] New-MoveRequest : Beginning processing &
VERBOSE: [11:34:27.362 GMT] New-MoveRequest : Instantiating handler with index 0 for cmdlet extension agent "Admin
Audit Log Agent".
WARNING: When an item can't be read from the source database or it can't be written to the destination database, it
will be considered corrupted. By specifying a non-zero BadItemLimit, you are requesting that Exchange not copy such
items to the destination mailbox. At move completion, these corrupted items won't be available in the destination
mailbox.
VERBOSE: [11:34:27.362 GMT] New-MoveRequest : Searching objects "{c5d6ea95-07b3-4a52-9868-e41e808a76fe}" of type
"MailboxDatabase" under the root "$null".
VERBOSE: [11:34:27.362 GMT] New-MoveRequest : Previous operation run on domain controller 'SRVPGVMDC02.peermont.com'.
VERBOSE: [11:34:27.393 GMT] New-MoveRequest : Current ScopeSet is: { Recipient Read Scope: {{, }}, Recipient Write
Scopes: {{, }}, Configuration Read Scope: {{, }}, Configuration Write Scope(s): {{, }, }, Exclusive Recipient Scope(s):
{}, Exclusive Configuration Scope(s): {} }
VERBOSE: [11:34:27.393 GMT] New-MoveRequest : Searching objects "0fa7d17e-3637-4708-a51b-f14eaae17968" of type "ADUser"
under the root "$null".
VERBOSE: [11:34:27.471 GMT] New-MoveRequest : Previous operation run on domain controller 'SRVPGVMDC02.peermont.com'.
VERBOSE: [11:34:27.471 GMT] New-MoveRequest : Processing object "$null".
VERBOSE: [11:34:27.487 GMT] New-MoveRequest : [DEBUG] No RequestJob messages found.
VERBOSE: [11:34:27.487 GMT] New-MoveRequest : [DEBUG] MDB c5d6ea95-07b3-4a52-9868-e41e808a76fe found to belong to Site:
peermont.com/Configuration/Sites/Peermont
VERBOSE: [11:34:27.487 GMT] New-MoveRequest : [DEBUG] MRSClient: attempting to connect to 'SRVPGVMEXCH02.peermont.com'
VERBOSE: [11:34:27.627 GMT] New-MoveRequest : [DEBUG] MRSClient: connected to 'SRVPGVMEXCH02.peermont.com', version
14.3.178.0 caps:07
VERBOSE: [11:34:27.627 GMT] New-MoveRequest : [DEBUG] Loading source mailbox info
VERBOSE: [11:34:28.844 GMT] New-MoveRequest : Failed to reconnect to Active Directory server
SRVUMVMDC02.umfolozi.local. Make sure the server is available, and that you have used the correct credentials. --> A
local error occurred.
VERBOSE: [11:34:28.844 GMT] New-MoveRequest : Admin Audit Log: Entered Handler:OnComplete.
Failed to reconnect to Active Directory server SRVUMVMDC02.umfolozi.local. Make sure the server is available, and that
you have used the correct credentials.
+ CategoryInfo : NotSpecified: (0:Int32) [New-MoveRequest], RemoteTransientException
+ FullyQualifiedErrorId : F48FD74B,Microsoft.Exchange.Management.RecipientTasks.NewMoveRequest
+ PSComputerName : srvpgvmexch02.peermont.com
VERBOSE: [11:34:28.859 GMT] New-MoveRequest : Ending processing &
Troubleshooting Performed
1. When submitting mailbox move request tried the following credential inputs:
1.1. DOMAIN\Username
1.2. FQDN\Username
1.3. userPrincipalName
2. Confirmed domain trust between source and target domain is in place and validated.
3. Confirmed name resolution in source and target domain is functioning as expected.
4. Confirmed network connectivity between source and target domain controllers as well as source and target exchange servers.
5. Tried to create new Linked Mailbox to account in source forest, can’t select Global Catologue via the wizard;
Tried to specify the credentials for the account forest and got the following error when tried to select Global Catalog from wizard:

The error talk about the credential. Did you check the credential
Did you tried this command?
New-MoveRequest -Identity "Distinguished name of User in Target Forest" -RemoteLegacy -TargetDatabase "E2K10 Mailbox Database Name" -RemoteGlobalCatalog "FQDN of Source DC" -RemoteCredential $Remote -TargetDeliveryDomain "Target
domain name"
http://blogs.technet.com/b/exchange/archive/2010/08/10/3410619.aspx
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Exchange 2013 - can no longer move mailboxes from Exchange 2010 to Ex 2013.

Migrating to Exchange 2013 from Exchange 2010. Created Ex 2013, moved some mailboxes OK. Then could no longer move mailboxes. No errors. The Migration email says complete. Synced: none, Total Mailboxes: none.
Tried several mailboxes. Same result.
Ex 2010 is SP3 RU6, (at least it says RU6 is installed in Programs/Features. The build is for SP3 w/o RU6???)
Ex 2013 is SP1 aka CU4.
How to proceed???
john11

After many attempts to fix the issue (move remaining 4 mailboxes from Exchange 2010 to Exchange 2013) I contacted Microsoft and we resolved the issue. Here's how.
btw - Thanks for the suggestions from Ed. However, they did not seem to move us forward.
What did work:
1. On the Exchange 2010 box, create a new database. (Someone else suggested this also). Then move the remaining Exchange 2010 mailboxes to this new db. Then after that, move the 4 mailboxes to Exchange 2013 using the GUI on Ex 2013. This only worked for one
of the four mailboxes. The other 3 failed.
2. Apparently, we need to restart the Microsoft Exchange Mailbox Replication service on the Exchange 2013 after several failed move attempts to clear cache related to the moves.
3. Then on the Exchange 2013 box, use this Exchange shell command:
New-MoveRequest -identity "[email protected]" -TargetDatabase "Exchange 2013 DB name" -BadItemLimit '500' -verbose
This moved the remaining 3 mailboxes including the Discovery mailbox. It took some time. But we could check the progress using
Get-MoveRequest
The MS Tech was terrific. Really knew his stuff. And all mailboxes are on Exchange 2013. Well, the last one is still moving, but I am optimistic.
Thanks for the suggestions. I had to get this done and the MS Tech made that happen.
john11

Is it supported to connect Exchange 2013 Mailbox using Exchange 2010 CAS in Co-existence?

Hi Team,
I am in the phase of upgrading Exchange 2010 to 2013, and introduced 4 MBX and 2 CAS of 2013 servers in co-existence.
Only one production mailbox of 2010 moved to 2013. The owa of the mailbox moved to 2013, is working OK internally coz only internally configured, but when I configure outlook using 2010 settings, it got configured but when I open outlook it doesn't
open and throws an error of some "cannot open set of folders".
Is it supported to connect Exchange 2013 Mailbox using Exchange 2010 CAS in Co-existence? because I havnt configured 2013 CAS servers yet.
Kindly share some KB or tip. Any help is appreciated. Thank You.
Muhammad Nadeem Ahmed Sr System Support Engineer Premier Systems (Pvt) Ltd T. +9221-2429051 Ext-226 F. +9221-2428777 M. +92300-8262627 Web. www.premier.com.pk

I'll change Adam's wording slightly - you *MUST* install a CAS 13 server into every site where there is a MBX 13 server.
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

OST corrupt when moving Mailbox from Exchange 2010 to Exchange 2010

Anyone come across this?
Moving a mailbox on Exchange 2010 to Exchange 2013 - the outlook client wont connect, if you remove the OST and allow outlook to recreate it comes good again.
outlook client knows the mailbox has moved as it connects to the new server
Not happening to every mailbox
thak=nks

Hi,
After you move mailbox from Exchange 2010 to Exchange 2013, Outlook should still work.
Is there any error message when these affected users try to connect? If there is, please post here for further analysis.
I saw someone failed to connect to the new Exchange server after they moved mailbox, then they restarted the Microsoft Exchange Information Store service and restarted Outlook, it worked.
If you haven't tried this, you can restart the Microsoft Exchange Information Store service to check the result.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Move mailbox from exchange 2010 2003 , Transient error MapiExceptionLogonFailed has occurred.

We are currently migrating from Exchange 2003 to Exchange 2010, same domain.
We have successfully moved some mailboxes from exchange 2003 to exchange 2010 without any problems.
Now we need to move 1 mailbox back from exchange 2010 to exchange 2003.
After creating the moverequest it stucks on 0% and the log shows the error below.
After using Bing I found this post -> http://social.technet.microsoft.com/Forums/exchange/en-US/ef41ae05-8816-4c0c-968a-c48f0e3d50b5/move-mailbox-back-from-exchange-2010-to-exchange-2003-failure?forum=exchangesvrdeploylegacy
This suggest ->
After I give FULL permissions to each Mailbox Stores on Exchange 2003 server, I was able to move my mailbox back onto the Exchange 2003 server. In details:
Simply right click Storage Group\Mailbox Store and go to Security, in there you may see Exchange Servers group already there, if no add it in, then give it FULL permissions! and thats it!
Create a new move request but still stuck on 0% and error as below
20-3-2014 16:32:10 [ex2010p11] 'contoso.com/Users/exadmin' created move request.
20-3-2014 16:32:11 [ex2010p21] The Microsoft Exchange Mailbox Replication service 'exchangep21.contoso.com' (14.3.151.0 caps:07) is examining the request.
20-3-2014 16:32:11 [ex2010p21] Connected to target mailbox 'Primary (82b54f9e-27ff-44d2-9142-f949d567e1e7)', database 'ex2003\Basic\Basic', Mailbox server 'ex2003.contoso.com' Version 0.0 (Build 7638.0).
20-3-2014 16:32:11 [ex2010p21] Connected to source mailbox 'Primary (82b54f9e-27ff-44d2-9142-f949d567e1e7)', database 'EX2010DB', Mailbox server 'ex2010p20.contoso.com' Version 14.3 (Build 174.0).
20-3-2014 16:32:11 [ex2010p21] Request processing started.
20-3-2014 16:32:11 [ex2010p21] Transient error MapiExceptionLogonFailed has occurred. The system will retry (1/60).
Error details: MapiExceptionLogonFailed: Unable to make connection to the server. (hr=0x80040111, ec=1010)
Diagnostic context:
Lid: 13720 dwParam: 0x6D9 Msg: EEInfo: Flags: 0
Lid: 11672 dwParam: 0x6D9 Msg: EEInfo: NumberOfParameters: 4
Lid: 8856 dwParam: 0x6D9 Msg: EEInfo: prm[0]: Unicode string: ncacn_ip_tcp
Lid: 8856 dwParam: 0x6D9 Msg: EEInfo: prm[1]: Unicode string: ex2003
Lid: 12952 dwParam: 0x6D9 Msg: EEInfo: prm[2]: Long val: -545057711
Lid: 12952 dwParam: 0x6D9 Msg: EEInfo: prm[3]: Long val: 382312662
Lid: 45169 StoreEc: 0x824
Lid: 44273
Lid: 59431 EMSMDB.EcDoConnectEx called [length=163]
Lid: 34855 EMSMDB.EcDoConnectEx returned [ec=0x3F2][length=56][latency=0]
Lid: 56945
Lid: 59431 EMSMDB.EcDoConnectEx called [length=163]
Lid: 34855 EMSMDB.EcDoConnectEx returned [ec=0x3F2][length=56][latency=0]
Lid: 59505 StoreEc: 0x3F2
Lid: 52465 StoreEc: 0x3F2
Lid: 60065
Lid: 33777 StoreEc: 0x3F2
Lid: 59805
Lid: 52209 StoreEc: 0x3F2
Lid: 56583
Lid: 52487 StoreEc: 0x3F2
Lid: 19778
Lid: 27970 StoreEc: 0x3F2
Lid: 17730
Lid: 25922 StoreEc: 0x3F2
at Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message, Int32 hresult, SafeExInterfaceHandle iUnknown, Exception innerException)
at Microsoft.Mapi.ExRpcConnection.Create(ConnectionCache connectionCache, ExRpcConnectionCreateFlag createFlags, ConnectFlag connectFlags, String serverDn, String userDn, String user, String domain, String password, String httpProxyServerName,
Int32 ulConMod, Int32 lcidString, Int32 lcidSort, Int32 cpid, Int32 cReconnectIntervalInMins, Int32 cbRpcBufferSize, Int32 cbAuxBufferSize, Client xropClient, Byte[] clientSessionInfo, TimeSpan connectionTimeout)
at Microsoft.Mapi.MapiStore.OpenMapiStore(String serverDn, String userDn, String mailboxDn, Guid guidMailbox, Guid guidMdb, String userName, String domainName, String password, String httpProxyServerName, ConnectFlag connectFlags, OpenStoreFlag
storeFlags, CultureInfo cultureInfo, Boolean wantRedirect, String& correctServerDN, ClientIdentityInfo clientIdentity, String applicationId, Client xropClient, Boolean wantWebServices, Byte[] clientSessionInfo, TimeSpan connectionTimeout)
at Microsoft.Mapi.MapiStore.OpenMailbox(String serverDn, String userDn, String mailboxDn, String userName, String domainName, String password, String httpProxyServerName, ConnectFlag connectFlags, OpenStoreFlag storeFlags, CultureInfo cultureInfo,
WindowsIdentity windowsIdentity, String applicationId)
at Microsoft.Exchange.MailboxReplicationService.MapiUtils.OpenSystemMailbox(Guid mdbGuid, String serverDN, String dcName, NetworkCredential cred, String& systemMailboxDn)
at Microsoft.Exchange.MailboxReplicationService.LocalMailbox.OpenSystemMailbox()
at Microsoft.Exchange.MailboxReplicationService.LocalMailbox.Microsoft.Exchange.MailboxReplicationService.IMailbox.SaveSyncState(Byte[] key, String syncStateStr)
at Microsoft.Exchange.MailboxReplicationService.MailboxWrapper.<>c__DisplayClass57.<Microsoft.Exchange.MailboxReplicationService.IMailbox.SaveSyncState>b__56()
at Microsoft.Exchange.MailboxReplicationService.ExecutionContext.Execute(GenericCallDelegate operation)
at Microsoft.Exchange.MailboxReplicationService.MailboxWrapper.Microsoft.Exchange.MailboxReplicationService.IMailbox.SaveSyncState(Byte[] key, String syncState)
at Microsoft.Exchange.MailboxReplicationService.MailboxCopierBase.ClearSyncState()
at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.<>c__DisplayClass23.<CleanupOrphanedDestinationMailbox>b__22(MailboxMover mbxCtx)
at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.ForeachMailboxContext(MailboxMoverDelegate del)
at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.CleanupOrphanedDestinationMailbox(Object[] wiParams)
at Microsoft.Exchange.MailboxReplicationService.CommonUtils.CatchKnownExceptions(GenericCallDelegate del, FailureDelegate failureDelegate)
Error context: --------
Operation: IMailbox.SaveSyncState
OperationSide: Target
Primary (82b54f9e-27ff-44d2-9142-f949d567e1e7)
Key: F2FA63B0116C564EA4C598D69786443D9E4FB582FF27D2449142F949D567E1E7E0CA914F6695624C98892FA527AAA91E
SyncStateLength: 0
20-3-2014 16:32:41 [ex2010p21] The Microsoft Exchange Mailbox Replication service 'ex2010p21.contoso.com' (14.3.151.0 caps:07) is examining the request.
20-3-2014 16:32:41 [ex2010p21] Connected to target mailbox 'Primary (82b54f9e-27ff-44d2-9142-f949d567e1e7)', database 'ex2003\Basic\Basic', Mailbox server 'ex2003.contoso.com' Version 0.0 (Build 7638.0).
20-3-2014 16:32:41 [ex2010p21] Connected to source mailbox 'Primary (82b54f9e-27ff-44d2-9142-f949d567e1e7)', database 'EX2010DB', Mailbox server 'ex2010p20.contoso.com' Version 14.3 (Build 174.0).
20-3-2014 16:32:41 [ex2010p21] Request processing started.
20-3-2014 16:32:41 [ex2010p21] Transient error MapiExceptionLogonFailed has occurred. The system will retry (2/60).

Hello，
When you move mailbox from exchange 2010 to exchange 2003, please check if the following situations exist:
http://technet.microsoft.com/en-us/library/dd638157(v=exchg.141).aspx
Before you move mailbox again, please clear the previous move request.
I recommend you use EXBPA to check your exchange server 2003 and exchange 2010.
Please check if inheritable permission is missing on the mailbox store on Exchange Server 2003.
Cara Chen
TechNet Community Support

Primary mailbox (on Exchange 2010) and Personal Archive (on Exchange 2013), possible?

Current environment is Exchange 2010 SP3 RU5 supporting 4,000 Users. Client estate is Outlook 2010 SP1 going on SP2.
We're pulling our Archiving solution away from 3rd party and back into Exchange. Implementing a new set of Exchange 2010 Servers (old DAG or in a new Archive DAG) would be easy. But is there Exchange 2013 stepping stone potential?
Can the Archive DAG / Archive mailboxes be on 2013? i.e. for any given User, leave their primary mailbox on Exchange 2010 and create new Archive mailbox on 2013.
I want to avoid implementing 2010 Archive Servers and then go 2013 Archive 6 months or a year later.
This article suggests 'no':
http://technet.microsoft.com/en-gb/library/dd979800(v=exchg.150).aspx
"Locating a user’s mailbox and archive on different versions of Exchange Server is not supported."
I've found little info but the odd statement here / there.
Is this the latest position? Is it that cut & dry? Anyone tried it? Why won't it work (or will it but it's not supported)?
Thanks!

<I had a response from MS>
Below is a summary of the case for your records:
Symptom:
=============
Is it possible to implement a 2013 environment to host the Archive mailboxes? i.e. for any given User, their primary mailbox is on Exchange 2010 and their Archive
mailbox is on 2013.
Resolution:
=============
It’s not supported to have a user’s primary mailbox reside on an older Exchange version than the user’s archive. If the user’s primary mailbox is still on Exchange
2010, you must move it to Exchange 2013 before or at the same time when you move the archive to Exchange 2013.
http://technet.microsoft.com/en-us/library/jj651146(v=exchg.150).aspx
as per the repro in our lab, having the archive mailbox in higher version of exchange would fail with the error above
<the scenario isn't completely relevant, looks like he's trying to put the Primary on 2013 and not the Archive, no matter, we've established there are problems, question is whether they are looking into this area / to patch, they go on...>
At this point in time we don’t have a conformation from the product team, if the above would change in the future exchange versions.
<MS did say on the call that they were not looking at fixing it, naturally this isn't a "never", as per previous statement - they can't commit 100% to the future, but they've provided me the answer - they are not currently looking at resolving/providing
this as a migration scenario, end.>

Script Powershell In Place Hold Mailbox with Exchange 2010

Hello,
I have a script that allows me to make a InPlaceHold newly created mailboxes via Exchange 2010.
But every time I run, he released me an error message: See attached picture.
Here is the script in question:
#Initialize variables
$policyname = "In Place - Hold"
$members = Import-CSV "C:\migration\Script\New_User\New_User_List.csv" -delimiter ";"
$Result = "C:\migration\Script\New_User\New_User_Result.log"
$powerUser = "******"
$powerPass = "******"
$password = ConvertTo-SecureString $powerPass -AsPlainText -Force
$adminCredential = New-Object -TypeName System.Management.Automation.PSCredential -argumentlist $powerUser,$password
$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $adminCredential -Authentication Basic -AllowRedirection
Import-PSSession $Session
#Get current mailboxes in our mailbox search
$InPlaceHoldMailboxes = (Get-MailboxSearch $policyname).sourceMailboxes
#Add another user to the array, the line bellow can be a loop of more than one user.
foreach ( $member in $members)
if ($InPlaceHoldMailboxes -contains($member.name))
Write-Host $("User " + $member.name + " already present") -ForegroundColor:yellow
Out-File -FilePath $Result -InputObject $("IN-PLACE HOLD - WARNING, User " + $member.name + " already present in members") -Encoding UTF8 -append
else
$InPlaceHoldMailboxes += $member.upn
Write-Host $("User " + $member.name + " added") -ForegroundColor:green
Out-File -FilePath $Result -InputObject $("IN-PLACE HOLD - SUCCESS, User " + $member.name + " added to members") -Encoding UTF8 -append
#Add them to the MailboxSearch
Try
Set-MailboxSearch $policyname -SourceMailboxes $InPlaceHoldMailboxes -Force -ErrorAction 'Stop'
Write-Host $("SUCCESS, " + $policyname + " updated") -ForegroundColor:green
Out-File -FilePath $Result -InputObject $("IN-PLACE HOLD - SUCCESS, " + $policyname + " updated") -Encoding UTF8 -append
Catch
Write-Host $("ERROR, policie " + $policyname + " NOT updated") -ForegroundColor:red
Out-File -FilePath $Result -InputObject $("IN-PLACE HOLD - ERROR, " + $policyname + " NOT updated") -Encoding UTF8 -append
Write-Error $_.Exception.ToString() > $Result
Exit
#start the mailboxsearch
Start-MailboxSearch -Identity $policyname -Force
Remove-PSSession $Session
I use Powershell 4.0
Thank you for your help.

Please read the error message carefully as it tells you what is wrong. "You cannot update multiple mailboxes". You must do one at a time.
¯\_(ツ)_/¯

OSX 10.5.8 and Microsoft Exchange 2010

Hello
Is it possible to get Entourage on Mac OSX 10.5.8 to work with A microsoft exchange 2010 server? I know it will work if we upgrade to Snow Leopard but some of our staff still have power pc macs and therefore can't use Snow Leopard.
Thanks
Gary

There is no reason why it should not work, it worked with exchange 2003 and 2007.

Configure sharepoint 2013 with Microsoft exchange 2010

Hi,
I am want to configure SharePoint 2013 with Microsoft exchange 2010.
Please let me how can I integrate these server to Send/ Receive domain E-mails.
Thanks,
C Mahone

For email integration there really isn't anything special about Exchange 2010 vs. any other mail server. Check the links here on configuring Incoming and Outgoing mail in SharePoint:
http://technet.microsoft.com/en-us/library/ee956941(v=office.15).aspx
Paul Stork SharePoint Server MVP
Principal Architect: Blue Chip Consulting Group
Blog: http://dontpapanic.com/blog
Twitter: Follow @pstork
Please remember to mark your question as "answered" if this solves your problem.

Beware of Linked Mailbox status - Moving Unity_server mailboxes to Exchange 2010

Hi all -
Here is a problem I encountered that I want to pass along to you:
When partnering Unity to Exchange 2010, the Unity_servername, USBMS_servername, EAdmin, and unitymsgstoresvc inboxes are moved from the old Exchange to the new 2010 server. Using the Exchange Management Console, the users should show up as User Mailboxes, not Linked Mailbox. A Linked mailbox in Exchange 2010 is an external account, i.e. an account in another forest. If this occurs for the Unity_servername mailbox, external caller voice messages remain in UMR (UnityMTA) and you will see many application event log errors. In EMC you will observe the account mailboxes show in Disconnected status.
If this happens to you, here is the fix:
Disable the Account from EMC in Exchange 2010. Note you will get a prompt that the Exchange properties are being removed but the email inbox is NOT deleted.
Re-enable the account from ADUC.
In EMC, go to Disconnected Mailboxes, select the Unity mailbox and select Connect. In the Connect wizard, re-associate with the existing account. Re-enter the user alias and complete the wizard.
Restart AvUMRSynchSvr service on Unity.
Hope this helps someone in the future!
Sincerely, Ginger

Thanks Brad :-) I forgot to mention I discovered a number of Internet hits that say this can happen with Move Mailbox. Here's the link I used to begin researching the problem (hint: go all the way to the bottom of the web page - http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_26308671.html). Got to give kudo's to this most excellent Exchange resource - has helped me a bunch over the years!

"Microsoft.Exchange.2010.Reports.Transport.Platform.TopUsers "Report show no result

hello,
i have an issue in my SCOM 2012 report.when i go to
Reporting --> Exchange Server 2010 Report Library-->and open the report Microsoft.Exchange.2010.Reports.Transport.Platform.Top users.
in my scom 2012 console and execute the report for top users on the basis of Messages Send or Messages Received ,it return zero result.
thank you

Hi,
Blank reports can be a common issue with System Center Operations Manager. These are caused by many different reasons, and for the focus of this article we will discuss the following:
1. The wrong type of entity was selected as the report target.
2. The corresponding performance collection rule or the script that generates the performance data is not enabled for the report target.
3. There is a functional problem with the Health Service on the agent.
4. Management servers are unable to insert data into the OperationsManagerDW database.
5. Data is stuck in the staging tables in the OperationsManagerDW database.
More details:
https://support2.microsoft.com/kb/2573329?wa=wsignin1.0
In addition, it is suggested to configure the Exchange management pack according to the mangement pack guide.
And here are two links that should be helpful for you regarding to this issue, please refer to them:
http://zoomindia111.wordpress.com/configure-exchange-2010-sp1-management-pack-in-scom-2007-r2/
http://blogs.technet.com/b/emreguclu/archive/2011/09/26/empty-exchange-2010-server-statistics-mailflow-reports-if-default-log-directory-has-changed.aspx
Regards,
Yan Li
Regards, Yan Li

Export Mailbox from Exchange 2010 and Import to Exchange 2007

Hello,
I exported mailbox (1GB in size) from Exchange 2010 to *.pst file; I need to import it into
Exchange 2007 mailbox. Is it supported ?
The operation completed successfully (no errors) but no items were imported; is it due to unsupported backward compatibility or some other issue ?
Thank you,
Luca
Disclaimer: This posting is provided AS IS with no warranties or guarantees, and confers no rights. Whenever you see a helpful reply, click on [Vote As Help] and click on [Mark As Answer] if a post answers your question.

I also have the same issue. Exported mailboxes on Exchange 2010 SP3 latest updates using
New-MailboxExportRequest and then tried to import into mailbox on Exchange 2007 SP3 with latest updates. The 32-bit client machine used for the import has Outlook 2010 SP1 (SP2 and later updates causes a different error). I used Outlook 2010 because the E2K10
New-MailboxExportRequest documentation states that you have to use Outlook 2010 or later. The PST files created can be opened and imported via Outlook but not with the
Import-Mailbox cmdlet (with no error as stated in this thread). Other PSTs, not created from E2K10 export do import just fine. I also ran ScanPST.exe against the exported PST and then ran the import again and it worked, everything got imported. Interestingly
the test mailbox PST file I was using was 761 KB but after the ScanPST it was 1,257 KB - must be some difference in the PST format that the Import-Mailbox cmdlet can't deal with.
Does anyone have any other solutions or
workarounds to this. I've got over 900 mailboxes I need this for due to an
acquisition? Has anyone tried using Outlook 2013 on the machine used for doing
the Exchange 2007 imports or does Outlook 2013 also have the same issue as later versions of Outlook 2010 (Exchange Mailbox import failed with error code 2147221233)?

BB Torch 9810 direct access mailbox Microsoft Exchange 2010

Similar Messages

Maybe you are looking for