I have a fairly new Exchange 2010 (4gigs of memory) box with CAS and HUB roles installed. No mailboxes or stores have been configured. One thing I am noticing is that after using powershell sometimes, the memory usuage from w3wp.exe goes way up. It has previously caused exhausted resource messages in the event viewer. w3wp.exe was using about 1 Gig. I am able to free up virtuaul memory by recycling the MSExchangePowerShellAppPool and I am considering scheduling recycling in IIS. I want to know if others have seen this issue and if there are any thoughts about scheduling recycling for this specific app pool.

You shouldn't need to do anything like recycling the AppPool to get the memory use down. I have a server holding all three roles at home and have a PowerShell session open all the time and it is consuming about 200mb, so something isn't right there. Usual causes for odd memory things are third party applications. Do you have anything other than Exchange installed on the server? Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

Besides turn off some third party applications, please also refer to the following article to troubleshoot the issue. http://support.microsoft.com/kb/919790 Thanks. NovakPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Thanks for the help troubleshooting this issue although my server doesn't any 3rd party apps at the moment. The links will come in handy. I haven't had another problem since I recycled the app pool although my current memory usuage for the powershell app pool is 517mb (private bytes) and 3.1gb (virtual bytes) which still seems high. The memory will rise after opeing the EMC or powershell and never goes back down. I will try rebooting the server at some point and see if things change at all. What caused the exhausted resources initially was from running memory intensive powershell get commands piped with set commands (changing remotepowershellenabled flags for users). It seems even after closing the shell, the memory was still tied up which caused problems. The private bytes was close to a gig but I don't recall what the virutal bytes was at. Just the fact the memory doesn't seem to be given back to the system after closing the EMC or shell is making me still lean towards enabling a set recyling schedule off hours.

OK. Please take some times to reboot the server to check the result. If the issue persists, please post the exhausted resource messages in Event Viewer here for research. Thanks. NovakPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.