Migrating from Exchange 2003

Hello!
I have a question regarding ISA Server 2006. Currently, we have Exchange 2003 and we are proceeding with upgrading to Exchange 2010 sp 2, primarily because of the Windows 2003 EOL. We have two ISA servers and they are both on Windows 2003.
From what I have read, ISA server 2006 can co-exist with Exchange 2010. Is this correct? Or will I need to replace the two ISA boxes with Edge Transport boxes?
Thank you!
P.S. I have only worked with Exchange 2000 and 2010, but this is the first time I have worked in an environment with 2003. :)

Hi,
Yes, ISA server 2006 can co-exist with Exchange 2010 SP2.
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]
Mavis Huang
TechNet Community Support

Similar Messages

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

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.

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

Exchange 2010 Log files keep filling up following migration from Exchange 2003

I am migrating from Exchange server 2003 to 2010.
Having only moved one mailbox and set-up Public Folder replication, I noticed that the 20GB Drive allocated for the logs are filling up the entire drive, even before I have time to run my scheduled backup.
As a temporary measure, I have enable circular logging as a workaround.
Q/ Whilst this is not ideal, shall I leave it like this until the Public Folders are fully replicated and all mailboxes moved over?
Q/ What risk am I exposing myself to as a result of using Circular logging (I am running full backups every night).
Q/ Could there be another cause as to why the log files would grow so quick in such a short amount of time?

Hello,
Remember that logs are truncated after successful backups so if you have a lot of data replicated between backups, a lot of logs will be stored on disk.
"Q/ Whilst this is not ideal, shall I leave it like this until the Public Folders are fully replicated and all mailboxes moved over?"
The best option is to run backups to truncate logs. Circular Logging is useful in test and high available deployments as it can cause data loss (loss of data created between backups).
"Q/ What risk am I exposing myself to as a result of using Circular logging (I am running full backups every night)."
The same as mentioned above.
"Q/ Could there be another cause as to why the log files would grow so quick in such a short amount of time?"
Enormous logs generation can be caused by bugs in Exchange and connecting devices, i.e. iPhones can cause quick logs creation in some configurations. If you have latest Exchange 2010 build, it shouldn't be problem.
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.

Public folder content disapear immediately after starting replication during migration from exchange 2003

Hello,
I'm in the middle of exchange 2003 to 2010 migration. The migration of the user mailboxes is completed with no problems. Today I try to start the replication of the public folders (~ 160 GB). I used the following instructions (http://www.petenetlive.com/KB/Article/0000426.htm)
to set the replication for all folders. After a short time the first users calls, they were missing the objects in the public folder hierarchie. The routing group connector between the to servers lists a lot of wating mails but nothing really happens. I try
to revert the process by deleting the replications server settings bu everything is very slow and the objects in the public folder hierarchie are still missing.
Any suggestions?

Hmm sounds like you might have replicated things backwards if the folders are missing.
Did you happen to make a backup just prior to starting the replication?
Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline Exchange Mailbox and Public Folder EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003 -->
2007 --> 2010 --> 2013 with Lucid8's
DigiScope

Question regarding Exchange ActiveSync migration from Exchange 2003

Hello,
I am a bit confused about info about requirements when migrating Exchange ActiveSync (EAS) from 2003 to 2010. Now this question is related to EAS only, forget about other services, such as OWA or Outlook Anywhere, for a while.
Basically, all migration guides state that you have to configure and setup a legacy url for legacy services for co-existence. Based on that, I have had an understanding that Exchange 2010 CAS cannot proxy EAS users that are still on Exchange 2003, but issues
a redirect command to EAS client.
However, this article shows information that, based on my understanding, states that Exchange 2010 CAS DOES proxy EAS clients that are still on 2003: http://blogs.technet.com/b/exchange/archive/2009/12/08/3408985.aspx
For migration from 2007 EAS to 2010 EAS the article shows redirecting, but not with 2003.
So my question is: While talking about only EAS, do I need to configure legacy external url/namespace/name resolution or not?
Thanks for answering!

Hello,
I agree with Rajith's suggestion.
Additional article for your reference.
http://technet.microsoft.com/en-us/library/bb310763(v=exchg.141).aspx
Cara Chen
TechNet Community Support

Mail-enabled Public Folders not accepting email from external users after migrating from Exchange 2003

We are in the process of trying to decommission our Exchange 2003 server, all of the replicas have been moved to the Exchange 2010 SP3 servers. However, each time we dismount the public folder store on the 2003 server (just to see what won't work) nobody
from outside the company can send mail to the mail-enabled public folders (we use these to communicate with vendors and customers).....they sit in the 2003 mail queue until I remount the store.
I have mail disabled them on the 2010 PF server, waited a few hours and then mail enabled them again. Same issue. Interesting to note is that when the PF store on the 2003 server is dismounted people inside
the company can still send to the mail-enabled PFs (which is good). I am stumped.
HDL

Hi,
There is similar issue in the below post.
https://social.technet.microsoft.com/Forums/exchange/en-US/20dc0f53-41c2-4275-a391-fd9b0907a7e1/after-move-all-replicas-to-exchange-2010-mail-enable-public-folder-stops-receiving-external-emails?forum=exchangesvrdeploylegacy

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)

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

Shared mailbox access from exchange 2003 to 2010 users

We'd successfully migrated from exchange 2003 to 2010. still some of the users are yet to be migrate.
The issue is only in MAC (Apple) Migrated users was unable to access the shared folder residing in 2003 environment.
but the migrated 2010 users are able to access the shared folders in the windows environment.
Any one can assist or suggest this issue.
Awaiting for ur reply.
Regards
kart26

Hi Kart26,
Please install certificate in your MAC App Client.
Thanks
Mavis
Mavis Huang
TechNet Community Support

Migrate from Server 2003 (no Exchange, single server) to SBS 2011

Are there any Technets or other Microsoft documentation on migrating from Server 2003 (no Exchange, single server) to SBS 2011? I understand it is possible, but I would like confirmation and some documentation before purchasing the appropriate hardware
and licenses.
Thanks,
Doug
Doug Orr

Hi Doug,
In general, the migration is the similar with migrating process from SBS 2003. In addition, also have main
difference.
“The main difference is that you don’t have to remove the source and that you have to follow the migration
instructions as the SBS migration wizard will not launch.”
You can get above description from following similar thread. Please refer to.
Migrate from Windows Server Standard 2003 (not SBS) to SBS 2011
http://social.technet.microsoft.com/Forums/en-US/68790e41-b833-4e81-8200-63852ab9e196/migrate-from-windows-server-standard-2003-not-sbs-to-sbs-2011?forum=smallbusinessserver
Meanwhile, please refer to the following article. It may be helpful.
Step By Step Guide To Migrating To SBS 2011
http://www.techieshelp.com/step-by-step-guide-to-migrating-to-sbs-2011/
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft
does not guarantee the accuracy of this information.
However, as Robert suggests, would you please confirm specific version of SBS? It may help us to understand
clearly and provide correct information.
Hope this helps.
Best regards,
Justin Gu

Cross Forest Migration from Exchange 2007 to Exchange 2013

Hi
Could anybody advice me the steps also the pros and cons for below mentioned environment if we are going for the cross forest migration.
Source
Domain - test.local
Active Directory - Windows 2003
Exchange Server - 2007
Target
Domain - test.net
Active Directory - Windows 2012
Exchange Server - 2013
Also if it is possible ,
How could I remove the source environment including the exchange servers. after the migration ?
Regards
Muralee

Hi Oliver ,
Please suggest us.
In my environment we are in a plan to migrate from exchange 2007 to exchange 2013 (cross forest migration).
Source : Exchange 2007 with sp3 ru 10
Target : Exchange 2013 with cu2 ( new environment yet to be created).
Trust : Forest trust in place (two way )
Domain and forest functional level : 2003 in both target and source
Migration Steps :
Step1 :
We are in a plan to execute 'preparemoverequest.ps1' first in the target forest ,so that we will get the disable MEU
in the target forest.
Step2:
Then we are going to use ADMT to migrate users SID'S and password .
Step3:
Then we are going to move the mailboxes with New-moverequest
Please have a look in to our steps and suggest us ,whether we are going to proceed the migration in a right way or not
.Is anything needs to be changed please intimate me .
Thanks
S.Nithyanandham
Hey there,
Sorry for taking a little while to get back to you, i've been busy working on Hosted Lync deployments!
Use ADMT first, then when using preparemoverequest.ps1 script using the -uselocalobject cmdlet. This will then tie it up to the ADMT migrated account.
More info in this thread here: http://social.technet.microsoft.com/Forums/windowsserver/en-US/2916e931-36a0-4ba4-8c04-196dbe792b44/preparemoverequestps1-and-admt?forum=winserverMigration
Oliver
Oliver Moazzezi | Exchange MVP, MCSA:M, MCITP:Exchange 2010,MCITP:Exchange 2013, BA (Hons) Anim | http://www.exchange2010.com | http://www.cobweb.com | http://twitter.com/OliverMoazzezi

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.

Accidently removed a mailbox on the SBS 2008 server during the migration from SBS 2003

I accidently removed a legacy mailbox from the SBS 2008 server while still doing the migration from SBS 2003. I meant to click on the Move Mailbox like the instructions said but clicked on the Remove option, then clicked the 'X' to close the box since
I figured that would cancel what I did however it removed the mailbox from the SBS 2008 list.
Please tell me that I can get it back. It still shows up in the old SBS Exchange System Manager but now when an email is sent, it sends back a no delivery message. It's like the account doesn't exist any more.
Can it be recovered and if so, how?
thanks,
Jeff

Hi Jeff,
Would you please let us know current situation of this issue? Just check if above suggestions can help you.
If any update, please feel free to let us know.
In addition, please also refer to following article and thread, and then check if can help you.
How
to use a Recovery Storage Group in SBS 2008
How
to recover a deleted user and mailbox on SBS 2008
Hope this helps.
Best regards,
Justin Gu

Migrating from Exchange 2003

Similar Messages

Maybe you are looking for