Comments on: Exchange Server 2016 Client Access Namespace Configuration

By: pleschi

pleschi — Sat, 07 May 2022 19:38:54 +0000

In reply to herp-derpo. excellent approach. I did so.

By: pleschi

pleschi — Sat, 07 May 2022 19:37:16 +0000

Paul,
Thank you so much for your effort and tremendous explanations. It cleaned up my configuration and is a tutorial for me. I learned allot from your articles .
Thanks again!

By: herp-derpo

herp-derpo — Fri, 23 Apr 2021 19:34:22 +0000

In reply to Aleksey. how about edit the command yourself and do a find-replace for Get-ClientAccessServer to Get-ClientAccessService?

By: Aleksey

Aleksey — Sun, 31 Jan 2021 21:36:05 +0000

Hi Paul,
thanks for u great site.
One question. Script used old command The Get-ClientAccessServer cmdlet
You have plane for update scripts for using new command Get-ClientAccessService ?

By: Charlie Campbell

Charlie Campbell — Mon, 17 Aug 2020 11:56:29 +0000

Ive always used your script when setting up new Exchange boxes, saves a lot of time and hassle, But now I come to a very odd issue, with one specific user I cannot get Outlook 2016/19 to connect to the Exchange server 2016 (migrated from 2010, either through the wizard or via the 32 bit client app, its doesn’t want to find the EAS, yet with other accounts its fine. removing the profile doesn’t work, Ive had to roll back to Outlook 2013 to get it to work, the only difference with this user AD is that it was renamed ages ago, CAS is setup as should be as per your script work fine for other accounts, Any ideas guys?

By: LMS

LMS — Wed, 22 Jul 2020 08:20:57 +0000

Thanks for Your great post Paul.

We have one Q. Recently we modified our company name. We updated all user primary mail IDs with new name and also created Autodiscover SRV record which points to old Autodiscover (_Autodiscover._tcp.newdomain.com = Autodiscover.olddomain.com). Also the UPN has been configured for the new domain. The autodiscover works fine with Outlook anywhere, but for ActiveSync it doesn’t work as we have to change the server URL manually. We didn’t modify the external and internal URLs, still uses the same old and also the wild card doesn’t contain new SMTP domain name. What might be the cause for this, do we need to include new domain name with wild card SAN (we will modify all URL in another weeks with new name)

By: Jatinder Bawa

Jatinder Bawa — Wed, 15 Apr 2020 13:08:28 +0000

Dear Paul,

i have installed exchange server 2019 3 month back,

I am very upset because i am not able to stop spammer to use my smtp relay.

i have created the new receive connector for smtp rely for anonymous users for external use.

below are the permission for this new receive connector

User ExtendedRights
—- ————–
ms-Exch-SMTP-Accept-Authoritative-Domain-Sender
{ms-Exch-SMTP-Submit
ms-Exch-Accept-Headers-Routing
ms-Exch-SMTP-Accept-Any-Sender
ms-Exch-SMTP-Accept-Any-Recipient

User ExtendedRights
—- ————–
MS Exchange\Externally Secured Servers
ms-Exch-SMTP-Submit
ms-Exch-Accept-Headers-Routing
ms-Exch-Bypass-Message-Size-Limit
ms-Exch-SMTP-Accept-Authoritative-Domain-Sender
ms-Exch-SMTP-Accept-Any-Sender
ms-Exch-SMTP-Accept-Exch50
ms-Exch-Bypass-Anti-Spam
ms-Exch-SMTP-Accept-Any-Recipient
ms-Exch-SMTP-Accept-Authentication-Flag

daily i am fighting with alot of external spammer.

they have shoot 1 lacs mail daily through my SMTP relay server

i have installed the GFI essential , but still not able to find the proper solution.

please provide the best solution for external SMTP relay so no body can access the same from outside.

please provide the solution asap.

my domain is seasia.in

By: LMS

LMS — Thu, 19 Mar 2020 09:14:54 +0000

Thanks a lot Paul

We are looking for best way to re-configure the namespaces with new domain name.

We have changed our company name and modified primary mail address to @newdomain.com and kept old address @olddomain.com as secondary. Created MX records and SRV record with external DNS which points to old as _Autodiscover._tcp.newdomain.com = Autodiscover.olddomain.com and all users can connect with @newdomain.com. As of now all users are using old address space olddomain.com for mail access. We bought new wild card certificate with *.newdomain.com & *.olddomain.com as SANs and want to re configure the name spaces with minimum interruption for end users.

Our setup consists of 2 X Exchange 2016 servers with F5 load balancer and published the URLs using Firewall. Internally & externally we are using same name space (mail.olddomain.com, internally it points to the load balancer IP and externally to the Firewall IP).

Thanks in advance

By: Scott Renton

Scott Renton — Wed, 22 Jan 2020 21:17:39 +0000

Two questions, if you would:

1. I have a machine who’s current FQDN is mail.contoso.com. I want external name of new exhcange to be mail.contoso.com. Is it ok to do the external name setup? the external name will not be updated in public DNS and firewall until after new server is all setup. if that is an issue, I can use another name.
2. Do you setup namespace before or after setting up SSL certificates? If you change external name, do you need to reissue CSR & setup new SSL cert?

By: Brian Hampson

Brian Hampson — Wed, 09 Oct 2019 17:11:15 +0000

In reply to

Paul Cunningham

. But then you leak internal infrastructure information via the SANs on the certificates.