Error in uninstall Exchange 2003 after Exchange 2010 migration.

Setup encountered an error while checking prerequisites for component "Microsoft Exchange": 0X80072030 (8240): There is no such object on the server.  I searched about the error and most of the hit is referring to postmaster account point
to the old server and that doesn't apply to our environment.
http://support.microsoft.com/kb/283089
below is the errors from the setup log.  Other users had reported this problem but didn't find any solution other than manually uninstall the last Exchange 2003 server.  The problem is I couldn't find any official KB for manually
remove legacy Exchange server from Exchange 2010 org, bb288905 or kb833396 do not provide enough information.  So is my only choice is to call Microsoft Support?
thanks
[22:38:41] Entering ScConstructAddressListServiceDNAndCN
[22:38:41] Leaving ScConstructAddressListServiceDNAndCN
[22:38:41] === IGNORING PREVIOUS ERRORS === ScPRQ_ServerGroupsHaveNotBeenMovedOrRenamed (f:\titanium\admin\src\udog\excommon\prereq.cxx:8080)
           The operation has completed successfully.
[22:38:41] Entering CCompDomainPrep::ScGetEffectiveMode
[22:38:41] Leaving CCompDomainPrep::ScGetEffectiveMode
[22:38:41] Entering ScDetermineIfLocalDomainServerGroupHasAlreadyBeenACLedOnExchangeCT
[22:38:41] Using cached result for domain "/dc=org/dc=cityofwpg/dc=ad"
[22:38:41] The required permissions have already been set
[22:38:41] Leaving ScDetermineIfLocalDomainServerGroupHasAlreadyBeenACLedOnExchangeCT
[22:38:41] Attempting to create the SRS DOB [checking whether SRS is installed].
[22:38:41] Entering ScFindRoutingGroupThatContainsServer
[22:38:41] Leaving ScFindRoutingGroupThatContainsServer
[22:38:41] Entering ScPRQ_DoesNotContainLastMAPIMDBInMixedModeAG
[22:38:41] This prerequisite has PASSED -- ID:62235 --
[22:38:41] Leaving ScPRQ_DoesNotContainLastMAPIMDBInMixedModeAG
[22:38:41]  ScPRQ_ServerIsNotRUSResponsibleServerInTheNonEmptyOrg (f:\titanium\admin\src\udog\excommon\prereq.cxx:3133)
           Error code 0X80072030 (8240): There is no such object on the server.
[22:38:41]  CCompServer::ScCheckEVSPrerequisites (f:\titanium\admin\src\udog\exsetdata\components\server\compserver.cxx:1358)
           Error code 0X80072030 (8240): There is no such object on the server.
[22:38:41]  CCompServer::ScCheckPrerequisites (f:\titanium\admin\src\udog\exsetdata\components\server\compserver.cxx:955)
           Error code 0X80072030 (8240): There is no such object on the server.
[22:38:41]  CComExchSetupComponent::ScCheckPrerequisites (f:\titanium\admin\src\udog\bo\comboifaces.cxx:1598)
           Error code 0X80072030 (8240): There is no such object on the server.
[22:38:41]  CComExchSetupComponent::ScCheckPrerequisites (f:\titanium\admin\src\udog\bo\comboifaces.cxx:1598)
           Error code 0X80072030 (8240): There is no such object on the server.
[22:38:41] === IGNORING PREVIOUS ERRORS === HrSetProblemOnInstallAction, while calling ScCheckPrerequisites (f:\titanium\admin\src\udog\bo\comboifaces.cxx:1399)
           The operation has completed successfully.
[22:38:41] Setup encountered an error while checking prerequisites for the component "Microsoft Exchange":
0X80072030 (8240): There is no such object on the server.
[22:43:09]  CComBOIFacesFactory::QueryInterface (f:\titanium\admin\src\udog\bo\bofactory.cxx:54)
           Error code 0X80004002 (16386): No interface.

Did you also check for other accounts, i.e. non-postmaster?
Setup will check to make sure that there are no mailboxes homed onto this server.    This attribute homeMDB could still be set for a mailbox that has the Exchange attributes remove.  Seen that before when people set attributes directly
via scripts.....
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.
Yes, I did.  Nothing has MDB = the legacy server.    The error from setup log seems to suggest a different problem.

Similar Messages

  • Decommissioning Exchange 2003 after Office 365 Migration

    Hello,
    My company recently migrated from Exchange 2003 to Office 365 and are working on decommissioning our on-premises Exchange 2003 server.  We believe everything is ready to go, however this Microsoft article: http://help.outlook.com/en-us/140/ff959224.aspx#nextsteps has
    a big Caution box warning of "unintended consequences" and recommending I contact Microsoft Support:
    I've tried my Office 365 support options, but they only tell me that Exchange 2003 is no longer supported and they can't help me, despite the fact that I'm trying to remove it, not maintain it.  So
    I'm allowed to pay for a new service, but shouldn't expect assistance in safely moving from my old service...
    Regardless, they directed me here, so I was hoping someone might be able to advise about what these "unintended consequences" actually are so I can feel fully prepared to decommission.
    Thanks in Advance,
    Jim

    Hi,
    After you’ve verified that all e-mail is being routed directly to the cloud-based mailboxes, completed the migration, and no longer need to maintain your on-premises e-mail organization or don’t plan on implementing a single sign-on solution, you can uninstall
    Exchange from your servers and remove your on-premises Exchange organization. For more information, see the following:
    How to Uninstall Exchange Server 2003
    http://technet.microsoft.com/en-us/library/bb125110(EXCHG.65).aspx
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Moving public folders from exchange 2003 to exchange 2010 error while moving replicas

    Dear All,
    i am in the process of migrating from Microsoft Exchange 2003 to Exchange 2010,
    i am done with moving all the mailboxes 300 mailbox almost with a 1.5 TB DB with no issues 
    when i tried all the processes, procedures, instructions and forums to move the public folder or 
    to use move all replicas from Exchange 2003 to Exchange 2010 i always get errors , now when i try 
    to open PF Management console from the exchange 2010 server i get it but it is disconnected
    then i can choose to coneect to the new server name EXCHANGE2010 with no issues
    when i try to expand the default folder and system folder i get the following error.
    OAB is set on the new server as default.
    when i try to add replica using power shell i get this error:
    WARNING: An unexpected error has occurred and a Watson dump is being generated: Object reference not set to an inst
     of an object.
    Object reference not set to an instance of an object.
        + CategoryInfo          : NotSpecified: (:) [Get-PublicFolder], NullReferenceException
        + FullyQualifiedErrorId : System.NullReferenceException,Microsoft.Exchange.Management.MapiTasks.GetPublicFolder
    following error when trying to expand PF on EXCHANGE 2010
    Microsoft Corporation
    Microsoft® Windows® Operating System
    6.0.6000.16386
    Unexpected error [0x7653450B] while executing command 'get-publicfolder -getchildren -identity '\' -server 'Exchange2010.ptdubai.com''.
    Microsoft.Exchange.Configuration.MonadDataProvider.CommandExecutionException: Unexpected error [0x7653450B] while executing command 'get-publicfolder -getchildren -identity '\' -server 'Exchange2010.ptdubai.com''. ---> System.NullReferenceException: Object
    reference not set to an instance of an object.
       at Microsoft.Exchange.Configuration.Tasks.MapiTaskHelper.GetMapiPublicFolderDatabasesIdentities(ADSystemConfigurationSession configurationSession, ADObjectId serverId, TaskErrorLoggingDelegate errorHandler)
       at Microsoft.Exchange.Configuration.Tasks.MapiTaskHelper.ValidateServerContainsPFDatabase(Server server, ADSystemConfigurationSession scSession, TaskErrorLoggingDelegate errorHandler)
       at Microsoft.Exchange.Configuration.Tasks.MapiTaskHelper.ResolvePublicFolderServerAndUserLegacyDNs(ADSystemConfigurationSession scSession, ServerIdParameter serverIdParameter, String& serverLegacyDN, String& userLegacyDN, Fqdn& serverFQDN,
    TaskErrorLoggingDelegate errorHandler)
       at Microsoft.Exchange.Configuration.Tasks.GetMapiObjectTask`2.CreateSession()
       at Microsoft.Exchange.Configuration.Tasks.DataAccessTask`1.InternalStateReset()
       at Microsoft.Exchange.Configuration.Tasks.GetTaskBase`1.InternalStateReset()
       at Microsoft.Exchange.Management.MapiTasks.GetPublicFolder.InternalStateReset()
       at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
       at System.Management.Automation.CommandProcessor.ProcessRecord()
       --- End of inner exception stack trace ---
       at Microsoft.Exchange.Configuration.MonadDataProvider.MonadPipelineProxy.ClosePipeline(MonadAsyncResult asyncResult)
       at Microsoft.Exchange.Configuration.MonadDataProvider.MonadPipelineProxy.InternalEndInvoke(IAsyncResult results)
       at Microsoft.PowerShell.HostingTools.PipelineProxyBase.EndInvoke(IAsyncResult results)
       at Microsoft.Exchange.Configuration.MonadDataProvider.MonadCommand.EndExecute(MonadAsyncResult asyncResult)
       at Microsoft.Exchange.Configuration.MonadDataProvider.MonadDataReader.Close()
       at Microsoft.Exchange.Configuration.MonadDataProvider.MonadDataReader.Dispose(Boolean disposing)
       at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
       at System.Data.Common.DbDataAdapter.Fill(DataTable[] dataTables, Int32 startRecord, Int32 maxRecords, IDbCommand command, CommandBehavior behavior)
       at System.Data.Common.DbDataAdapter.Fill(DataTable dataTable)
       at Microsoft.Exchange.Management.SystemManager.DataTableLoader.Fill(RefreshRequestEventArgs e)
       at Microsoft.Exchange.Management.SystemManager.DataTableLoader.OnDoRefreshWork(RefreshRequestEventArgs e)
       at Microsoft.Exchange.Management.SystemManager.RefreshableComponent.worker_DoWork(Object sender, DoWorkEventArgs e)
       at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
    mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
    Microsoft.ManagementConsole, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
    MMCFxCommon, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    System.Configuration, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
    System.Xml, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
    System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
    System.Drawing, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
    Microsoft.Exchange.Management.PublicFolders, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Management.SystemManager, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
    Microsoft.ManagementGUI, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Data.Common, Version=14.0.631.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.ManagementGUI, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Configuration.ObjectModel, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
    Microsoft.Exchange.Diagnostics, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
    Microsoft.Exchange.Data.Directory, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.PowerShell.HostingTools, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    System.Drawing.Design, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
    Microsoft.Exchange.ManagementGUI.resources, Version=14.0.0.0, Culture=en, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Data, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Management, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Isam.Interop, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Data.Transport, Version=14.0.631.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.PowerShell.HostingTools, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    BPA.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    BPA.UserInterface, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Interop.adsiis, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Interop.Migbase, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.DKM.Proxy, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.AirSync, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Approval.Applications, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.CabUtility, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Cluster.Replay, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Configuration.RedirectionModule, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Data.ApplicationLogic, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Data.Mapi, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Data.Providers, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Data.Storage, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.EdgeSync.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.EdgeSync.DatacenterProviders, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Extensibility.Internal, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.InfoWorker.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Live.DomainServices, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.MailboxReplicationService.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.MessageSecurity, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.MessagingPolicies.Rules, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Net, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Rpc, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Search.ExSearch, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Search.Native, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Security, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.StoreProvider, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Transport.Agent.AntiSpam.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Transport.Agent.SenderId.Core, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Transport, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Transport.Logging.Search, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Transport.Sync.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Transport.Sync.Worker, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.UM.UMCommon, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.UM.UmDiagnostics.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Rtc.Collaboration, Version=3.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Rtc.Media, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    MSExchangeLESearchWorker, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    System.Management.Automation, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Core.Strings, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Core.Strings.resources, Version=14.0.0.0, Culture=en, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.HelpProvider, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    pspluginwkr, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    System.Management, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
    System.DirectoryServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
    System.Design, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
    Accessibility, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
    MMCEx, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Anonymously Hosted DynamicMethods Assembly, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null
    Microsoft.Exchange.Data.Directory.resources, Version=14.0.0.0, Culture=en, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Data.resources, Version=14.0.0.0, Culture=en, PublicKeyToken=31bf3856ad364e35
    Microsoft.Exchange.Configuration.ObjectModel.resources, Version=14.0.0.0, Culture=en, PublicKeyToken=31bf3856ad364e35
    i will be thankful for any assistant.
    PF DB is arounf 90 GB with alot of public folders and sub-folders. around 60 mail PF and too many subfolders.

    First and the most important thing you need to do is, upgrade exchange 2010 to SP2 and RU5.
    Exchange 2010 RTM support is long gone.
    http://www.microsoft.com/en-us/download/details.aspx?id=36768
    http://www.microsoft.com/en-us/download/details.aspx?id=41480
    Your exchange 2010 is still in stogeage ;)
    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.

  • Free/Busy availability and Out of Office not working after Exchange 2003 to Exchange 2010

    We just migrated from Exchange 2003 to Exchange 2010 as an intermediate step before we get to Exchange 2013.  I want to make sure everything is working OK before we start the migration to Exchange 2013.  
    The users have Outlook 2010, and there are 2 issues.  They can't view free/busy times for other people using the scheduling assistant, and they can't set their Out of Office messages.  If they go in through Outlook Web Access, then these features
    work!
    I've searched the forums, and I see a few similar issues, but I don't think this is related to the .Net issue on the CAS server.
    Any suggestions?
    Thanks!
    --Kent 

    Hi Kent,
    Try checking the free busy info Outlook 2010 with running  /cleanfreebusy switch
    Check the Free/Busy System Public Folder and pointed out to the correct server on each mailbox DB in Exchange 2010
    Find the public folder replica database
    get-publicfolder -Identity "\NON_IPM_SUBTREE\SCHEDULE+ FREE BUSY" -Recurse | fl name,Replicas
    In E2k10 check if the exchange 2003 is added in the replica list. If not try adding them and check.
    force Public folder content replication.
    Please mark as helpful if you find my contribution useful or as an answer if it does answer your question.
    That will encourage me - and others - to take time out to help you.
    Regards,
    Sathish

  • 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."

  • Unable to manage Distribution list membership since moving from Exchange 2003 to Exchange 2010

    Hi,
    We have recently started migrating from Exchange 2003 to Exchange 2010.  One of our customers used to be able to manage a security group through the outlook address book.  This is a mail enabled security group where the customer is on
    the "Managed by" entry and the "Manager can update membership list" is ticked. 
    Now that the users mailbox has been migrated to Exchange 2010, if they try and modify the membership using outlook by finding the group in the address book they get the error "changes to the distribution list membership cannot be saved. you do not have
    sufficient permission to perform this operation on this object".
    I have now added a test account to the managed by entry on the security group to test the problem.
    I have followed the article
    http://blogs.technet.com/b/exchange/archive/2009/11/18/3408844.aspx that explains how to use the EMS to give users the right to amend groups that users own.  I did not run the script but entered the following commands:
    New-ManagementRole -name “MyDistributionGroupsManagement_Test” -parent MyDistributionGroups
    Remove-ManagementRoleEntry “MyDistributionGroupsManagement_Test\New-DistributionGroup” -confirm:$false
    Remove-ManagementRoleEntry “MyDistributionGroupsManagement_Test\Remove-DistributionGroup” -confirm:$false
    New-ManagementRoleAssignment -name “MyDistributionGroupsManagement_Test-Default Role Assignment Pol” -role “MyDistributionGroupsManagement_Test” -policy “Default Role Assignment Policy”
    All appears to have worked ok and I have seen no errors while doing this
    If I use OWA and then use the ECP, I can now see the "Public groups I own" but no groups are listed.
    I have created some new distribution groups in Exchange 2010 (One dist list and one security group) to test and added the test account as an owner of both and a member of both.  I still cannot amend the membership using outlook address book and the
    ECP still shows no groups under "Public Groups I own"
    I have seen a number of articles on how to do this and it looks like I am doing everything right and it has worked for plenty of other people.  I just don't know what's going wrong.
    I would be very grateful if anyone can help. 
    Matt

    Hi Rajith,
    I deleted the outlook profile and recreated it but this did not work.
    I have now created a brand new mailbox on Exchange 2010 added this to the "managed by" section of the Exchange 2010 dist lists and I still get the error.  I also do not see the groups listed when logging in as that user to OWA ECP and clicking on the
    Groups link.
    I had a look at the link you sent me and I could see that from the Exchange server when I opened the User roles to get to the ECP, clicked on Roles and Auditing and then User Roles the only policy applied is "Default role assignment".  When I select
    the details for this, under Distribution groups, "My Distribution Groups" is not ticked but my new one that I created "My DistributionGroupsManagement_Test" is.  So this looks ok.
    Any other ideas?
    Matt

  • Exchange 2003 to Exchange 2010 migration steps

    HI ,
    I have migrated windows 2003 to windows 2008.Its successfully migrated.
    Second phase i have a plan to migrate exchange 2003 to exchange 2010.
    My current setup
    windows 2008 64bit (DC)
    exchange 2003 sp2
    1
    Bring the Exchange organization to Exchange Native Mode.
    2
    Upgrade all Exchange Servers to Exchange Server 2003 Service Pack 2.
    3
     Bring the AD forest and domains to Windows Server 2003 Functional (or higher) levels.
    4
     Upgrade at least one Global Catalog domain controller in each AD site that will house Exchange Server
    to Windows Server 2003 SP2 or greater.
    5
     Prepare a Windows Server 2008 (RTM or R2) x64 edition server for the first Exchange 2010 server.
    6
    Install the AD LDIFDE tools on the new Exchange 2010 server (to upgrade the schema).
    7
     Install any necessary prerequisites (WWW for CAS server role).
    8
    Run setup on the Exchange 2010 server, upgrade the schema, and prepare the forest and domains. (Setup runs all in one step or separate
    at the command line.)
    9
     Install CAS server role servers and configure per 2010 design. Validate functionality.
    10
    Transfer OWA, ActiveSync, and Outlook Anywhere traffic to new CAS servers.
    11
     Install Hub Transport role and configure per 2010 design.
    12
     Transfer inbound and outbound mail traffic to the HT servers.
    13
     Install mailbox servers and configure Databases (DAG if needed).
    14
    Create public folder replicas on Exchange 2010 servers using pfmigrate.wsf script, AddReplicaToPFRecursive.ps1, or Exchange 2010
    Public Folder tool.
    15
    Move mailboxes to Exchange Server 2010 using Move Mailbox Wizard or Power Shell.
    16
     Rehome the Offline Address Book (OAB) generation server to Exchange Server 2010.
    17
    1Rehome the public folder hierarchy on the new Exchange Server 2010 admin group.
    18
     Transfer all Public Folder Replicas to Exchange Server 2010 Public folder store(s).
    19
     Delete Public and Private Information Stores from Exchange 2003 server(s).
    20
     Delete Routing Group Connectors to Exchange Server 2003.
    21
    Delete Recipient Update Service agreements using ADS Edit.
    22
    Uninstall all Exchange 2003 servers.
    This  is my plan to migrate.But  i have a doubt in installing exchange 2010 in this scenario.
    Is it necessary to use
    Setup.com /PrepareLegacyExchangePermissions,
    Please help me what excactly i have to do

    I think that <a href="http://www.micronobal.com/blog/2014/5/1/exchange-server-migration-to-the-cloud-ensure-a-seamless-transition" title="Exchange Server Migrations">Exchange Server
    Migration</a>  is a very delicate project and to be taken very seriously as it is a detailed work as well. You are giving us some great tips. 
    Some Articles I would like to share as well:
    <a href="http://www.micronobal.com/blog/2014/5/1/exchange-server-migration-to-the-cloud-ensure-a-seamless-transition" title="Exchange Server Migration to the Cloud - Seamless Transition.">
    Exchange Server Migration to the Cloud</a>
      It takes a lot of time and effort to get it right. Thank you for helping
    Here some information about services for migrations
    <a href="http://www.micronobal.com/business/cloud/advancedtechnologyservices" title="Migrate your email to the cloud.">Business Email migration</a>

  • Exchange 2003 to Exchange 2010

    We have about 18 sites and most of them have been migrated to Exchange 2010. I'm trying to uninstall Exchange 2003 on the legacy servers but I am running into an issue with the routing groups. Since the server is the master member under the routing group
    I am unable to uninstall exchange 2003. All the documents that I could find are in regards to removing the last exchange 2003 server from the org and these will not be the last servers to be removed but they are the last in their sights. I have tried deleting
    the connector from exchange 2010 then from exchange 2003 and I can't because it contains a member server and I can't delete that member server  because it is a master and every doc that I can find wants me to replace the master but I want the RG to completely
    go away! This should not be that difficult. Any advice would be greatly appreciated.
    I know this is in the wrong form but there isn't a way to select Exchange 2003 or Exchange 2010 so I apologize about that.
    -J

    Hi,
    I think you only need to remove the RGC:
    To Remove the Last Legacy Exchange Server, please follow the article below:
    http://technet.microsoft.com/en-us/library/bb288905(v=EXCHG.80).aspx
    Thanks,
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Simon Wu
    TechNet Community Support

  • How to migrate public folders from legacy (exchange 2003 ) to exchange 2010

    How to migrate public folders from legacy (exchange 2003 ) to exchange 2010 . Please suggest ?
    Aditya Mediratta

    Hi Aditya,
    please find the answer in
    http://blogs.technet.com/b/agobbi/archive/2010/08/04/how-to-move-public-folder-from-exchange-2003-to-exchagne-2010.aspx
    Please ensure you have a working mailflow from Exchange 2003 to 2010, vice versa, before you begin. 
    Basically it's the same procedure as adding some PF Database in E2K3; just
    run .\AddReplicaToPFRecursive.ps1 -server "Exchange 2010 Server" -TopPublicFolder "\" -ServerToAdd "Exchange 2010 Server"
    Wait until some initial data started to replicate; after that run
    Update-PublicFolderHierarchy -Server "Exchange 2010 Server"
    After replication has finished you can do a
    .\MoveAllReplicas.ps1 -Server "Exchange 2003 Server" -NewServer "Exchange 2010 Server"
    Please let me know if it worked.
    Kind regards,
    Martin

  • Exchange 2003 to Exchange 2010 under same DC

    Hi there!
    our status is:
    1 Domain controller (win2008serverx64). 
    1 Exchange server (OS: win2003server x32, Exch2003EnterpriseSP 2x32) EX1
    The exchange is populated. It's configured in front-end with an apache.
    our intention is:
    to create another Exchange Server (OS: win2008R2server x64, Exch2010SP1) EX2 under the same domain. After deployment we intend to migrate all contents from EX1 to EX2. Then do disable and eliminate EX1 in order to keep EX2 as the only Exchange server.
    So far we have the EX2 OS in place. AD is an win2008
    Questions are:
    1. How o create another Exchange Server (OS: win2008R2server, Exch2010SP1) EX2 under the same domain?
    2. How to migrate all contents from EX1 to EX2 ?
    3. What to do to eliminate EX1 in order to keep EX2 as the only Exchange server?
    Thanks

    Hi
    You can install a new server and join it to your domain. Setup all the prereqs for exchange and then install exchange 2010.
    after that you can setup your connectors etc. plan your migration, do not rush it especially if you have public folders.
    look here regarding migration:
    http://exchangeserverpro.com/ebooks/exchange-2003-to-2010-migration-guide/
    http://www.petenetlive.com/KB/Article/0000234.htm
    http://social.technet.microsoft.com/Forums/exchange/en-US/f9c69120-a0bb-495a-ba2f-f74d62e6e303/exchange-2003-to-exchange-2010-migration-steps?forum=exchangesvrdeploylegacy

  • 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.

  • Exchange 2003 to Exchange 2010 Migration

    Is there anything I have to do to migrate Exchange 2003 to Exchange 2010 aside from migrating the database(s)? I believe autodiscover picks up the new server when people open Outlook?

    It will definitely HELP
    you with the migration process, its not a guaranty for a successful one.
    You should be familiar with both systems (Exchange 2003 & 2010) and know the migration process and be familiar with each step .
    Best practice is to make the migration in lab environment that is a copy of you production environment first. that way you will get an experience with the process and know in advance if there are any issues before go to production. I
    know that in real world this is not always possible.
    Here is another grate guide from Pete Long:
    http://www.petenetlive.com/KB/Article/0000234.htm
    As a side note, Exchange SP1 or SP2 no longer supported, so make sure your Exchange 2010 is installed with minimum SP3 (RU5 is better).
    Please take a moment to Vote as Helpful and/or Mark as Answer where applicable. Thanks.

  • Issue with Exchange 2003 after upgrading Active Directory

    I upgraded AD from 2003 to 2008 R2. Before I could go into AD to create users, click on the email check box and the user would have an account on Exchange. Now this feature is not available. How do I create mailboxes on my Exchange 2003 Server for users
    now?

    You can't, You have to administer Exchange 2003 functionality from Active Directory Users and Computers on the Exchange 2003 server.
    FYI: Companies running Exchange 2003 after April 8, 2014 will be responsible for their own for support. More importantly, because Microsoft will no longer provide security updates, companies that choose to continue running Exchange 2003 accept the risk associated
    with that.
    Enfo Zipper
    Christoffer Andersson – Principal Advisor
    http://blogs.chrisse.se - Directory Services Blog

  • Connector help ( Coexistence Exchange 2003 and Exchange 2010)

    Dear all,
    we are in a Coexistence state where all the mailboxes are not yet migrated to Exchange Sever 2010.
    On Exchange server 2003 we have two connectors 1) Internal 3) External
    1) Internal connector is used to have mail flow between postfix mail and Exchange server.
    2) External Connector is used for sending/receiving emails from External domains (like gmail,yahoo etc...)
    3) when we added first Exchange 2010 that time it created one RGC used for sending/receving emails between Legacy and new server.
    What I want to achieve is created new two more connectors on Exchange server which will act as Internal & External connector.
    if these works then delete connectors on legacy server and go ahead with for rest migration
    is it possible if not then how do it ? 
    TheAtulA

    Hi AtulA,
    Thank you for your question.
    Internal:
    To support coexistence between these two routing topologies, all Exchange 2010 servers are automatically added to a single routing group when Exchange 2010 is installed. The Exchange 2010 routing group is recognized in Exchange System Manager in Exchange
    2003 as Exchange Routing Group within Exchange Administrative Group.
    During the installation of the first Exchange 2010 Hub Transport server in an existing Exchange organization, we must specify an Exchange 2003 bridgehead server to which to establish the first routing group connector. We recommend that you select a bridgehead
    server located in a hub routing group or in a routing group that has many mailboxes. The routing group connector links the routing group where the Exchange 2003 server resides and the Exchange 2010 routing group. The Exchange 2010 routing group includes all
    Exchange 2010 servers, regardless of the Active Directory site in which they reside.
    Notice: Don't move Exchange 2010 servers out of Exchange Routing Group (DWBGZMFD01QNBJR), and don't rename Exchange Routing Group (DWBGZMFD01QNBJR) by using a low-level directory editor. Neither action is supported. Exchange 2010 must use
    this routing group for communication with Exchange 2003.
    External:
    We could create send connector and receive connector to send/receive email from Internet, we should modify the firewall setting to point to Exchange 2010.
    If there are any questions regarding this issue, please be free to let me know. 
    Best Regard,
    Jim

  • 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

Maybe you are looking for

  • My 30gb Ipod Classic wont sync all the songs in my library

    My ipod wont sync all the songs from my library, my library is only about 6gb so that cant be the problem. I tried to sync a playlist of the songs that werent syncing and still didnt show up on my ipod. How can i fix this?

  • Satellite M30x + Win7 : DVD's not detected by the CD/DVD drive

    Hi, I'm using a M30x since 2004 with its CD/DVD drive Mat****a DVD-RAM UJ-831 S. When I was using Windows XP, I never had problems to read or write on CD, CD-R, DVD, DVD-R or DVD-RW. But recently i have installed windows seven, and since this day the

  • BIZTALK bts action mapping problem with Message Schemas for the Composite Operation

    Hi, I have a message schema made with the composite operation. now, I have re-deployed my biztalk project and in the send port for this Oracle composite message the SOAP action header hasn't updated the correct action. now I tried several verations f

  • PGI problem related to CO object

    Dear Gurus, While doing pgi getting error as, Account 41201100 requires an assignment to a CO object. Not allowing to do the pgi. Pl help. Regards, Santosh

  • Query on Physical and Logical structures

    Hi All Please Open the following link that opens a figure a 12-1 Logaical and physical storage . Please explain me how an data file can have many extents ( An arrow between Data file and extent i.e one to many relation ship ) , as the data file store