Error Creating New Migration Endpoint: Staged Migration from Exchange 2003 to Office 365

I am unable to create a new migration endpoint, receiving the following message:
***BEGINQUOTE***
error
We couldn't discover the migration endpoint. Consider using the Exchange Remote Connectivity Analyzer (https://testexchangeconnectivity.com) to diagnose the connectivity issues.
***END QUOTE***
When I visit the test connectivity site and perform the Outlook Anywhere (RPC over HTTP) test, I don't get any errors.
Where do I go from here?

Well... I think I may look silly.
I kept pounding at this problem and discovered the following: in the exchange server box I needed to put the local computer name of my exchange server instance. In the RPC Proxy server, I needed to put the public domain name of the server. So
in the first box I just have "mycomputername" and in the second box I have "mail.mydomain.com" Now it works... I think.
(I tried to insert an image, but apparently my account is not confirmed)

Similar Messages

Migrate Exchange 2003 to Office 365

Dear all,
We are going to migrate Exchange 2003 to Office 365. Because of the large number of mailboxes and mail databases, we decide to build hybrid to support coexistence during the migration period.
According to "Exchange Server Deployment Assistant" I found that we can build more Exchange 2010 for that requirement
http://technet.microsoft.com/en-us/exdeploy2013/Checklist?state=2419-W-BwAIAAAAQAAAAAEAiFIAAAA~
I just wonder that after deploying the Exchange 2010, can we move directly the mailboxes from Exchange 2003 to Office 365 or we need to move to Exchange 2010 first (as a "buffer") before moving to Office 365
Thanks a lot !!!

Hello,
The main goal of a staged migration is to migrate Exchange on-premises servers when:
1. You have more than 2000 mailboxes.
2. You plan to migrate over a few weeks and months rather than in a single batch.
3. You want to migrate to the Cloud completely and remove your on-premises Exchange deployment.
Hybrid scenarios are useful when you do not want to remove your on-premises deployment. In some cases there is no technical possibility, it is not cost-effective etc. to move a whole organization to Office 365. In these situations you may decide that moving
only some mailboxes to Office 365 is a good option and create a hybrid deployment.
You need to consider all pros and cons, especially when Exchange 2003 has gone out of support lifecycle and then choose the better option for your organization.
Hope it helps,
Adam
CodeTwo: Software solutions for Exchange and Office 365
If this post helps resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others find the answer faster.

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

Migrate exchange 2003 to office 365 with single singon

Dear All,
We are going to migrate our mail systems from exchange server 2003 to office 365 with single sing-on.
Please advice me the best way and guide line (information) to do it smoothly.
Thanks in advance.

Dear Andres parnova,
Thanks for your information.
I found series of articles in msexchange.org
http://www.msexchange.org/articles-tutorials/office-365/exchange-online/performing-staged-exchange-migration-office-365-exchange-online-part1.html which has very nice and clear information.
But, in the articles the author did not include ADFS configuration and steps.
I would like to know how to configure ADFS and single sing-on.
Thanks
Min

Migrating to Exchange 2013 from Exchange 2003, EV7, Office 2003 and XP

What is the best approach for migrating our 300 user Exchange 2003 organisation to Exchange 2013.? We use Enterprise vault v7.5 and the clients are Office 2003 on an XP desktop.
We are also planning to upgrade to Windows7 and Office 2013 this year so I am trying to understand the sequence. Should we just aim to upgrade to Exchange 2010 with Outlook 2010 instead?
Many thanks.

Hi,
You can't install Exchange 2013 until and unless you decommission your Exchange 2003. Coexistence of Exchange 2013 with Exchange 2003 is not supported. You first need to upgrade to Exchange 2010 SP3 and then move users to Exchange 2010 and decommission your
Exchange 2003 servers. Once you are done with the decommissioning of your Exchange 2003 server you will be able to install your first Exchange 2013 machine in your messaging infrastructure.
Kindly mark this as answer if it fulfill your requirements. Thanks.
Regards, Riaz Javed Butt Consultant Microsoft Professional Services MCITP, MCITP (Exchange), MCSE: Messaging, MCITP Office 365

Exchange 2010 to office 365 migration lab

I am looking out for free migration lab if any available online from Microsoft or any vendor related to migrate from exchange 2010 to office 365 . Please suggest ?
Aditya Mediratta

Hi,
Unfortunately, there’s no related lab for use.
We can Microsoft Exchange Server Deployment Assistant to generates a custom step-by-step checklist that will help you deploy different versions of Exchange Server for different types of scenarios. For your reference:
https://technet.microsoft.com/en-us/office/dn756393.aspx
Thanks
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Allen Wang
TechNet Community Support

How to move from EOP to Hybrid Office 365 configuration?

I have a customer that just completed their transition from FOPE to EOP. Everything is working, but the customer would like to move all Exchange 2010 mailboxes to Exchange Online. They already have licenses, and have more than 2000 seats. A
cutover migration is not possible, so a hybrid migration is my only choice. I have been unable to find any documentation on this scenario (EOP-to-Hybrid).
Does anyone have any references or documentation that points to the correct steps to make this transition? Some blogs indicate that the only way to make this work is to point the MX record elsewhere, remove the existing EOP connectors, and have the
Hybrid configuration wizard re-create them.
Any help here is appreciated! Thanks.

Hi
Your question is not that easy to be answered since the planning and migrating depends upon the current environment setup, status and everything.
However you can follow this conitious thread step by step for Migrating from Exchange 2013 to Office 365 which will help you to plan accordingly to your environment
http://www.msexchange.org/articles-tutorials/office-365/exchange-online/configuring-exchange-2013-hybrid-deployment-and-migrating-office-365-exchange-online-part11.html
I would recommend you to open up a ticket with Microsoft for a hassle free migration from Exchange 2013 to O365
But for migration from Notes to o365 we need some kind of third party softwares like Quest Tools to throttle the process quickly and also you need to set few throttling policies in Exchange end as well inorder to integrated well with Microsoft Cloud
during Migration process. Its better you can open up a ticket with Microsoft and Quest for planning the migration acording do your needs and proceed.
Below one is for your reference
http://www.export-notes.com/how-to-migrate-lotus-domino-to-office365.html
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

Calendar Free/Busy permissions being ignored for users migrated from Exchange 2003, fine for new users created on Exchange 2010

I have uncovered a situation where it seems the free/busy permissions are being ignored for users that were migrated from Exchange 2003 to Exchange 2010.
I have the default permissions set to only show Free/Busy Time, not Details. However if I look at the calendar for a users who was migrated from the old Exchange 2003 server, I can see details. If I look
at a newer user who was added directly to the Exchange 2010 server, I (correctly) only see the times and "Free" or "Busy", not the specific details.
I verified the permissions on the migrated mailboxes many different ways (Exfolders, cmdlets, etc) and all signs point to only allow showing Free/Busy Times, but alas, I can still see the Details as well.
My users are using Outlook 2010.

Hi,
Does this issue occur on Outlook only or both Outlook and OWA?
Since you have double checked the permissions via multiple methods, it seems there is nothing problem on permission. Please make sure the migration from Exchange 2003 server completed successfully.
If in OWA everything goes well (cannot see details), it should be an issue on the Outlook client side.
I suggest run Outlook under safe mode to avoid some AVs and add-ins.
I suggest re-create profile to refresh the caches.
Thanks
Mavis
Mavis Huang
TechNet Community Support

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

AR: Error Creating new Customer

Hello,
I am having error the following error creating new customer in AR 12.1.1 "Invalid value for currency_code. Please enter currency_code value from fnd_currencies". The currencies are all enabled.
Thanks,

Please see these docs.
Cannot Add Customers. Error: Invalid Value For Currency_code. [ID 554555.1]
CUSTOMER INTERFACE STATUS ERROR CODES [ID 1073634.6]
Resource Addresses and Subinventory Assignment Fails with APP-295320: Provide a positive integer [ID 986655.1]
Thanks,
Hussein

Migrate from Google Apps to Office 365 with admin credentials only

Hi team,
We are migrating from Google Apps to Office 365. I know the normal procedure of migrating, but I want to know how to migrate from gmail to office 365 with administrator credentials. Normally for migration, we use user's mail ID and password in CSV file.
But I don't want to use users credentials, instead I want to use only Administrator credentials.
Thanks in Advance...

A third party tool such as MigrationWiz can accomplish this task. More information on how to set up administrative access can be found here:
https://community.bittitan.com/kb/Pages/GoogleApps%20to%20Office365%20Migration%20Guide.aspx

Creating new DMS info record directly from purchase order transactions

Hello Everybody,
does anyone knows of a way to make it possible for users to Create New DMS info record directly from the purchase order transactions ?
e.g:
in ME22N there is a button of "Documents" for an item level in the order, but that button only allows to link an existing info record.
Link To a screenshot:
http://img263.imageshack.us/i/me22n1.jpg/
Regards,
Yossi Fridman.

hi
This query has already been addressed in the following Forum by Christoph Hopf..
pls chk link below.
Create DIR through P.O and Sales order screen
Thanks
john
Edited by: johnpp on Feb 15, 2011 11:54 AM
Edited by: johnpp on Feb 15, 2011 11:57 AM

Migration from Exchange 2003

Hi,
We are a small business. We currently use Small Business Server 2003 which has Exchange 2003 built-in.
Can we migrate from Exchange 2003 to Mac OS X Server mail services?
Can Office 2011 connect to Mac mail services? If so, what protocols?
Many thanks,
Ciaran.

We are a small business. We currently use Small Business Server 2003 which has Exchange 2003 built-in.
What features of Exchange are you using? Push notifications? Calendaring. Sharepoint? Figure out what you want and what you need (and which are two separate lists) and then map that over to what Mac OS X Server, or to what a Mac box with the Kerio Connect package loaded, might provide you.
Can we migrate from Exchange 2003 to Mac OS X Server mail services?
That's rather open-ended. It's possible, but there's no single definition of small business mail requirements. Some small businesses can and have, and some might find themselves missing critical features.
Can Office 2011 connect to Mac mail services? If so, what protocols?
iWork does well enough to read and write Office files locally, so I don't have experience with Microsoft Office. The Windows mail clients can certainly access Unix mail servers. As for what connectivity is present within Office, I'm way too rusty with Windows to comment. What used to be the Outlook Express client worked just fine with Unix mail servers. The full-on Office Outlook client was pretty flaky with stuff other than Exchange, but that was some years ago.
Biggest issues with SBS migrations tend to be with shared Address Book, with shared Calendars and with Sharepoint services; if you're heavy users of those features, you might find the Mac OS X Server implementations lacking. Kerio can potentially help here.
Look around the forums for some other folks. This particular SBS migration has been fairly common fodder for discussions.

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.

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

Error Creating New Migration Endpoint: Staged Migration from Exchange 2003 to Office 365

Similar Messages

Maybe you are looking for