No-reply mailbox in Exchange 2003

You basically want a sending only account.
So create one on exchange or have your system that is generating these emails send from [email protected], add a disclaimer to emails from this address stating this is unmanaged, and at your spam/filter/gateway have it accept then drop the message - if someone does reply, they will think it got delivered, but in fact your server would take it then delete it.
It in effect would be 'an unmanaged mailbox' no one would ever see any replies sent to this address.

Hi..
We need to set up a mechanism for a system to send no-reply mail through our exchange 2003 server. I saw a post on having the exchange server simple do a NDR. However, I did not understand what that meant.
1- Do I need to make a mailbox in exchange in order for the exchange server to forward the system generated emails out?2- If, in fact, I do need a mailbox, how do I keep the account from filling up the sent file associated with the user? If it collects, it will waste disk space and eventually lock the prevent the user (system) from sending due to server mailbox size restrictions.
The account will rarely, if ever, be accessed by a person (so no way to archive /drop old sent messages.)
I would like some scheme that would allow someone (if needed) to go into the account and look back a month or so and see what was sent out, but it is...
This topic first appeared in the Spiceworks Community

Similar Messages

  • Cannot Move Mailbox from Exchange 2003 to Exchange 2007

    Hello,
         I am migrating exchange 2003 to Exchange 2007 and have moved almost all the mailboxes without any issue, but there are some mailboxes which are not being moved since they are giving me the below error.
    Error:
    Error was found for John Doe ([email protected]) because: Error occurred in the step: Opening source mailbox. Failed to open mailbox with error: ClassFactory cannot supply requested class, error code: -1056749262
    Initially I found that the account was disabled from Active
    Directory so enabled it but and also replicated the active Directory but still the problem is there, its not hidden in the GAL aswell.
    http://www.arabitpro.com

    Thanks everybody .. I have solved the problem myself. 
    To resolve this issue I had to give the account "SELF" permissions for "Associated external account". If the user does not have these
    permissions to its own account it is unable to set the msExchMasterAccountSID attribute for the disabled account causing the error. By setting this permission on the disabled account, it allows it to mark the msExchMasterAccountSID attribute.
    To do this follow this procedure:
    1. In the Active Directory Users and Computers snap-in, on the View menu, click Advanced Features.
    2. In the Exchange Advanced properties of the disabled user object that owns the mailbox, click Mailbox Rights, and then search the list of accounts for one
    that has the Associated External Account permission.
    4. If no account has this permission, grant the SELF account Associated External Account and Full Mailbox Access permissions.
    https://support.microsoft.com/kb/278966?wa=wsignin1.0
    http://www.arabitpro.com

  • PowerShell Report of Deleted Mailboxs on Exchange 2003

    Preparing for Migration from Exchange 2003 to Exchange 2010/13
    and or Office 365, you'll need to find "Deleted Mailboxes".
    Since PowerShell doesn't have any Calls direct to Ex2003 for this, we have to pull WMI objects.
    This Script will pull all the Deleted Mailboxes from Ex2003 from your Ex2010 Native or Hybid Server.
    $now = Get-Date #Used for timestamps
    $date = $now
    $Deleted_Mailboxes = Get-Wmiobject -namespace root\MicrosoftExchangeV2 -class Exchange_Mailbox -computer EX2003Server -Filter "DateDiscoveredAbsentInDS is not null" MailboxDisplayName,ServerName,StorageGroupName,StoreName,Size,DateDiscoveredAbsentInDS | sort-object MailboxDisplayName
    $Deleted_Mailboxes | Export-Csv "F:\Reports\Deleted_Mailboxes$Date.csv" -NoTypeInformation
    #Exports collected Data From Ex2003Server (your server name) to CSV on F drive

    Hi Bakasan,
    Thanks for your sharing.
    Best regards,
    Amy Wang
    TechNet Community Support

  • Mailboxes are moved to Exchange 2007 but still appearing in exchange 2003 With Red Cross

    Hello,
     I am moving  mail boxes from exchange 2003 to exchange 2007 sp1. Excahnge 2007. After the mailboxes
    are moved successfully to exchange 2007 i can still see some mailboxes in exchange 2003 with red mark on them. Please check the attached snapshot.
    http://www.arabitpro.com

    Followed this Kb article and finished 
    http://support.microsoft.com/kb/930363
    http://www.arabitpro.com

  • Exchange 2003 to 2010 Migration Mailbox Migration "Object not found"

    I am introducing an Exchange 2010 Server to a single server Exchange 2003 organization. I have HT, CAS and MB roles installed already on 2010 w/ SP1. Prepped the Schema, AD, Domain and LegacyExchangePermissions by using the setup.com of the SP1
    installation files.
    Right now, when I try to initiate a New Local Move Request on 2010 EMC for a mailbox on Exchange 2003, I get an error for all the users saying "Object not found" with a white X in a red circle. I'm not sure what to do at this point to get Exchange 2010
    recognize the 2003 mailboxes. Any ideas?
    Thank you,
    -S

    Tim,
    Here is what I'm getting from ExBPA:
    Error Offline address book replica not found Organization CGU Didn't find a replica of folder 'OAB Version 4' for offline address book 'Default Offline Address List'. Either a replica doesn't exist, or this folder hasn't been created yet. If an OAB generation
    attempt has not yet been made, you can ignore this error.
    Error Couldn't find any writeable domain controllers Admin Group Exchange Administrative Group (FYDIBOHF23SPDLT) There were no writeable domain controllers found in Active Directory site 'Default-First-Site-Name'. At least one writeable domain controller
    is required for Exchange to function properly.
    Error Database backup critical Admin Group Exchange Administrative Group (FYDIBOHF23SPDLT) Database 'Public Folder Database' on server EXCH-2010 has never had a full online backup.
    ====
    And this is what happens if I put go ahead with the move request
    Summary: 1 item(s). 0 succeeded, 1 failed.
    Elapsed time: 00:00:00
    Test User
    Failed
    Error:
    Mailbox database "EXCH-01\First Storage Group\Mailbox Store (EXCH-01)" doesn't exist.
    Click here for help...
    http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.140).aspx?v=14.1.218.11&t=exchgf1&e=ms.exch.err.Ex23B42B
    Exchange Management Shell command attempted:
    'cgucpa.com/Users/Test User' | New-MoveRequest -TargetDatabase 'Mailbox Database'
    Elapsed Time: 00:00:00
    Thank you for your help,
    -S

  • 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

  • Exchange 2003 and Exchange 2010 Coexistence Activesync Issue

    Hello,
    I am currently on the progress of migrating mails from Exchange 2003 SP2 to Exchange 2010 SP3. Before I can do actual migration, I need to make sure that OWA and Activesync works when Exchange 2010 becomes Internet facing.
    Right now Exchange 2003 is Internet facing while Exchange 2010 is internal LAN only. OWA login from Exchange 2010 to a mailbox in Exchange 2003 works fine. However, trying to open a mailbox in Exchange 2003 from Exchange 2010 Activesync fails.
    Activesync login from Exchange 2010 to a mailbox in Exchange 2010 works fine, as well as logging in from Exchange 2003 to mailbox in Exchange 2003.
    Tests using AccessMyLAN ActiveSync Tester using Exchange 2010 as entry point are inconclusive. The test shows the app successfully contacting ActiveSync version 6.5 which is Exchange 2003, but results in "Activesync detected, but not correctly configured."
    Tests using Test-ActiveSyncConnectivity from Exchange 2010 reveals Error HTTP 400 when contacting Exchange 2003. The cmdlet also shows it successfully contacting Activesync version 6.5 (Exchange 2003).
    I have searched around, installed hotfix KB937031, enabled Integrated Windows Authentication on Exchange 2003 Microsoft-Server-Activesync, disabled Require SSL for Microsoft-Server-Activesync and exchange-oma, yet I still can't connect to a mailbox inside
    Exchange 2003 through ActiveSync 2010. Website Multiple Identities for port 80 has been set correctly. Exchange 2003 has Forms-Based Authentication Enabled and is the one thing we haven't tried disabling yet.
    We want to make sure everything works first, then make Exchange 2010 Internet facing, and finally do the mail migration. We do not want to migrate everyone in a single sitting. Please if anyone have ideas any help is welcomed!

    Exchange 2010 will proxy ActiveSync for Exchange 2003.  For OWA, it will redirect, so you need a legacy redirect URL.  You can test all of this internally without changing your Internet connection.  For ActiveSync you can use a WiFi connection.
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • SPAM rules on Inbox after migration from Exchange 2003 - GFI Mail Essentials

    Hello,
    Few times ago, we had an Exchange 2003 server with mailboxes which were configured with "rulemgmt.exe" tool (from Microsoft ?) to manage users mailboxes and SPAM redirection in these mailboxes.
    GFI MailEssentials (antispam) was installed on a mail relay and once a SPAM was detected, it was redirected in Inbox/SPAM folder on user mailbox thanks to the rule defined by "rulemgmt.exe".
    Recently, we did a migration from Exchange 2003 to 2010. Unfortunately, "rulemgmt.exe" doesn't work anymore on Exchange 2010 and it's replaced by a "Transport Rule" which works fine but only to redirect SPAMs in Junk e-mail folder. However,
    if I don't set up this transport rule, SPAM redirection still works from mailboxes which were created on Exchange 2003 and e-mails go to Inbox/SPAM as before... For new mailboxes on Exchange 2010, it doesn't work which is normal.
    My question is: for old mailboxes from Exchange 2003, where are the SPAM redirection (Inbox/SPAM) information stored? I don't understand how SPAM can be redirected if the information is not stored in Exchange...
    The aim is to use Junk E-mail folder with the Transport Rule at the end everywhere and to clean old rules used for Inbox/SPAM.
    I contact GFI support but they couldn't help me.
    Any idea?
    Regards,
    DeltaSM
               

    Those old mailboxes probably have old rules still set.  You can use the Outlook.exe /cleanrules switch to purge those old rules.  This would require that you create an outlook profile for each of those impacted mailboxes.
    You can also look at using MFCMapi -
    http://support.microsoft.com/kb/2860406/en-us
    When that is done, you might want to perform a Clean-MailboxDatabase and then look at the mailbox rules (get-inboxrule).  If that does not work for you, could be something else within the mailbox and as such, I would recommend working with MS to get
    more info.
    DaDougInc

  • Need detail information, steps would be nicer, to upgrade from Exchange 2003 to Exchange 2010 to setup in test system first then try on production, since not much room for downtime, thanks bekir

    Need detail information, steps would be nicer,  to upgrade from Exchange 2003 to Exchange 2010 to setup in test system first then try on production, since not much room for downtime, thanks bekir

    Hi,
    Overview of the upgrade progress from Exchange 2003 to Exchange 2010 including the following steps:
    Installing Exchange 2010 within your organization on new hardware.
    Configuring Exchange 2010 Client Access.
    Creating a set of legacy host names and associating those host names with your Exchange 2003 infrastructure.
    Obtaining a digital certificate with the names you'll be using during the coexistence period and installing it on your Exchange 2010 Client Access server.
    Associating the host name you currently use for your Exchange 2003 infrastructure with your newly installed Exchange 2010 infrastructure.
    Moving mailboxes from Exchange 2003 to Exchange 2010.
    Decommissioning your Exchange 2003 infrastructure.
    For more details, please refer to this following document.
    http://technet.microsoft.com/en-us/library/ff805040(v=exchg.141).aspx
    Best Regards.

  • Migration; Exchange 2003 SP2 to Exchange 2013 on new Domain and DC

    I wasn't prepared for this task, and it was thrown at me to do...  Eyes are bleeding from planning reading and planning, would LOVE any input from you guys.  First time posting, here and have heard great things about these forums.  The Company
    I work for obtained a new client and a network that is in a cluster at the moment, so I'm having to dig through everything and restructure..
    Scenario:
    Old Domain/Server: (To be decommissioned)
    Server 2003 Standard SP2 (Domain: cosco.com; NETBIOS name: coscoex)
    Exchange 2003 SP2 (6.5.7638.1)
    Server is a domain controller and exchange server.
    Migrating to:
    Server 2012 R2 Datacenter (New Domain ad.cosco.com; NETBIOS name: cosco)
    VM #1: Server 2012 R2 Domain Controller at 2012 R2 Functionality 
    VM #2: Server 2012 R2 with Exchange 2013 Standard (Not Yet Installed) Joined to ad.cosco.com domain
    VM #3: Server 2012 R2 with Exchange 2010 (Not Yet Installed) joined to ad.cosco.com domain
    These are probably not ideal conditions, but I have to work with what I'm given.
    Host server (2012 R2) is in work group mode.  Hyper V Installed with a VM of Server 2012 R2 and as a DC at a functionality level of Server 2012 R2.  I had intended starting at a lower functionality level and raising
    it later, but.... ya I forgot to change it.  If needed I can spool up a new DC with a lower functional level.
    DNS, AD and group policy is all jacked up on the 2003 DC so that doesn't matter, All user accounts are going to be created under the new domain.  The concern is migrating the mailboxes from Exchange 2003 on the old domain to
    Exchange 2013 on the new domain.  The client is going to provide CSV of the AD accounts that are still valid (a lot of accounts are no longer used or are from people that no longer with the organization.)
    I had some ideas, but I'm not sure if they will work.  This is something I have never done before (Senior Engineer Quit).
    My thoughts:
    - Establish a two way trust relationship between the two domains.
    - Create two VM's, one with Exchange 2010 and one with Exchange 2013 (They have a 2010 licence that was not used).
    - Create the users on the new domain
    - Use the double hop method from Exchange 2003 > Exchange 2010 > Exchange 2013 
    - Link Exchange accounts to the correct user accounts on the new DC.
    Can this be done cleanly? Am I going about this the correct way?  Any feedback would be GREATLY appreciated.
    Note: We are forced to use ad.cosco.com (Obviously not the actual domain name)

    Hi,
    Base on my experience, your idea is feasible.
    However, before getting started, you should note that Exchange 2010 (with any service pack or update rollups) is not (yet) supported to install on Windows 2012 R2. More details refer to the following link: 
    http://technet.microsoft.com/library/ff728623(v=exchg.150).aspx
    After all the preparations complete, you can refer to the following articles to migration exchange 2003 to 2010, then to 2013:
    Exchange 2003 to 2010 Cross-Forest Migration Step by Step Guide
    Exchange 2010/2007 to 2013 Migration and Co-existence Guide
    Best regards,
    Niko Cheng
    TechNet Community Support

  • Can't change RUS in interop environment Exchange 2003/Exchange 2010

    Hello!
    We have interop environment with Exchange 2003 and Exchange 2010 Servers. We have many Exchange 2010 servers, and not so many days ago had a lot of exchange 2003 servers. So we moved all mailboxes from Exchange 2003 servers and started to remove exchange
    2003 servers after that.  Now it's all come to 2 Exchange 2003 servers. So what we have now:
    Server 2003-A has replica of some Public folders, master in Routing group and a lot of other systems still use this server to send messages directly through SMTP.
    Server 2003-B only assigned as exchange server in Recipient Update Service (RUS).
    I wanted to change RUS properties from Server 2003-B to Server 2003-A and leave it as the last one, but it's impossible. I can't choose another server, can't even pick "Computers" in Objects during search. Also I can't create new RUS for the same
    reasons.
    Is there any possibility to change RUS from Server 2003-B to Server 2003-A or no at all?

    What if you click on the Advanced Tab and then Find Now...don't you find Server
    2003-A when you do?
    Martina Miskovic

  • Exchange 2003 migrate to Exchange 2010 - single forest multiple domain. Active Sync problem

    Hi All, 
    I have AD single forest and multiple domain. for example, the forest domain is jakarta.co.id, and the other domain is bali.co.id.
    Exchange 2003 deployed in jakarta.co.id, User mail enabled in domain jakarta.co.id and bali.co.id.
    Then, I upgrade to Exchange 2010 (deploy in jakarta.co.id) and move mailbox from Exchange 2003 to Exchange 2010.
    All users in bali.co.id are able to access email from Owa, BlackBerry (BIS), Outlook, but cannot access from Android, Windows Phone. (Active-Sync).
    I got error information generated from https://testconnectivity.microsoft.com, as following:
    Attempting the FolderSync command on the Exchange ActiveSync session.
    The test of the FolderSync command failed.
    Tell me more about this issue and how to resolve it
    Additional Details
    Exchange ActiveSync returned an HTTP 500 response (Internal Server Error).
    Active-Sync still not work even I check option "Include inheritable permissions from this object" in security tab.
    any idea to fix this issue?
    Thanks.
    Endrik
    Endrik | blog: itendrik.wordpress.com Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading
    the thread.

    Hi Sathish, 
    We are planning to migrate Exchange 2003 to Exchange 2013, all user already in Exchange 2010 and Exchange 2003 was decommissioned
    Event Viewer log as following:
    Log Name:      Application
    Source:        MSExchange ActiveSync
    Date:          1/17/2014 10:00:48 PM
    Event ID:      1008
    Task Category: Requests
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      EXC2010.jakarta.co.id
    Description:
    An exception occurred and was handled by Exchange ActiveSync. This may have been caused by an outdated or corrupted Exchange ActiveSync device partnership. This can occur if a user tries to modify the same item from multiple computers. If this is the case,
    Exchange ActiveSync will re-create the partnership with the device. Items will be updated at the next synchronization. 
    URL=/Microsoft-Server-ActiveSync/default.eas?Cmd=Sync&User=bali%5Csteveng&DeviceId=SAMSUNG123456789&DeviceType=SAMSUNGGTN7000
    --- Exception start ---
    Exception type: Microsoft.Exchange.AirSync.AirSyncPermanentException
    Exception message: A null value was received for the NTSD security descriptor of container CN=ExchangeActiveSyncDevices,CN=Steven Gerrard,OU=IT,DC=bali,DC=co,DC=id.
    Exception level: 0
    HttpStatusCode: 500
    AirSyncStatusCode: 110
    XmlResponse: 
    This request does not contain a WBXML response.
    Exception stack trace:    at Microsoft.Exchange.AirSync.ADDeviceManager.SetActiveSyncDeviceContainerPermissions(ActiveSyncDevices container)
       at Microsoft.Exchange.AirSync.ADDeviceManager.CreateActiveSyncDeviceContainer(Boolean retryIfFailed)
       at Microsoft.Exchange.AirSync.ADDeviceManager.CreateActiveSyncDevice(GlobalInfo globalInfo, ExDateTime syncStorageCreationTime, Boolean retryIfFailed)
       at Microsoft.Exchange.AirSync.ADDeviceManager.CreateActiveSyncDevice(GlobalInfo globalInfo, ExDateTime syncStorageCreationTime)
       at Microsoft.Exchange.AirSync.Command.UpdateADDevice(GlobalInfo globalInfo)
       at Microsoft.Exchange.AirSync.Command.CompleteDeviceAccessProcessing()
       at Microsoft.Exchange.AirSync.Command.WorkerThread()
    --- Exception end ---.
    I think KB817379 is not related because Exchange 2003 was decommissioned.
    Regards, 
    Endrik
    Endrik | blog: itendrik.wordpress.com Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading
    the thread.

  • Migrating exchange 2003 to 2010 while everyone is running SMTP, POP3 and IMAP on the old exchange 2003

    Hi all
    We have a legacy Exchange 2003 running with more than 800 users and with a very mixed configuration for client access. Most of users are running POP3/SMTP on the Exchange, some are running IMAP/SMTP and some are running MAPI access. 
    Please note that THERE IS NO WAY that we move all users to MAPI access before the installation (due to deadlines).
    We plan to install a new Exchange 2010, starting with a CAS/HUB server. We do not need to migrate users automatically, and we can proceed later to move them individually to the new Exchange 2010 infrastructure in a non-transparent way. 
    More importantly, we need to maintain that everyone receives their e-mail and all communication through the exchange 2003 continues uninterrupted. 
    My question is can we install the new CAS/HUB server, while maintaining the old exchange server running with it's old name and create new names for the CAS/HUB server. In such a configuration, will all the Exchange 2003 services continue to run as usual
    (POP3/IMAP/SMTP/MAPI)?

    In addition, you may also spend some times at below mentioned helpful resources to check the prerequisites before moving all mailboxes from exchange 2003 to 2010 :
    http://exchangeserverpro.com/wp-content/uploads/2011/02/Exchange-Server-2003-to-2010-Migration-Guide-V1.3-Planning-Chapter.pdf
    http://technet.microsoft.com/en-us/library/dd638130(v=exchg.141).aspx
    https://www.simple-talk.com/sysadmin/exchange/upgrade-exchange-2003-to-exchange-2010/
    Moreover, to avoid any interruption  during the completion of migration process, you can also take a look at this application(http://www.exchangemigrationtool.com/) that could be a good alternate approach
    for you.

  • Outlook 2010 appointment with exchange 2003 - organizer question

    Hi Sir / Madam,
    I have a exchange 2003 server and containing confernece room mailbox. The conference room mailbox is
    same as a normal user mailbox since exchange 2003 don't has resource booking feature. And I have following
    issue need to be fixed and don't know if this possible for my environment.
    Each user can create the appointment in the conference room's calendar but when they select conference room
    as resource (location), when all other users open that appointment, then will see the organizer name is conference
    room, only the creator can see the appointment was created by himself/herself. I found that if the creator leave
    the resource as blank, all users can see the correct organize name.
    Anyone know how to fix this issue? Thx
    Jeffrey

    Hi Jeffrey,
    According to your posting, I noticed that each user can create the appointment or meeting in the conference room’s calendar. If so, please check if the Default Calendar permission of this room Calendar is set to Author or higher permission.
    Generally, if the user creates the calendar items directly from a room’s calendar instead of creating meeting request and sending it to this room, the Organizer name would not be shown as the creator.
    Therefore, it is not recommended to directly create meeting request in a room’s calendar. Please create meeting requests in the organizer’s calendar and add the room as a resource, then send the meeting request to the room and attendees. Now check whether
    the organizer is shown correctly.
    Regards,
    Winnie Liang
    TechNet Community Support

  • Exchange 2003 /2010 Co-existence plus 2010 migration to new hardware

    Hi,
    Here is our current scenario;
    Exchange 2003/2010 co-existence. This has been running perfectly for a couple of months now.
    Exchange 2003 - exch1.domain.lan
    Exchange 2010 (SP3) - exch2.domain.lan (local domain name)  /  mail.domain.com.au (external domain name)
    ActiveSync, autodiscover, legacy etc are all working. Our UAC certificate from GoDaddy has all the required names for exch2 - except it doesn't have the local domain name as they don't allow certificates with that anymore. I've configured all the required
    services to be the external domain name and am running split DNS.
    The first Exchange 2010 server I installed was lower spec'd and only has about 25 users on it. I now need to install a second Exchange 2010 server (exch3.domain.local), which is properly spec'd and will host the entire company. I won't be running DAG as
    I need to repurpose the first Exchange 2010 server once it's removed.
    My high level questions are;
    1) Should I migrate everyone off Exchange 2003 onto Exchange 2010, decommission the 2003 server, and then install the second 2010 server? OR
    2) Should I install the second Exchange 2010 server, migrate everyone from the first Exchange 2010 server, decommission that one, then do the migration from 2003 to 2010?
    OR does it matter which way I do it?
    I've read what I can find about installing the second Exchange 2010 server into the organisation. It seems to be pretty simple at first. Just install Exchange 2010 with HT, mailbox and CAS roles which will automatically configure it into the same Exchange
    organisation.
    1) Do I configure CAS to be externally facing right from the get go or do I do that later?
    2) As soon as I install the second Exchange 2010 server, will I encounter any mail flow problems? Will mail be trying to flow out of the second Exchange 2010 server as well as the first?
    In regards to SSL, so obviously the second Exchange 2010 server will have a different local domain name than the first, but ultimately, I want it to have the same external domain name, eg mail.domain.com.au. As my certificate doesn't contain any local domain
    names, can I export the certificate from exch1 and import it into exch2, or should I just generate a new CSR from exch2 and get GoDaddy to reissue it?
    OR should I look at creating a CAS Array from exch1 and adding exch2 to it. (I don't fully understand the workings of this at the moment).
    Any guidance on the above is helpful.
    Thanks.
    Steve

    Hi Steve I will try my best to answer each of these 
    My high level questions are;
    1) Should I migrate everyone off Exchange 2003 onto Exchange 2010, decommission the 2003 server, and then install the second 2010 server? OR
    2) Should I install the second Exchange 2010 server, migrate everyone from the first Exchange 2010 server, decommission that one, then do the migration from 2003 to 2010?
    OR does it matter which way I do it?
    doesn't matter at all. Since you want to move to a new hardware you can setup a new Server CASH/HUB/Mailbox. Once installed start migrating the mailboxes from Exchange 2003 to this mailbox server. This way you will not have to redo the migration from 2010
    to new 2010 sever -- like you mentioned in 1) it will save you a lot of time and repeating procedure. 
    I've read what I can find about installing the second Exchange 2010 server into the organisation. It seems to be pretty simple at first. Just install Exchange 2010 with HT, mailbox and CAS roles which will automatically configure it into the same Exchange organisation.
    1) Do I configure CAS to be externally facing right from the get go or do I do that later?
    Keep your existing 2010 internet facing for now. Once you finished migrating the mailboxes then you will need to do it.
    2) As soon as I install the second Exchange 2010 server, will I encounter any mail flow problems? Will mail be trying to flow out of the second Exchange 2010 server as well as the first?
    Mail will not flow to 2ndry server unless you add that server as a source serve in the transport.
    In regards to SSL, so obviously the second Exchange 2010 server will have a different local domain name than the first, but ultimately, I want it to have the same external domain name, eg mail.domain.com.au. As my certificate doesn't contain any local domain
    names, can I export the certificate from exch1 and import it into exch2, or should I just generate a new CSR from exch2 and get GoDaddy to reissue it?
    You  can always export the certificate and then import it to the newly installed Exchange 2010.
    OR should I look at creating a CAS Array from exch1 and adding exch2 to it. (I don't fully understand the workings of this at the moment).
    You will only need to setup the CAS array if you are going to use both the server which can be done later.
    Hope that help
    Where Technology Meets Talent

Maybe you are looking for