RE: NLB name and OWA

2010-03-25 Thread Michael B. Smith 
It's easier to configure if the NLB matches the external domain, but it really 
doesn't matter.

But I would recommend you name the RPCCAA the same as the external OWA domain.

[Definitive guidance is expected Real Soon Now. The "truth" is that there are 
several workable configurations.]

Regards,

Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com

From: Russ Patterson [mailto:rus...@gmail.com]
Sent: Thursday, March 25, 2010 10:55 AM
To: MS-Exchange Admin Issues
Subject: NLB name and OWA

Hello all -

We've decided to go with a WIndows NLB cluster for a CAS array on Exchange 
2010. I'm seeing conflicting info about naming & was hoping the experts here 
would chime in & help us out.

The name of the NLB cluster - should it be the same as the name we give 
end-users to access OWA externally? Some folks are saying no, others are saying 
yes. As an example - nlb.ourdomain.local for the NLB cluster, and endusers use 
mail.ourdomain.com for owa.

If we don't do that, will we need to add the nlb cluster name to our cert 
request?

Is the only reason to use the same name for both to reduce the number of names 
(& therefore cost) on the cert request?

Is the only reason to use different names to reduce troubleshooting confusion, 
if it becomes necessary?

Thanks!

RE: NLB name and OWA

2010-03-25 Thread Michael B. Smith 
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/alternative;
boundary="_000_206E053EFD8D754CB67242D59E47B8371DCCB627Win2008R2Ex2010_"
MIME-Version: 1.0

--_000_206E053EFD8D754CB67242D59E47B8371DCCB627Win2008R2Ex2010_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

STOP! I got it exactly backwards.

You do NOT want the RPCCAA to match the Outlook Anywhere connection point. =
That will cause Outlook to attempt to use RPC to connect to the RPCCAA firs=
t, causing about a 30 second startup delay.

I apologize!

Regards,

Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com

From: Michael B. Smith
Sent: Thursday, March 25, 2010 11:16 AM
To: MS-Exchange Admin Issues
Subject: RE: NLB name and OWA

It's easier to configure if the NLB matches the external domain, but it rea=
lly doesn't matter.

But I would recommend you name the RPCCAA the same as the external OWA doma=
in.

[Definitive guidance is expected Real Soon Now. The "truth" is that there a=
re several workable configurations.]

Regards,

Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com

From: Russ Patterson [mailto:rus...@gmail.com]
Sent: Thursday, March 25, 2010 10:55 AM
To: MS-Exchange Admin Issues
Subject: NLB name and OWA

Hello all -

We've decided to go with a WIndows NLB cluster for a CAS array on Exchange =
2010. I'm seeing conflicting info about naming & was hoping the experts her=
e would chime in & help us out.

The name of the NLB cluster - should it be the same as the name we give end=
-users to access OWA externally? Some folks are saying no, others are sayin=
g yes. As an example - nlb.ourdomain.local for the NLB cluster, and enduser=
s use mail.ourdomain.com<http://mail.ourdomain.com> for owa.

If we don't do that, will we need to add the nlb cluster name to our cert r=
equest?

Is the only reason to use the same name for both to reduce the number of na=
mes (& therefore cost) on the cert request?

Is the only reason to use different names to reduce troubleshooting confusi=
on, if it becomes necessary?

Thanks!

--_000_206E053EFD8D754CB67242D59E47B8371DCCB627Win2008R2Ex2010_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

http://schemas.microsoft.com/office/2004/12/omml"; xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
-->STOP! I got it exactly backwards. You do NOT w=
ant the RPCCAA to match the Outlook Anywhere connection point. That will ca=
use Outlook to attempt to use RPC to connect to the RPCCAA first, causing a=
bout a 30 second startup delay. I apologize! =
Regards,&n=
bsp;Michael B. Smith<=
p class=3DMsoNormal>=
Consultant and Exchange MVPhttp://TheEssentia=
lExchange.com From: Michael B. Smith <=
br>Sent: Thursday, March 25,=
 2010 11:16 AMTo: MS-Exc=
hange Admin IssuesSubject: RE: NLB name and OWA It’s easier to configure=
 if the NLB matches the external domain, but it really doesn’t matter=
. But I w=
ould recommend you name the RPCCAA the same as the external OWA domain. [Definitive g=
uidance is expect

RE: NLB name and OWA

2010-03-25 Thread Neil Hobson 
I'd just like to add to what Michael said and note that in my last
deployment of Exchange 2010 the NLB cluster name didn't match the external
OWA name and also that the NLB cluster name was not in the cert list, but
the CAS array name obviously was.  It's important to distinguish between NLB
cluster names, CAS array names and OWA names - not to mention EAS names,
Outlook Anywhere names, etc, etc.  Everything appears to be fine in this
deployment so far.  

 

From: Russ Patterson [mailto:rus...@gmail.com] 
Sent: 25 March 2010 14:55
To: MS-Exchange Admin Issues
Subject: NLB name and OWA

 

Hello all - 

 

We've decided to go with a WIndows NLB cluster for a CAS array on Exchange
2010. I'm seeing conflicting info about naming & was hoping the experts here
would chime in & help us out. 

 

The name of the NLB cluster - should it be the same as the name we give
end-users to access OWA externally? Some folks are saying no, others are
saying yes. As an example - nlb.ourdomain.local for the NLB cluster, and
endusers use mail.ourdomain.com for owa.

 

If we don't do that, will we need to add the nlb cluster name to our cert
request? 

 

Is the only reason to use the same name for both to reduce the number of
names (& therefore cost) on the cert request? 

 

Is the only reason to use different names to reduce troubleshooting
confusion, if it becomes necessary?

 

Thanks!