For production I'd leave them unchecked so people don't see a performance hit each time the worker process gets recycled. Depending on the number of users, 2G for the worker process might be fairly reasonable. I have sites where the average is 3G, but they have lots of users. If memory continues to climb, and depending on your version, there *may* be some memory creep going on. I'm not sure LANDesk would agree with that very general statement, but if you are on an older version, it might be prudent to look at an upgrade or make enquires of your local support team for any issues on the system you are running.
But as I said, 2G is pretty OK for a small/medium sized system. .NET apps love memory and will generally consume about 60% of available memory if the demand is there to use it.