I'm set up a new Exchange 2003 EE on a server running Windows 2003 Standard
Edtion. My new server has 4 GB RAM. I'll add /3 gb /userva=3030 in
boot.ini. But I
m wondering if I need to modify the registry for
HeapDeCommitFreeBlockThreshold. Some articles said that it's not necessary
but monitor the performance of Exchage. Some said you should do it in the
first place. So, is it a good practice to do it with checking how Exchange
works first?

Thanks,

Re: memory setting for new installation by Ed

Ed
Wed Sep 19 10:50:07 PDT 2007

I wouldn't change it unless you see symptoms that indicate that it's
necessary.
--
Ed Crowley
MVP - Exchange
"Protecting the world from PSTs and brick backups!"

"Chris" <Chris@discussions.microsoft.com> wrote in message
news:D2C5CBE1-33D3-42FF-B01D-33B6F316DC38@microsoft.com...
> I'm set up a new Exchange 2003 EE on a server running Windows 2003
> Standard
> Edtion. My new server has 4 GB RAM. I'll add /3 gb /userva=3030 in
> boot.ini. But I
> m wondering if I need to modify the registry for
> HeapDeCommitFreeBlockThreshold. Some articles said that it's not
> necessary
> but monitor the performance of Exchage. Some said you should do it in the
> first place. So, is it a good practice to do it with checking how
> Exchange
> works first?
>
> Thanks,
>



Re: memory setting for new installation by Chris

Chris
Wed Sep 19 15:28:04 PDT 2007

I got event id 9665 without it. After the registery change for
HeapDeCommitFreeBlockThreshold it disappeared. Does that mean I do need it?
I haven't created any mailbox on this server yet. No user access at all.

"Ed Crowley [MVP]" wrote:

> I wouldn't change it unless you see symptoms that indicate that it's
> necessary.
> --
> Ed Crowley
> MVP - Exchange
> "Protecting the world from PSTs and brick backups!"
>
> "Chris" <Chris@discussions.microsoft.com> wrote in message
> news:D2C5CBE1-33D3-42FF-B01D-33B6F316DC38@microsoft.com...
> > I'm set up a new Exchange 2003 EE on a server running Windows 2003
> > Standard
> > Edtion. My new server has 4 GB RAM. I'll add /3 gb /userva=3030 in
> > boot.ini. But I
> > m wondering if I need to modify the registry for
> > HeapDeCommitFreeBlockThreshold. Some articles said that it's not
> > necessary
> > but monitor the performance of Exchage. Some said you should do it in the
> > first place. So, is it a good practice to do it with checking how
> > Exchange
> > works first?
> >
> > Thanks,
> >
>
>
>

Re: memory setting for new installation by John

John
Wed Sep 19 15:58:53 PDT 2007

You should set heapdecommitfreeblockthreshold to 0x40000. If you run exbpa,
it'll tell you this.


"Chris" <Chris@discussions.microsoft.com> wrote in message
news:D2C5CBE1-33D3-42FF-B01D-33B6F316DC38@microsoft.com...
> I'm set up a new Exchange 2003 EE on a server running Windows 2003
> Standard
> Edtion. My new server has 4 GB RAM. I'll add /3 gb /userva=3030 in
> boot.ini. But I
> m wondering if I need to modify the registry for
> HeapDeCommitFreeBlockThreshold. Some articles said that it's not
> necessary
> but monitor the performance of Exchage. Some said you should do it in the
> first place. So, is it a good practice to do it with checking how
> Exchange
> works first?
>
> Thanks,
>