TechNet
Get flash to fully experience Pearltrees
Topic Last Modified: 2012-10-16 Understanding storage options and requirements for the Mailbox server role in Microsoft Exchange Server 2013 is an important part of your Mailbox server storage design solution. Contents Storage architectures Physical disk types
Understanding Storage Configuration: Exchange 2010 Help
Applies to: Exchange Server 2013 Topic Last Modified: 2013-03-15 Protocol logging records the SMTP conversations that occur on Send Connectors and Receive connectors as part of message delivery. Estimated time to complete: 15 minutes You need to be assigned permissions before you can perform this procedure or procedures. To see what permissions you need, see the "Transport Service", "Front End Transport service", "Mailbox Transport service", "Receive connectors" and "Send connectors" entries in the Mail Flow Permissions topic. You can use the Exchange admin center (EAC) to enable or disable protocol logging for Send connectors and Receive connectors in the Transport service on Mailbox servers, and for Receive connectors in the Front End Transport service on Client Access servers.
Configure Protocol Logging: Exchange 2010 Help
For a list of current recommendations to help alleviate these issue, click here Recently, there has been a rash of performance issues on Exchange 2007 Mailbox servers where they become unresponsive due to excessive paging. Previously this was tracked down to .NET garbage collection not occurring properly which caused managed services to consume excessive amounts of memory.
Excessive Paging on Exchange
Windows Disk Timeouts and Exchange Server 2010 - Exchange Team Blog
A few months Bruce Langworthy wrote an excellent article regarding some new recommendations for setting the Windows Disk Timeout value - http://blogs.msdn.com/b/san/archive/2011/08/15/the-windows-disk-timeout-value-understanding-why-this-should-be-set-to-a-small-value.aspx . This post got me thinking about Exchange and how we deal with I/O problems. If you haven't read Bruce’s article, it explains that the default disk timeout of 60 seconds means that Windows will not report the hung I/O for 60 seconds and won’t retry the I/O for 8 minutes. 8 minutes is far too long to wait before retrying a hung IO, so Microsoft is releasing new guidance recommending changing the Windows Disk Timeout setting to a value that aligns with your storage architecture.
In my quest to better understand the interworking of how NTFS stores information on disk, I have been researching what happens to a file as it grows in size and complexity. The reason I’m after this knowledge is so I can better troubleshoot certain storage issues. Recently, I realized that I’d stuffed my head with enough information to make a pretty good blog. Read along as I explain what I call ‘the four stages of file growth’. Before we can address file growth, we need to first look at how NTFS works under the covers. Let’s start out with some basics.
NTFS File Growth
Hi, Ned here. I’m a Technical Lead in Directory Services out of Charlotte, NC. Today I’m going to talk a little bit about a common customer question: how do I leverage group policy to deploy custom registry settings?
Process Monitor and Registry via GP
Inside Microsoft, we maintain a repository of tools written by our engineers and technical staff. Many of the tools that are posted are very specific to Microsoft engineering— tools to help developers and testers better manage their project in our internal source control system, provide better visibility into our internal bug/issue tracking system, etc. Since these tools are very specific to the Microsoft environment, most of them don't get released externally. About eight months ago, I came across a tool in the repository called Remote Desktop Connection Manager ("RDCMan" for short) written by Julian Burger, one of our principal developers on the Windows Live Experiences team. RDCMan is a central place where you can organize, group, and manage your various Remote Desktop connections. This is particularly useful for system administrators, developers, testers, and lab managers who maintain groups of computers and connect to them frequently.
Every Windows Sysadmin Need This!