Anyone have experience with WSRM on 2008 R2?

Home Forums Server Operating Systems Windows Server 2008 / 2008 R2 Anyone have experience with WSRM on 2008 R2?

Viewing 1 post (of 1 total)
  • Author

  • shmengie

    Hi there:

    I got a couple questions about WSRM; hopefully someone here is familiar.

    First, and hopefully easiest: Can anyone tell me the difference between managing policy and profile policy? A couple of Google hits, but they all say “…Then choose managing policy or profile policy” without explaining what the hell those are!

    Now, the meat of the issue…

    We have a service running on this 2008 R2 box. It’s basically a messaging service between servers ( This was implemented by a developer who is no longer here, but this box is in production. This service shows as being well within parameters in task manager at 81MB. But, the second that service starts, the used RAM climbs up and pegs at 100% used (32GB box), while still showing normal usage in task manager. So, I thought I could use WSRM to limit the service to, say, 12GB, leaving me 10GB headroom. But…

    After configuring WSRM, the service is still pegging the RAM. So, can Windows manage a poorly written service that has a gaping memory leak? If so, what the heck am I doing wrong? Should I be more concerned with the working memory or the committed memory? Or both?

    Oh, I know…can someone just do this for me? :)


Viewing 1 post (of 1 total)

You must be logged in to reply to this topic.

Don't leave your business open to attack! Come learn how to protect your AD in this FREE masterclass!REGISTER NOW - Thursday, December 2, 2021 @ 1 pm ET

Active Directory (AD) is leveraged by over 90% of enterprises worldwide as the authentication and authorization hub of their IT infrastructure—but its inherent complexity leaves it prone to misconfigurations that can allow attackers to slip into your network and wreak havoc. 

Join this session with Microsoft MVP and MCT Sander Berkouwer, who will explore:

  • Whether you should upgrade your domain controllers to Windows Server
    2019 and beyond
  • Achieving mission impossible: updating DCs within 48 hours
  • How to disable legacy protocols and outdated compatibility options in
    Active Directory

Sponsored by: