Could be more indepth - config examples would be nice.

hughesg4a 11/4/2006 2:56:15 AM

Quote: "You can override this limitation with the addition of /PAE and /3GB switches to the boot.ini file, which changes the server to physical address extension (PAE) mode and lets your non-kernel applications use up to 3GB of memory. Keep in mind that all of a server's applications—including those we forget about, such as antivirus or monitoring software—must share those 3GB."
Isn't it so, that by using the /3Gb switch, you increase the user memory part for each process (which is not shared between applications) to 3Gb, and decrease the kernel memory part (which is shared between all applications) to 1 Gb?
Gé Brander

ge@familie-brander.nl 10/27/2005 4:26:37 AM

Be sure to remember, that if you plan on deploying x64 systems, Windows server 2003 x64 doesn't for the time being support .NET 1.1 - that means e.g. no Reporting Services.

Jacob5/13/2005 1:18:17 AM

You bring up some excellent points. One thing I would like to point out, however, is that if an organization already has multiple 32-bit servers in place in either an active-passive or active-active setup, there is a way to go to N+1 without the "gotchas" and without upgrading everything to 64-bit. Simply make the "+1" server, i.e. the failover server, a 64-bit server which would be able to handle several 32-bit active clusters failing at the same time. True, they would be relagating their most powerful hardware to a role where it is usually not (hopefully never) used, but that is cheaper than going to an all 64-bit setup or multiple active-passive clusters and avoids the gotchas of the active-active scenario.

Andrew Steitz
acsteitz_(a)_yahoo.com

STEVEN5/5/2005 1:06:34 PM