Re: SBS2003 STD Exchange 2003 SP1 errata?
From: Frank McCallister (anonymous)
Date: 06/30/04
- Next message: Stephanie Doakes [MSFT]: "RE: Exchange issue"
- Previous message: Stephanie Doakes [MSFT]: "RE: are Guest accounts needed?"
- In reply to: Mark Medici: "SBS2003 STD Exchange 2003 SP1 errata?"
- Next in thread: Les Connor [SBS MVP]: "Re: SBS2003 STD Exchange 2003 SP1 errata?"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 30 Jun 2004 12:44:29 -0500
Hi Mark
>From another NG from MS
snip-
Exchange 2003 SP1 is safe to install on SBS 2003 and we do recommend you to
install it. However, there are a couple of tweaks needed:
1. By default, after running CEICW, the component will set the Default
Domain property on the corresponding IIS sub-directories (under
Authentication -> Access Control) as following:
/Exchange/: \
/Microsoft-Server-ActiveSync/: SBS domain name
/OMA/: SBS domain name
However, Exchange 2003 SP1 replaces the OWA logon screen (Program
Files\Exchsrvr\bin\auth\usa\logon.asp) and it caused OWA now to ask for
domain\username instead of simply just the username. To fix this problem
before SBS SP1 comes out, you can edit the SP1 logon.asp or (which is
recommended) just add the domain name in the Exchange virtual directory,
Directory Security, Authentication and access control, Default Domain.
The same goes to the OWA and Server-ActiveSync sub-sites, we can just set
the "SBS domain name" back. This is considering the fact that some PPC or
mobile phone cannot use the reverse backslash character when inputting
credential.
2. After installing Exchange 2003 SP1 to SBS server, you may notice that
store.exe is consuming more memory than before. It also occurs on normal
Exchange 2K3 server, the only difference is that SBS has the monitoring
component which will send out e-mail notification once the threshold is
reached.
This issue occurs no matter the amount of the memory is below or above 1
GB. In addition, many of the partners has also implemented the suggestions
in the following KB, it makes things better but the store memory usage is
still higher than SP1 was applied:
815372 How to Optimize Memory Usage in Exchange Server 2003
http://support.microsoft.com/?id=815372
Prior to SP1, the database cache bytes are counted as mapped bytes. In SP1,
the database cache is counted under private bytes. Thus, the private bytes
will be considerably higher (about 940 MB higher) for SP1 than before, and
mapped bytes will be correspondingly lower. If people are using private
bytes as the measure of memory, then yes, it changed dramatically between
Ti and Ti SP1. Working set and Virtual Bytes should be mostly unaffected.
Since SBS Monitoring is counting the Private Bytes, it will be 940MB higher
than before. This won't impact the server's normal operation.
Workaround is to add 1000 or above to the counter so that you will not
receive the warning that frequently. The best is to run a performance
monitor over for a few days and get an average Private Byte of Store.exe
(Set Performance Object to Process, and Counter to Private Bytes, and
Instance to Store). Once you have the average/baseline, then maybe increase
it by 30%-40% and use it for the threshold, and then set it by using the
steps outlined in the following knowledge base article:
867628 Monitoring programs report that the Store.exe process consumes
additional memory after you install Exchange Server 2003 SP1
http://support.microsoft.com/?id=867628
You may also check Susan's Website for more information:
http://www.sbslinks.com/exchange.htm
NOTE: This response contains a reference to a third party World Wide Web
site. Microsoft is providing this information as a convenience to you.
Microsoft does not control these sites and has not tested any software or
information found on these sites; therefore, Microsoft cannot make any
representations regarding the quality, safety, or suitability of any
software or information found there. There are inherent dangers in the use
of any software found on the Internet, and Microsoft cautions you to make
sure that you completely understand the risk before retrieving any software
from the Internet.
3. You may see the error below after install Exchange 2003 SP1 and then
logon to OWA and try to spell check if the /exchweb/bin virtual directory
doesn't have the default domain specified.
The spelling in this item can't be checked. Try again later.
This does NOT occur if you haven't changed the "Default Domain" value under
"/Exchange" from "/" to your domain name and using "Domain name\User name"
to logon OWA.
To resolve this issue, change the domain name setting for ExchWeb/Bin to
match Exchage. To do so:
A. Open SBS Server Management console.
B. Expand Advanced Management -> Internet Information Services -> server
name -> Web Sites -> Default Web Site.
C. Right-click Exchange and click Properties.
D. On the Directory Security tab, click Edit under the "Authentication and
access control" section. Note down the setting configured in "Default
domain".
F. In IIS Manager, expand ExchWeb, right-click Bin and click Properties.
G. On the Directory Security tab, click Edit in the "Authentication and
access control" section, configure the default domain setting as Exchange
virtual directory.
H. Restart IIS service by running "iisreset".
In addition, I'd suggest you make a full backup of your server immediately
before and after you upgrade your servers to Exchange 2003 SP1. Making this
backup will ensure that you have a valid backup of your server should you
require one. Making a full backup of servers is considered a best practice
for all upgrades.
snip -
Frank McCallister
COMPUMAC
"Mark Medici" <mark@dbma.EXAMPLE.com> wrote in message
news:udcuigsXEHA.2824@TK2MSFTNGP10.phx.gbl...
> Excuse me if this has already been addressed. I can only view the past 2
> weeks worth of newsgroup traffic, and could not find definitive
> information
> regarding Exchange 2003 SP1 on SBS2003. I also searched MS Knowledgebase
> for issues (only the STORE.EXE memory alert problem is returned).
>
> I have a customer running SBS on a Compaq server that uses a single
> Pentium-4 with HTT (Hyperthreading Technology). They are experiencing
> frequent MSExchangeAL Event ID 8331 errors, (unexpected exception in
> lservagent.cpp), and are having occasional setup problems in Outlook (The
> name could not be resolved. The name could not be matched to a name in the
> address list). According to MSKB article 837444, these issues are related
> and are fixed in Exchange 2003 SP1.
>
> So I need to decide which is worse: the current problems or the new
> problems
> that SP1 introduces. I'm not confident I understand the issues with
> Exchange 2003 SP1 on SBS 2003. All I've found so far are:
>
> 1. Spurrious STORE.EXE memory utilization errors
> 2. OWA users must logon with domain\username instead of just
> username.
> 3. OMA users also must logon with domain\username
>
> I also found one message that indicates Remote Web Workplace is somehow
> affected.
>
> Is this the full extents of the problems observed installing Ex2k3-SP1 on
> SBS2k3? These seem to be issues that can easily be worked-around. Or are
> there other, more troublesome issues introduced?
>
> Thanks
>
>
- Next message: Stephanie Doakes [MSFT]: "RE: Exchange issue"
- Previous message: Stephanie Doakes [MSFT]: "RE: are Guest accounts needed?"
- In reply to: Mark Medici: "SBS2003 STD Exchange 2003 SP1 errata?"
- Next in thread: Les Connor [SBS MVP]: "Re: SBS2003 STD Exchange 2003 SP1 errata?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
