RE: Stop CAS from being used

2011-06-09 Thread Sobey, Richard A
Set-CASServer -Identity  -AutodiscoverServiceInternalUri fdqn.owa.url

Replace fqdn.owa.url with the name of your published OWA address, including 
https://.

Your users will still connect to the server, but they'll be redirected to your 
production boxes for the response.

Any good?

From: bounce-9351734-8066...@lyris.sunbelt-software.com 
[mailto:bounce-9351734-8066...@lyris.sunbelt-software.com] On Behalf Of Rimmel, 
Carl
Sent: 09 June 2011 15:50
To: MS-Exchange Admin Issues
Subject: Stop CAS from being used

We are running Exchange 2007 and have recently stood up a new CAS server that 
we are using for testing a 3rd party product.  We would like to stop users from 
hitting this new CAS server via autodiscover but I can't find anything that 
definitively states a way to do this.

I realize that the Service-Connection-Point that is published in AD is probably 
the primary reason that this server is being hit.

Can I just delete the SCP from AD to stop our clients from hitting this new CAS 
server?

Will removing the SCP cause anything else to fail?

Any suggestions would be appreciated.

Thanks

==

CONFIDENTIALITY NOTICE: This email contains information from the sender that

may be CONFIDENTIAL, LEGALLY PRIVILEGED, PROPRIETARY or otherwise protected

from disclosure. This email is intended for use only by the person or entity

to whom it is addressed. If you are not the intended recipient, any use,

disclosure, copying, distribution, printing, or any action taken in reliance

on the contents of this email, is strictly prohibited. If you received this

email in error, please contact the sending party by reply email, delete the

email from your computer system and shred any paper copies.



Note to Patients: There are a number of risks you should consider before using

e-mail to communicate with us. See our Privacy Policy and Henry Ford My Health

at www.henryford.com for more detailed information. 
If you do not believe that

our policy gives you the privacy and security protection you need, do not send

e-mail or Internet communications to us.

==

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe exchangelist

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe exchangelist

RE: Stop CAS from being used

2011-06-09 Thread Rimmel, Carl
We already did that and it works fine but still doesn't actually take the 
server "out of the mix".

From: Sobey, Richard A [mailto:r.so...@imperial.ac.uk]
Sent: Thursday, June 09, 2011 11:19 AM
To: MS-Exchange Admin Issues
Subject: RE: Stop CAS from being used

Set-CASServer -Identity  -AutodiscoverServiceInternalUri fdqn.owa.url

Replace fqdn.owa.url with the name of your published OWA address, including 
https://.

Your users will still connect to the server, but they'll be redirected to your 
production boxes for the response.

Any good?

From: bounce-9351734-8066...@lyris.sunbelt-software.com 
[mailto:bounce-9351734-8066...@lyris.sunbelt-software.com] On Behalf Of Rimmel, 
Carl
Sent: 09 June 2011 15:50
To: MS-Exchange Admin Issues
Subject: Stop CAS from being used

We are running Exchange 2007 and have recently stood up a new CAS server that 
we are using for testing a 3rd party product.  We would like to stop users from 
hitting this new CAS server via autodiscover but I can't find anything that 
definitively states a way to do this.

I realize that the Service-Connection-Point that is published in AD is probably 
the primary reason that this server is being hit.

Can I just delete the SCP from AD to stop our clients from hitting this new CAS 
server?

Will removing the SCP cause anything else to fail?

Any suggestions would be appreciated.

Thanks

==

CONFIDENTIALITY NOTICE: This email contains information from the sender that

may be CONFIDENTIAL, LEGALLY PRIVILEGED, PROPRIETARY or otherwise protected

from disclosure. This email is intended for use only by the person or entity

to whom it is addressed. If you are not the intended recipient, any use,

disclosure, copying, distribution, printing, or any action taken in reliance

on the contents of this email, is strictly prohibited. If you received this

email in error, please contact the sending party by reply email, delete the

email from your computer system and shred any paper copies.



Note to Patients: There are a number of risks you should consider before using

e-mail to communicate with us. See our Privacy Policy and Henry Ford My Health

at www.henryford.com<http://www.henryford.com> for more detailed information. 
If you do not believe that

our policy gives you the privacy and security protection you need, do not send

e-mail or Internet communications to us.

==

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com>
with the body: unsubscribe exchangelist

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com>
with the body: unsubscribe exchangelist

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe exchangelist

RE: Stop CAS from being used

2011-06-09 Thread Robinson, Chuck
I believe the following will do what you want.

Get-ClientAccessServer CAS01 | Set-ClientAccessServer 
-AutoDiscoverServiceInternalUri $null

Chuck Robinson
___
Sr. Solutions Architect
MCITP:EA, Messaging / MCSE: Messaging
EMC Consulting
Mobile: 973-865-0394
chuck.robin...@emc.com
www.emc.com/consulting

Transforming Information Into Business Results

From: Rimmel, Carl [mailto:crimm...@hfhs.org]
Sent: Thursday, June 09, 2011 10:50 AM
To: MS-Exchange Admin Issues
Subject: Stop CAS from being used

We are running Exchange 2007 and have recently stood up a new CAS server that 
we are using for testing a 3rd party product.  We would like to stop users from 
hitting this new CAS server via autodiscover but I can't find anything that 
definitively states a way to do this.

I realize that the Service-Connection-Point that is published in AD is probably 
the primary reason that this server is being hit.

Can I just delete the SCP from AD to stop our clients from hitting this new CAS 
server?

Will removing the SCP cause anything else to fail?

Any suggestions would be appreciated.

Thanks

==

CONFIDENTIALITY NOTICE: This email contains information from the sender that

may be CONFIDENTIAL, LEGALLY PRIVILEGED, PROPRIETARY or otherwise protected

from disclosure. This email is intended for use only by the person or entity

to whom it is addressed. If you are not the intended recipient, any use,

disclosure, copying, distribution, printing, or any action taken in reliance

on the contents of this email, is strictly prohibited. If you received this

email in error, please contact the sending party by reply email, delete the

email from your computer system and shred any paper copies.



Note to Patients: There are a number of risks you should consider before using

e-mail to communicate with us. See our Privacy Policy and Henry Ford My Health

at www.henryford.com for more detailed information. 
If you do not believe that

our policy gives you the privacy and security protection you need, do not send

e-mail or Internet communications to us.

==

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe exchangelist

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe exchangelist