exchange, windows server

my server went to back pressure. is process explorer good tool to check which computers or servers caused this.
pramod1Asked:
Who is Participating?
 
Scott CSenior Systems EnginerCommented:
Take a look at these 2 articles.

From <https://technet.microsoft.com/en-us/library/bb201658(v=exchg.141).aspx
From <https://technet.microsoft.com/en-us/library/bb201658.aspx

Probably not process explorer as it's a shortage of resources that cause back pressure.

Connections are being refused due to lack of resources.  Check disk space first.
1
 
pramod1Author Commented:
it has enough disk space free
0
 
pramod1Author Commented:
I need to know the connections which could cause high lsass.exe and in turn back pressure
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
pramod1Author Commented:
I have physical memory : 10gb, virtual : average virtual :9.6
0
 
IvanSystem EngineerCommented:
Hi,

as ScottCha said, those 2 articles as good one.

By default, the high level of memory utilization by all processes is 94 percent of total physical memory.
9.6 out of 10Gb is 96%. That means that there is high level of memory utilization and message dehydration is occurring.

Regards,
Ivan.
0
 
pramod1Author Commented:
yes I see that in error, but as per logs I see lot of active sync connections at that time, is that the primary issue
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.