Friday, September 16, 2011

Does the LSASS.EXE have enough memory, on your Domain Controller?


The Key performance of the DC (Domain Controller) is the how much of the database can be cached into the memory. The process is responsible from this task is the LSAAA.EXE caching mechanism, releases cache to free memory when OS requires it. The Domain controller who are not strong enough (low memory) will not be able cache as much and this will be noticeable performance issue on the Domain controller. Therefore it is a good idea to make sure the DC's have enough memory installed on them and the other processes are not eating up from DC memory.
The core Process LSASS.EXE is also responsible from replication, authentication, Net logon, and KCC. If the LSASS is not happy this is going to cause Busy and tired DC (Domain Controller). Any other process other than LSASS MUST is investigated on the domain controllers if they are utilizing most of the CPU resources on a Domain Controller.
The similar behavior in Exchange is the Store.exe if you remember.
What is LSASS.EXE, The LSAS management of local security authority domain authentication and Active Directory Management?
The Lsass.exe process is responsible for management of local security authority domain authentication and Active Directory management. This process handles authentication for both the client and the server, and it also governs the Active Directory engine. The Lsass.exe process is responsible for the following components:
  • Local Security Authority
  • Net Logon service
  • Security Accounts Manager service
  • LSA Server service
  • Secure Sockets Layer (SSL)
  • Kerberos v5 authentication protocol
  • NTLM authentication protocol
Lsass.exe usually uses 100 MB to 300 MB of memory. Lsass.exe uses the same amount of memory no matter how much RAM is installed in the computer. However, when a larger amount of RAM is installed, Lsass can use more RAM and less virtual memory
Try to use Server Performance Advisor V1.0 this is FREE Utility from Microsoft. Service Performance Advisor is a server performance diagnostic tool developed to diagnose root causes of performance problems in a Windows Server™ 2003 operating system

Free eBook: Microsoft Office 365: Connect and Collaborate Virtually Anywhere, Anytime


We are very excited to announce that we are able to offer Microsoft Office 365: Connect and Collaborate Virtually Anywhere, Anytime (ISBN 9780735656949), by Katherine Murray, as a free eBook.
For details on this book, including the Table of Contents, see our previous blog post here.
Updates to this eBook, as well as additional eBook formats, will become available in the future, so check this blog for updates.
To download your free PDF eBook, click here.http://blogs.msdn.com/b/microsoft_press/archive/2011/08/17/free-ebook-microsoft-office-365-connect-and-collaborate-virtually-anywhere-anytime.aspx

DAG: Beyond the “A”: An excellent Exchange 2010 DAG


Definitions

We all know that in the Microsoft Exchange world DAG stands for “Database Availability Group”.
Database – because on a highly available Exchange 2010 Mailbox server, the database, not the server, is the unit ofavailability and it is the database that can be failed over or switched over between multiple servers within a DAG. This concept is known as database mobility.
Group – because the scope of availability is determined by Mailbox servers in a DAG combined in a failover cluster and working together as a group.
Availability – this word seems to be the least obvious and the most obfuscated term here (and also referred to by both other terms). Ironically, it has a straightforward mathematical definition and plays an important role in understanding overall Exchange design principles.
For more details Exchange Team Blog: