Exchange 2013 CU3 and Firefox 26.0

I upgraded Exchange 2013 to CU3 last night. I tested the mail flow and everything worked fine sending and recieving. The problem that I am having is with OWA in firefox 26.0 (currently newest version). I get weird graphical glitches when
OWA first loads. Once you click around the display stabilizes but the biggest problem is that not all of the emails are displayed in a folder. I have a folder with a bunch of system data emails that are collected throughout the day and in firefox
I can see ~20 while in IE 9 I can see them all. The inbox also has 5 emails in it but there is a scroll bar that is completely unnecessary in firefox but not IE 9. Do you have any thoughts on this? Thank you in advance.

There's no way, as there's nothing wrong with the server.
You will have to wait for the update from Firefox to get it fixed.
It's purely Browser issue As I said before.
Cheers,
Gulab Prasad,
Technology Consultant
Blog:
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.

Similar Messages

Exchange 2013 CU3 Databases only activate on one mailbox server

Hi, guys
I have two Exchange 2013 CU3 Mailbox servers installed, one DAG, 5 databases, each has one copy. I found that if I activated three databases on Mailboxserver1 or Mailboxserver2, then after a few hours, all databases will be activated on the mailbox
server which has three databases activated. All the databases can be activated on Mailboxserver1 or Mailboxserver2, and they work well. I disabled DAC mode for preventing Event 4133 and 4376. And it has the same problem if I enable DAC mode.
From the event log, I found the log when activate one database on another mailbox server, it is Event 3169:
Managed availability system failover initiated by Responder=OutlookMapiHttpDeepTestFailover Component=Outlook.
This caused the database activated on another server.
And I got the message from SCOM, like this:
Alert: Health Set unhealthy
Source: test-mbx - Outlook.Protocol
Path: test-mbx.contoso.local;test-mbx.contoso.local
Last modified by: System
Last modified time: 11/12/2013 5:15:46 AM Alert description: EMSMDB.DoRpc(Logon) step of OutlookRpcDeepTestProbe/DB-01 has failed against test-mbx.contoso.local proxying to test-mbx.contoso.local for [email protected].
Latency: 00:00:00.0320000
ActivityContext:
Outline: [30] EMSMDB.Connect(); [1][FAILED!] EMSMDB.DoRpc(Logon); Likely root cause: Momt
Details:
Error: Error returned in LogonCallResult. Error code = WrongServer (0x00000478)
Log:     Mailbox logon verification
        EMSMDB.Connect()
        Task produced output:
        - TaskStarted = 11/12/2013
5:15:25 AM
        - TaskFinished = 11/12/2013
5:15:25 AM
        - ErrorDetails =
        - RespondingRpcClientAccessServerVersion
= 15.0.712.4012
Latency = 00:00:00.0303884
        - ActivityContext =
    EMSMDB.Connect() completed successfully.
        EMSMDB.DoRpc(Logon)
        Task produced output:
        - TaskStarted = 11/12/2013
5:15:25 AM
        - TaskFinished = 11/12/2013
5:15:25 AM
        - Exception = Microsoft.Exchange.RpcClientAccess.RopExecutionException:
Error returned in LogonCallResult. Error code = WrongServer (0x00000478)
        - ErrorDetails =
        - Latency = 00:00:00.0018801
        - ActivityContext =
    EMSMDB.DoRpc(Logon) failed.
    Task produced output:
    - TaskStarted = 11/12/2013 5:15:25 AM
    - TaskFinished = 11/12/2013 5:15:25 AM
    - Exception = Microsoft.Exchange.RpcClientAccess.RopExecutionException:
Error
States of all monitors within the health set:
Note: Data may be stale. To get current data, run: Get-ServerHealth -Identity 'test-mbx' -HealthSet 'Outlook.Protocol'
State               Name
TargetResource                     HealthSet
AlertValue     ServerComponent
NotApplicable       OutlookMapiHttpDeepTestMonitor
Outlook.Protocol              Unhealthy      None
NotApplicable       OutlookRpcDeepTestMonitor
Outlook.Protocol              Healthy        None
NotApplicable       OutlookRpcSelfTestMonitor
Outlook.Protocol              Healthy        None
NotApplicable       OutlookMapiHttpSelfTestMonitor                                             Outlook.Protocol
Healthy        None
NotApplicable       PrivateWorkingSetWarning....cclienta... microsoft.exchange.rpcclientacc... Outlook.Protocol              Healthy
None
NotApplicable       PrivateWorkingSetError....rpcclienta... microsoft.exchange.rpcclientacc... Outlook.Protocol              Healthy
None
NotApplicable       ProcessProcessorTimeWarning....ienta... microsoft.exchange.rpcclientacc... Outlook.Protocol              Healthy
None
NotApplicable       ProcessProcessorTimeError....clienta... microsoft.exchange.rpcclientacc... Outlook.Protocol              Healthy
None
NotApplicable       ExchangeCrashEventError....pcclienta... microsoft.exchange.rpcclientacc... Outlook.Protocol              Healthy
None
NotApplicable       LongRunningWatsonWarning....cclienta... microsoft.exchange.rpcclientacc... Outlook.Protocol              Healthy
None
NotApplicable       LongRunningWerMgrWarning....cclienta... microsoft.exchange.rpcclientacc... Outlook.Protocol              Healthy
None
This test is a cause that mailbox databases in DAG is doing failover to another server
Log Name:      Application
Source:        MSExchangeRepl
Date:          12.11.2013 4:49:46
Event ID:      3169
Task Category: Service
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      test-mbx-2
Description:
(Active Manager) Database DB-01 was successfully moved from test-mbx.contoso.local to test-mbx-1.contoso.local. Move comment: Managed availability system failover initiated by Responder=OutlookRpcDeepTestFailover Component=Outlook.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="MSExchangeRepl" />
    <EventID Qualifiers="16388">3169</EventID>
    <Level>4</Level>
    <Task>1</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-11-12T00:49:46.000000000Z" />
    <EventRecordID>1606248</EventRecordID>
    <Channel>Application</Channel>
    <Computer>test-mbx-2.contoso.local</Computer>
    <Security />
</System>
<EventData>
    <Data>DB-01</Data>
    <Data>test-mbx.contoso.local</Data>
    <Data>test-mbx-1.contoso.local</Data>
    <Data>Managed availability system failover initiated by Responder=OutlookRpcDeepTestFailover Component=Outlook.</Data>
</EventData>
</Event>
I don't know why, anyone know what's the problem?
Thank you.
Nile Jiang- Please mark the post as answer if it answers your question.
http://www.usefulshare.com

Hi,
After deleting all the health mailboxes and restart
the Exchange Health Manager service, the health mailboxes are recreated successfullly, but when I check the outlook.protocol health, the OutlookRpcDeepTestMonitor or the OutlookMapiHttpDeepTestMonitor is still unhealthy. How can I fix it?
[PS] C:\Windows\system32> Get-ServerHealth -Identity 'MAILBOX1' -HealthSet 'Outlook.Protocol' | ft server,state,name,ale
rtvalue -AutoSize
Server state Name AlertValue
MAILBOX1 OutlookRpcDeepTestMonitor Healthy
MAILBOX1 OutlookMapiHttpDeepTestMonitor Unhealthy
MAILBOX1 OutlookRpcSelfTestMonitor Healthy
MAILBOX1 OutlookMapiHttpSelfTestMonitor Healthy
MAILBOX1 PrivateWorkingSetWarning....cclientaccess.service Healthy
MAILBOX1 PrivateWorkingSetError....rpcclientaccess.service Healthy
MAILBOX1 ProcessProcessorTimeWarning....ientaccess.service Healthy
MAILBOX1 ProcessProcessorTimeError....clientaccess.service Healthy
MAILBOX1 ExchangeCrashEventError....pcclientaccess.service Healthy
MAILBOX1 LongRunningWatsonWarning....cclientaccess.service Healthy
MAILBOX1 LongRunningWerMgrWarning....cclientaccess.service Healthy
Nile Jiang- Please mark the post as answer if it answers your question.
http://www.usefulshare.com

Exchange 2010 mailbox not able to access auto-mapped Exchange 2013 CU3 mailbox

Hi,
We are in co-existence with Exchange 2010 SP3 and Exchange 2013 CU3.
Outlook Anywhere and Autodiscover pointed towards Exchange 2013 CAS servers. Everything works fine irrespective where is mailbox is located Exchange 2010 or 2013.
When I tried to access auto-mapped mailbox from Exchange 2010 as primary mailbox accessing auto-mapped Exchange 2013 mailbox "Cannot expand the folder. The set of folders cannot be opened. Microsoft Exchange is not available. Either there are network
problems or the Exchange server is down for maintenance".
Exchange 2013 OutlookAnywhere "Externalclientauthenticationmethod" is Basic and "Internalclientauthencitcationmethod" is NTLM. Everything is setup as per the Tech-net recommendations.
Checked both these articles but still it is not working:
http://support.microsoft.com/kb/2839517
http://support.microsoft.com/kb/2834139
Please let me know if there are any other ideas.
Raman

Hi,
I recommend you refer to the following articles to troubleshoot the issue:
Troubleshooting Mailbox Auto-Mapping : Autodiscover
Details about the shared mailbox that is to be accessed will be returned to the Outlook client by the autodiscover process. This is really handy to know if you are ever in the position where you need to troubleshoot why the auto-mapping feature isn’t working
correctly
Troubleshooting Mailbox Auto-Mapping : Permissions
When you use either the Exchange Management Console or the Exchange Management Shell to grant a user with full access permission against another mailbox, permissions changes are made to allow this as you might expect. Certain Active Directory attributes
are also updated to reflect both the Active Directory account of the mailbox being accessed as well as the Active Directory account of the accessing mailbox. Specifically, you can check the contents of the msExchDelegateListLink and msExchDelegateListBL Active
Directory attributes to see these details and it is worth checking these if you have any suspicions that things aren’t working correctly.
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support

Exchange 2013 CU3 Retention Policy Not working for Calendar & Tasks

We are currently on Exchange 2013 CU3 with Online Archiving Enabled for the user
Default policy is set to move all the items in mailbox which are older than 30 days to online archive mailbox.
Calendar and Tasks Items are also getting archived alongwith other Outlook items from Inbox,Deleted Items etc
Followed Technet website and created RPT for Calendar and Tasks with retention disabled
Still DPT takes precedence and move all the items under Calendar and Task to Online Archive Mailbox

Hi Sam,
I recommend you refer to the following article, despite this for Exchange 2010, however the same applies to exhcnage 2013:
Prevent archiving of items in a default folder in Exchange 2010
To prevent the <acronym title="Default Policy Tag">DPT</acronym> from being applied to a default folder, you can create a disabled <acronym title="Retention Policy Tag">RPT</acronym> for that folder (or disable
any existing RPT for that folder). The Managed Folder Assistant, a mailbox assistant that processes mailbox items and applies retention policies, does not apply the
retention action of a disabled tag. Since the item/folder still has a tag, it's not considered untagged and the DPT isn't applied to it.
Why are items in the Notes folder still archived?
If you create a disabled <acronym title="Retention Policy Tag">RPT</acronym> for the
Notes folder, you'll see items in that folder are not deleted, but they do continue to be moved to the archive! Why does this happen? How do you prevent it?
It's important to understand that:
A retention policy can have a <acronym title="Default Policy Tag">DPT</acronym> to
archive items (using the Move to Archive retention action) and a DPT to
delete items (using the Delete and Allow Recovery or
Permanently Delete retention actions). Both apply to untagged items.
The move and delete actions are exclusive of each other. Mailbox folders and messages can have both types of tags applied - an archive tag and a delete tag. It's not an either/or proposition.
If you create a disabled RPT for the Notes folder to not delete items, the archive DPT for the mailbox would still apply and move items.
When it comes to archiving, there's only one archive policy that administrators can enforce – the <acronym title="Default Policy Tag">DPT</acronym> with 'Move to archive' action.
You can't create a <acronym title="Retention Policy Tag">RPT</acronym> with the 'Move to archive' action. This rules out using the disabled RPT approach to prevent items from being moved.
Best regards,
Niko Cheng
TechNet Community Support

Exchange 2013 CU3 - Outlook Web App LogOff

Hello All,
I have Exchange 2013 CU3 installed and i'm using TMG server for authentication. I am able to login through OWA but when i try to logoff it shows me message of "Close All your Browser Windows.." but OWA does not sign out.
On TMG, only Basic and NTLM authentication is supported. And in IIS Authentication for the OWA Virtual Directory is set to basic.
Can anyone please help me for TMG settings for exchange server 2013? Thankyou for the answers.

Hi,
Thank you for your patience and support.
I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.
Thank you for your understanding and support.
Best Regards
Quan Gu

Exchange 2013 SP1 and CUCM 9.1.2 - Exch not recognizing called extension

I think I'm almost there in getting Exchange 2013 SP1 UM working with CUCM 9.1.2...I've got two issues at the moment that I need a little help with.
1) When I dial my VM pilot (6040) from a UM enabled extension it prompts to enter an extension. When I dial the same extension and let it ring to VM, Exchange picks up and says "the person you are trying to reach does not have a valid voice mail box
on our system".
2) This just started happening this afternoon, when I dial my VM pilot (6040) exch3 picks up as thats what I have my route pattern pointing to. If I enter the extension of a mailbox on exch2, I get stuck in a endless loop.
I've followed this post as a guide but it hasn't resolved my issue.
https://supportforums.cisco.com/discussion/11914031/exchange-2013-um-and-cucm-86
My Exchange environment looks like this:
Site 1:
exch1 - CAS/Mailbox, used for mainly utility type work, journal, dedicated SMTP flows etc
exch2 - CAS/Mailbox, part DAG13
exch3 - CAS/Mailbox, part of DAG13
Site 2:
exch2dr - CAS/Mailbox, part of DAG13
exch3dr - CAS/Mailbox, part of DAG13
DAG13 is stretched between two sites, there are no users at our DR site so CUCM is pointing to Site 1 for UM. Each site has an internet facing CAS-only server for OWA/EAS etc.
Any help is greatly appreciated. I'd love to get rid of Unity.
EDIT:
I just found this event in the event logs:
The Microsoft Exchange Unified Messaging service on the Mailbox server received a diverted call with ID "d51600-3a3140c5-9b8-c1414ac@EXCH3-IPADDR" for extension "4099" on UM dial plan "CUCM" from UM IP gateway "CUCM IP",
but no UM-enabled mailbox for the corresponding extension could be found. Please check the extension and make sure that the corresponding mailbox is enabled for UM and associated with the correct UM dial plan.

9.1.2 I think it is, we upgraded to avoid the known DNS bug
I cant see how to PM you either
The crux of it was outlined below with some tweaks
http://blogs.technet.com/b/canitpro/archive/2014/04/30/step-by-step-integration-between-exchange-2013-um-and-cisco-unified-communication-manager.aspx
As we have multiple combined role servers, our trunks are set up as follows:
1. 1 x CAS Trunk - contains all CAS Servers on port 5060
2. 4 x MBX Trunks - contains Maibox Server with ports 5062-5068
On top of that, we had to Allow "Redirecting Diversion Header Delivery - Inbound (and Outbound)" on the CAS Trunk but DISABLE it on the Mailbox Trunks
Also, make sure that you are using Telephone Extension Dial plans in Exchange 2013 (Despite them being unable to be associated with a 13 Server - EX13 answers for all calls anyway)
Lastly, the MS documentation is a little strange - it says that as your last step of UM migration, you should point your Call Manager to 2013 - I don't agree with that statement, EX13 routes calls back to 2010 UM Servers perfectly fine, so treat it the same
as any other CAS based service - point to 2013, and it will handle the rest

Exchange 2013 backup and log truncation question

I have a scenario where I have 5 Exchange mailbox servers as members of a DAG, everything running fine, log truncation is working, but seems to be working differently than I am expecting it to work, as in previous versions of Exchange. I am used to the
logs being truncated immediately after the full backup completes. What is happening is that the server is retaining a weeks worth of logs. Everything older than 7 days gets truncated after a full backup completes. Is this expected behavior? I am running Exchange
2013 CU3 on Server 2012, backup software is HP Data Protector 8 running the latest updates. I am running a VSS backup. The DAG is not a lagged copy of the DB's either.

I will check the HP Data Protector setting, but I do not think that setting is valid or anything configurable.
Here is the contents of some various commands for one of my databases, all of which are configured identically, tell me if you see something set incorrectly. Hopefully I have redacted enough internal stuff:
Get-MailboxDatabaseCopyStatus
RunspaceId                            : 8467f253-8c82-4206-a002-14779e701b0e
Identity                              : DB1\EX2013-MB1
Id                                    : DB1\EX2013-MB1
Name                                  : DB1\EX2013-MB1
DatabaseName                          : DB1
Status                                : Mounted
InstanceStartTime                     : 12/10/2013 7:02:44 PM
LastStatusTransitionTime              :
MailboxServer                         : EX2013-MB1
ActiveDatabaseCopy                    : EX2013-MB1
ActiveCopy                            : True
ActivationPreference                  : 1
StatusRetrievedTime                   : 1/7/2014 12:54:19 PM
WorkerProcessId                       : 10292
ActivationSuspended                   : False
ActionInitiator                       : Unknown
ErrorMessage                          :
ErrorEventId                          :
ExtendedErrorInfo                     :
SuspendComment                        :
RequiredLogsPresent                   :
SinglePageRestore                     : 0
ContentIndexState                     : Healthy
ContentIndexErrorMessage              :
ContentIndexVersion                   : 1
ContentIndexBacklog                   : 0
ContentIndexRetryQueueSize            : 0
ContentIndexMailboxesToCrawl          :
ContentIndexSeedingPercent            :
ContentIndexSeedingSource             :
CopyQueueLength                       : 0
ReplayQueueLength                     : 0
ReplaySuspended                       : False
ResumeBlocked                         : False
ReseedBlocked                         : False
MinimumSupportedDatabaseSchemaVersion : 0.121
MaximumSupportedDatabaseSchemaVersion : 0.126
RequestedDatabaseSchemaVersion        :
LatestAvailableLogTime                :
LastCopyNotificationedLogTime         : 1/7/2014 12:38:09 PM
LastCopiedLogTime                     :
LastInspectedLogTime                  :
LastReplayedLogTime                   :
LastLogGenerated                      : 3510
LastLogCopyNotified                   : 3510
LastLogCopied                         : 0
LastLogInspected                      : 0
LastLogReplayed                       : 0
LowestLogPresent                      : 2875
LastLogInfoIsStale                    : False
LastLogInfoFromCopierTime             : 1/7/2014 12:54:19 PM
LastLogInfoFromClusterTime            : 1/7/2014 12:54:16 PM
LastLogInfoFromClusterGen             : 3510
LogsReplayedSinceInstanceStart        : 0
LogsCopiedSinceInstanceStart          : 0
LatestFullBackupTime                  : 12/9/2013 10:31:32 PM
LatestIncrementalBackupTime           :
LatestDifferentialBackupTime          :
LatestCopyBackupTime                  :
SnapshotBackup                        : True
SnapshotLatestFullBackup              : True
SnapshotLatestIncrementalBackup       :
SnapshotLatestDifferentialBackup      :
SnapshotLatestCopyBackup              :
LogReplayQueueIncreasing              : False
LogCopyQueueIncreasing                : False
ReplayLagStatus                       : Enabled:False; PlayDownReason:None; Percentage:0; Configured:00:00:00; Actual:00:00:00
DatabaseSeedStatus                    :
OutstandingDumpsterRequests           : {}
OutgoingConnections                   : {}
IncomingLogCopyingNetwork             :
SeedingNetwork                        :
DiskFreeSpacePercent                  : 99
DiskFreeSpace                         : 4.365 TB (4,798,945,292,288 bytes)
DiskTotalSpace                        : 4.366 TB (4,800,702,836,736 bytes)
ExchangeVolumeMountPoint              :
DatabaseVolumeMountPoint              : C:\Disks\DB1\
DatabaseVolumeName                    : \\?\Volume{b95c7aa2-2cd9-430e-ab75-ea4b0efba659}\
DatabasePathIsOnMountedFolder         : True
LogVolumeMountPoint                   : C:\Disks\DB1\
LogVolumeName                         : \\?\Volume{b95c7aa2-2cd9-430e-ab75-ea4b0efba659}\
LogPathIsOnMountedFolder              : True
LastDatabaseVolumeName                :
LastDatabaseVolumeNameTransitionTime :
VolumeInfoError                       :
IsValid                               : True
ObjectState                           : Unchanged
[PS] C:\Windows\system32>Get-MailboxDatabase -Identity db1 |fl
RunspaceId                                   : 8467f253-8c82-4206-a002-14779e701b0e
JournalRecipient                             :
MailboxRetention                             : 30.00:00:00
OfflineAddressBook                           : \Default Offline Address Book
OriginalDatabase                             :
PublicFolderDatabase                         : CMBS1CC\CMBS1PF\CMBS1PF
ProhibitSendReceiveQuota                     : Unlimited
ProhibitSendQuota                            : 2 GB (2,147,483,648 bytes)
RecoverableItemsQuota                        : 30 GB (32,212,254,720 bytes)
RecoverableItemsWarningQuota                 : 20 GB (21,474,836,480 bytes)
CalendarLoggingQuota                         : 6 GB (6,442,450,944 bytes)
IndexEnabled                                 : True
IsExcludedFromProvisioning                   : False
IsExcludedFromInitialProvisioning            : False
IsSuspendedFromProvisioning                  : False
IsExcludedFromProvisioningBySpaceMonitoring : False
DumpsterStatistics                           :
DumpsterServersNotAvailable                  :
ReplicationType                              : Remote
AdminDisplayVersion                          : Version 15.0 (Build 775.38)
AdministrativeGroup                          : Exchange Administrative Group (FYDIBOHF23SPDLT)
AllowFileRestore                             : False
BackgroundDatabaseMaintenance                : True
ReplayBackgroundDatabaseMaintenance          :
BackgroundDatabaseMaintenanceSerialization   :
BackgroundDatabaseMaintenanceDelay           :
ReplayBackgroundDatabaseMaintenanceDelay     :
MimimumBackgroundDatabaseMaintenanceInterval :
MaximumBackgroundDatabaseMaintenanceInterval :
BackupInProgress                             :
DatabaseCreated                              : True
Description                                  :
EdbFilePath                                  : C:\Disks\DB1\DB\DB1.edb
ExchangeLegacyDN                             : /o=%%%%%/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=EX2013-MB1/cn=Microsoft
Private MDB
DatabaseCopies                               : {DB1\EX2013-MB1, DB1\EX2013-MB2, DB1\EX2013-MB3, DB1\EX2013-MB1-DR,
DB1\EX2013-MB2-DR}
InvalidDatabaseCopies                        : {}
AllDatabaseCopies                            : {DB1\EX2013-MB1, DB1\EX2013-MB2, DB1\EX2013-MB3, DB1\EX2013-MB1-DR, DB1\EX2013-MB2-DR}
Servers                                      : {EX2013-MB1, EX2013-MB2,
EX2013-MB3, EX2013-MB1-DR, EX2013-MB2-DR}
ActivationPreference                         : {[EX2013-MB1, 1], [EX2013-MB2, 2], [EX2013-MB3, 3], [EX2013-MB1-DR, 4], [EX2013-MB2-DR, 5]}
ReplayLagTimes                               : {[EX2013-MB1, 00:00:00], [EX2013-MB2, 00:00:00], [EX2013-MB3,
00:00:00], [EX2013-MB1-DR, 00:00:00], [EX2013-MB2-DR, 00:00:00]}
TruncationLagTimes                           : {[EX2013-MB1, 00:00:00], [EX2013-MB2, 00:00:00], [EX2013-MB3, 00:00:00], [EX2013-MB1-DR,
00:00:00], [EX2013-MB2-DR, 00:00:00]}
RpcClientAccessServer                        : EX2013-MB1.%%%%%%.local
MountedOnServer                              :
DeletedItemRetention                         : 60.00:00:00
SnapshotLastFullBackup                       :
SnapshotLastIncrementalBackup                :
SnapshotLastDifferentialBackup               :
SnapshotLastCopyBackup                       :
LastFullBackup                               :
LastIncrementalBackup                        :
LastDifferentialBackup                       :
LastCopyBackup                               :
DatabaseSize                                 :
AvailableNewMailboxSpace                     :
MaintenanceSchedule                          : {Sun.1:00 AM-Sun.5:00 AM, Mon.1:00 AM-Mon.5:00 AM, Tue.1:00 AM-Tue.5:00 AM, Wed.1:00
AM-Wed.5:00 AM, Thu.1:00 AM-Thu.5:00 AM, Fri.1:00 AM-Fri.5:00 AM, Sat.1:00 AM-Sat.5:00 AM}
MountAtStartup                               : True
Mounted                                      :
Organization                                 : %%%%%%%
QuotaNotificationSchedule                    : {Sun.1:00 AM-Sun.1:15 AM, Mon.1:00 AM-Mon.1:15 AM, Tue.1:00 AM-Tue.1:15 AM, Wed.1:00 AM-Wed.1:15 AM, Thu.1:00 AM-Thu.1:15
AM, Fri.1:00 AM-Fri.1:15 AM, Sat.1:00 AM-Sat.1:15 AM}
Recovery                                     : False
RetainDeletedItemsUntilBackup                : False
Server                                       : EX2013-MB1
MasterServerOrAvailabilityGroup              : DAG1
WorkerProcessId                              :
CurrentSchemaVersion                         :
RequestedSchemaVersion                       :
AutoDagExcludeFromMonitoring                 : False
AutoDatabaseMountDial                        : GoodAvailability
DatabaseGroup                                :
MasterType                                   : DatabaseAvailabilityGroup
ServerName                                   : EX2013-MB1
IssueWarningQuota                            : 1.9 GB (2,040,110,080 bytes)
EventHistoryRetentionPeriod                  : 7.00:00:00
Name                                         : DB1
LogFolderPath                                : C:\Disks\DB1\LOGS
TemporaryDataFolderPath                      :
CircularLoggingEnabled                       : False
LogFilePrefix                                : E01
LogFileSize                                  : 1024
LogBuffers                                   :
MaximumOpenTables                            :
MaximumTemporaryTables                       :
MaximumCursors                               :
MaximumSessions                              :
MaximumVersionStorePages                     :
PreferredVersionStorePages                   :
DatabaseExtensionSize                        :
LogCheckpointDepth                           :
ReplayCheckpointDepth                        :
CachedClosedTables                           :
CachePriority                                :
ReplayCachePriority                          :
MaximumPreReadPages                          :
MaximumReplayPreReadPages                    :
DataMoveReplicationConstraint                : SecondCopy
IsMailboxDatabase                            : True
IsPublicFolderDatabase                       : False
MailboxProvisioningAttributes                :
AdminDisplayName                             : DB1
ExchangeVersion                              : 0.10 (14.0.100.0)
DistinguishedName                            : CN=DB1,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative
Groups,CN=%%%%%,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=%%%%%%,DC=%%%
Identity                                     : DB1
Guid                                         : 765d01d0-4468-43fd-a1e8-ad205b25c8ee
ObjectCategory                               : %%%%%%.%%%/Configuration/Schema/ms-Exch-Private-MDB
ObjectClass                                  : {top, msExchMDB, msExchPrivateMDB}
WhenChanged                                  : 12/10/2013 7:02:44 PM
WhenCreated                                  : 11/13/2013 11:00:58 AM
WhenChangedUTC                               : 12/11/2013 12:02:44 AM
WhenCreatedUTC                               : 11/13/2013 4:00:58 PM
OrganizationId                               :
OriginatingServer                            : %%%%%-DC4.%%%%%.%%%
IsValid                                      : True
ObjectState                                  : Changed
[PS] C:\Windows\system32>Get-MailboxDatabase -Status | ft Name,Server,LastF*Backup,LastI*Backup,LastD*Backup -AutoSize
Name       Server        LastFullBackup       LastIncrementalBackup LastDifferentialBackup
MB1-DB0    EX2013-MB1    1/6/2014 11:30:46 PM
DB1        EX2013-MB1    1/6/2014 11:30:46 PM
DB2        EX2013-MB1    1/6/2014 11:30:46 PM
MB3-DB0    EX2013-MB3    1/6/2014 10:45:44 PM
DB5        EX2013-MB3    1/6/2014 10:45:44 PM
DB6        EX2013-MB3    1/6/2014 10:45:44 PM
MB2-DB0    EX2013-MB2    1/6/2014 10:15:39 PM
DB3        EX2013-MB2    1/6/2014 10:15:39 PM
DB4        EX2013-MB2    1/6/2014 10:15:39 PM
MB1-DR-DB0 EX2013-MB1-DR 1/6/2014 8:00:23 PM
MB2-DR-DB0 EX2013-MB2-DR 1/6/2014 8:15:22 PM

Cross-forest migration to Exchange 2013 SP1 and Outlook 2013 SP1

Hello! I have two forest: Exchange 2010 SP2 RU5 - resource forest and Exchange 2013 SP1 - account forest. I make cross-forest migration from resource forest (linked mailboxes with account forest) to forest with Exchange 2013 SP1.
I have moved mailbox from resource forest exchange 2010 to exchange 2013 sp1 forest.
Outlook 2010 connect to migrated mailbox without any problem, but outlook 2013 sp1 cannot connect to migrated mailbox.
Error look like - cannot find exchange server.
I created new mailbox in Exchange 2013 organization and can connect to it with outlook 2010 and outlook 2013 sp1.
Someone have the same problem with migrated mailbox? How to solve it?
Truly, Valery Tyurin

You can use New-MoveRequest to perform a cross-forest move. Here is a well post and step-wise explanation you can check for cross forest migration from exchange 2010 to exchange 2013(http://msexchangeguru.com/2013/11/03/e2013crossforestmigration/).
Moreover, you can try this utility (
http://www.exchangemigrationtool.com/ ) to accomplish this task.

Exchange 2013 migration and Lync server

hi guys,
i wanna upgrade my exchange 2010 to 2013 in our company.
but i faced with a question
will exchange migration has effect on Lync server an should i reinstall it again in our caompany or not?
plz help me
thanks guys

Hi,
you will need to config IM in OWA for Exchange 2013 server.As i can remember voice and everything else should be fine.
Here is a guide for enabling IM in OWA:
http://www.expta.com/2010/09/how-to-integrate-lync-server-2010-with.html
Just remember to point DNS to the New Exchange 2013 server and it should be fine.
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Off2work

The Microsoft Exchange Administrator has made a change that requires you to Quit and restart outlook in Exchange 2013 CU3

I have a Exchange 2013, That has been running for a few months now since we moved it over, but now I get the Microsoft Outlook Message "The Microsoft Exchange Administrator has made a change that requires you to quit and restart Outlook." It only
shows up on certain users but not on others. What could be the problem? The only answers I have seen are for Exchange 2010.
All Help is much appreciated

This one? http://support.microsoft.com/kb/2934750

Exchange 2013 CU3 Can't Access ECP from Office365 Enabled Account

We recently upgraded our Exchange 2013 server to CU3 to fix the OWA redirection error. Unfortunately, we've now noticed that any admin mailboxes that have been 'moved' to Office365 can not access ECP and instead get a redirect warning to OWA.
I had to create a new, onprem admin account to access in the meantime. This is the message I see:
Use the following link to open this mailbox with the best performance:
http://outlook.com/owa/ACME.onmicrosoft.com
X-FEServer: EXCHANGE
Date: 12/3/2013 6:13:23 PM
more detail...
I assume this is due to the fix for OWA redirection? How do I manage Exchange with my 'oncloud' mailbox accounts?

Hi,
I think it will be more suitable to ask this question on Exchange Online forum:
http://social.technet.microsoft.com/Forums/msonline/en-US/home?forum=onlineservicesexchange
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

Exchange 2013 SP1 and SCOM 2012 R2

Hi there,
Hopefully someone can assist me with this issue, if it is one...
I am halfway through an Exchange migration, from Exchange 2010 SP3 on Server 2008 R2 to Exchange 2013 SP1 on Server 2012 R2.
76 users in total, roughly 80GB of Public Folders.
I have configured the 2013 environment with a cross datacenter DAG, also increased all of the timeouts of the cluster to take this into consideration, and everything appears to function as expected.
Added both 2013 machines to SCOM 2012 R2 for at least a week with no active users on it, and all monitoring reported ok, no issues.
Exchange 2010 is configured to use webmail.company.com for RPC over HTTP, which is what I have configured 2013 to use as well.
Implemented Microsoft ARR for client access to Exchange 2013, as opposed to ISA we've used for Exchange 2010.
A week ago, changed the DNS records for webmail.company.com from ISA to ARR, and all clients connected perfect.
Thought, ok, now we can start the migration. So far everything "seems" to be going perfect with the mailbox moves, however, SCOM is really noisy.
Attempted to reran the probe for EWS and got the error below:
Is there perhaps anyone that can assist me with these errors?
Cheers

FYI... IIS ARR is not supported for Exchange Server.
Check in event log if you are getting anything related to the issue.
About Outlook POP UP to end users. Check the event log on 2010/2013 for MRS events.
Are those mailboxes still moving or in move request?
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.

Exchange 2013 SP1 and Exchange Online Protection (EOP)

Hello, I have just set up a new install of Exchange 2013 and connected mail flow with EOP. Mail is flowing, and I can access emails through the Outlook Web App. However, I cannot get Outlook 2013 to link up to the new configuration. I got Outlook for Mac
to work, no problem. But, I get an error on outlook 2013 that says it must sync folders for a first time to open.
Any help would be appreciated.
Thanks!

Hi
Use another user to test, check whether he can use Outlook to access his mailbox or not?
If this user also cannot connect to his mailbox, I suggest you go to check whether all the Exchange services are started, make sure RPC client access service is started.
You do need to replace the self-signed certificate.
If you don't want to buy a certificate from a Third-Party Issuer, then install Windows CA and issue a certificate from there.
Even if it does work with the self-signed certificate using Outlook 2007, it is not a supported configuration and you will not be able to connect with Outlook 2010/2013.
I have seen new installation of EX13 having SSLOffloading turned on causing the problems. Turn if off if you do.
Set-OutlookAnywhere -Identity 'SERVERNAME\rpc (Default Web Site)' -SSLOffloading $false
Let us know the output of the above so that we can proceed further.
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com

Exchange 2013 ECP and DAG issue

Good Day,
We have Exchange 2013 setup in Coexistence with Exchange 2007. Everything is working well except for two small issues I have noticed.
Current Setup of 2013:
SiteA:
2x CAS Servers on Windows 2012 R2 configured with windows NLB (Internet Facing).
2x MBX servers Configured in a DAG also running on Windows 2012 R2.
SiteB:
2x CAS Server on Windows 2012 R2.
2x MBX servers Configured in a DAG also running on Windows 2012 R2.
Issues I am having:
Issue 1:
When working on the ECP:
I can do all tasks on servers in the same site but get some errors when trying to do tasks on servers in the other site.
When trying to Activate a DB copy on the DAG at SiteB I get "The Microsoft Exchange Replication service does not appear to be running on Server name"
And just trying to go to the properties of a server at SiteB "An error occurred while accessing the registry on the server servername"
This happens vice versa.
I can access all servers on the same site but not between sites with some tasks.
I have made sure firewall is disabled and remote registry is indeed running but no luck.
From a network perspective all ports are open between the sites.
Issue 2:
When I reboot a DAG member with the active mailbox databases for testing outlook connectivity I get two issues.
Then I cannot access ECP at all until the server is up again.
Outlook keeps staying on trying to connect until it is reopened.
Any Ideas?
I will gladly give more information if needed.
Thank You
Riaan Rourke
Senior System Engineer

Since I don't see this with Hyper-V I'll assume this is on ESX. Please let me know it that's not correct.
In terms of virtualization best practices - whose list was that :)
There are multiple configuration things that you *MUST* do when using WLBS on ESX. It will depend upon multiple things in the environment. I'd start with this
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1556
Fix that, and chances are the other item will be also remediated.
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Exchange 2010 to Exchange 2013 Migration and Architect a resilient and high availability exchange setup

Hi,
I currently have a single Exchange 2010 Server that has all the roles supporting about 500 users. I plan to upgrade to 2013 and move to a four server HA Exchange setup (a CAS array with 2 Server as CAS servers and one DAG with 2 mailbox Servers). My
goal is to plan out the transition in steps with no downtime. Email is most critical with my company.
Exchange 2010 is running SP3 on a Windows Server 2010 and a Separate Server as archive. In the new setup, rather than having a separate server for archiving, I am just going to put that on a separate partition.
Here is what I have planned so far.
1. Build out four Servers. 2 CAS and 2 Mailbox Servers. Mailbox Servers have 4 partitions each. One for OS. Second for DB. Third for Logs and Fourth for Archives.
2. Prepare AD for exchange 2013.
3. Install Exchange roles. CAS on two servers and mailbox on 2 servers. Add a DAG. Someone had suggested to me to use an odd number so 3 or 5. Is that a requirement?
4. I am using a third party load balancer for CAS array instead of NLB so I will be setting up that.
5. Do post install to ready up the new CAS. While doing this, can i use the same parameters as assigned on exchange 2010 like can i use the webmail URL for outlook anywhere, OAB etc.
6. Once this is done. I plan to move a few mailboxes as test to the new mailbox servers or DAG.
7. Testing outlook setups on new servers. inbound and outbound email tests.
once this is done, I can migrate over and point all my MX records to the new servers.
Please let me know your thoughts and what am I missing. I like to solidify a flowchart of all steps that I need to do before I start the migration.
thank you for your help in advance

Hi,
okay, you can use 4 virtual servers. But there is no need to deploy dedicated server roles (CAS + MBX). It is better to deploy multi-role Exchange servers, also virtual! You could install 2 multi-role servers and if the company growths, install another multi-role,
and so on. It's much more simpler, better and less expensive.
CAS-Array is only an Active Directory object, nothing more. The load balancer controls the sessions on which CAS the user will terminate. You can read more at
http://blogs.technet.com/b/exchange/archive/2014/03/05/load-balancing-in-exchange-2013.aspx Also there is no session affinity required.
First, build the complete Exchange 2013 architecture. High availability for your data is a DAG and for your CAS you use a load balancer.
On channel 9 there is many stuff from MEC:
http://channel9.msdn.com/search?term=exchange+2013
Migration:
http://geekswithblogs.net/marcde/archive/2013/08/02/migrating-from-microsoft-exchange-2010-to-exchange-2013.aspx
Additional informations:
http://exchangeserverpro.com/upgrading-to-exchange-server-2013/
Hope this helps :-)

Exchange 2013 CU3 and Firefox 26.0

Similar Messages

Maybe you are looking for