| Author |
Message |
Steven
Guest
|
 Posted:
Wed Dec 07, 2005 5:58 pm Post subject:
Bug in ExBPA (current version)? |
|
|
when running ExBPA against a Window's 2003 SP1\Exchange 2003 SP1 cluster
that we just build the health check complains about two things:
-the 3gb switch is not set (this is not accurate)
-hot-add memory config (not a problem..this is accurate)
The 3GB switch is indeed set on both nodes of the cluster:
--
[boot loader]
timeout=5
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windows Server 2003,
Enterprise" /fastdetect /NoExecute=OptOut /3gb /userva=3030 /maxmem=4096
C:\CMDCONS\BOOTSECT.DAT="Microsoft Windows Recovery Console" /cmdcons
--
Is it that the gb part is not in CAPs?
|
|
| Back to top |
|
 |
Steven
Guest
|
| Posted:
Wed Dec 07, 2005 5:58 pm Post subject:
Re: Bug in ExBPA (current version)? |
|
|
Oh and to add to this ExBPA detects that the cluster nodes have 9983 MB of
memory detected when they only have 4gb installed (3.75gb according to the
OS)
On Wed, 07 Dec 2005 11:39:20 -0500, Steven <spresley@qualcomm.com> wrote:
| Quote: | when running ExBPA against a Window's 2003 SP1\Exchange 2003 SP1 cluster
that we just build the health check complains about two things:
-the 3gb switch is not set (this is not accurate)
-hot-add memory config (not a problem..this is accurate)
The 3GB switch is indeed set on both nodes of the cluster:
--
[boot loader]
timeout=5
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windows Server 2003,
Enterprise" /fastdetect /NoExecute=OptOut /3gb /userva=3030 /maxmem=4096
C:\CMDCONS\BOOTSECT.DAT="Microsoft Windows Recovery Console" /cmdcons
--
Is it that the gb part is not in CAPs?
|
--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ |
|
| Back to top |
|
|
Steven
Guest
|
| Posted:
Wed Dec 07, 2005 5:58 pm Post subject:
Re: Bug in ExBPA (current version)? |
|
|
Oh and to add to this ExBPA detects that the cluster nodes have 9983 MB of
memory detected when they only have 4gb installed (3.75gb according to the
OS).
On Wed, 07 Dec 2005 11:39:20 -0500, Steven <spresley@qualcomm.com> wrote:
| Quote: | when running ExBPA against a Window's 2003 SP1\Exchange 2003 SP1 cluster
that we just build the health check complains about two things:
-the 3gb switch is not set (this is not accurate)
-hot-add memory config (not a problem..this is accurate)
The 3GB switch is indeed set on both nodes of the cluster:
--
[boot loader]
timeout=5
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windows Server 2003,
Enterprise" /fastdetect /NoExecute=OptOut /3gb /userva=3030 /maxmem=4096
C:\CMDCONS\BOOTSECT.DAT="Microsoft Windows Recovery Console" /cmdcons
--
Is it that the gb part is not in CAPs?
|
--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
|
|
| Back to top |
|
|
Paul Bowden [MSFT]
Guest
|
| Posted:
Thu Dec 08, 2005 12:37 am Post subject:
Re: Bug in ExBPA (current version)? |
|
|
Hi Steven,
Would you mind exporting the output XML file, then zip and send it to
pbowden@microsoft.REMOVETHIS.com (e-mail address intentionally obscured).
I'll take a look, and then report back to the newsgroup on the problem (or
to you personally, if you prefer).
Many thanks,
--
Paul Bowden
Program Manager
Exchange Server Best Practices Analyzer
http://www.microsoft.com/exchange/analyzers
This posting is provided "AS IS" with no warranties, and confers no rights.
"Steven" <spresley@qualcomm.removethis.com> wrote in message
news:op.s1fbglz653e3d3@spresley3.na.qualcomm.com...
| Quote: | Oh and to add to this ExBPA detects that the cluster nodes have 9983 MB of
memory detected when they only have 4gb installed (3.75gb according to the
OS).
On Wed, 07 Dec 2005 11:39:20 -0500, Steven <spresley@qualcomm.com> wrote:
when running ExBPA against a Window's 2003 SP1\Exchange 2003 SP1 cluster
that we just build the health check complains about two things:
-the 3gb switch is not set (this is not accurate)
-hot-add memory config (not a problem..this is accurate)
The 3GB switch is indeed set on both nodes of the cluster:
--
[boot loader]
timeout=5
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windows Server 2003,
Enterprise" /fastdetect /NoExecute=OptOut /3gb /userva=3030 /maxmem=4096
C:\CMDCONS\BOOTSECT.DAT="Microsoft Windows Recovery Console" /cmdcons
--
Is it that the gb part is not in CAPs?
--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ |
|
|
| Back to top |
|
|
Paul Bowden [MSFT]
Guest
|
| Posted:
Thu Dec 08, 2005 1:59 am Post subject:
Re: Bug in ExBPA (current version)? |
|
|
FYI - I worked with Steven offline. It looks as if the server in question
wasn't rebooted after the Boot.ini changes were put in place.
--
Paul Bowden
Program Manager
Exchange Server Best Practices Analyzer
http://www.microsoft.com/exchange/analyzers
This posting is provided "AS IS" with no warranties, and confers no rights.
"Paul Bowden [MSFT]" <pbowden@microsoft.REMOVETHIS.com> wrote in message
news:%230fmF11%23FHA.924@TK2MSFTNGP12.phx.gbl...
| Quote: | Hi Steven,
Would you mind exporting the output XML file, then zip and send it to
pbowden@microsoft.REMOVETHIS.com (e-mail address intentionally obscured).
I'll take a look, and then report back to the newsgroup on the problem (or
to you personally, if you prefer).
Many thanks,
--
Paul Bowden
Program Manager
Exchange Server Best Practices Analyzer
http://www.microsoft.com/exchange/analyzers
This posting is provided "AS IS" with no warranties, and confers no
rights.
"Steven" <spresley@qualcomm.removethis.com> wrote in message
news:op.s1fbglz653e3d3@spresley3.na.qualcomm.com...
Oh and to add to this ExBPA detects that the cluster nodes have 9983 MB
of
memory detected when they only have 4gb installed (3.75gb according to
the
OS).
On Wed, 07 Dec 2005 11:39:20 -0500, Steven <spresley@qualcomm.com> wrote:
when running ExBPA against a Window's 2003 SP1\Exchange 2003 SP1 cluster
that we just build the health check complains about two things:
-the 3gb switch is not set (this is not accurate)
-hot-add memory config (not a problem..this is accurate)
The 3GB switch is indeed set on both nodes of the cluster:
--
[boot loader]
timeout=5
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windows Server 2003,
Enterprise" /fastdetect /NoExecute=OptOut /3gb /userva=3030 /maxmem=4096
C:\CMDCONS\BOOTSECT.DAT="Microsoft Windows Recovery Console" /cmdcons
--
Is it that the gb part is not in CAPs?
--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in