There have been a couple of similar reports here. 20M seems to be
the default value when the system (for one reason or another)
doesn't like the values that you have set.
Here are 2 quotes from previous posts that I saved:
"I FINALLY got it to change, but only by going through the Wizard
under Help. THEN, the Min/Max values were blank, and when I set
them to 4095 and restarted, it showed VMem as 4095."
"I had a similar problem with a server that was recommending a
high virtual memory setting due to large amount of physical RAM.
If you tried to set the recommended setting, the server would
reset to 20MB. In the end I found that the total of Paging file
and Registry size had to be less than 4096. Once I set this if
worked OK."
--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---
"Victor" <(E-Mail Removed)> wrote in
news:17efa01c449ae$8aac2090$(E-Mail Removed):
> I have a Terminal Server that has a virtual Memory
> problem. The currently allocated amount of memory is
> stable at 20 MB even though the Paging file has an initial
> size of 1536 MB and Maximum size of 2000 MB. No changes
> after a reboot. When I set the maximum values to different
> value the currently allocated amount changes but when the
> system doesn't tell me to reboot. After a reboot the
> allocated amount is back to 20 MB. If I change both values
> I'm asked to reboot and immediately I'm back to 20MB.
> I have no warning in my event log.
>
> Any ideas?
> Thanks in advance, Victor