Update reports exchange 2013

Becouse updates for exchange 2013 ar not in wsus
Is there page in can monitor by rss feed that just reports updates of exchange 2013 ?
I know the exchange team blog, there are alot more post.
I want to be triggerd only when there is an update voor exchange 2013
With kind regards, Bas van den Dikkenberg

Actually there is one option and it's best available option.
You can use Exchange Team Blog
http://blogs.technet.com/b/exchange/
All the updates for new release comes here first.
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.

Similar Messages

Security Update for exchange 2013 SP1 (KB3040856) failed mid-way / power problem mailbox server disconnected

While applying todays security update for exchange 2013 (KB3040856) there was a power issue (sad story) and the update was interrupted halfway through. A bunch of service were left deactivated and I beleive I brought them back.
At this point the exchange admin center brings me to the login and when I do login, I get an enable to display page msg after the login.
I have an ActiveSync error log "cannot access the mailbox because the mail box server is disconnected" translated from french.
I also have ASP.NET 4.0 error "MapiExceptionMdbOffline"
What could be the next step in fixing this if it is at all possible ? I am not an expert in cmdlet but can manage if pointed in the right direction.
Any help would be greatly appreciated.
Thank you.

I ran update KB3040856, and it disabled all Exchange services, and a few others besides (IIS and filtering). I ran the test-servicehealth cmdlet and eventually got all the services set to automatic and all running.
This is really a stupid thing for an update to do, what is going on? Exchange 2013 is trouble enough already, we really do not need this sort of agro.

Update from Exchange 2013 Cu2 to SP1 - Outlook 2010 with SP2 clients disconnected

Hi,
we recently upgraded a standalone Exchange 2013 Server to SP1. Owa works fine, but all internal Outlook 2010 Clients (with SP2) get disconnected. Creating a new Profile, and testing the internal autodiscovery leeds to an Error 12030 (Connection reset) during
the discovery process.
I already checked the Service Point, the discovery URLs, even recreated the autodiscover virtual Directory in iis. But nothing changed.
The self signed certificate, that was used before the update is further used, and well known to all Clients. As I tested, OWA is working well everywhere.
Anyone some new ideas?
Best regards
Bernhard

Hi,
How did you recreate outlook profile? Manually or Automatic?
If automatic failed, please try to recreate manually and check the result.
If manual failed, please refer to the following methods to troubleshoot the issue:
1>Try to open the following link and check the result:
https://CASName/autodiscover/autodiscover.xml
2>Try to use RCA to test outlook autodiscover and check the result.
https://testconnectivity.microsoft.com/
Thansk.
Niko Cheng
TechNet Community Support

Update from Exchange 2013 SP1 to CU8 error

hi,
i've got problem when update to cu8.
the file 'c:\program files\microsoft\exchange server\v15\transportroles\agents\hygiene\asdat.msi' is not a valid installation package for the product microsoft exchange 2007 standard anti-spam filter updates. try to find the installation package 'asdat.msi'
in a folder from which you can install microsoft exchange 2007 standard anti-spam filter updates.
please help me..

hi,
i've got problem when update to cu8.
the file 'c:\program files\microsoft\exchange server\v15\transportroles\agents\hygiene\asdat.msi' is not a valid installation package for the product microsoft exchange 2007 standard anti-spam filter updates. try to find the installation package 'asdat.msi'
in a folder from which you can install microsoft exchange 2007 standard anti-spam filter updates.
please help me..
     The following error was generated when "$error.Clear();
          uninstall-MsiPackage -ProductCode '{C3F10D8C-BD70-4516-B2B4-BF69019807
41}' -LogFile ($RoleSetupLoggingPath + "\UninstallASDat.msilog")
        " was run: "Microsoft.Exchange.Configuration.Tasks.TaskException: Couldn
't remove product with code c3f10d8c-bd70-4516-b2b4-bf6901980741. The installati
on source for this product is not available. Verify that the source exists and t
hat you can access it. Error code is 1612. ---> System.ComponentModel.Win32Excep
tion: The installation source for this product is not available. Verify that the
source exists and that you can access it
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception
, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception
, ErrorCategory category, Object target)
   at Microsoft.Exchange.Management.Deployment.UninstallMsi.RemoveProductCode(Gu
id productCode)
   at Microsoft.Exchange.Management.Deployment.UninstallMsi.InternalProcessRecor
d()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String fun
cName, Action func, Boolean terminatePipelineIfFailed)".
The Exchange Server setup operation didn't complete. More details can be found
in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.

Error when updating Client Access Front End Service to Exchange 2013 Update 6

When updating to Exchange 2013 Update 6 we received the following error at the Step 11 of 13: Client Access role: Client Access Front End service step:
Error:
The following error was generated when "$error.Clear();
$fe = get-ActiveSyncVirtualDirectory -server $RoleFqdnOrName -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
if ($fe -eq $null)
new-ActiveSyncVirtualDirectory -DomainController $RoleDomainController -Role ClientAccess;
else
update-ActiveSyncVirtualDirectory $fe -DomainController $RoleDomainController -InstallIsapiFilter $true
" was run: "System.Management.Automation.ParameterBindingException: Cannot convert 'System.Object[]' to the type 'Microsoft.Exchange.Configuration.Tasks.VirtualDirectoryIdParameter' required by parameter 'Identity'. Specified method is not supported. ---> System.NotSupportedException: Specified method is not supported.
at System.Management.Automation.ParameterBinderBase.CoerceTypeAsNeeded(CommandParameterInternal argument, String parameterName, Type toType, ParameterCollectionTypeInformation collectionTypeInfo, Object currentValue)
--- End of inner exception stack trace ---
at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)
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)".
Problem was that if you have more than one ActiveSyncVirtualDirectory, the installer for Update 6 fails because it's not expecting an array of virtual directories to be returned. Solution is to remove the "extra" virtual directory, perform the
installation, and then re-add the virtual directory.
None of the other types of virtual directories are susceptible to this, only ActiveSync.

Hi,
Please try to reset registrar state:
http://tsoorad.blogspot.in/2013/04/lync-2013-ee-pool-wont-start.html
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make
sure that you completely understand the risk before retrieving any suggestions from the above link.
Kent Huang
TechNet Community Support

Exchange 2013 CU6 update cannot pass preresquites?

When I go to update our Exchange 2013 server to CU6 (from CU5) I get the following error:
I was doing something with the Tasks, which cannot be scheduled anymore. How do I fix this?
Thanks
Error:
The following error was generated when "$error.Clear();
try
$Target = $env:COMPUTERNAME
try
$exSrv = get-ExchangeServer $Target -ErrorAction SilentlyContinue
catch
Write-ExchangeSetupLog -Warning "Unable to set monitoring and server state to inactive. Setup will continue.";
if ($exSrv -eq $null)
Write-ExchangeSetupLog -Warning "$Target is not an Exchange Server. Unable to set monitoring and server state to inactive. Setup will continue.";
return
Set-ServerComponentState $Target -Component Monitoring -Requester Functional -State Inactive
Write-ExchangeSetupLog -Info "Monitoring has been set to Inactive while setup is running."
Set-ServerComponentState $Target -Component RecoveryActionsEnabled -Requester Functional -State Inactive
Write-ExchangeSetupLog -Info "RecoveryActionsEnabled has been set to Inactive while setup is running."
Set-ServerComponentState $Target -Component ServerWideOffline -Requester Functional -State InActive
Write-ExchangeSetupLog -Info "The server state has been set to Inactive while setup is running."
catch
Write-ExchangeSetupLog -Warning "Unable to set monitoring and server state to inactive. Setup can not continue.";
throw;
" was run: "Microsoft.Exchange.Data.Directory.ADOperationException: Active Directory operation failed on EXCH01.domain.local. This error is not retriable. Additional information: Insufficient access rights to perform the operation.
Active directory response: 00002098: SecErr: DSID-03150E49, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0
---> System.DirectoryServices.Protocols.DirectoryOperationException: The user has insufficient access rights.
at System.DirectoryServices.Protocols.LdapConnection.ConstructResponse(Int32 messageId, LdapOperation operation, ResultAll resultType, TimeSpan requestTimeOut, Boolean exceptionOnTimeOut)
at System.DirectoryServices.Protocols.LdapConnection.SendRequest(DirectoryRequest request, TimeSpan requestTimeout)
at Microsoft.Exchange.Data.Directory.PooledLdapConnection.SendRequest(DirectoryRequest request, LdapOperation ldapOperation, Nullable`1 clientSideSearchTimeout, IActivityScope activityScope, String callerInfo)
at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException, Boolean isSync)
--- End of inner exception stack trace ---
at Microsoft.Exchange.Data.Directory.ADDataSession.AnalyzeDirectoryError(PooledLdapConnection connection, DirectoryRequest request, DirectoryException de, Int32 totalRetries, Int32 retriesOnServer)
at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException, Boolean isSync)
at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException)
at Microsoft.Exchange.Data.Directory.ADDataSession.Save(ADObject instanceToSave, IEnumerable`1 properties, Boolean bypassValidation)
at Microsoft.Exchange.Management.SystemConfigurationTasks.SetServerComponentState.InternalProcessRecord()
at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
Error:
The following error was generated when "$error.Clear();
try
$Target = $env:COMPUTERNAME
try
$exSrv = get-ExchangeServer $Target -ErrorAction SilentlyContinue
catch
Write-ExchangeSetupLog -Warning "Unable to set monitoring and server state to inactive. Setup will continue.";
if ($exSrv -eq $null)
Write-ExchangeSetupLog -Warning "$Target is not an Exchange Server. Unable to set monitoring and server state to inactive. Setup will continue.";
return
Set-ServerComponentState $Target -Component Monitoring -Requester Functional -State Inactive
Write-ExchangeSetupLog -Info "Monitoring has been set to Inactive while setup is running."
Set-ServerComponentState $Target -Component RecoveryActionsEnabled -Requester Functional -State Inactive
Write-ExchangeSetupLog -Info "RecoveryActionsEnabled has been set to Inactive while setup is running."
Set-ServerComponentState $Target -Component ServerWideOffline -Requester Functional -State InActive
Write-ExchangeSetupLog -Info "The server state has been set to Inactive while setup is running."
catch
Write-ExchangeSetupLog -Warning "Unable to set monitoring and server state to inactive. Setup can not continue.";
throw;
" was run: "Microsoft.Exchange.Data.Directory.ADOperationException: Active Directory operation failed on EXCH01.domain.local. This error is not retriable. Additional information: Insufficient access rights to perform the operation.
Active directory response: 00002098: SecErr: DSID-03150E49, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0
---> System.DirectoryServices.Protocols.DirectoryOperationException: The user has insufficient access rights.
at System.DirectoryServices.Protocols.LdapConnection.ConstructResponse(Int32 messageId, LdapOperation operation, ResultAll resultType, TimeSpan requestTimeOut, Boolean exceptionOnTimeOut)
at System.DirectoryServices.Protocols.LdapConnection.SendRequest(DirectoryRequest request, TimeSpan requestTimeout)
at Microsoft.Exchange.Data.Directory.PooledLdapConnection.SendRequest(DirectoryRequest request, LdapOperation ldapOperation, Nullable`1 clientSideSearchTimeout, IActivityScope activityScope, String callerInfo)
at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException, Boolean isSync)
--- End of inner exception stack trace ---
at Microsoft.Exchange.Data.Directory.ADDataSession.AnalyzeDirectoryError(PooledLdapConnection connection, DirectoryRequest request, DirectoryException de, Int32 totalRetries, Int32 retriesOnServer)
at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException, Boolean isSync)
at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException)
at Microsoft.Exchange.Data.Directory.ADDataSession.Save(ADObject instanceToSave, IEnumerable`1 properties, Boolean bypassValidation)
at Microsoft.Exchange.Management.SystemConfigurationTasks.SetServerComponentState.InternalProcessRecord()
at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
Error:
The following error was generated when "$error.Clear();
try
$Target = $env:COMPUTERNAME
try
$exSrv = get-ExchangeServer $Target -ErrorAction SilentlyContinue
catch
Write-ExchangeSetupLog -Warning "Unable to set monitoring and server state to inactive. Setup will continue.";
if ($exSrv -eq $null)
Write-ExchangeSetupLog -Warning "$Target is not an Exchange Server. Unable to set monitoring and server state to inactive. Setup will continue.";
return
Set-ServerComponentState $Target -Component Monitoring -Requester Functional -State Inactive
Write-ExchangeSetupLog -Info "Monitoring has been set to Inactive while setup is running."
Set-ServerComponentState $Target -Component RecoveryActionsEnabled -Requester Functional -State Inactive
Write-ExchangeSetupLog -Info "RecoveryActionsEnabled has been set to Inactive while setup is running."
Set-ServerComponentState $Target -Component ServerWideOffline -Requester Functional -State InActive
Write-ExchangeSetupLog -Info "The server state has been set to Inactive while setup is running."
catch
Write-ExchangeSetupLog -Warning "Unable to set monitoring and server state to inactive. Setup can not continue.";
throw;
" was run: "Microsoft.Exchange.Data.Directory.ADOperationException: Active Directory operation failed on EXCH01.domain.local. This error is not retriable. Additional information: Insufficient access rights to perform the operation.
Active directory response: 00002098: SecErr: DSID-03150E49, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0
---> System.DirectoryServices.Protocols.DirectoryOperationException: The user has insufficient access rights.
at System.DirectoryServices.Protocols.LdapConnection.ConstructResponse(Int32 messageId, LdapOperation operation, ResultAll resultType, TimeSpan requestTimeOut, Boolean exceptionOnTimeOut)
at System.DirectoryServices.Protocols.LdapConnection.SendRequest(DirectoryRequest request, TimeSpan requestTimeout)
at Microsoft.Exchange.Data.Directory.PooledLdapConnection.SendRequest(DirectoryRequest request, LdapOperation ldapOperation, Nullable`1 clientSideSearchTimeout, IActivityScope activityScope, String callerInfo)
at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException, Boolean isSync)
--- End of inner exception stack trace ---
at Microsoft.Exchange.Data.Directory.ADDataSession.AnalyzeDirectoryError(PooledLdapConnection connection, DirectoryRequest request, DirectoryException de, Int32 totalRetries, Int32 retriesOnServer)
at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException, Boolean isSync)
at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException)
at Microsoft.Exchange.Data.Directory.ADDataSession.Save(ADObject instanceToSave, IEnumerable`1 properties, Boolean bypassValidation)
at Microsoft.Exchange.Management.SystemConfigurationTasks.SetServerComponentState.InternalProcessRecord()
at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

Based on "Was Run" error it looks like you don't have permission to store something in AD. Can you try putting server into maintenance mode first and see if you can?
http://windowsitpro.com/blog/installing-exchange-2013-cu1-dag-member-servers-some-care-and-maintenance-mode-required
http://vanhybrid.com/2013/11/28/script-putting-exchange-server-2013-into-maintenance-mode/
If server goes into maintenance mode successfully then re-run the setup...

High Amount of Spam on Exchange 2013 - Content Filtering is Enabled but Pfizer Spam Filling Up Everyone's Mailboxes

Hello
Previously I used Exchange 2010 with Forefront Threat Protection installed and this used to do a good job of stopping all the spam.
However since updating to Exchange 2013 earlier this year and enabling the integrated spam filtering everyone noticed a sudden increase in the amount of spam which was getting through which has been bad for a long time.
We have been living with it but in the last 3 weeks everyone has started getting about 40 emails a day from Pfizer for Viagra. All these seem to defeat the content filtering as Viagra is spelt with an extra I and the email address is always different.
Also images in emails are blocked by default but somehow all the images on these spam messages appear for everyone.
I am not sure the spam filtering is working at all and I'm not sure how to tell as ForeFront gives you a nice graphical dashboard but I can find nothing similar to this in Exchange and PowerShell seems the only way to configure the limited functionality
of the content filter.
Is there any way to get rid of these messages as it doesn't look very good when they are constantly popping up for everyone?
Thanks
Robin
Robin Wilson

Hello ManU
Thanks for the reply.
I have checked the logs and see this quite often:
AcceptMessage,,SCL,not available: policy is disabled
But other times it says this:
RejectMessage,550 5.7.1 Message rejected as spam by Content Filtering
Which seems to indicate it is rejecting some.
This is what one of the email headers look like:
Received: from RWS-MAIL.rwsservices.net (192.168.2.151) by
RWS-MAIL.rwsservices.net (192.168.2.151) with Microsoft SMTP Server (TLS) id
15.0.775.38 via Mailbox Transport; Sat, 28 Dec 2013 10:59:26 +0000
Received: from RWS-MAIL.rwsservices.net (192.168.2.151) by
rws-mail.rwsservices.net (192.168.2.151) with Microsoft SMTP Server (TLS) id
15.0.775.38; Sat, 28 Dec 2013 10:58:38 +0000
Received: from [90.169.106.204] (90.169.106.204) by mail.rwsservices.net
(192.168.2.151) with Microsoft SMTP Server id 15.0.775.38 via Frontend
Transport; Sat, 28 Dec 2013 10:58:37 +0000
Date: Sat, 28 Dec 2013 12:05:58 +0200
From: US.Pfizer eStore <[email protected]>
To: robin.wilson <[email protected]>
Message-ID: <[email protected]>
Subject: Dear robin.wilson up to 65% OFF!
X-Mailer: Airmail (223)
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="dd2ee3ea_586bb9e4_6f04"
Return-Path: [email protected]
X-MS-Exchange-Organization-PRD: 001-taxis.co.uk
X-MS-Exchange-Organization-SenderIdResult: Neutral
Received-SPF: Neutral (rws-mail.rwsservices.net: 90.169.106.204 is neither
permitted nor denied by domain of [email protected])
X-MS-Exchange-Organization-Network-Message-Id: e8825204-1f32-48be-a331-08d0d1d30209
X-MS-Exchange-Organization-SCL: 1
X-MS-Exchange-Organization-PCL: 2
X-MS-Exchange-Organization-Antispam-Report: DV:3.3.13223.464;SID:SenderIDStatus Neutral;OrigIP:90.169.106.204
X-EXCLAIMER-MD-CONFIG: 079171ba-394f-46d5-a160-56e416712e8e
X-MS-Exchange-Organization-AVStamp-Enterprise: 1.0
X-MS-Exchange-Organization-AuthSource: rws-mail.rwsservices.net
X-MS-Exchange-Organization-AuthAs: Anonymous
The emails use a different sender email address every time and there is always a poem in very light grey writing in the body of the email. The drugs are always misspelt as well. Is this why these are getting through?
Thanks
Robin
Robin Wilson

"The Microsoft Exchange Administrator has made a change that requires you quit and restart Outlook" in Exchange 2013

In Exchange 2013, Outlook finds a new connection point made up of the user’s mailbox GUID + @ + the domain portion of the user’s primary SMTP address. This change makes
it much less likely that users will see the dreaded message “Your administrator has made a change to your mailbox.”
http://technet.microsoft.com/en-us/library/dd298114(v=exchg.150).aspx
Although the error message in the topic has been already improved a lot in Exchange 2013, the users may still encounter them in some specific scenarios. We have collected them and let’s discuss them in this thread.
Symptom
=======================================
Consider the following scenario:
Exchange 2013 was installed for a migration from Exchange 2007/2010.
The legacy Exchange server is removed after successful migration.
Exchange 2013 may be updated to Exchange 2013 SP1.
Some users were being randomly prompted with a popup in their outlook client with the following message when connecting with Exchange 2013 server:
“The Microsoft Exchange Administrator has made a change that requires you quit and restart Outlook”
Cause
=======================================
The issue may be caused due to Public Folders.
The msExchHomePublicMDB attribute on Exchange 2013 databases was set to deleted legacy public folder object.
Solution
=======================================
Removed the Public Folder from all the Exchange
2013 Databases. To do it, we can use ADSIedit.msc and remove the arrtibute - msExchHomePublicMDB from all the Databases:
1. Open ADSIEdit.
2. Connect to the Configuration container.3.
Expand Configuration, expand CN=Configuration,DC=Domain,DC=com.4. Expand CN=Services -> CN=Microsoft Exchange -> CN=Domain -> CN=Administrative Groups -> CN=Exchange
Administrative Group -> CN=Databases.5. In the right hand pane you will see a list of databases.6.
Right-click the listed database object -> Properties.7. Check whether the msExchHomePublicMDB value is set to an unavailable value. If you see reference to the old database,
please clear the value.8. Click OK.9. Check the rest of the databases to make sure
that they are not populated in the same way.
References:
https://social.technet.microsoft.com/Forums/en-US/2f736bdd-1c00-4a22-97a5-95faeadf1495/exchange-2013-sp1-users-randomly-prompted-with-the-microsoft-exchange-administrator-has-made-a?forum=exchange2010
https://social.technet.microsoft.com/Forums/lync/en-US/7a7b3cf8-8761-421c-9d55-6c84e05531c0/the-administrator-has-made-a-change?forum=exchangesvrclients
https://social.technet.microsoft.com/Forums/en-US/0d71c843-b662-493c-ab6e-30708929ef18/2013-sp1-problem-the-microsoft-exchange-administrator-has-made-a-change-that-requires-you-quit-and?forum=exchangesvrdeploy
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

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

Exchange 2013 SP1 & Custom OWA Theme

On Friday of last week we updated from Exchange 2013 CU2 to Exchange 2013 SP1. Since updating our custom OWA theme no longer works. We configured it according to the following guide:
http://technet.microsoft.com/en-us/library/bb201700(v=exchg.150).aspx
The theme we customized was stored in the following location:
\Client Access\OWA\version\Owa2\resources\themes\"title of our theme"
Themes no longer appear to be stored in this location and I am uncertain as to where they have moved and how to apply them. Has anyone else run into this issue?

Hi,
Can we try to re-importing the theme again?
Thanks
Mavis
Mavis Huang
TechNet Community Support

Exchange 2013- Outlook will stop working intermittently but OWA works that time

Hello everyone. Hope someone can help me with this issue. We are experiencing a strange issue with our exchange 2013 server. We only have one exchange 2013 server and it is up to the CU2 level. The issue is sometimes the outlook clients
will stop working and the only way to fix this issue is by restarting the server . I tried restarting the exchange services but it didn't fix the issue. The outlook web access will work without any issue during this time. My research indicates
that the exchange server is getting some kind of disconnection/timeout from the Active directory. I can see the following event logs on the exchange server:
Log Name:      Microsoft-Exchange-MailboxDatabaseFailureItems/Operational
Source:        Microsoft-Exchange-MailboxDatabaseFailureItems
Date:          13/03/2014 1:12:20 PM
Event ID:      1
Task Category: Store
Level:         Information
Keywords:
User:          SYSTEM
Computer:      xxEXCHSVR.xxxx.local
Description:
Failure Item (Namespace=Store, Tag=HungStoreWorker, Database=CN=Mailbox Database 0572517180,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=xxxxxxxxx,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=xx,DC=local,
Instance=Mailbox Database 0572517180)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Microsoft-Exchange-MailboxDatabaseFailureItems" Guid="{08E893EA-4C11-4FFF-A737-99B9EEDEE4F4}" />
    <EventID>1</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>1</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2014-03-13T02:42:20.026303800Z" />
    <EventRecordID>8180</EventRecordID>
    <Correlation />
    <Execution ProcessID="5980" ThreadID="14380" />
    <Channel>Microsoft-Exchange-MailboxDatabaseFailureItems/Operational</Channel>
    <Computer>xxEXCHSVR.xxxxxx.local</Computer>
    <Security UserID="S-1-5-18" />
</System>
<UserData>
    <EventXML xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="myNs">
      <Version>1</Version>
      <Namespace>1</Namespace>
      <Tag>38</Tag>
      <DatabaseGuid>{D789BB55-9D2A-445C-B29E-E7EA510E89D6}</DatabaseGuid>
      <DatabaseInstanceName>Mailbox Database 0572517180</DatabaseInstanceName>
      <Component>StoreService</Component>
      <IOErrorIsSpecified>false</IOErrorIsSpecified>
      <NotificationEventIsSpecified>false</NotificationEventIsSpecified>
      <IOError>
        <Category>0</Category>
        <FileName>
        </FileName>
        <Offset>0</Offset>
        <Size>0</Size>
      </IOError>
      <NotificationEvent>
        <EventID>0</EventID>
        <ParameterBufferSize>0</ParameterBufferSize>
        <ParameterBuffer>
        </ParameterBuffer>
      </NotificationEvent>
    </EventXML>
</UserData>
</Event>
Log Name:      Microsoft-Exchange-HighAvailability/Operational
Source:        Microsoft-Exchange-HighAvailability
Date:          3/03/2014 1:43:53 PM
Event ID:      841
Task Category: Database Action
Level:         Error
Keywords:
User:          SYSTEM
Computer:      xxEXCHSVR.xxxx.local
Description:
ListMdbStatus failed to server 'xxexchsvr': Microsoft.Mapi.MapiExceptionTimeout: MapiExceptionTimeout: RPC operation (ExRpcAdmin.Create) to the Microsoft Exchange Information Store service timed out. Operation did not complete within the given timeout of 00:00:05.
(hr=0x80040401, ec=0) ---> System.TimeoutException: Operation did not complete within the given timeout of 00:00:05.
   at Microsoft.Exchange.Data.Storage.Cluster.InvokeWithTimeout.InternalInvoke(Action invokableAction, Action foregroundAction, TimeSpan invokeTimeout, Boolean sendWatsonReportNoThrow, Object cancelEvent)
   at Microsoft.Exchange.Data.Storage.Cluster.InvokeWithTimeout.Invoke(Action invokableAction, Action foregroundAction, TimeSpan invokeTimeout, Boolean sendWatsonReportNoThrow, Object cancelEvent)
   at Microsoft.Exchange.Cluster.Replay.SafeRefCountedTimeoutWrapper.ProtectedCallWithTimeout(String operationName, TimeSpan timeout, Action operation)
   --- End of inner exception stack trace ---
Server stack trace:
   at Microsoft.Exchange.Cluster.Replay.SafeRefCountedTimeoutWrapper.ProtectedCallWithTimeout(String operationName, TimeSpan timeout, Action operation)
   at Microsoft.Exchange.Cluster.Replay.StoreRpcController.get_ExRpcAdmin()
   at Microsoft.Exchange.Cluster.Replay.StoreRpcController.<>c__DisplayClass19.<ListMdbStatus>b__18()
   at Microsoft.Exchange.Cluster.Replay.SafeRefCountedTimeoutWrapper.<>c__DisplayClass2.<ProtectedCallWithTimeout>b__0()
   at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)
Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(Message reqMsg, Boolean bProxyCase)
   at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(Object NotUsed, MessageData& msgData)
   at System.Action.EndInvoke(IAsyncResult result)
   at Microsoft.Exchange.Data.Storage.Cluster.InvokeWithTimeout.InternalInvoke(Action invokableAction, Action foregroundAction, TimeSpan invokeTimeout, Boolean sendWatsonReportNoThrow, Object cancelEvent)
   at Microsoft.Exchange.Data.Storage.Cluster.InvokeWithTimeout.Invoke(Action invokableAction, Action foregroundAction, TimeSpan invokeTimeout, Boolean sendWatsonReportNoThrow, Object cancelEvent)
   at Microsoft.Exchange.Cluster.Replay.SafeRefCountedTimeoutWrapper.ProtectedCallWithTimeout(String operationName, TimeSpan timeout, Action operation)
   at Microsoft.Exchange.Cluster.Replay.StoreRpcController.ListMdbStatus(Boolean isBasicInformation)
   at Microsoft.Exchange.Cluster.ActiveManagerServer.AmStoreHelper.GetAllDatabaseStatuses(AmServerName serverName, Boolean isBasicInformation, MdbStatus[]& mdbStatuses, Exception& exception)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Microsoft-Exchange-HighAvailability" Guid="{455E3D31-77EF-4853-94A1-032A399567EC}" />
    <EventID>841</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>1</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2014-03-03T03:13:53.421449100Z" />
    <EventRecordID>15370</EventRecordID>
    <Correlation />
    <Execution ProcessID="7264" ThreadID="5188" />
    <Channel>Microsoft-Exchange-HighAvailability/Operational</Channel>
    <Computer>xxEXCHSVR.xxxxx.local</Computer>
    <Security UserID="S-1-5-18" />
</System>
<UserData>
    <EventXML xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="myNs">
      <NodeName>xxexchsvr</NodeName>
      <Message>Microsoft.Mapi.MapiExceptionTimeout: MapiExceptionTimeout: RPC operation (ExRpcAdmin.Create) to the Microsoft Exchange Information Store service timed out. Operation did not complete within the given timeout of
00:00:05. (hr=0x80040401, ec=0) ---> System.TimeoutException: Operation did not complete within the given timeout of 00:00:05.
   at Microsoft.Exchange.Data.Storage.Cluster.InvokeWithTimeout.InternalInvoke(Action invokableAction, Action foregroundAction, TimeSpan invokeTimeout, Boolean sendWatsonReportNoThrow, Object cancelEvent)
   at Microsoft.Exchange.Data.Storage.Cluster.InvokeWithTimeout.Invoke(Action invokableAction, Action foregroundAction, TimeSpan invokeTimeout, Boolean sendWatsonReportNoThrow, Object cancelEvent)
   at Microsoft.Exchange.Cluster.Replay.SafeRefCountedTimeoutWrapper.ProtectedCallWithTimeout(String operationName, TimeSpan timeout, Action operation)
   --- End of inner exception stack trace ---
Server stack trace:
   at Microsoft.Exchange.Cluster.Replay.SafeRefCountedTimeoutWrapper.ProtectedCallWithTimeout(String operationName, TimeSpan timeout, Action operation)
   at Microsoft.Exchange.Cluster.Replay.StoreRpcController.get_ExRpcAdmin()
   at Microsoft.Exchange.Cluster.Replay.StoreRpcController.<>c__DisplayClass19.<ListMdbStatus>b__18()
   at Microsoft.Exchange.Cluster.Replay.SafeRefCountedTimeoutWrapper.<>c__DisplayClass2.<ProtectedCallWithTimeout>b__0()
   at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)
Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(Message reqMsg, Boolean bProxyCase)
   at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(Object NotUsed, MessageData& msgData)
   at System.Action.EndInvoke(IAsyncResult result)
   at Microsoft.Exchange.Data.Storage.Cluster.InvokeWithTimeout.InternalInvoke(Action invokableAction, Action foregroundAction, TimeSpan invokeTimeout, Boolean sendWatsonReportNoThrow, Object cancelEvent)
   at Microsoft.Exchange.Data.Storage.Cluster.InvokeWithTimeout.Invoke(Action invokableAction, Action foregroundAction, TimeSpan invokeTimeout, Boolean sendWatsonReportNoThrow, Object cancelEvent)
   at Microsoft.Exchange.Cluster.Replay.SafeRefCountedTimeoutWrapper.ProtectedCallWithTimeout(String operationName, TimeSpan timeout, Action operation)
   at Microsoft.Exchange.Cluster.Replay.StoreRpcController.ListMdbStatus(Boolean isBasicInformation)
   at Microsoft.Exchange.Cluster.ActiveManagerServer.AmStoreHelper.GetAllDatabaseStatuses(AmServerName serverName, Boolean isBasicInformation, MdbStatus[]& mdbStatuses, Exception& exception)</Message>
    </EventXML>
</UserData>
</Event>
Can anyone please tell me what causing this issue?
Thanks in advance.

Hi,
According to your description, your Outlook client intermittently cannot work. I recommend you try to use RPC trace log to find the root cause.
Additionally, I recommend you update to Exchange 2013 sp1 and then check if the issue still can be reproduced.
http://blogs.technet.com/b/rmilne/archive/2014/02/25/exchange-2013-sp1-released.aspx
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

Security Update for exchange server 2013SP1 KB3011140 Stops all services and failes to install

Hi All,
Over the past 2 days this update has tried to run on the server in the evening but ends up failing. When it fails it is causing all of our exchange services to stop working and when we try to check e-mails the following day we find out the e-mail service
has been offline since the update.
Is there anything specific we need to do before running this update?
Cheers,

Hi,
As what Hotaka says, this update is available from
Windows Update. If it fails, we can also download and install the updates manually. The following stand-alone file is available for download from the Microsoft Download Center:
Download the security update for Exchange 2013 Service Pack 1 package now.
Download the security update for Exchange 2013 Cumulative Update 6 package now.
Regards,
Winnie Liang
TechNet Community Support

Exchange 2013 CU2 to CU3 OWA now redirects to IIS page

so i did the the update from Exchange 2013 CU2 to CU3 last night and i am unable to access OWA. when i go to the site i initially received a 403 forbidden error but i cleared out the require SSL, which somehow got re-enabled, and now it redirects to the
IIS 8 page.
In IIS it seems like the redirect values for default web site got cleared away. I put in the address that was previously there and then e-mail for the whole company goes down after an IIS reset. In the default web site i entered to redirect to https://mail.contoso.com/owa
like how it was before but that doesn't work.
any ideas/feedback would be great!
Thanks!

I guess you are running a multirole server.
Did you try removing the OWA virtual directories - for both Default Website and Exchange Back End site with:
#Replace ServerName
Remove-OwaVirtualDirectory "ServerName\owa (Default Web Site)"
Remove-OwaVirtualDirectory "ServerName\owa (exchange back end)"
and re-creating them again with:
#Replace ServerName & mail.domain.com
New-OwaVirtualDirectory -InternalUrl "https://ServerName/owa" -ExternalUrl "https://mail. domain.com/owa"
New-OwaVirtualDirectory -InternalUrl "https://ServerName/owa" -ExternalUrl "https://mail. domain.com/owa" -WebSiteName "Exchange Back End"

Exchange 2013 Readiness Check Error

I have been trying to install Exchange 2013 for a while now and have continued to run into the same error during the readiness check. The readiness check stalls at 40% completed and I receive the following error:
Error:
The following error was generated when "$error.Clear();
if (Get-Service MSDTC*|?{$_.Name -eq 'MSDTC'})
Set-Service MSDTC -StartupType Automatic
Start-SetupService -ServiceName MSDTC
"was run:"The task failed because a Win32 error occurred: "Access is denied". Could not open the service "MSDTC".".
I have tried to install this both onto Windows Server 2008 R2 as well as Windows Server 2012. I have installed all of the prerequisites as noted in the Microsoft documentation. I have tried to install this as the first Exchange server in a brand
new AD environment as well as trying to install it into an AD environment where I had already installed Exchange Server 2010 with SP3. I always receive the same error message during the readiness check when it stalls at 40%.
Any help here would be very much appreciated.
Thank you.

Ok, I have figured out what was causing the problem.
It appears to be something with the order that prerequisites are installed prior to installing Exchange 2013.
I had previously following the steps listed in the following page:
http://technet.microsoft.com/en-us/library/bb691354(v=exchg.150).aspx.
I was following the section for installing Windows Server 2012 prerequisites for combined Mailbox and Client Access server roles.
I installed the required Windows components using the PowerShell script and then installed Unified Communications Managed API 4.0, Office 2010 Filter Pack, and finally Office 2010 Filter Pack SP1.
After doing this and applying updates, I tried to install Exchange 2013 CU1 and received the error that I mentioned in my initial post.
I have been able to duplicate this issue when installing Exchange 2013 CU1 into a vanilla environment with Windows Server 2012 as the AD server and Exchange 2013 onto a Windows Server 2012 box.
I also had the issue when trying to install into a coexistence environment with AD being on Server 2008 R2 and another 2008 R2 server hosting Exchange 2010 with SP3.
I decided to change the order of the prerequisite installs and after doing so, I was able to install Exchange 2013 CU1 successfully.
Here are the steps that I went through to successfully install Exchange 2013 CU1.
Installed Unified Communications Managed API 4.0
Installed Office 2010 Filter Pack
Installed Office 2010 Filter Pack SP1
Ran Powershell script to install all of the required components (the Technet article says to do this first)
Applied all outstanding updates from Microsoft Update
Installed Exchange 2013 Cumulative Update 1
By following the numbered procedure that I laid out above, I was able to successfully install Exchange 2013 CU1 into both of the lab environments that I described above without any issue.
There was a suggestion that I might have bad media.
I used the same media that I tried originally using my new procedure and it worked fine so it was not the media.
I hope this helps someone out.
Thanks for everyone’s help.

DC Restart when start installing Exchange 2013 CU6

I have a domain installed on windows server 2012 R2 with function level 2008 R2 and when i try to install "as a administrator" Update for exchange 2013 CU6 or CU5 DC restart and am facing this error :
Error:
The following error was generated when "$error.Clear();
install-CannedAddressLists -DomainController $RoleDomainController
" was run: "Microsoft.Exchange.Data.Directory.ADTransientException: Failed to reconnect to Active Directory server Make sure the server is available, and that you have used the correct credentials. ---> System.DirectoryServices.ActiveDirectory.ActiveDirectoryServerDownException:
Active Directory server is not available. Please retry at a later time.
--- End of inner exception stack trace ---
at Microsoft.Exchange.Data.Directory.ConnectionPoolManager.GetConnectionFromPool(ConnectionPoolType connectionPoolType, ADObjectId domain, String serverName, Int32 port, Boolean& serverConnectionPresentButDownOrDisconnected)
at Microsoft.Exchange.Data.Directory.ConnectionPoolManager.GetConnection(ConnectionType connectionType, String partitionFqdn, ADObjectId domain, String serverName, Int32 port, NetworkCredential credential)
at Microsoft.Exchange.Data.Directory.ConnectionPoolManager.GetConnection(ConnectionType connectionType, String partitionFqdn, NetworkCredential networkCredential, String serverName, Int32 port)
at Microsoft.Exchange.Data.Directory.ADDataSession.GetConnection(String preferredServer, Boolean isWriteOperation, String optionalBaseDN, ADObjectId& rootId, ADScope scope)
at Microsoft.Exchange.Data.Directory.ADDataSession.GetWritableConnection(String preferredServer, ADObjectId identity, ADRawEntry scopeDeterimingObject)
I already prepare AD and Schema before start install
Please Advice Thanks

Hi Midoooz
Thank you for your question.
Do you install the Exchange Server on the DC?
From you posted error, I think you can try to make your exchange server in maintenance mode, then you can try install exchange CU6.
You can refer to the following link:
http://support2.microsoft.com/kb/2713696
Note:
Stop Maintenance Mode on the computer that is running Exchange Server after the Exchange Server 2013 CU6 upgrade is completed.
If there are any questions, please let me know.
Best Regard,
Jim

RPC error when configuring Exchange 2013 servers in 2nd site

Hello. I'm running into an error when trying to configure any of my Exchange 2013 servers in my 2nd AD site. To get into the loop of what my server structure looks like, please check below:
Site 1 servers:
DC1 - Domain Controller
DC2 - Domain Controller
CAS1 - CAS server
CAS2 - CAS server
MBX1 - Mailbox server
MBX2 - Mailbox server
MATHAFTMG - TMG server
Site 2 servers:
CCCDC1 - Domain Controller
CCCDC2 - Domain Controller
CCCCAS1 - CAS server
CCCCAS2 - CAS server
CCCMBX1 - MBX server
CCCMBX2 - MBX server
CCCTMG - TMG server
Currently I have a site-to-site vpn connection between site 1 and site 2 TMG servers via Internet connection; I can access the servers of the other site perfectly (whether I am in Site 1 or Site 2).
All user mailboxes are currently in Site 1 MBX servers; when users are in Site 2, they connect to the CAS servers in Site 1 to access their mailboxes.
Many users will stay permanently in Site 2, so it makes sense to have Exchange servers in Site 2 to provide faster access to mailboxes. I created the Site 2 domain controllers, and made sure AD replication is working; and it is. I then added the MBX servers
and CAS servers in Site 2 in this order: CCCMBX1, then CCCCAS1, then CCCMBX2, then CCCCAS2.
All Exchange servers in Site 2 installed beautifully. But then I tried to access the servers via ECP to proceed with the configuration. In ECP, I click on the server link, and all Exchange servers in both sites appear. If I try to configure the virtual directories
of Site 1 CAS servers, no problem. But when I try to configure virtual directories of Site 2 CAS servers, I get this error message:
The task wasn't able to connect to IIS on the server 'CCCCAS1.domain.com'. Make sure that the server exists and can be reached from this computer: The RPC server is unavailable.
The virtual directories issue is just an example. Same thing happens if I try to configure Outlook Anywhere for Site 2 CAS servers.
Users connect to Site 1 CAS servers via mail.domain.com. I have the A record mail.domain.com pointing to the IP address of CAS1 server, and another A record mail.domain.com pointing to the IP address of CAS2 server. Not the best load balancing going on here,
but it works great with Exchange 2013.
From mail.domain.com I can access OWA and ECP internally and externally; no problems there. From ECP I can access and configure any Site 1 Exchange 2013 servers.
The only problem is when I access ECP to configure the Site 2 Exchange 2013 servers, I get the same error message:
The task wasn't able to connect to IIS on the server '<server name>.domain.com'. Make sure that the server exists and can be reached from this computer: The RPC server is unavailable.
Even if I try to access a Site 2 Exchange 2013 server via https://localhost/ecp to configure it, it get the same error message.
I updated all Exchange 2013 servers in both sites to CU2 v2 and rebooted the servers in the proper order; problem still there.
Any clue what might the problem be?
Thank you!

Hello. I'm running into an error when trying to configure any of my Exchange 2013 servers in my 2nd AD site. To get into the loop of what my server structure looks like, please check below:
Site 1 servers:
DC1 - Domain Controller
DC2 - Domain Controller
CAS1 - CAS server
CAS2 - CAS server
MBX1 - Mailbox server
MBX2 - Mailbox server
MATHAFTMG - TMG server
Site 2 servers:
CCCDC1 - Domain Controller
CCCDC2 - Domain Controller
CCCCAS1 - CAS server
CCCCAS2 - CAS server
CCCMBX1 - MBX server
CCCMBX2 - MBX server
CCCTMG - TMG server
Currently I have a site-to-site vpn connection between site 1 and site 2 TMG servers via Internet connection; I can access the servers of the other site perfectly (whether I am in Site 1 or Site 2).
All user mailboxes are currently in Site 1 MBX servers; when users are in Site 2, they connect to the CAS servers in Site 1 to access their mailboxes.
Many users will stay permanently in Site 2, so it makes sense to have Exchange servers in Site 2 to provide faster access to mailboxes. I created the Site 2 domain controllers, and made sure AD replication is working; and it is. I then added the MBX servers
and CAS servers in Site 2 in this order: CCCMBX1, then CCCCAS1, then CCCMBX2, then CCCCAS2.
All Exchange servers in Site 2 installed beautifully. But then I tried to access the servers via ECP to proceed with the configuration. In ECP, I click on the server link, and all Exchange servers in both sites appear. If I try to configure the virtual directories
of Site 1 CAS servers, no problem. But when I try to configure virtual directories of Site 2 CAS servers, I get this error message:
The task wasn't able to connect to IIS on the server 'CCCCAS1.domain.com'. Make sure that the server exists and can be reached from this computer: The RPC server is unavailable.
The virtual directories issue is just an example. Same thing happens if I try to configure Outlook Anywhere for Site 2 CAS servers.
Users connect to Site 1 CAS servers via mail.domain.com. I have the A record mail.domain.com pointing to the IP address of CAS1 server, and another A record mail.domain.com pointing to the IP address of CAS2 server. Not the best load balancing going on here,
but it works great with Exchange 2013.
From mail.domain.com I can access OWA and ECP internally and externally; no problems there. From ECP I can access and configure any Site 1 Exchange 2013 servers.
The only problem is when I access ECP to configure the Site 2 Exchange 2013 servers, I get the same error message:
The task wasn't able to connect to IIS on the server '<server name>.domain.com'. Make sure that the server exists and can be reached from this computer: The RPC server is unavailable.
Even if I try to access a Site 2 Exchange 2013 server via https://localhost/ecp to configure it, it get the same error message.
I updated all Exchange 2013 servers in both sites to CU2 v2 and rebooted the servers in the proper order; problem still there.
Any clue what might the problem be?
Thank you!

Update reports exchange 2013

Similar Messages

Maybe you are looking for