7,920 questions
@Kael Yao
PS please reply so that i can accept your answer
Service Connection Point will not set on either 2007 or 2013 Exchanges
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(35.2, 40%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMS%3C/text%3E%3C/svg%3E)
Matt Saul
96
Reputation points
don't ask but doing a temporary coexistence of EX2007 and EX2013.
Then a jump to EX2019
Have used the Microsoft Deployment Assistant extensively and have both up and running but am unable to set the CAS url's on either Exchange 2007 nor on the new Exchange 2013 server. can run the EX management shell commands no errors just nothing changes - both are blank.
I am an enterprise admin and organisation management member
Matt
Exchange | Exchange Server | Management
{count} votes
-
Matt Saul 96 Reputation points
2021-10-27T15:57:37.953+00:00 sorry forgot to add disjointed domains :-
pc suffix and email suffix are different
Have set all virtuals using email suffix
have SSL SAN installed with mail.email-domain, plus legacy. on ex2007
Sign in to comment
Accepted answer
-
Matt Saul 96 Reputation points
2021-11-02T11:29:21.323+00:00 -
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(246.4, 22%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKY%3C/text%3E%3C/svg%3E)
Kael Yao 37,746 Reputation points Moderator2021-11-03T01:26:52.59+00:00 Hi,
Glad to hear your issue has been resolved!I have converted my reply to an answer.
Please feel free to accept it as the answer to the question if it actually helps with this issue.
Thanks for the sharing.
Sign in to comment -
7 additional answers
Sort by: Most helpful
-
Kael Yao 37,746 Reputation points Moderator
2021-10-28T07:35:39.47+00:00 Hi Matt.
Did you mean if running the following command in EMS:
Get-ClientAccessServer | fl name,autodiscoverserviceinternaluriThe autodiscoverserviceinternaluri part both are blank.
If it is the case, please open ADSIEdit and locate the path in the following screenshot,check if the value of the serviceBindingInformation is also blank:
If it is also blank, please try manually adding the value and see if it can help with this issue.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.-
Matt Saul 96 Reputation points
2021-10-28T09:46:03.27+00:00 Hi @Kael Yao ,
Yes that is what i meant
Thanks for your prompt repsonse,
I did check in ADSIEDIT before posting and oddly
the ex2013 has
https://Ex2013serverhostname.domain/autodiscover/autodiscover.xml
and the EX2007 has
https://autodiscover.domain/autodiscover/autodiscover.xmI "thought" both should be pointing to the EX2013 server hostname i.e.
https://ex2013serverhostname..domain/autodiscover/autodiscover.xmlMatt
-
Kael Yao 37,746 Reputation points Moderator
2021-10-29T01:30:24.15+00:00 Hi,
I "thought" both should be pointing to the EX2013 server hostname i.e.
https://ex2013serverhostname..domain/autodiscover/autodiscover.xmlYes. It should both be pointing to Exchange 2013.
It is also mentioned in the Microsoft Deployment Assistant.
Sign in to comment -
-
Matt Saul 96 Reputation points
2021-10-29T08:03:40.577+00:00 also would you mind clarifying - is it ok to use https://autodiscover.domain.autodiscover.autodiscover.xml
OR should it be https://exchangeserver-hostname.domain.etc ??-
Kael Yao 37,746 Reputation points Moderator
2021-10-29T09:26:50.55+00:00 Hi,
i will edit via ADSIEDIT, but question remains why don't they show in EX managmement shell.
No overly concerned that they dont show BUT will the ADSIEDIT inputs work if "not seen" in the shell ??Would you mind posting a screenshot of the result of Get-ClientAccessServer | fl name,autodiscoverserviceinternaluri command?
(Don't forget to hide your personal information)also would you mind clarifying - is it ok to use https://autodiscover.domain.autodiscover.autodiscover.xml
OR should it be https://exchangeserver-hostname.domain.etc ??Yes.
Since it is the internal Autodiscover URL, you can use https://autodiscover.domain/autodiscover/autodiscover.xml instead of the host name, and point autodiscover.domain to Exchange 2013 on internal DNS server.
Sign in to comment -
-
Matt Saul 96 Reputation points
2021-10-29T09:39:12.68+00:00 both blank :- on Exchange 2013 server ran it twice -under my login - I'm enterprise admin
and also manually right clicked and ran as me - same results
ran it also on Exchange 2007 shell -same result[PS] C:\Windows\system32>Get-ClientAccessServer | fl name,autodiscoverserviceinternaluri
Name : Exchange 2007 server
AutoDiscoverServiceInternalUri :Name : Exchange 2013 server
AutoDiscoverServiceInternalUri :on PDC DC in ADSIEDIT both exchange servers show https://autodiscover.domain/autodiscover/autodiscover.xml
DOES it matter than PC & Servers are in sub.domain whereas our email address is @keyman