Team,

Please suggest me tools which will help me for complete automization tool of my exchange 2013 server.

Which provide me health status of exchange server, Provides me all critical warning events  alerts, Health of Database, Mailflow, Health for services.

Hi everyone,

We are all aware of the restriction on migrating public folders from an Exchange Server 2003 to Office 365.

http://technet.microsoft.com/en-us/library/jj983799(v=exchg.150).aspx

This is a small workaround that might help some of you

1. On the on-premises exchange server select a migrated user and add him as an owner on each public folder to be migrate
2. Assign the user as an owner on the ROOT directory of the online Public Folders
3. Using Outlook and a non-migrated user, export the the Public Folder to PST files (user should be an owner as well)
4. Using outlook and the migrated user, import the PST files to the user's inbox (IMPORTANT not to the online public folder)
5. Right-Click each folder and copy to the online Public Folder (this might take some time)
6. Once all folders are copied, delete the folder from the users inbox and remove the access permissions

Hopefully this could help

Cheers to everyone

Hello, i've got some errors during Exchange 2013 installation after remove previous Exchange 2013 organisation with ADCI

removed:

CN=Configuration [domain] → CN=Services →

CN=Microsoft Exchange

CN=Microsoft Exchange Autodiscover 

CN=Microsoft Exchange Security Groups
CN=Microsoft Exchange Security Objects

while setting up mailbox role from Clear new install Cu6 i got error:

Environment: 1x Exchange 2013 Mailbox server

     1x Exchange 2013 CAS server

      All users migrated to office365. MX record pointed to Office365

DIRSync implemented

Clarification: All users are now using Office365. As per recommendation from Microsoft there should be 1 exchange server to be retained and the rest can be decommissioned. I tried to test the scenario by shutting down the exchange server with the mailbox role and leaving the exchange server with CAS role online. I tried to run Exchange Management shell on the CAS but I'm getting errors. To clarify, once I have uninstalled the Exchange server mailbox will the CAS still look for the mailbox server? Or do I need to decommission both Exchange servers and then install a new Exchange server with CAS role?

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

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

webmail.company.com

legacy.company.com

autodiscover.company.com

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

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

I was just wondering if anyone has stumbled upon any good "how-to" sites for those of us that (up to now) have been used to using SBS servers but now find ourselves needing to go the manual route with separate new servers (domain controller and Exchange 2013 server)?

I'm trudging along with my first Server 2012 R2 and Exchange 2013 SP1 installation and configuration, but since I'm used to things configuring themselves in SBS, the piecemeal approach to 2013 is presenting challenges for me.  

Considering the market for SBS is small business (and for me, typical 20 users), I'm looking for some direction and help in configuring these new servers to act like SBS 2011 replacement servers, with similar capabilites, etc...from the viewpoint of an SBS administrator, per se.

Maybe nothing exists and we have to start from scratch, but I was hoping with as big as the SBS market was, there would be some useful info out there with the realization that we're coming from SBS.

Thanks.

Hi All,

Getting this error when trying to install a new exchange 2013 server. Thanks in advance

Error:
The following error was generated when "$error.Clear();
          if ( ($server -eq $null) -and ($RoleIsDatacenter -ne $true) )
          {
            Update-RmsSharedIdentity -ServerName $RoleNetBIOSName
          }
        " was run: "Microsoft.Exchange.Data.DataValidationException: Database is mandatory on UserMailbox.
   at Microsoft.Exchange.Data.Directory.ADDataSession.Save(ADObject instanceToSave, IEnumerable`1 properties, Boolean bypassValidation)
   at Microsoft.Exchange.Data.Directory.Recipient.ADRecipientObjectSession.Save(ADRecipient instanceToSave)
   at Microsoft.Exchange.Management.Deployment.UpdateRmsSharedIdentity.Link()
   at Microsoft.Exchange.Management.Deployment.UpdateRmsSharedIdentity.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

I am performing a Public Folder Migration to Office 365 according to the steps at http://technet.microsoft.com/en-us/library/jj983799(v=exchg.150).aspx#Scripts. I made it down to Step 5, substep 5 where we are supposed to start the migration with a New-PublicFolderMigrationRequest. The script fails with the following error message:

Starting a command on remote server failed with the following error message : [ClientAccessServer=BN1PR07CA0067,BackEndServer=co1pr07mb395.namprd07.prod.outlook.com,RequestId
=0f9fb78e-1c50-4371-9add-414cbbfc9f69,TimeStamp=10/30/2014 3:24:26 PM] [FailureCategory=Cafe-HttpProxyException] Cannot replay request as bufferedRegionStream cannot be reset
. For more information, see the about_Remote_Troubleshooting Help topic.
    + CategoryInfo          : OperationStopped: (System.Manageme...pressionSyncJob:PSInvokeExpressionSyncJob) [], PSRemotingTransportException
    + FullyQualifiedErrorId : JobFailure

Any help or guidance is very much appreciated.

Randy Goodson

Hi all,

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

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

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

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

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

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

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

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

Event Viewer I got these error,

1. Application MSExchange Common Error 4999

2. System Service Control Manager Error 7031

How can I fix this service restart issue?

Thanks and Regards,

Low

Setup Log

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

I am configuring inbound internet message for my exchange 2013 system. and was planning on routing traffic from my DMZ edge servers to my internal CAS servers. I just realized that I will not be able to search messagetracking logs on the CAS servers should we have delivery issues and need to trouble shoot transport.
- is there a way to trace messages through a CAS server? ( no mailbox role )

Would a preferrable configuration be to
- add the Mailbox Role to the CAS servers to enable messagetracking ( no user mailboxes )
- or to stand up a couple dedicated mailbox servers ( again, no user mailboxes ) to act as HUB servers for routing traffic

We are a large organization, think 20,000+ mailboxes, and there fore a LOT of traffic.

Tom

On our Exchange 2010 SP3 RU7 server the update (.NET Framework 4.5.1) is available for installation (listed in the Windows Updates).

If you check .NET 4.5.1 compatability list then Exchange 2010 SP3 isnot compatible with .NET Framework 4.5.1

Does anybody knows if i can install the .NET update 4.5.1 update on our Exchange servers?

Our Exchange environment is:
- Exchange 2010 SP3 RU7 (2x multirole servers)
- DAG
- Windows 2008 R2 SP1
- .NET Framework 4.5

I'm working on a Lotus Notes to Office 365 migration and have deployed two Exchange 2013 CU6 CAS/MBX servers, each in a different AD site.  These servers will be used for SMTP relays and O365 management, there was no on-premises Exchange environment before these two servers were installed.  SITE A contains one CAS/MBX server (SERVER A) and has a mailbox for the user with Org Mgmt rights.  SITE B contains one CAS/MBX server (SERVER B) with no mailboxes currently.  On both servers, the internal and external URLs are set to the same value (the internal FQDN of the server).  These CAS servers are not internet-facing.  There are no AD replication issues between sites.

So when the mail administrator logs in to SERVER A and logs intohttps://localhost/ecp with his account, he is able to see the EAC.  No problems.  However, if he goes to SERVER B and typeshttps://localhost/ecp, we see the address bar update to point to the FQDN for SERVER A, but then an error is thrown similar to the below (servernames changed to protect the innocent).

A problem occured while you were trying to user your mailbox.X-OWA-Error: Microsoft.Exchange.Data.Storage.UserHasNoMailboxException 
X-OWA-Version: 15.0.955.28 
X-FEServer: SERVER A 
X-BEServer: SERVER A

I've never seen something like this.  Has anyone else?  Any assistance is appreciated.

Don

I have Exchange 2007 and 2013.  I want to migrate to 2013 but I'm having issues in the testing phase.  I have a test account that I moved the mailbox to the new server.  I have a test PC with a modified hosts file that points to the new Exch 2013 server IP address.

When I log in with this test user, Outlook appears to connect and download the mailbox.  However a Windows Security dialog box pops up saying Microsoft Outlook Connecting to test@domain.com and it has a username and password field.  No matter what is entered here, it is NOT accepted, nor if forcefully entering the wrong information is the account locked out.

I can click cancel here and it proceeds to update the inbox and then says All folders are up to date.  But at the bottom in Outlook 2013 it says Need password and Outlook's icon in the taskbar has a yellow triangle on it.  I can send myself a test email and I get it (I personally am on the 2007 server), but after it sends Outlook 2013 prompts again for the password, and since it does not accept anything, I have to click cancel.

I have done ALL the windows updates available on this test PC.  Exchange 2013 is on CU6 which is the latest at the time of this writing.

Another thing is in the Lync 2013 client it says "Exchange needs your credentials".  No matter what is entered here, it will not make this message go away unless you click the X on this warning bar.  Lync itself appears to work regardless.

Any ideas?

I just changed the ExternalClientAuthenticationMethod from Ntlm to Negotiage.  Now the Outlook prompt does accept the domain password, but I don't want anyone to have to enter any type of credentials just to get on.  Note, this test is on the same LAN as the servers, so I haven't even tackled an external test yet, though last time I tried it was the same results.

Hello, i've got some errors during Exchange 2013 installation after remove previous Exchange 2013 organisation with ADCI

removed:

CN=Configuration [domain] → CN=Services →

CN=Microsoft Exchange

CN=Microsoft Exchange Autodiscover 

CN=Microsoft Exchange Security Groups
CN=Microsoft Exchange Security Objects

while setting up mailbox role from Clear new install Cu6 i got error:

Hi

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

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

Can this work???

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

jk

Hi,

i have Exchange 2013 Rollup 5, we set the limitation for user mailboxes on database level, there is not limitation on user level,

we notice that users do not receive quota warning messages. is there any differences between 2010 and 2013 ?

I have used two mail server (Exchange 2013 and Linux sendmail) for mailing in the same domain like abc.com.

I have converted authoritative domain in to internal relay for sending mail in Linux mail user, and create a send connector point to Linux mail system as a smart host. in that case my exchange user send mail to Linux user and internet via Linux smart host,

then I create a receive connector in exchange server for receiving mail from Linux mail system as edge transport custom connector & permission set to anonymous, when Linux user send mail to my exchange user it queued in my exchange message queue and the error is:

Last Error:A local loop was detected.

What's the problem?

Dears,

I'm facing a issue with Exchange 2013 SP1 CU5 "15.00.0913.022" suddenly after 2 month of the migration from Exchange 2010 i get the "Unknown" status for Content Index status on any database hosted on two servers only

my new Exchange 2013 topology is : 3 CAS servers & DAG contains 6 Mailboxes servers and 4 lagged Mailboxes servers

The following is the errors and warnings logs on my effected mailboxes servers:

The indexing of mailbox database DB53 encountered an unexpected exception. Error details: Microsoft.Exchange.Search.Core.Abstraction.OperationFailedException: The component operation has failed. ---> Microsoft.Exchange.Search.Engine.FeedingSkippedException: "Feeding was skipped for '3a5ec474-ea70-42b5-a123-d7ff7e5aadc3 (DB53)' due to the state 'Unknown', error code: 'Unknown'."

   at Microsoft.Exchange.Search.Engine.SearchFeedingController.InternalExecutionStart()

   at Microsoft.Exchange.Search.Core.Common.Executable.InternalExecutionStart(Object state)

   --- End of inner exception stack trace ---

   at Microsoft.Exchange.Search.Core.Common.Executable.EndExecute(IAsyncResult asyncResult)

   at Microsoft.Exchange.Search.Engine.SearchRootController.ExecuteComplete(IAsyncResult asyncResult)

The FastFeeder component received a connection exception from FAST. Error details: System.ServiceModel.FaultException`1[System.ServiceModel.ExceptionDetail]: Internal error while processing request (Fault Detail is equal to An ExceptionDetail, likely created by IncludeExceptionDetailInFaults=true, whose value is:

Microsoft.Ceres.InteractionEngine.Component.ProcessingEngineException: Internal error while processing request

   at Microsoft.Ceres.InteractionEngine.Component.CieProcessingEngine.LogAndRethrowException(Exception e)

   at Microsoft.Ceres.InteractionEngine.Component.CieProcessingEngine.GetItems(Guid flowIdentifier, String outputName)

   at SyncInvokeGetItems(Object , Object[] , Object[] )

   at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)

   at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)

   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)

   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc& rpc)

   at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)).

----------------------------------------------------------------------------------------------------------------------------------------------------------------------

Event 169 (Search) of severity 'Error' occurred 14 more time(s) and was suppressed in the event log

-------------------------------------------------------------------------------------------------------------------------------------

An operation attempted against a FAST endpoint exprienced an exception. This operation may be retried. Error details: Microsoft.Exchange.Search.Fast.PerformingFastOperationException: An Exception was received during a FAST operation. ---> System.ServiceModel.CommunicationObjectAbortedException: The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it has been Aborted.

Server stack trace:

   at System.ServiceModel.Channels.CommunicationObject.ThrowIfDisposedOrNotOpen()

   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)

   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)

   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]:

   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)

   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)

   at Microsoft.Ceres.CoreServices.Admin.IAdminServiceManagementAgent.SystemInfo()

   at Microsoft.Exchange.Search.Fast.NodeManagementClient.CheckForAllNodesHealthy(Boolean retry)

   at Microsoft.Exchange.Search.Fast.IndexManager.<UpdateConfiguration>b__8()

   at Microsoft.Exchange.Search.Fast.FastManagementClient.<>c__DisplayClass1.<PerformFastOperation>b__0()

   at Microsoft.Exchange.Search.Fast.FastManagementClient.PerformFastOperation[T](Func`1 function, String eventLogKey)

   --- End of inner exception stack trace ---

------------------------------------------------------------------------------------------------------------------------------------

Exchange Server Information Store has encountered an error while executing a full-text index query ("string("ItemWarmUpSearch31febf7b418e44878df6e5623e37c828*", mode="and")"). Error information: System.ServiceModel.FaultException`1[System.ServiceModel.ExceptionDetail]: Internal error while processing request (Fault Detail is equal to An ExceptionDetail, likely created by IncludeExceptionDetailInFaults=true, whose value is:

Microsoft.Ceres.InteractionEngine.Component.ProcessingEngineException: Internal error while processing request

   at Microsoft.Ceres.InteractionEngine.Component.CieProcessingEngine.LogAndRethrowException(Exception e)

   at Microsoft.Ceres.InteractionEngine.Component.CieProcessingEngine.ExecuteSearchFlow(String flowName, IEnumerable`1 inputData)

   at SyncInvokeExecuteSearchFlow(Object , Object[] , Object[] )

   at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)

   at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)

   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)

   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc& rpc)

   at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)).

What i have tried to solve the issue with no luck is: 

1- Reseed the effected Databases

2- Reset the index manually by stop the Search and Search Host Controller services and delete the index folder and start the services again in order to force it to rebuild the index

3- Restart the mailbox server that has the index issue

4- Create the AD group "ContentSubmitters" and then grant Admistrators and NetworkService full access to the group as the following technet article http://support.microsoft.com/kb/2807668

Any Idea will be much appreciated.

Thanks,

Ayman Saleh

Ayman Saleh