Scenario:

suddnely i noticed some room mailboxes are not available in exchange server, but im sure they were there nearly a month before.

I used "search-adminauditlog" PS cmdlet with various parameters such as "set-mailbox","remove-mailbox","disable-mailbox" but no where i can find the audit logs specific to those lost mailboxes.

Search-AdminAuditLog -Cmdlets disable-mailbox -StartDate 08/01/2014 -EndDate 11/04/2014 >mailboxaudit_disablemailbox.txt

I beleive the AD account of those room mailboxes were deleted by someone which has indeed deleted the mailboxes from exchange server too, this is the reason why I cant see any audit report for those mailbox's in while im running the above PS cmdlets.

anyone have experienced the same issue and anymore ideas to identify what went wrong with those mailboxes? 

This one is driving me absolutely crazy,  hours and hours spent on this with no luck.  This is 2007/2013 env.  The issue is, if I move a mailbox to 2007 then 2013 OWA is fine, then if I move the mailbox back to 2007 I can't access the mailbox via OWA when going through a 2013 CAS server.  yes I've read the posts about permissions inheritance etc.. yes I've cranked up AD and OWA logging nothing.. yes I've imported the IIS logs into log parser and I'm seeing various errors mostly 302.  Yes, I've ruled out 2007 servers, it's 2013.  If I recreate the mailbox it works then when move back and forth from 2007 to 2013 problem re-appears.  Yes, I have dumped AD attributes and compared them with working and non working mailbox can't find anything.  Yes, I've rebooted servers.  Yes this happens with multiple mailboxes.

In fact I have this example right now makes no sense.  I have two 2013 servers, if I go through the 2013 servers CAS servers to access the mailbox using OWA that resides on the 2007 server, it works through one server and the other it doesn't with the above errors.  I'd love to hear suggestions.. I'm at the end of my rope

 

Hello,

I recently installed Exchange 2013 CAS And Mailbox server roles on single server.  The server is a VMWare instance.  The databaseis located on an ISCSi connected drive located on our SAN.  When I go to enable the Federation Trust I get this message:

The operation has been stopped.

Greetings

In Technet, I can see the Port details for Exchange 2010. But i do not find such article for Exchange 2013. 

Can somebody please let me know the Port details for Exchange 2013.

Regards

K2

---

Hi Everyone-

I'm migrating my PF from 2007 to 2013 and ran into a weird issue.  I've gone through the steps outlined in this guide twice: http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx

1st attempt: After running through all checks - the initial sync, waiting for 'AutoSuspended' failed because of too many bad items.  Read some more about the error and ended up deleting some old system public folders / public folders that it was had the error on (http://support.microsoft.com/kb/555978). I know without a doubt that the cleanup of a previous 2003-2007 migration was not completed.  I chalked it up to that.  I increased the baditemlimit to 20, and resumed the request.  Finally was able to reach autosuspend - locked down PF - and went in to finalize.  After finally restarting the legacy information store, was able to get it to attempt a final sync.  Attached below is the final error.

2nd attempt:  Wasn't sure if the PF's i deleted were sync'd and now causing issues on the 2013 system - went ahead and deleted PF mailbox on 2013, and Migration request.  Unlocked PF's on 2007 - everything came back fine.  Started over again, re-created PF mailbox and started new migration request.  Got to 'autosuspended' almost immediately.  Moved forward as normal, ultimately hitting the same error as attempt 1.

I've deleted all existence of the 'exchangeV1' entities out of the system PF.

Please advise

Thank you!

I've changed the names of my servers - Exchange 2007 = LEGACY2007.DOMAIN.NAME

  Exchange 2013 = NEW2013.DOMAIN.NAME

RunspaceId                       : f1b4ac3d-8a05-4abe-9bd3-87144947df9d
Name                             : PublicFolderMigration
Status                           : Failed
StatusDetail                     : FailedOther
SyncStage                        : IncrementalSync
Flags                            : IntraOrg, Pull, Suspend
RequestStyle                     : IntraOrg
Direction                        : Pull
Protect                          : False
Priority                         : Normal
Suspend                          : True
SourceVersion                    : Version 8.3 (Build 327.0)
SourceDatabase                   : LEGACY2007\Public Folders Storage Group\Public Folders
SourceServer                     : LEGACY2007.DOMAIN.NAME
BatchName                        : 
OutlookAnywhereHostName          : 
RemoteCredentialUsername         : 
AuthenticationMethod             : Basic
RemoteMailboxLegacyDN            : 
RemoteMailboxServerLegacyDN      : 
BadItemLimit                     : 5
BadItemsEncountered              : 303
LargeItemLimit                   : 0
LargeItemsEncountered            : 0
FolderToMailboxMap               : {\}
QueuedTimestamp                  : 10/22/2014 2:27:36 PM
StartTimestamp                   : 10/22/2014 2:27:43 PM
LastUpdateTimestamp              : 10/22/2014 2:35:18 PM
InitialSeedingCompletedTimestamp : 10/22/2014 2:27:46 PM
FinalSyncTimestamp               : 
CompletionTimestamp              : 
SuspendedTimestamp               : 
OverallDuration                  : 00:08:27
TotalFinalizationDuration        : 
TotalDataReplicationWaitDuration : 
TotalSuspendedDuration           : 00:04:09
TotalFailedDuration              : 00:00:46
TotalQueuedDuration              : 00:00:03
TotalInProgressDuration          : 00:00:22
TotalStalledDueToCIDuration      : 
TotalStalledDueToHADuration      : 
TotalStalledDueToReadThrottle    : 
TotalStalledDueToWriteThrottle   : 
TotalStalledDueToReadCpu         : 
TotalStalledDueToWriteCpu        : 
TotalStalledDueToReadUnknown     : 
TotalStalledDueToWriteUnknown    : 
TotalTransientFailureDuration    : 
TotalIdleDuration                : 00:00:01
MRSServerName                    : 
EstimatedTransferSize            : 0 B (0 bytes)
EstimatedTransferItemCount       : 0
BytesTransferred                 : 930.6 KB (952,985 bytes)
BytesTransferredPerMinute        : 
ItemsTransferred                 : 9
PercentComplete                  : 95
PositionInQueue                  : 
PreventCompletion                : False
FailureCode                      : -2146233088
FailureType                      : TooManyBadItemsPermanentException
FailureSide                      : 
Message                          : Error: This mailbox exceeded the maximum number of corrupted items that were 
                                   specified for this move request.
FailureTimestamp                 : 10/22/2014 2:35:17 PM
IsValid                          : True
ValidationMessage                : 
OrganizationId                   : 
RequestGuid                      : 5d826d67-05d5-49d4-9453-58bc40f69c5a
RequestQueue                     : DB01
ExchangeGuid                     : d08583f4-6475-45da-ac01-059dee1cd29e
Identity                         : 830182b4-863f-4214-b0e2-f11fbc7c1158\5d826d67-05d5-49d4-9453-58bc40f69c5a
DiagnosticInfo                   : 
Report                           : 10/22/2014 2:27:36 PM [NEW2013] 'DOMAIN.NAME/.Privileged Accounts/Server 
                                   Support/admin, asimpson' created request.
                                   10/22/2014 2:27:41 PM [NEW2013] The Microsoft Exchange Mailbox Replication 
                                   service 'NEW2013.DOMAIN.NAME' (15.0.913.7 caps:0FFF) is examining the request.
                                   10/22/2014 2:27:41 PM [NEW2013] Connected to target mailbox 
                                   'd08583f4-6475-45da-ac01-059dee1cd29e', database 'DB01', Mailbox server 
                                   'NEW2013.DOMAIN.NAME' Version 15.0 (Build 913.0), proxy server 
                                   'NEW2013.DOMAIN.NAME' 15.0.913.7 caps:FFFFCB07FFFF.
                                   10/22/2014 2:27:41 PM [NEW2013] Connected to source mailbox '', database 
                                   'LEGACY2007\Public Folders Storage Group\Public Folders', Mailbox server 
                                   'LEGACY2007.DOMAIN.NAME' Version 8.3 (Build 327.0).
                                   10/22/2014 2:27:41 PM [NEW2013] Request processing started.
                                   10/22/2014 2:27:41 PM [NEW2013] Cleared sync state for request 
                                   00000000-0000-0000-0000-000000000000 due to 'CleanupOrphanedMailbox'.
                                   10/22/2014 2:27:43 PM [NEW2013] Stage: CreatingFolderHierarchy. Percent 
                                   complete: 10.
                                   10/22/2014 2:27:43 PM [NEW2013] Initializing folder hierarchy from mailbox 
                                   '': 38 folders total.
                                   10/22/2014 2:27:43 PM [NEW2013] Folder creation progress: 0 folders created 
                                   in mailbox 'd08583f4-6475-45da-ac01-059dee1cd29e'.
                                   10/22/2014 2:27:44 PM [NEW2013] Folder hierarchy initialized for mailbox 
                                   'd08583f4-6475-45da-ac01-059dee1cd29e': 6 folders created.
                                   10/22/2014 2:27:44 PM [NEW2013] Stage: CreatingInitialSyncCheckpoint. Percent 
                                   complete: 15.
                                   10/22/2014 2:27:44 PM [NEW2013] Initial sync checkpoint progress: 0/38 
                                   folders processed. Currently processing mailbox 
                                   'd08583f4-6475-45da-ac01-059dee1cd29e'.
                                   10/22/2014 2:27:44 PM [NEW2013] Initial sync checkpoint completed: 6 folders 
                                   processed.
                                   10/22/2014 2:27:44 PM [NEW2013] Stage: LoadingMessages. Percent complete: 20.
                                   10/22/2014 2:27:44 PM [NEW2013] Messages have been enumerated successfully. 9 
                                   items loaded. Total size: 818.8 KB (838,451 bytes).
                                   10/22/2014 2:27:44 PM [NEW2013] Stage: CopyingMessages. Percent complete: 25.
                                   10/22/2014 2:27:44 PM [NEW2013] Copy progress: 0/9 messages, 0 B (0 
                                   bytes)/818.8 KB (838,451 bytes), 5/38 folders completed.
                                   10/22/2014 2:27:45 PM [NEW2013] Copying messages is complete. Copying rules 
                                   and security descriptors.
                                   10/22/2014 2:27:46 PM [NEW2013] A corrupted item was encountered: Folder ACL 
                                   "schema-root"
                                   10/22/2014 2:27:46 PM [NEW2013] A corrupted item was encountered: Folder ACL 
                                   "microsoft"
                                   10/22/2014 2:27:46 PM [NEW2013] A corrupted item was encountered: Folder ACL 
                                   "Default"
                                   10/22/2014 2:27:46 PM [NEW2013] Initial seeding completed, 9 items copied, 
                                   total size 818.8 KB (838,451 bytes).
                                   10/22/2014 2:27:46 PM [NEW2013] Stage: IncrementalSync. Percent complete: 95.
                                   10/22/2014 2:27:46 PM [NEW2013] Folder hierarchy changes reported in source 
                                   '': 0 changed folders, 0 deleted folders.
                                   10/22/2014 2:27:47 PM [NEW2013] Incremental Sync 
                                   'd08583f4-6475-45da-ac01-059dee1cd29e' completed: 0 hierarchy updates, 0 content 
                                   changes.
                                   10/22/2014 2:27:47 PM [NEW2013] Stage: IncrementalSync. Percent complete: 95.
                                   10/22/2014 2:27:47 PM [NEW2013] Automatically suspending job.
                                   10/22/2014 2:31:32 PM [NEW2013] 'DOMAIN.NAME/.Privileged Accounts/Server 
                                   Support/admin, asimpson' modified request.
                                   10/22/2014 2:31:55 PM [NEW2013] 'DOMAIN.NAME/.Privileged Accounts/Server 
                                   Support/admin, asimpson' resumed request.
                                   10/22/2014 2:31:56 PM [NEW2013] Job resumed with status 'InProgress'.
                                   10/22/2014 2:31:56 PM [NEW2013] Relinquishing job.
                                   10/22/2014 2:35:03 PM [NEW2013] The Microsoft Exchange Mailbox Replication 
                                   service 'NEW2013.DOMAIN.NAME' (15.0.913.7 caps:0FFF) is examining the request.
                                   10/22/2014 2:35:03 PM [NEW2013] Connected to target mailbox 
                                   'd08583f4-6475-45da-ac01-059dee1cd29e', database 'DB01', Mailbox server 
                                   'NEW2013.DOMAIN.NAME' Version 15.0 (Build 913.0), proxy server 
                                   'NEW2013.DOMAIN.NAME' 15.0.913.7 caps:FFFFCB07FFFF.
                                   10/22/2014 2:35:03 PM [NEW2013] Connected to source mailbox '', database 
                                   'LEGACY2007\Public Folders Storage Group\Public Folders', Mailbox server 
                                   'LEGACY2007.DOMAIN.NAME' Version 8.3 (Build 327.0).
                                   10/22/2014 2:35:03 PM [NEW2013] Request processing continued, stage 
                                   IncrementalSync.
                                   10/22/2014 2:35:03 PM [NEW2013] Folder hierarchy changes reported in source 
                                   '': 5 changed folders, 0 deleted folders.
                                   10/22/2014 2:35:03 PM [NEW2013] Content changes reported for mailbox '': 
                                   Batch 1, New 401, Changed 0, Deleted 0, Read 0, Unread 0, Total 401. 
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"abstract_d.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"account_ct.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"adminfolderdescription_ex.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"alldayevent_c.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"appointment_cc.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"approved_h.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"Author_o.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"baseschema_s.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"bcc_h.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"bcc_m.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"bday_ct.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"billinginformation_ct.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"binding_frm.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"browser_frm.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"businesshomepage_ct.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"busystatus_c.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"Bytes_o.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"calendarfolder_cc.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"calendarmessage_cc.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"callbackphone_ct.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"Category_o.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"cc_h.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"cc_m.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"Characters_o.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"childcount_d.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"childrensnames_ct.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"closedexpectedcontentclasses_s.xml", 
                                   Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"cmd_frm.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"cn_ct.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"codebase_s.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"comclassid_s.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"Comments_o.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"comment_d.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"comment_h.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"companies_ex.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"Company_o.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"comprogid_s.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"computernetworkname_ct.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"conflict_excc.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"contactfolder_cc.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"contacturl_c.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"contact_c.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"content-base_h.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"content-class_h.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"content-description_h.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"content-disposition-type_m.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"content-disposition_h.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"content-id_h.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"content-language_h.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"content-location_h.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"content-media-type_m.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                     

Hello to every member of the TechNet community!

I have here a little question to which some of you may be able to answer. I have this project to migrate our actual server (SBS 2003 including Exchange 2003) to a brand new machine with Windows Server Essentials 2012 R2. I've read quite a few tutorials but still, I have a doubt in mind: each time that someone talks about the mailing options in Server 2012, they offer two choices: either you migrate to Office 365 or you can have another server on-prem to run your Exchange.

My question is: is it possible to install and run Exchange 2013 on Server 2012 R2 Essentials and reunite my every needs into only 1 physical server? I've read tutorials in which they explain that it might be possible if you install additionnal roles and every prerequisite, but I would like some expert advices on the subject. Both 365 and on-prem 2nd server are not options I could deal with, so I hope that it's remotely possible.

Awaiting your answers with great hope!

Thanks a lot for the time you'll put into this and best regards,

Alex

P.S:  I mean to use the Code2 software to ease the mailboxes migration from Exchange 2003 to 2013. Does anyone have experimented this piece of software? I would rather use that than do the double "hop" from 2003->2010->2013. Would it be a good alternative solution? Thanks again!

Hi all.

I've been working on setting up Exchange 2013 in our Exchange 2007 environment.  I've managed to install it, configure it, move a handful of mailboxes, and fix several issues (2013 users being asked to login, free/busy maximum settings mismatch, Autodiscover not really updating the settings in Outlook clients...).  However, I'm stuck on getting Exchange 2013 users to access Exchange 2007 public folders.  Because the new server is very much in a development stage, I can't migrate the public folders over and won't until the mailboxes are thoroughly tested and fully migrated.

According to the public folders FAQ at http://technet.microsoft.com/en-us/library/jj150538(v=exchg.150).aspx, it's both possible and impossible to get new users to access legacy folders.

From "Considerations:"

Exchange 2013 no longer supports public folder databases. Therefore, there’s no coexistence with legacy public folders. As a result, Exchange 2013 is unable to read from the hierarchy stored in a public folder database on Exchange 2010 or Exchange 2007 servers.

From "Migrate public folders from previous versions:"

...However, user mailboxes on Exchange 2013 servers or Exchange Online can connect to legacy public folders. Exchange 2013 public folders and legacy public folders can’t exist in your Exchange organization simultaneously....

I did originally start to build the master hierarchy in 2013 before finding this page, but I have since deleted the hierarchy from Exchange and from AD via ADSIEdit.

When a 2013 user tries to access a 2007 public folder, they are met with "Cannot expand the folder. Microsoft Exchange is not available. Either there are network problems of the Exchange server is down for maintenance. (<correct info about the the legacy 2007 server's DN>)"

I've reviewed the RPC logs from the new server and am seeing what looks like a proper redirect command to the Outlook client.  But the Outlook client can't connect to the public folders.

I've tested public folders in OWA and they don't work there.  I've verified that the services are started on both the new and old servers.  And I've used the Outlook Connection Status tool to observe how Outlook seems stuck in a perpetual "connecting" state to the old mail server, even when I'm not trying to access a public folder.

So my question then, is using Exchange 2013 to access Exchange 2007 public folders actually possible or not?  If so, what else can I check to find out why I can't open legacy public folders?  We need to access some of the shared folders for collaboration, and I'm trying to avoid moving the upgraded users back into Exchange 2007.  This seems to be about the last major problem I have before I can start migrating all of the other users.

Thanks!

Alan

PS - Microsoft, please update your Exchange 2013 Public Folders FAQ to clarify if this is possible or not.  You state both in two adjacent sections.

 

Hello,

What exactly is required for the virtual directory url setup for Exchange 2010 coexisting with Exchange 2013? I have been searching online a lot preparing for my Exchange 2013 deployment and can't see to find a clear answer. The information I have come across from TechNet and other sources is all over the place with some stuff saying the external url needs to be empty while others say it should match Exchange 2013's setup. Others say the internal url should be empty while only the external should be populated. And I have even seen others say nothing on Exchange 2010 has to be touched and that Exchange 2013 will figure proxying out on its own once I configure the new url's on it.

So what is supposed to be setup for the ExternalUrl and InternalURL to in Excahnge 2010 for coexistence with 2013? Currently my existing Exchange 2010 is internet facing with the plan of moving that to Exchange 2013 once that goes in as per Microsoft directions on implementing coexistence.

Hi all,

I am facing a very frustrating situation as in my Exchange CAS's Microsoft Exchange Service Host not able to start, keep restarting.

Let me share what is the whole story. I installed Exchange 2013 SP1 CU6 on a Server 2012 R2. Fully patch.

Configured DAG, load balance on CAS, installed DigiCert and applied services.

And then found out that the performance is very bad, as in running a simple PowerShell can take up to 30 minutes or more, same as ECP.

So I highly suspect the culprit was CU6, where previous installation performance I done before was not that bad.

I proceed to uninstall one of the CAS in my environment, and it was successful, until I reinstall a Exchange 2013 SP1 (no CU),

it prompt error at the Step 8. I can only click on "Exit"  *The error from the setup log I posted below*

Now I cannot uninstall the Exchange, and the service, Microsoft Exchange Service Host is keep restarting on its own.

Event Viewer I got these error,

1. Application MSExchange Common Error 4999

Watson report about to be sent for process id: 7524, with parameters: E12IIS, c-RTL-AMD64, 15.00.0847.032, M.Exchange.ServiceHost, M.Exchange.Management, M.E.M.IISConfigurationUtilities.UpdateAuthenticationModules, System.TypeLoadException, ccc1, 15.00.0995.028.

ErrorReportingEnabled: True

2. System Service Control Manager Error 7031

The Microsoft Exchange Service Host service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 5000 milliseconds: Restart the service.

How can I fix this service restart issue?

Thanks and Regards,

Low

Setup Log

[10/30/2014 02:25:20.0916] [1] The following 2 error(s) occurred during task execution:
[10/30/2014 02:25:20.0916] [1] 0.  ErrorRecord: The term 'C:\Program Files\Microsoft\Exchange Server\V15\\Scripts\ConfigureNetworkProtocolParameters.ps1' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
[10/30/2014 02:25:20.0916] [1] 0.  ErrorRecord: System.Management.Automation.CommandNotFoundException: The term 'C:\Program Files\Microsoft\Exchange Server\V15\\Scripts\ConfigureNetworkProtocolParameters.ps1' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
   at System.Management.Automation.CommandDiscovery.LookupCommandInfo(String commandName, CommandTypes commandTypes, SearchResolutionOptions searchResolutionOptions, CommandOrigin commandOrigin, ExecutionContext context)
   at System.Management.Automation.CommandDiscovery.LookupCommandProcessor(String commandName, CommandOrigin commandOrigin, Nullable`1 useLocalScope)
   at System.Management.Automation.ExecutionContext.CreateCommand(String command, Boolean dotSource)
   at System.Management.Automation.PipelineOps.AddCommand(PipelineProcessor pipe, CommandParameterInternal[] commandElements, CommandBaseAst commandBaseAst, CommandRedirection[] redirections, ExecutionContext context)
   at System.Management.Automation.PipelineOps.InvokePipeline(Object input, Boolean ignoreInput, CommandParameterInternal[][] pipeElements, CommandBaseAst[] pipeElementAsts, CommandRedirection[][] commandRedirections, FunctionContext funcContext)
   at System.Management.Automation.Interpreter.ActionCallInstruction`6.Run(InterpretedFrame frame)
   at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
[10/30/2014 02:25:20.0916] [1] [ERROR] The following error was generated when "$error.Clear();
          . "$RoleInstallPath\Scripts\ConfigureNetworkProtocolParameters.ps1";
          Enable-ExtendedTcpPortRange
        " was run: "The term 'C:\Program Files\Microsoft\Exchange Server\V15\\Scripts\ConfigureNetworkProtocolParameters.ps1' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.".
[10/30/2014 02:25:20.0916] [1] [ERROR] The term 'C:\Program Files\Microsoft\Exchange Server\V15\\Scripts\ConfigureNetworkProtocolParameters.ps1' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
[10/30/2014 02:25:20.0916] [1] 1.  ErrorRecord: The term 'Enable-ExtendedTcpPortRange' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
[10/30/2014 02:25:20.0916] [1] 1.  ErrorRecord: System.Management.Automation.CommandNotFoundException: The term 'Enable-ExtendedTcpPortRange' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
   at System.Management.Automation.CommandDiscovery.LookupCommandInfo(String commandName, CommandTypes commandTypes, SearchResolutionOptions searchResolutionOptions, CommandOrigin commandOrigin, ExecutionContext context)
   at System.Management.Automation.CommandDiscovery.LookupCommandProcessor(String commandName, CommandOrigin commandOrigin, Nullable`1 useLocalScope)
   at System.Management.Automation.ExecutionContext.CreateCommand(String command, Boolean dotSource)
   at System.Management.Automation.PipelineOps.AddCommand(PipelineProcessor pipe, CommandParameterInternal[] commandElements, CommandBaseAst commandBaseAst, CommandRedirection[] redirections, ExecutionContext context)
   at System.Management.Automation.PipelineOps.InvokePipeline(Object input, Boolean ignoreInput, CommandParameterInternal[][] pipeElements, CommandBaseAst[] pipeElementAsts, CommandRedirection[][] commandRedirections, FunctionContext funcContext)
   at System.Management.Automation.Interpreter.ActionCallInstruction`6.Run(InterpretedFrame frame)
   at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
[10/30/2014 02:25:20.0916] [1] [ERROR] The following error was generated when "$error.Clear();
          . "$RoleInstallPath\Scripts\ConfigureNetworkProtocolParameters.ps1";
          Enable-ExtendedTcpPortRange
        " was run: "The term 'Enable-ExtendedTcpPortRange' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.".
[10/30/2014 02:25:20.0916] [1] [ERROR] The term 'Enable-ExtendedTcpPortRange' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
[10/30/2014 02:25:20.0916] [1] [ERROR-REFERENCE] Id=CafeComponent___60cf5d14f7cd4fdeb396508a1dae1514 Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[10/30/2014 02:25:20.0916] [1] Setup is stopping now because of one or more critical errors.
[10/30/2014 02:25:20.0916] [1] Finished executing component tasks.
[10/30/2014 02:25:20.0932] [1] Ending processing Install-CafeRole
[10/30/2014 02:25:57.0224] [0] CurrentResult setupbase.maincore:396: 0
[10/30/2014 02:25:57.0224] [0] End of Setup

Hello,

I finally(!!!!) successfully installed Exchange server 2013 on a test server running win server 2012 r2. My problem now is that when I try to create mailboxes with OWA, I get the message "https://localhost:444/owa" followed by "Bad Request". Now I assume this is the admin website to administer exchange server.  Why am I getting this message?  I have checked my firewall settings and I am listening for requests on port 444.  

Any suggestions would help.  This is a trial version of Exchange 2013 and we are not going to spend days trying to get this software running to decide if we will purchase this product. We also want to create test email accounts.  There is no overt tool or application under the Exchange Application header that stands out to accomplish this.  What do I do?  Any help is appreciated.

Thanks

John G.

---

John Grace

Hello Guys

I have a mailflow issue, hoping someone can help with detail description, below is the setup

Exchange server 2010 SP3 with all roles in one server

Exchange server 2013 SP1 with CU6 with all roles in one server - this server is in a different subnet to the 2010 server. I am able to see exchange 2010 databases and mailboxes from Exchange 2013. For testing purposes, I have moved 3 mailbox from 2010 to 2013. These 3 mailbox, is able to send and receive email from Internet but to each other via OWA or Outlook. These 3 mailbox also not able to send to receive email from any mailbox that is still in 2010 server via OWA or Outlook. I am not planning the whole server cutover in a go and planning to do state by stage mailbox migration so I need mailflow working properly. When I send an email from one of the migrated mailbox that is in 2013 server, I can see that the email leaves the mailbox outbox and sits in the queue ..

Can someone please provide detailed solution what needs to be configured?

---

MCITP, MCSA, MCSE,VCP - Consultant, Solution Design, Implementation

Has anybody got this product to work yet on a 2012R2 DC server, if I install Client Access Role at the same time on the same machine or install it afterwards on the same machine, I get Access denied when I run Exchange Management Shell, if I do not install Client Access Role I can run the Exchange Management Shell but I am not sure what to do with it or how to configure Exchange with it, I normally use the GUI for administering Exchange, the GUI administrator program or EAC as it is now called is not installed without installing the Client Access Mode.

How can I configure this program without the CAR installed.

This is not an inexpensive program, my customer is doing his nut and I can not get paid until it is installed and working.

I am running a Microsoft Exchange 2013 Server on a privately owned and run Windows Server 2012 R2 system that has IIS8.

Currently we have 4 users

administrator@
sales@
stuart@
arun.mathew@

We need to create some generic mailboxes such as enquiries@ which both stuart@ & arun.mathew@ need to be able to receive messages sent to that mailbox and send out messages as that mailbox regardless of whether accessing from outlook 2013 on desktop, outlook web access or via their ipads/iphonesIf i set it up under the recipients tab then only the one person can access it as you cant forward messages from one mailbox automatically to more than 1 recipient via mailflow

if setting up as a shared mailbox it works okay in outlook 2013 on the desktop but you cant see those messages in your outlook web access and cant see them on your ipad/iphone because ios says your duplicating an existing email account.

so i need to know what is the best way of setting this up and how to do it.

Stuart

Dear all,

I am in this situation

Domain A (AD and Exchange 2003)

Domain B (AD and Exchange 2010) two domain is in trust

must I migrate the server exchange with the domain A to domain B, the mailbox are already going on the Exchange DB of domain B, to make the migration of the server I can use simply the migration computer (ADMT) , or it is necessary to do differently?

the migration is necessary to make the backups of the old mailbox from Exchange DB 2003.

thank you very much

I'm in the process of migrating user mailboxes from Exchange 2007 to Exchange 2013

It seems that many of the users (not all) are having problems seeing free/busy once they have been migrated.  If we remove the Outlook profile and recreate it, all is good.  Problem is that this is happening to more and more people.  Everyone is on Outlook 2010

Test-OutlookWebServices -ClientAccessServer Ex2013 -identity MyName -MailboxCredential $cred    Results in:

 Autodiscover: Outlook Provider Failure
 Exchange Web Services          Failure
 Availability Service           Skipped
 Offline Address Book           Failure

The same if I run that command against the Exchange 2007 server.

What am I doing wrong?

Hello all

We currently have a single Exchange 2013 CU6 server with a Hybrid configuration. The goal is to move everything to O365 and then de-commission the on-prem Exchange server.

Some users have been moved to O365, and some users are still on-prem. Public folders have been migrated about one year ago from Exchange 2010 to Exchange 2013, and are still on-prem.

I have been looking for several hours for guidance on how to move the (modern) public folders from our on-prem Exchange 2013 to O365, but all I find are detailed articles that speak about legacy PB (aka Exchange 2007/2010). This is not what I am looking for, and some stuff (like the proxy mailbox) are probably not needed at all, but it seems hard to figure out. 

What I have done so far:

• Moved the PF-Hierarchy and PF-Mailbox1 and PF-Mailbox2 accounts into an OU that get's synchronized with O365 (via DirSync) - and verified that these three accounts are present in O365.
• Checked that the Exchange org still points to the local PB: Get-OrganizationConfig | fl PublicFoldersEnabled -> Shows Local

Does anyone have any advice on how to proceed?

Thanks for reading
/Maurice

We currently have a certificate from Thwate with a single namespace    "webmail.company.com"

I would like to get a new certificate from Thwate with the following namepaces defined.

webmail.company.com

legacy.company.com

autodiscover.company.com

My peers have said that this will require revoking the current certificate, and issuing a new one.  We will have to update all 2007 servers and the ISA server with the new cert immediately.

I was not aware we would have to immediately update any the current 2007 servers, does MS have any documentation on this?

My environment we have an exchange 2007. We installed 2010, planning to migrate to 2010. We pointed our external namespace to the 2010CAS servers and was just about to migrate to 2010 when it was decided that we would go to Exchange 2013 instead. We installed Exchange 2013 and then pointed our external namespace to the 2013 CAS. We never migrated a mailbox to 2010. Now that we have started moving mailboxes to 2013 we decided to remove the Exchange 2010 servers. I read that any system/arbitration mailboxes on 2010 had to be moved to 2013 before uninstalling and removing the servers. I ran the command get-mailbox -arbitration and there were 3 mailboxes on the 2010 sever that I moved. I removed the 2010 exch server and now I am getting the following errors when I open the 2007 EMC.

--------------------------------------------------------
Microsoft Exchange Warning
--------------------------------------------------------
Warnings

get-recipient
Completed

Warning:
Object domain.com/Users/SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9} has been corrupted and it is in an inconsistent state. The following validation errors have occurred:

Warning:
The value of property 'RecipientTypeDetails', 8388608, is not defined in the Enum type 'RecipientTypeDetails'.

Warning:
Object domain.com/Users/SystemMailbox{1f05a927-ac20-4215-bc7c-4f1618438874} has been corrupted and it is in an inconsistent state. The following validation errors have occurred:

Warning:
The value of property 'RecipientTypeDetails', 8388608, is not defined in the Enum type 'RecipientTypeDetails'.

Warning:
Object domain.com/Users/FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 has been corrupted and it is in an inconsistent state. The following validation errors have occurred:

Warning:
The value of property 'RecipientTypeDetails', 8388608, is not defined in the Enum type 'RecipientTypeDetails'.

When I run the get-mailbox -arbitration on the 2013 server I get the following mailboxes listed( this is the short version). with no errors. Is there a problem that needs to be resolved.

WindowsEmailAddress

MSExchApproval1f05a927-3be2-4fb9-aa03-b59fe3b56f4c@domain.com

MsExchDiscoverye0dc1c29-89c3-4034-b678-e6c29d823ed9@domain.com

FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042@domain.com

SystemMailboxbb558c35-97f1-4cb9-8ff7-d53741dc928c@domain.com

Migration.8f3e7716-2011-43e4-96b1-aba62d229136@domain.com

Hello,

We are in process of migrating SBS 08 to WS 2012. SBS had disabled Exchange 2007 so we have almost fresh Exchange 2013 install. SBS 08 is still CA in domain and we generated certificate for Exchange from it.

Domain name is .local in internal network.

Certificate has internal and external name in itself. Exchange is not yet visible on its external adress, since there is now Kerio mailserver operating.

Autodiscover configuration from outlook is having problems with certificate name and it looks like it is looking for external URL instead of local.

Please any suggestions ?

Hi

I want to build a new AD domain and Exchange 2013 in this new domain in Site A. I will be setting up Outlook Anywhere and OWA.

I have users on other AD domains in different locations. These locations just have Internet with not network connectivity to Site A. I want users in these different locations to access the Exchange in Site A via Outlook Anywhere and OWA for mail services.

Can this work???

Since the users are on other AD domains, what are the implications for AutoDiscover???

---

jk