NO INCOMING POP MAIL from exchange 2003 server.-

My university uses a exchange 2003 server for mail and pop access is enabled on all professor accounts. Since a couple of weeks ago I had no problem at all with my university mail account on apple mail, although I had to use :
incoming mail server: "mail.myuniversity.edu.do"
user: "DOMAIN\username"
Password: "mypassword"
Authentication: Password
After december the 5th I'm not getting any mail at all, even thou the activity monitor says "incoming messages.... 83 of 83" but no message shows up on the inbox. I have noticed that the number keeps growing (84, 85, 86...) but still no message in my inbox.
the weird thing is that I'm able to see my university mail in my iphone using the synced account settings in Itunes. I thought it was a problem of my machine I have made a clean format and reinstall of osX 10.6 with the 10.6.2 combo update. I did not transfered files nor configuration, just copied my documents and reconfigured mail from scratch. I did not imported any message. After all that, the problem persist.
I have used Connection Doctor and everything looks ok. The Detail window shows this:
******************************** BEGIN OF LOG ********************************
CONNECTED Dec 25 20:37:28.201 [kCFStreamSocketSecurityLevelNone] -- host:mail.pucmm.edu.do -- port:110 -- socket:0x115c88b70 -- thread:0x115c74d30
CONNECTED Dec 25 20:37:28.216 [kCFStreamSocketSecurityLevelNone] -- host:mail.pucmm.edu.do -- port:25 -- socket:0x116e81d40 -- thread:0x116e6f3d0
READ Dec 25 20:37:28.648 [kCFStreamSocketSecurityLevelNone] -- host:mail.pucmm.edu.do -- port:110 -- socket:0x115c88b70 -- thread:0x115c74d30
+OK Microsoft Exchange Server 2003 POP3 server version 6.5.7638.1 (SvrMailAdm.rsta.pucmm) ready.
WROTE Dec 25 20:37:28.656 [kCFStreamSocketSecurityLevelNone] -- host:mail.pucmm.edu.do -- port:110 -- socket:0x115c88b70 -- thread:0x115c74d30
USER RSTA\sterlingjimenez
READ Dec 25 20:37:28.682 [kCFStreamSocketSecurityLevelNone] -- host:mail.pucmm.edu.do -- port:25 -- socket:0x116e81d40 -- thread:0x116e6f3d0
220 mail.pucmm.edu.do Microsoft ESMTP MAIL Service, Version: 6.0.3790.3959 ready at Fri, 25 Dec 2009 20:38:10 -0400
WROTE Dec 25 20:37:28.695 [kCFStreamSocketSecurityLevelNone] -- host:mail.pucmm.edu.do -- port:25 -- socket:0x116e81d40 -- thread:0x116e6f3d0
EHLO [10.0.1.33]
READ Dec 25 20:37:29.012 [kCFStreamSocketSecurityLevelNone] -- host:mail.pucmm.edu.do -- port:110 -- socket:0x115c88b70 -- thread:0x115c74d30
+OK
WROTE Dec 25 20:37:29.019 [kCFStreamSocketSecurityLevelNone] -- host:mail.pucmm.edu.do -- port:110 -- socket:0x115c88b70 -- thread:0x115c74d30
PASS ***********
READ Dec 25 20:37:29.030 [kCFStreamSocketSecurityLevelNone] -- host:mail.pucmm.edu.do -- port:25 -- socket:0x116e81d40 -- thread:0x116e6f3d0
250-mail.pucmm.edu.do Hello [200.88.1.167]
250-TURN
250-SIZE
250-ETRN
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-8bitmime
250-BINARYMIME
250-CHUNKING
250-VRFY
250-X-EXPS GSSAPI NTLM LOGIN
250-X-EXPS=LOGIN
250-AUTH GSSAPI NTLM LOGIN
250-AUTH=LOGIN
250-X-LINK2STATE
250-XEXCH50
250 OK
WROTE Dec 25 20:37:29.036 [kCFStreamSocketSecurityLevelNone] -- host:mail.pucmm.edu.do -- port:25 -- socket:0x116e81d40 -- thread:0x116e6f3d0
AUTH LOGIN
READ Dec 25 20:37:29.391 [kCFStreamSocketSecurityLevelNone] -- host:mail.pucmm.edu.do -- port:110 -- socket:0x115c88b70 -- thread:0x115c74d30
+OK User successfully logged on.
WROTE Dec 25 20:37:29.397 [kCFStreamSocketSecurityLevelNone] -- host:mail.pucmm.edu.do -- port:110 -- socket:0x115c88b70 -- thread:0x115c74d30
QUIT
READ Dec 25 20:37:29.436 [kCFStreamSocketSecurityLevelNone] -- host:mail.pucmm.edu.do -- port:25 -- socket:0x116e81d40 -- thread:0x116e6f3d0
334 VXNlcm5hbWU6
WROTE Dec 25 20:37:29.447 [kCFStreamSocketSecurityLevelNone] -- host:mail.pucmm.edu.do -- port:25 -- socket:0x116e81d40 -- thread:0x116e6f3d0
UlNUQVxzdGVybGluZ2ppbWVuZXo=
READ Dec 25 20:37:29.823 [kCFStreamSocketSecurityLevelNone] -- host:mail.pucmm.edu.do -- port:110 -- socket:0x115c88b70 -- thread:0x115c74d30
+OK Microsoft Exchange Server 2003 POP3 server version 6.5.7638.1 signing off.
READ Dec 25 20:37:29.927 [kCFStreamSocketSecurityLevelNone] -- host:mail.pucmm.edu.do -- port:25 -- socket:0x116e81d40 -- thread:0x116e6f3d0
334 UGFzc3dvcmQ6
WROTE Dec 25 20:37:29.954 [kCFStreamSocketSecurityLevelNone] -- host:mail.pucmm.edu.do -- port:25 -- socket:0x116e81d40 -- thread:0x116e6f3d0
READ Dec 25 20:37:30.410 [kCFStreamSocketSecurityLevelNone] -- host:mail.pucmm.edu.do -- port:25 -- socket:0x116e81d40 -- thread:0x116e6f3d0
235 2.7.0 Authentication successful.
WROTE Dec 25 20:37:30.425 [kCFStreamSocketSecurityLevelNone] -- host:mail.pucmm.edu.do -- port:25 -- socket:0x116e81d40 -- thread:0x116e6f3d0
QUIT
******************************** END OF LOG ********************************
Can Anyone HELP ?
I'm Out of ideas.
Best Regards,
Sterling Jiménez R.

Hello metalcraft,
Thanks for using Apple Support Communities.
For more information on this, take a look at:
OS X Mountain Lion: Cannot connect to Exchange server in Mail after upgrading
http://support.apple.com/kb/TS4363
If you have issues connecting to the Exchange server or don't know what server addresses to use, contact your Exchange administrator or IT administrator.
Best of luck,
Mario

Similar Messages

How to get mail from exchange 2003

can any one help i have a new mac book pro and i wont to get mail from my companey
we use microsoft exchange server 2003 help help help please

Hello metalcraft,
Thanks for using Apple Support Communities.
For more information on this, take a look at:
OS X Mountain Lion: Cannot connect to Exchange server in Mail after upgrading
http://support.apple.com/kb/TS4363
If you have issues connecting to the Exchange server or don't know what server addresses to use, contact your Exchange administrator or IT administrator.
Best of luck,
Mario

Outlook 2011 for Mac users must click send/receive to get new mail from exchange 2013 server

I recently switched our primary CAS servers over from a single exchange 2010 cas/mailbox/hub server to a couple new exchange 2013 CAS/Mailbox servers. Exchange 2013 has cu3, and is hosted on windows server 2012. Anyone who has their mailbox hosted
on one of these exchange 2013 servers has an issue where they must click the send/receive button to get new messages downloaded to their client. This is only the case for outlook 2011 for mac client. Activesync clients, mac mail, OWA, and Outlook 2010/13
all behave normally.
Where can I look or what can I check to troubleshoot this issue?

Hi,
Any good news from the Mac Forum?
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

Installing certificate for access to exchange 2003 server

My exchange server requires that a certificate be installed to enable remote access. Since the iPhone does not support disk mode like the iPod there appears to be no way to install the certificate. Are there any workarounds?
iPhone Windows XP

Whole migration from Exchange 2003 server to Exchange 2010 server has been done and applied 3rd party SSL certificate on Exchange 2010 servers also.
Hi,
According to your description, everything about exchange 2010 is ready.
Why don't you follow the mail flow as below?
Internet Emails > Ironport > Exchange 2010 (smart host) > Exchange 2003 servers
Please refer to the following article:
Move Internet Mail Flow from Exchange 2003 to Exchange 2010
Configure mail flow by using one of the methods listed below depending on the needs of your organization. This will enable Internet message flow through your Exchange 2010 Hub Transport servers.
Configure Internet Mail Flow Through Exchange Hosted Services or an External SMTP Gateway
Configure Internet Mail Flow Directly Through a Hub Transport Server
Remove the SMTP connector in Exchange 2003 that is used to handle Internet mail. Your account needs to be a member of the local administrators group and a member of a group that has had the Exchange Administrators role applied at the administrative group
level.
In Exchange System Manager, expand the Organization node, expand
Administrative Groups, expand <AdministrativeGroupName>, expand
Routing Groups, expand <RoutingGroupName>, and then select
Connector.
In the right-hand pane, right-click the connector you want to delete and select
Delete.
Click OK to confirm the deletion.
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support

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

Trying to recover a mailbox from an old Exchange 2003 server

I still have a 2003 server in my environment but all functions and mailboxes are on Exchange 2010. The only reason the 2003 server is still around is for the off chance of requiring a restoration which has now come up. I have successfully restored a
mail store to a recovery storage group but I am unable to export mailboxes from it using exmerge.
I get the following error:
[10:16:16] Copying data from mailbox 'Jacques Legare' ('LEGARE') on Server 'MAIL-SERVER' to file 'C:\TEMP\LEGARE.PST'.
[10:16:16] Error opening message store (MSEMS). Verify that the Microsoft Exchange Information Store service is running and that you have the correct permissions to log on. (0x8004011d)
[10:16:16] Errors encountered. Copy process aborted for mailbox 'Jacques Legare' ('LEGARE').
I have read many, many articles regarding the requirement for “send as” permission. I have granted send as permissions to several different domain accounts and local accounts on the Exchange server but I get the same result with all of them.
It looks like the problem may be because the mailbox no longer exists on the Exchange 2003 server.
So what do I have to do to recover this mailbox? Can I create a mailbox for this user on the 2003 server without messing up his the mailbox on the 2010 server? Instead of restoring to the recovery storage group, should I restore and overwrite the original mailbox
store? Again, will that mess up anything with the 2010 server?

0x8004011d is permission related Error.
Refer to the link below and download EXMERGE guide which has complete procedure documented.
https://gallery.technet.microsoft.com/office/Guide-to-Use-Exmerge-to-fd00af49
If the mailbox that need to be restored has to be extracted from RSG is already moved to Exchange 2010 then you will not be able to run exmerge against it.
You might have to update the attribute MsExchOrigMDB on the RSG to point to Exchange 2010 Database where the mailbox is now located.
even this information is enclosed in the EMERGE Guide.
Revert back for any queries/outcome.
Pavan Maganti ~ ( Exchange | 2003/2007/2010/E15(2013)) ~~ Please remember to click “Vote As Helpful" if it really helps and "Mark as Answer” if it answers your question, “Unmark as Answer” if a marked post does not actually answer your
question. ~~ This Information is provided is "AS IS" and confers NO Rights!!

SAP Internet Mail Gateway for MS Exchange 2003 Server

Hi,
Has anybody successfully configured the IMG to work with MS Exchange 2003?
We have our 4.6C currently configured to talk to Exchange 2000 through SXC
Note 594428 - SXC: Exchange 2003 Server is not supported
Solution
R/3 Basis Release 3.1I to 4.6D:
Use IMG 4.6D and sendmail instead of the SXC (see note 101573), or
Upgrade your SAP system to Web Application Server (WAS) 6.10 or later and then use the SMTP plugin.
We only use outbound mail from SAP and this is sent to intranet users only, we are not planning on upgrading for a at least a year and would like to avoid installing another mail server.
Note 363154 - Internet mail gateway: use other MTA than Sendmail
This note suggests that any MTA (Mail Transfer Agent) can be used so long as it can be called from the command line, Exchange is an MTA, anybody now how to do a command line call for Exchange?
I have read the documentation
http://help.sap.com/saphelp_46c/helpdata/en/0c/39c93589c5ab53e10000009b38f839/frameset.htm
Jasper

hi,
we are in the process of configuring the Internet Mail Gateway on R/3 4.6c on Unix platform.
I have created the RFC Destinations in SM59 and also checked the Test Connection and its working fine. I then did the Unix configuration and went on to the check whether the configuration was successful in SO01 by sending a sample text message to my company's mail address. but i did not recieve any mails on my Microsoft Outlook, instead the count under the errors column increased by one.
on checking the status for the sent message in SO01, its saying "No Delivery to [email protected](for reason, see long text)... but there's no long text either...
Can anyone please let me know the reasons for it and it would also be really helpful if someone can let me know whether i have missed any configuration settings.
Also, can someone send the list of parameters that are to be entered for the Unix configuration under mlsomadm mailgw.ini, so that i can verify whether i have entered the parameters correctly....
Kindly revert back at the earliest...
Thanks & Regards
Manicks

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

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

Removing the last Exchange 2003 server from an Exchange 2010 organization

We're in the process of decommissioning our last Exchange 2003 server, I have proceeded through the steps in the Microsoft guide on how to do this and have deleted both the Mailbox and Public Folder stores, removed the RUS policies for Domain and Enterprise.
All mailboxes and public folders are now homed on the new Exchange so nothing resides on the old Exchange 2003 server.
I have today inserted the Exchange 2003 media into the Exch 2003 server and chosen the remove action, but it keeps telling me;
'The component "Microsoft Exchange Messaging and Collaboration Services" cannot be assigned the action "Remove" because: - One or more users currently use a mailbox store on this server.
I checked the server by searching ADUC and also checked this KB article http://support.microsoft.com/kb/279202 and nothing shows up.
I also checked this article on someones blog but no such luck http://smtp25.blogspot.co.uk/2007/04/having-trouble-to-uninstall-exchange.html
However someone made a comment that the used an ADSIedit query (&(objectCategory=user)(msExchHomeServerName=*)) however I am unsure how to do this in ADSI.
Any advice would be gratefully received.
Thanks!

Fantastic post ... thank you so much!
I found three active directory users account using that search which never had a mailbox assigned to them. I removed the exchange attributes from each account and the uninstall proceeded
flawlessly!

Changing the Default OAB from an Exchange 2003 server to an Exchange 2010

I am in the process of decommissioning my old Exchange 2003 servers. All mailboxes have been moved over to Exchange 2010. I already have OABs and Public Folders created on the Exchange 2010 servers. Since I see the "Default Offline Address List",
which is pointing to my old Exchange 2003 server and the Default OAB is set to "True", can I just make an existing Exchange 2010 OAB the "Default OAB"? I have read that I have to perform a move on the "Default Offline Address List"
OAB. Is this required?
thanks
Noe

Configure the Exchange 2010 mailbox databases to use the Exchange 2010 OAB, and leave the Exchange 2003 databases alone. You can delete the old OAB just before taking the Exchange 2003 servers out of production. The "Default" setting
means the OAB is the one that's assigned by default when you create a new mailbox database, so yes, you should set that.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

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

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.

Exchange 2007 setup, transitioning from Exchange 2003

Hello Exchange Experts,
I just setup a Exchange 2007 within our domain, transistioning from Exchange 2003, question: When I added the mailbox role on the setup of Exchange 2007, the mailboxes appeared instantly from our Exchange 2003..the connector I'm assuming automatically connected
during the 07 setup. Is this normal? I was under the assumption to migrate mailboxes from 03 to 07 Exchange, the wizard must be ran. All active mailboxes from 03 appear. I attempted to migrate one mailbox using the wizard, error after the wizard completed,
mailbox exists. Makes sense, just not understanding how the mailboxes flowed/migrated automatically without running the migration steps. Would someone explain? You could say, this migration is very new to me.
Thanks in advance!
James

Ronny, our company had an existing license for 2007. Of courser 2010 or 2013 would have been a better transition, but 2007 is it. The server 2007 has met all the criteria for the transition, spent last moth prepping everything on 2003 and 2007. I'm just
not understanding why the mailboxes appeared upon 2007 immediately after adding the mailbox role. The management console on 07 shows the mailboxes reside on 03 exchange server. I did not go through the process/wizard to move to 07. Perhaps because
during the installation of Exchange 07 created the connector from 2003? Maybe that's my question.
Mail flow is very responsive now, just wondering for the reasons of decommissioning exchange 2003 at a later date. Exchange 2003 is functioning now as a bridgehead, working perfectly now.
Thanks for your input.
James
Thanks Ronnie for your input! Issue resolved

NO INCOMING POP MAIL from exchange 2003 server.-

Similar Messages

Maybe you are looking for