Exchange 2013 SP1 On-prem - Disable Outlook Anonymous NTLM?

I'm aware there is a Group Policy admin template available to force Outlook to request only NTLM or basic authentication, however, I'd like to disable Outlook Anonymous NTLM on the server side in our Exchange 2013 SP1 on-premises installation.
Is there a method to disable Anonymous NTLM for Outlook client connections for the cas or organization? I've tried the "Set-OutlookAnywhere" InternalClientAuthenticationMethod and ExternalClientAuthentcationMethod but Outlook is still
able to connect with Anonymous Authentication selected for the logon network security.
Thanks
John Lowery

Hi Jim,
No luck. I checked the CAS Default Web Site\Rpc Authentication and the MBX Exchange Back End\Rpc as well, and both have Anonymous Authentication disabled. However, Exchange still allows Outlook to establish Anonymous NTLM connections.
My understanding is that the Authentication controls for the web site do not control the Outlook RPC over HTTP connection.
I have been able to use an administrative template to force Outlook clients to avoid Anonymous NTLM, but I would prefer to enforce it on the CAS or MBX, because doing it on the client side causes Office 365 Exchange connection failures - there's no way to
specify connection restrictions only for on-premises servers. See
http://support.microsoft.com/kb/2975918.
Thanks,
John

Similar Messages

Outlook 2013 can't connect to Exchange 2013 SP1

Hello,
I've already asked that question on Exchange 2013, now I'd like to ask it again in regard to Exchange 2013 SP1.
The question i s very easy: suppose I have just installed Exchange 2013 SP1 (in a Win2012 R2 domain) with three mailboxes (user1, user2, user3). I can successfully run ecp and owa for all users...
...but when I'm starting Outlook 2013 and trying to set up a profile manually, for example, [email protected], Exchange 2013 Sp1 keeps saying "Outlook can't log on...The name cannot be resolved."
In Exchange 2013 this could be fixed by adding the server's ip address to its Hosts file, but I thought it was a bug and it would be corrected later or sooner... Now the same problem with Exchange 2013SP1...
Would anybody please tell me is there anything special I must do to connect to Exchange 2013SP1 via Outlook 2013 (not Outlook 2013SP1 - without MAPI over HTTP)??? If yes what articles can I read about it?
Thank you in advance,
Michael

Hi,
When we automatically configure the account, Autodiscover service will help Outlook find the new type and we don't need to run the command to get the mailbox GUID until we manually configure the profile.
For more information, you can refer to the following article:
http://technet.microsoft.com/en-us/library/bb124251(v=exchg.150).aspx
"Through the Autodiscover service, Outlook finds a new connection point made up of the user’s mailbox GUID + @ + the domain portion of the user’s primary SMTP address."
Thanks,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Angela Shi
TechNet Community Support

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-SP1/Outlook 2013 connectivity issue.

We couldn't make Outlook 2013 (latest updates) to connect to our Exchange 2013-SP1 through the Internet.
Any PC inside the LAN (on the domain or outside the domain) can connect normally.
Any PC outside the LAN (WAN) cannot connect, it keep showing this error:
"The action cannot be completed. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action."
OWA is working fine from the WAN, smartphones (Android & Apple) are also working fine from the WAN.
Port 443 is open on the firewall.
So what we are missing!

Hi,
Firstly, I'd like to say, in Exchange 2013 SP1, Outlook 2013 SP1 clients may use MAPI over HTTP to connect to the server.
Before going further, let's confirm if they use MAPI over HTTP: Get-OrganizationConfig | FL MapiHttpEnabled
If the value of the above property is true, I recommend the following troubleshooting:
1. Check if your Exchange 2013 SP1 server is running on Windows Server 2012 R2.
2. Check MAPI virtual directory settings: get-MapiVirtualDirectory |fl
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

Exchange 2013 SP1 Installation Errors I Cannot Resolve

Good Afternoon All -
Note: I updated this post an hour after posting. Still no solution, but please see updated info at end of this post)
I'm trying to introduce Exchange into an existing, small environment. The server I'm trying to install it onto is an SBS 2011 server (single server.) Even though SBS comes with Exchange, I found out that it's installation was corrupted and someone
had attempted to uninstall it before. Yes, it's being installed onto a server with a DC. I considered creating a Hyper-V VM on the server for Exchange, but thought it may be better to try to install directly onto server instead.
Before I started, I made sure all Exchange data had been removed. I checked for and deleted (if present) all Exchange-related objects in ADSI, ADU&C, files, and registry entries.
When I try to install Exchange 2013 SP1, I get the below errors. I know that some are easily resolved by installing pre-requisites - however - others aren't - especially the pending reboot one. I've restarted the server many times when making
changes or applying various updates and still get flagged to restart during installation. I've tried the SBS 2011 repair disc as well, but had many issues with it. In all honesty, the whole server needs to be wiped and re-installed, but
cannot do at this point.
Besides the errors below, I've zipped up the ExchangeSetupLogs folder and placed them in the link below. Also below are system specs. The only edit I made in them is a find/replace for server and domain name.
ExchangeSetupLogs Folder
System Specs
Xeon E31270 3.4Ghz
16gb RAM
Windows Server 2011 SBS x64 (Domain Controller Role Installed & Used)
C:\ - RAID 1 = 500gb
D:\ - SATA HDD = 320gb
E:\ - SATA HDD = 320GB
Should I perhaps try to install to a VM on the server or think that would use too many unnecessary resources?
Any help would be appreciated - Thanks!
Error:
This computer requires the update described in Microsoft Knowledge Base article KB2619234 (http://go.microsoft.com/fwlink/?LinkId=262359).
Without this update, the Outlook Anywhere feature may not work reliably.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.Win7RpcHttpAssocCookieGuidUpdateNotInstalled.aspx
Error:
There is a pending reboot from a previous installation of a Windows Server role or feature. Please restart the computer and then
run Setup again.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.PendingRebootWindowsComponents.aspx
Error:
The Windows component RSAT-Clustering isn't installed on this computer and needs to be installed before Exchange Setup can begin.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.RsatClusteringInstalled.aspx
Error:
This computer requires the Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit. Please install the software from
http://go.microsoft.com/fwlink/?LinkId=260990.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.UcmaRedistMsi.aspx
Error:
An unsupported operating system was detected. Exchange Server 2013 Client Access, Mailbox, and Edge Transport server roles support
Windows Server 2008 R2 SP1 or later and Windows Server 2012.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ValidOSVersion.aspx
Warning:
Installing Exchange Server on a domain controller will elevate the permissions for Exchange Trusted Subsystem to domain administrators.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.WarningInstallExchangeRolesOnDomainController.aspx
Warning:
Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2007 server roles have been detected
in this topology. After this operation, you will not be able to install any Exchange 2007 servers.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE12ServerWarning.aspx
Warning:
Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have been detected
in this topology. After this operation, you will not be able to install any Exchange 2010 servers.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.aspx
Ben K.
UPDATE
I just tried fixing a few things and tried again. Still no luck. Below is what I changed as well as the errors received. Only option was Retry. Can I just not install it onto this environment?
What I Changed
Installed Unified Comm Managed API 4.0 (Required Uninstalling Speech Analysis app before it would install)
Installed KB2619234 for Outlook Anywhere
Installed 12 updates - Server fully patched
Exchange Setup Errors
Error:
An unsupported operating system was detected. Exchange Server 2013 Client Access, Mailbox, and Edge Transport server roles support
Windows Server 2008 R2 SP1 or later and Windows Server 2012.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ValidOSVersion.aspx
Warning:
Installing Exchange Server on a domain controller will elevate the permissions for Exchange Trusted Subsystem to domain administrators.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.WarningInstallExchangeRolesOnDomainController.aspx
Warning:
Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2007 server roles have been detected
in this topology. After this operation, you will not be able to install any Exchange 2007 servers.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE12ServerWarning.aspx
Warning:
Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have been detected
in this topology. After this operation, you will not be able to install any Exchange 2010 servers.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.aspx
Thanks Guys -

Hi,
Agree. Windows Server 2011 SBS x64 can be the problem.
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 | Another HTTP 500.0.0 Error

Help!
We are in the middle of migrating from Exchange 2010 SP3 to Exchange 2013 SP1 and we are being plagued with HTTP 500 errors on every Exchange 2013 server now.
I have two Client Access servers installed (EXCHFE01 & EXCHFE02) and one backend mailbox server (EXCHMB03) with the Client Access role also installed (for troubleshooting purposes). Once I get everything working I'll install two backend 2013 servers
with the mailbox role only for production (load-balanced, clustered, etc). I still have two Exchange 2010 mailbox servers left since one has a single large mailbox left on it and the other hosts public folders. I'll get to migrating those later. All Exchange
2013 servers are running Windows Server 2012. All are on the same LAN and no firewalls are between them.
On all three 2013 servers (EXCHFE01, EXCHFE02, EXCHMB03) I'm getting the dreaded HTTP 500 error whether I try to get to OWA or ECP. This did work at one point where I could at least login to the mailbox server (EXCHMB03) and migrate all my mailboxes over
to it. Sometime this morning after the two Client Access servers were installed the mailbox server stopped working (HTTP 500 errors). This is very frustrating because I can't even login to a console to manage Exchange from any server at this point.
Both Client Access servers aren't really showing anything of value in the event logs or the IIS logs. The mailbox server (EXCHMB03) does show the following event 3002:
Protocol /Microsoft-Server-ActiveSync failed to process request from identity NT AUTHORITY\SYSTEM. Exception: Microsoft.Exchange.Security.Authentication.BackendRehydrationException: Rehydration failed. Reason: Source server 'NT AUTHORITY\SYSTEM' does not have token serialization permission.
at Microsoft.Exchange.Security.Authentication.BackendRehydrationModule.ProcessRequest(HttpContext httpContext)
at Microsoft.Exchange.Security.Authentication.BackendRehydrationModule.OnAuthenticateRequest(Object source, EventArgs args).
...and I get the following when I run the Exchange Management Shell tool on the same mailbox server (along with lots of other red HTML text):
More Information:
This error means that there was a problem while processing the request. The request was received by the Web server, but during processing a fatal error occurred, causing the 500 error.
The Client Access servers show the following errors:
Performance counter updating error. Counter name is Location cache update time, category name is MSExchange Active Manager Client. Optional code: 3. Exception: The exception thrown is : System.InvalidOperationException: The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly.
at System.Diagnostics.PerformanceCounter.InitializeImpl()
at System.Diagnostics.PerformanceCounter.set_RawValue(Int64 value)
at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.set_RawValue(Int64 value)
Last worker process info : System.ArgumentException: Process with an Id of 4040 is not running.
at System.Diagnostics.Process.GetProcessById(Int32 processId)
at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.GetLastWorkerProcessInfo()
Processes running while Performance counter failed to update:
888 svchost
264 smss
532 conhost
2576 Microsoft.Exchange.UM.CallRouter
1596 WMSvc
3932 dllhost
4020 svchost
2308 dwm
5060 taskhostex
844 svchost
1972 Microsoft.Exchange.Directory.TopologyService
1228 inetinfo
1316 vmtoolsd
3896 svchost
780 svchost
1580 rundll32
1668 mqsvc
816 dwm
3840 slui
3532 rdpclip
3980 WmiPrvSE
4200 SppExtComObj
4288 winlogon
2140 SMSvcHost
676 svchost
1564 svchost
1296 Microsoft.Exchange.Diagnostics.Service
1472 Microsoft.Exchange.ServiceHost
1204 svchost
1292 ServerManagerLauncher
488 winlogon
664 svchost
572 lsass
3236 dllhost
2972 WmiPrvSE
4484 w3wp
388 csrss
1600 rundll32
564 services
1260 msdtc
5032 sppsvc
1448 MSExchangeHMHost
824 LogonUI
4204 VSSVC
2524 userinit
2700 MSExchangeFrontendTransport
1708 SMSvcHost
728 svchost
460 wininit
904 svchost
992 svchost
4996 TSTheme
4240 slui
4904 taskhost
452 csrss
4340 csrss
4 System
1164 spoolsv
1988 slClient
2760 MSExchangeHMWorker
0 Idle
Performance Counters Layout information: FileMappingNotFoundException for category MSExchange Active Manager Client : Microsoft.Exchange.Diagnostics.FileMappingNotFoundException: Cound not open File mapping for name Global\netfxcustomperfcounters.1.0msexchange active manager client. Error Details: 2
at Microsoft.Exchange.Diagnostics.FileMapping.OpenFileMapping(String name, Boolean writable)
at Microsoft.Exchange.Diagnostics.PerformanceCounterMemoryMappedFile.Initialize(String fileMappingName, Boolean writable)
at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.GetAllInstancesLayout(String categoryName)
... and...
A transient failure has occurred. The problem may resolve itself. Diagnostic information:
Microsoft.Exchange.Data.DataSourceOperationException: The request failed. The remote server returned an error: (503) Server Unavailable. ---> Microsoft.Exchange.WebServices.Data.ServiceRequestException: The request failed. The remote server returned an error: (503) Server Unavailable. ---> System.Net.WebException: The remote server returned an error: (503) Server Unavailable.
at System.Net.HttpWebRequest.GetResponse()
at Microsoft.Exchange.WebServices.Data.EwsHttpWebRequest.Microsoft.Exchange.WebServices.Data.IEwsHttpWebRequest.GetResponse()
at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.GetEwsHttpWebResponse(IEwsHttpWebRequest request)
--- End of inner exception stack trace ---
at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.GetEwsHttpWebResponse(IEwsHttpWebRequest request)
at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.ValidateAndEmitRequest(IEwsHttpWebRequest& request)
at Microsoft.Exchange.WebServices.Data.ExchangeService.InternalFindFolders(IEnumerable`1 parentFolderIds, SearchFilter searchFilter, FolderView view, ServiceErrorHandling errorHandlingMode)
at Microsoft.Exchange.WebServices.Data.ExchangeService.FindFolders(FolderId parentFolderId, SearchFilter searchFilter, FolderView view)
at Microsoft.Exchange.Data.Storage.Management.EwsStoreDataProvider.InvokeServiceCall[T](Func`1 callback)
--- End of inner exception stack trace ---
at Microsoft.Exchange.Data.Storage.Management.EwsStoreDataProvider.InvokeServiceCall[T](Func`1 callback)
at Microsoft.Exchange.Data.Storage.Management.EwsStoreDataProvider.GetOrCreateFolderCore(String folderName, FolderId parentFolder, Func`1 creator)
at Microsoft.Exchange.Data.Storage.Management.AsyncOperationNotificationDataProvider.GetDefaultFolder()
at Microsoft.Exchange.Data.Storage.Management.EwsStoreDataProvider.<>c__DisplayClass1b`1.<InternalFindPaged>b__13()
at Microsoft.Exchange.Data.Storage.Management.EwsStoreDataProvider.InvokeServiceCall[T](Func`1 callback)
at Microsoft.Exchange.Data.Storage.Management.EwsStoreDataProvider.<InternalFindPaged>d__21`1.MoveNext()
at Microsoft.Exchange.Data.Storage.Management.AsyncOperationNotificationDataProvider.<GetNotificationDetails>d__4.MoveNext()
at System.Linq.Enumerable.WhereEnumerableIterator`1.MoveNext()
at Microsoft.Exchange.Servicelets.CertificateNotificationServicelet.RemoveAllNotification()
at Microsoft.Exchange.Servicelets.CertificateNotificationServicelet.UpdateDataInMbx(List`1 certificates)
at Microsoft.Exchange.Servicelets.CertificateNotificationServicelet.Work()
I've tried all sorts of recommended fixes but none have worked so far:
ADSIEdit and remove msExchCanaryData0 data
Reinstall Exchange multiple times
Rebooted multiple times
This article: http://social.technet.microsoft.com/Forums/exchange/en-US/08d3777c-dc03-4411-8c87-7db37d2f406a/exchange-2013-owa-login-error-http-500?forum=exchangesvrclients
Rebooted DCs multiple times (no exchange servers are DCs)
I'm sure I've left out a few troubleshooting steps since I've been working at this for two days. Can anybody offer any advice? I'm at my wits end here...

Hi,
Please check whether the mail.mydomain.com is pointed to your Exchange 2010 or Exchange 2013. Please run the following command to check your OWA virtual directores and ECP virtual directories:
Get-OwaVirtualDirectory -ShowMailboxVirtualDirectories | Select Identity,name,Internalurl,ExternalUrl,*auth*
Get-EcpVirtualDirectory -ShowMailboxVirtualDirectories | Select Identity,name,Internalurl,ExternalUrl,*auth*
In IIS manager > Default Web Site, please make sure Anonymous Authentication is Enabled in Authentication. Confirm that "Require SSL" is checked on the SSL Settings of the default web site.
Regards,
Winnie Liang
TechNet Community Support

Exchange 2013 SP1 RU4 Public Folder Permissions

Hi All,
Exchange 2013 SP1 RU4 Public Folder Permissions
We have a weird problem after migrating our PF from Exchange 2010 to 2013.
Users do not have permission to create or delete in PF even thou they have owner permissions.
Example:-
I have created a '\test1' folder in the root which has the following permissions (this works OK):-
Myself - Owner
Default - Author
Anonymous - None
I have created another folder '\admin\test2' folder which has the same permissions as above but i get the "cannot create the folder. you don't have appropriate permissions to perform this operation"
I get this problem across all of the folders that were migrated. clean folders created at the root with the correct permission function as per expected.
Regards
Paul Sheldon

Hi,
I recommend you use the Get-PublicFolderClientPermission -Identity publicfolder command to check the client access permissions to a public folder.
If possible, please remove permission and re-add permission to check the result.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Exchange 2013 SP1 on Windows Server 2008 R2 Enterprise - BSOD after DAG creation

Hi,
We are running Exchange 2007 SP3 RU13 on Windows 2003 R2 with SP2 in a 2003 native AD environment and recently decided to upgrade to Exchange 2013. We installed a pair of new DELL R420 servers running Windows 2008 R2 Enterprise then threw Exchange 2013 SP1
onto them. This all went fine and the servers are running stable.
We connected the second NIC of each server to the other via a separate switch, the second NIC has Client for MS Networks and File/Printer Sharing disabled plus a totally separate subnet with no DNS or GW address assigned. DAG setup was run and completed
OK. I created the DAG network in Exchange and enabled replication, I also left replication enabled across the production LAN. Finally, I went into the advanced network settings and made sure the replication network was below the production network in the binding
order.
After an hour or two the BSOD's started.. both servers would crash within a few minutes of each other and reboot with a Kernel Panic. I have attached the contents of the dump file below. This seems to happen every few hours and it always seems to be the
server hosting the passive DB copies crashes first, followed by the server hosting the active copies. Note that if we disable the replication NIC on both servers they do not crash.
I got the impression from somewhere that perhaps the servers had mixed up the binding order and were trying to use the replication network as primary, losing access to AD and rebooting (which I have read is the behaviour for Exchange now). It appears the
Exchange Health service has killed WININIT which causes the crash.
Thanks!!!
The crash dump text is below:
CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa80192ebb30, Terminating object
Arg3: fffffa80192ebe10, Process image file name
Arg4: fffff80001dc37b0, Explanatory message (ascii)
Debugging Details:
PROCESS_OBJECT: fffffa80192ebb30
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: wininit
FAULTING_MODULE: 0000000000000000
PROCESS_NAME: MSExchangeHMWo
BUGCHECK_STR: 0xF4_MSExchangeHMWo
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80001e4cab2 to fffff80001abebc0
STACK_TEXT:
fffff880`0d7f39c8 fffff800`01e4cab2 : 00000000`000000f4 00000000`00000003 fffffa80`192ebb30 fffffa80`192ebe10 : nt!KeBugCheckEx
fffff880`0d7f39d0 fffff800`01df7abb : ffffffff`ffffffff fffffa80`1bcf3060 fffffa80`192ebb30 fffffa80`383ea060 : nt!PspCatchCriticalBreak+0x92
fffff880`0d7f3a10 fffff800`01d77674 : ffffffff`ffffffff 00000000`00000001 fffffa80`192ebb30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x17486
fffff880`0d7f3a60 fffff800`01abde53 : fffffa80`192ebb30 fffff880`ffffffff fffffa80`1bcf3060 00000000`00000000 : nt!NtTerminateProcess+0xf4
fffff880`0d7f3ae0 00000000`7772157a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`34eed638 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7772157a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: wininit.exe
FAILURE_BUCKET_ID: X64_0xF4_MSExchangeHMWo_IMAGE_wininit.exe
BUCKET_ID: X64_0xF4_MSExchangeHMWo_IMAGE_wininit.exe
Followup: MachineOwner

Hi Darrkon,
I suggest checking the status of the HealthMailbox on each of servers.
Also try to re-create the mailbox. You can safely delete and recreate health mailboxes.
Be aware that any local Managed Availability probes that are using the these mailboxes will fail until the Microsoft Exchange Health Manager is restarted. Once that service is restarted, it will recreate any mailboxes that it needs.
More details in the following similar thread, just for your reference:
BSOD after creating DAG
http://social.technet.microsoft.com/Forums/exchange/en-US/44d1cd98-cba1-4ed0-b0e7-8aa76ee3eabc/bsod-after-creating-dag
Thanks
Mavis
Mavis Huang
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 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 SP1 users not receiving quota warning email message

Hi,
We are on Exchange 2013 SP1 and Exchange 2010 SP3 co-existence mode and currently migrating users from Exchange 2010 to 2013. We have noticed that users are not receiving email message when their mailbox quota warning when its near to maximum limit.
If I log in via OWA it shows the notification (Pop up) that your mailbox is almost full but no message received in email. Most of the users do not log into OWA but only uses Outlook.
It looks like other people are also seeing this similar issue but I am unable to find any solution for it.
How users will know if their mailbox is almost full if they are traveling and only using Mobile phone for emails to send and receive.
Thanks,
Raman

Hi Thanks for your response. Our Quota is set on Database level. I am seeing these event ids as well.
Log Name: Application Source: MSExchangeIS Date: 12/31/2014 10:07:12 PM Event ID: 1077 Task Category: MAPI Level: Warning Keywords: Classic User: N/A Computer: Exch2013mail01.company.com Description: The mailbox e3d48b23-0740-46ab-89f7-3b035dacf28f on database
326f0997-4fe5-4b31-873b-6a3396e7a91c is approaching its storage limit. A notification has been sent to the user. This warning will not be sent again for at least twenty four hours.
========================
Log Name: Application Source: MSExchange Store Driver Submission Date: 12/31/2014 10:07:12 PM Event ID: 1012 Task Category: MSExchangeStoreDriverSubmission Level: Error Keywords: Classic User: N/A Computer: Exch2013mail01.company.com Description: The store
driver failed to submit event 8237691 mailbox e3d48b23-0740-46ab-89f7-3b035dacf28f MDB 326f0997-4fe5-4b31-873b-6a3396e7a91c and couldn't generate an NDR due to exception Microsoft.Exchange.MailboxTransport.StoreDriverCommon.InvalidSenderException at Microsoft.Exchange.MailboxTransport.Shared.SubmissionItem.SubmissionItemUtils.CopySenderTo(SubmissionItemBase
submissionItem, TransportMailItem message) at Microsoft.Exchange.MailboxTransport.Submission.StoreDriverSubmission.MailItemSubmitter.GenerateNdrMailItem() at Microsoft.Exchange.MailboxTransport.Submission.StoreDriverSubmission.MailItemSubmitter.<>c__DisplayClass1.<SubmitNdrForFailedSubmission>b__0()
at Microsoft.Exchange.MailboxTransport.StoreDriverCommon.StorageExceptionHandler.RunUnderTableBasedExceptionHandler(IMessageConverter converter, StoreDriverDelegate workerFunction).
Raman

BSOD after upgrading to exchange 2013 SP1

Hi,
I Have 4 servers, x2 Mailbox and x2 CAS, all with 2008 r2 OS, Mailboxes with DAG. Problem started after I upgraded all servers from Exchange 2013 CU3 to Ex13 SP1. All Servers are in Vmware, same hardware.
All servers getting BSOD, error is same as some other posts in Internet about:
CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa8007ab4890, Terminating object
Arg3: fffffa8007ab4b70, Process image file name
Arg4: fffff800019de7b0, Explanatory message (ascii)
Debugging Details:
PROCESS_OBJECT: fffffa8007ab4890
IMAGE_NAME: wininit.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: wininit
FAULTING_MODULE: 0000000000000000
PROCESS_NAME: MSExchangeHMWo
BUGCHECK_STR: 0xF4_MSExchangeHMWo
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
LAST_CONTROL_TRANSFER: from fffff80001a67ab2 to fffff800016d9bc0
LOGS:
RecoveryActionLogs: ForceReboot-ServerName -ActiveDirectoryConnectivityServerReboot: Throttling rejected the operation
RecoveryActionLogs: ForceReboot-ServerName -ActiveDirectoryConnectivityConfigDCServerReboot: Throttling
rejected the operation
Recovery Action Failed. (ActionId=RestartService, ResourceName=ServerName.contoso.com, Requester=ActiveDirectoryConnectivityRestart,
InstanceId=140408.062707.65292.001, ActualStartTime=2014-04-08T15:27:07.6529270Z, ActualEndTime=2014-04-08T15:27:07.7777262Z, ErrorMessage=Service ServerName.contoso.com was not found on computer '.'.)
when Server restarts, logs show
Bugcheck action reported by server 'ServerName' initiated by responder 'ActiveDirectoryConnectivityServerReboot'
Recovery Action Started. (ActionId=ForceReboot, ResourceName=ServerName, Requester=ActiveDirectoryConnectivityServerReboot, InstanceId=140408.063307.93261.004, ExpectedToFinishAt=2014-04-08T15:38:07.9326175Z
Recovery Action Succeeded. (ActionId=ForceReboot, ResourceName=ServerName, Requester=ActiveDirectoryConnectivityServerReboot, InstanceId=140408.063307.93261.004, ActualStartTime=2014-04-08T15:33:07.9326175Z, ActualEndTime=2014-04-08T15:35:07.0828500Z)
I found that it could restart like many times in a day, but
Throttling does not let it, just one restart per day.
I already spent four days trying to find problem but no luck.
Try'ed to add override
Add-GlobalMonitoringOverride
-Identity Exchange\ActiveDirectoryConnectivityConfigDCServerReboot -ItemType Responder -PropertyName Enabled -PropertyValue 0 -Duration 60.00:00:00
but
after
(Get-WinEvent
-LogName Microsoft-Exchange-ActiveMonitoring/responderdefinition | % {[XML]$_.toXml()}).event.userData.eventXml | ?{$_.Name -like “ActiveDirectoryConnectivityConfigDCServerReboot"} | ft name,enabled
still shows propertyValue 1, and servers are restarting no matter what, I just dont want to disable HealtManager
Service.
Try'ed to recreate all performance counters, did'nt worked
Try'ed to create prefered domain controller, did'nt worked
Try'ed to play with healthSet 'AD', but there is almost no information about it in TechNet, so I just looked which services are unhealthy, sometimes it shows ActiveDirectoryConnectivityServer
or ActiveDirectoryConnectivityConfigDCServer as unhealthy, but after few minutes it goes to
healthy, problem that Exchange could already restart the server
mainly reason I think is:
The AD Health Set has detected a problem with Server.contoso.com at 2014.04.09 06:33:11. The Health Manager is reporting that ActiveDirectoryConnectivityProbe/Server.contoso.com
Failed with Error message: Search took 1518 ms. Threshold 800 ms. Attempts to auto-recover from this condition have failed and requires Administrator attention. Exception Details: System.Exception: Search took 1518 ms. Threshold 800 ms
I really need some new ideas...
EDIT: Exchange 2013 sp1 works perfectly in test lab, there are cloned machines from production, the only difference is DomainController, there is just one (server), no replications, and no subdomains (production domain have subdomain).
Running DCDiag shows no errors

Hello Everyone,
We have 2 CAS and 4 Mailbox server that were installed from SP1 and seeing the same issue. This is a clean install still with no mailboxes migrated over as of yet. Opened a case with MS. also ran:
Add-GlobalMonitoringOverride
-Identity Exchange\ActiveDirectoryConnectivityConfigDCServerReboot -ItemType Responder -PropertyName Enabled -PropertyValue 0 -Duration 60.00:00:00
Waiting
for MS to get back and to see how this workaround does. Seems like the original issue was not resolved completely?
Will
post back when we get an update. Changing the DirectoryActiveMonitoringContext.xml and the above workaround do not seem suitable for us. We would like to see a complete resolution for this.
Good
luck!

ActiveSync is not working properly after migrating to new Exchange 2013 SP1 server?!

Few weeks ago we have added new Exchange 2013 SP1 onto our existing Exchange 2007 environment. I have migrated my mailbox to the new Ex2013 server. Everything (send/receive - internally/externally, OWA, OutlookAnywhere) for me and the existing Ex2007
users works fine. The only thing I have trouble with is the ActiveSync! After migrating to the new Ex2013 server my phone stops getting new emails…, existing Ex2007 users don’t have any problems with their mobile phones.
I did ActiveSync test for my user account with ActiveSync Tester and here is what I have:
As you can see from the error above ActiveSync Tester detects ActiveSync on Ex2013 server however something wrong there with form-based auth?! I can’t see any differences in settings for ActiveSync virtual folders in Ex2007 and Ex2013
virtual folders?!
What I’m missing here?! Please help.

Check if the Exchange Servers group does not have the appropriate permission to the mailbox object in Active Directory.
To check whether inheritance is disabled on the user:
1.Open Active Directory Users and Computers.
2.On the menu at the top of the console, click View > Advanced Features.
3.Locate and right-click the mailbox account in the console, and then click Properties.
4.Click the Security tab.
5.Click Advanced.
6.Make sure that the check box for "Include inheritable permissions from this object's parent" is selected.
Ref:
http://technet.microsoft.com/en-us/library/dd439375(v=exchg.80).aspx
Also check the Virtual directory authentication
Microsoft-Server-ActiveSync
•Basic authentication
•SSL required
•Requires 128-bit encryption
Ref:
http://technet.microsoft.com/en-us/library/gg247612(v=exchg.150).aspx
Check the IIS log if you are able to find any error message on it
Exchange Queries

Error in moving exchange 2010 mailboxes to Exchange 2013 SP1 during migration

Dear All,
We were running Exchange 2010 SP3 with MBX/HT/CAS role in single server. Now we are migrating our exchange 2010 to Exchange 2013 SP1. After configuring co-existence and during the mailbox move from Exchange 2010 to Exchange 2013 SP1, we are facing below
error. Please help to troubleshot. As per our search on net, people were suggesting that it can be due to not able to resolve NetBIOS name. We checked same and we are able to ping both servers by NetBIOS and FQDN names.
[PS] C:\Windows\system32>New-MoveRequest -Identity
'[email protected]' -TargetDatabase "CI-DB01"
MapiExceptionNetworkError: Unable to make connection to the server. (hr=0x80004005, ec=2423)
Diagnostic context:
    Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 1722
    Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 323
    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0
    Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 0
    Lid: 62184
    Lid: 16280   dwParam: 0x0 Msg: EEInfo: ComputerName: n/a
    Lid: 8600    dwParam: 0x0 Msg: EEInfo: ProcessID: 6004
    Lid: 12696   dwParam: 0x0 Msg: EEInfo: Generation Time: 0414-08-21T09:10:43.8970000Z
    Lid: 10648   dwParam: 0x0 Msg: EEInfo: Generating component: 18
    Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 1237
    Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 313
    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0
    Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 0
    Lid: 62184
    Lid: 16280   dwParam: 0x0 Msg: EEInfo: ComputerName: n/a
    Lid: 8600    dwParam: 0x0 Msg: EEInfo: ProcessID: 6004
    Lid: 12696   dwParam: 0x0 Msg: EEInfo: Generation Time: 0414-08-21T09:10:43.8970000Z
    Lid: 10648   dwParam: 0x0 Msg: EEInfo: Generating component: 18
    Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 10060
    Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 311
    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0
    Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 3
    Lid: 12952   dwParam: 0x0 Msg: EEInfo: prm[0]: Long val: 22964
    Lid: 15000   dwParam: 0x0 Msg: EEInfo: prm[1]: Pointer val: 0x0
    Lid: 15000   dwParam: 0x0 Msg: EEInfo: prm[2]: Pointer val: 0xFE01A8C000000000
    Lid: 62184
    Lid: 16280   dwParam: 0x0 Msg: EEInfo: ComputerName: n/a
    Lid: 8600    dwParam: 0x0 Msg: EEInfo: ProcessID: 6004
    Lid: 12696   dwParam: 0x0 Msg: EEInfo: Generation Time: 0414-08-21T09:10:43.8970000Z
    Lid: 10648   dwParam: 0x0 Msg: EEInfo: Generating component: 18
    Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 10060
    Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 318
    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0
    Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 0
    Lid: 53361   StoreEc: 0x977
    Lid: 51859
    Lid: 33649   StoreEc: 0x977
    Lid: 43315
    Lid: 58225   StoreEc: 0x977
    Lid: 39912   StoreEc: 0x977
    Lid: 54129   StoreEc: 0x977
    Lid: 50519
    Lid: 59735   StoreEc: 0x977
    Lid: 59199
    Lid: 27356   StoreEc: 0x977
    Lid: 65279
    Lid: 52465   StoreEc: 0x977
    Lid: 60065
    Lid: 33777   StoreEc: 0x977
    Lid: 59805
    Lid: 52487   StoreEc: 0x977
    Lid: 19778
    Lid: 27970   StoreEc: 0x977
    Lid: 17730
    Lid: 25922   StoreEc: 0x977
    + CategoryInfo          : NotSpecified: (:) [New-MoveRequest], RemoteTransientException
    + FullyQualifiedErrorId : [Server=Exch01,RequestId=f6886977-92f1-4148-991b-aa76b449aff5,TimeStamp=8/21/2014 9:1
   0:43 AM] [FailureCategory=Cmdlet-RemoteTransientException] 7FCC37,Microsoft.Exchange.Management.RecipientTasks.New
MoveRequest
+ PSComputerName        : Exch01.domain.local
Please help as we are stuck here!!
Thanks in advance!!

Can yo ping server by name not by FQDN? e.g. ping server1.
Make sure firewall/antivirus not blocking communication. Disable antivirus and try
Thanks,
MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Cannot write email body in OWA with Exchange 2013 SP1 CU6

Hi,
I have a problem with Exchange 2013 SP1 with CU6.
All of OWA user cannot write in the body of email. They can write the Object and the recipient but they cannot select body and write the body message. We have try with multiple Web brother and desactivate all Add-on but the problem still there...
The only way that works is to respond to an email, and in that case, it's working, we can write normally in the body of email.
Have you an idea ?
Thanks in advance!
Sebastien

Hi,
After contacting Microsoft support, we have found the solution.
The problem appear after we have recently install the patch described in this KB 2997209:
https://support.microsoft.com/kb/2997209?wa=wsignin1.0
But on 2013 Mailbox Server, Echange is not installed in the default path C:\ but on D:\
So we have to manually copy the content of folder D:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\Owa\prem\15.0.995.29 in the folder 15.0.995.31 (MAKE a BACKUP of FOLDER BEFORE!)
No need to reboot, or restart IIS, it's working after that!
@+
Sébastien

Exchange 2013 SP1 On-prem - Disable Outlook Anonymous NTLM?

Similar Messages

Maybe you are looking for