Memory Leak 2008 R2 Domain Controller

[Davit2005]

Trying to figure out what is possibly causing the memory leak on a 2008 R2 Domain Controller.

 

The DC was built a few years ago before I arrived but over the last 6 to 12 months has been using gradually high memory usage on a few occasions causing logon issues. The memory usage is ok after a reboot.

 

The DC is Virtual running on ESXi 5.1 with 8GB and 1 CPU Core/Socket

 

I done the usual of running all windows updates a few times but still the memory keeps rising.

 

I've heard people mention UMDH.exe but can't seem to find it anywhere.

Edited November 20, 2014 by Davit2005

[Boredguy]

We have memory leaks on both our 2008 R2 DC's (physical servers) but I can generally pin it down to the Volume Shadow Copy as it is normally chugging along happily until it starts a backup.

 

Thankfully we don't have too many issues so once a month I give it a reboot and it's fine for a while.

 

One of these days I'll find enough money to get some new servers and replace the DC's with nice shiny 2012R2 ones.

[Michael]

What role(s) does this server run? These days it's either a database or a bad driver (typically) printer which causes all memory to be used up quickly. What processes in Task Manager are using the most memory?

[Arthur]

KB3002301?

[Michael]

Also, depending how many virtual instances you have, if they're all sharing 8GB of ram, that isn't a large amount. It's not unrealistic to have 16GB, 24GB or 32GB of memory even for a few virtual instances.

[Davit2005]

What role(s) does this server run? These days it's either a database or a bad driver (typically) printer which causes all memory to be used up quickly. What processes in Task Manager are using the most memory?

 

They are strict DC's with DNS role only, I am pretty strict about these. The DC in question is just a Global Catalog.

 

The Isass.exe and TrustedInstaller.exe seem to be the main hogs.

 

Also, depending how many virtual instances you have, if they're all sharing 8GB of ram, that isn't a large amount. It's not unrealistic to have 16GB, 24GB or 32GB of memory even for a few virtual instances.

 

Sorry, my bad. The actual Virtual Server has 8GB of RAM and is currently sitting on a host with 128GB total. We have vMotion over 20 ESXi hosts that range from 64GB to 254GB (on shared storage) and the Virtuals move around as they please.

 

Thanks all for help

Edited November 20, 2014 by Davit2005

[Michael]

I presume these are running 2008 R2 + SP1, including the recommended update rollup KB2775511 ?

 

8GB of memory is more than plenty for just a DC. How many users is it processing/supporting/authenticating? You could try temporarily disabling the Windows Update service to isolate the issue with regards to the TrustedInstaller.exe process. As for Isass.exe, have a look here at this Microsoft KB.

[Davit2005]

I presume these are running 2008 R2 + SP1, including the recommended update rollup KB2775511 ?

 

8GB of memory is more than plenty for just a DC. How many users is it processing/supporting/authenticating? You could try temporarily disabling the Windows Update service to isolate the issue with regards to the TrustedInstaller.exe process. As for Isass.exe, have a look here at this Microsoft KB.

 

We probably have 2000 users trying to authenticate in all with 3 DC's (2 Virtual, 1 Physical)

 

It's just the one DC which seems to be mostly the problem.

 

I've disabled Updates on the DC for now so that should calm it down.

Edited November 20, 2014 by Davit2005

[Michael]

If it's literally just a DC, you could transfer the roles as appropriate and re-build it from scratch.