Hii all autodiscover not working at all , cannot find server at all if i serch manually the server, cannot find the server also if the mailbox connected to seme user mailbox i i want to connect another mail box with diffrent user, autodiscover not working

One of the error I can see is there is no A record registered at the public domain corresponding to autodiscover.pinkpil.co.il Also I can't be able to test https:/ /pinkpil.co.il/Autodiscover folder and autodiscover.xml Did you do the test internally?Regards from www.windowsadmin.info | www.blog.windowsadmin.info

One of the error I can see is there is no A record registered at the public domain corresponding to autodiscover.pinkpil.co.il Also I can't be able to test https:/ /pinkpil.co.il/Autodiscover folder and autodiscover.xml Did you do the test internally?Regards from www.windowsadmin.info | www.blog.windowsadmin.info

Hi Manu Philip, did you mean to creat new A record in dns ? yes, it's tested from the exchange server "mbxsvr01" if i create new object from adsiedit or iis, it's can help ?

Hi Manu Philip, did you mean to creat new A record in dns ? yes, it's tested from the exchange server "mbxsvr01" if i create new object from adsiedit or iis, it's can help ?

Hi Manu Philip, did you mean to creat new A record in dns ? yes, it's tested from the exchange server "mbxsvr01" if i create new object from adsiedit or iis, it's can help ?

On Sun, 24 Jun 2012 05:39:25 +0000, exhange.help wrote: >autodiscover not working at all , cannot find server at all if i serch manually the server, cannot find the server also if the mailbox connected to seme user mailbox > >i i want to connect another mail box with diffrent user, autodiscover not working Autodoscover isn't working because: 1) The "A" record for pinkpil.co.il points to a web sites whose SSL certificate doesn't pass the validation tests. 2) There's no "A" record for autodiscover.pinkpil.co.il to direct the test to your CAS. 3) You don't have a SRV record in your DNS for _autodiscover._tcp.pinkpil.co.il How do you want AutoDiscover to work? Should it use pinkpil.co.il, autodiscover.pinkpil.co.il, or _autodiscover.tcp.pinkpil.co.il? --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

On Sun, 24 Jun 2012 05:39:25 +0000, exhange.help wrote: >autodiscover not working at all , cannot find server at all if i serch manually the server, cannot find the server also if the mailbox connected to seme user mailbox > >i i want to connect another mail box with diffrent user, autodiscover not working Autodoscover isn't working because: 1) The "A" record for pinkpil.co.il points to a web sites whose SSL certificate doesn't pass the validation tests. 2) There's no "A" record for autodiscover.pinkpil.co.il to direct the test to your CAS. 3) You don't have a SRV record in your DNS for _autodiscover._tcp.pinkpil.co.il How do you want AutoDiscover to work? Should it use pinkpil.co.il, autodiscover.pinkpil.co.il, or _autodiscover.tcp.pinkpil.co.il? --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

I mean a public dns entry..which can resolve from internet.Regards from www.windowsadmin.info | www.blog.windowsadmin.info

On Sun, 24 Jun 2012 05:39:25 +0000, exhange.help wrote: >autodiscover not working at all , cannot find server at all if i serch manually the server, cannot find the server also if the mailbox connected to seme user mailbox > >i i want to connect another mail box with diffrent user, autodiscover not working Autodoscover isn't working because: 1) The "A" record for pinkpil.co.il points to a web sites whose SSL certificate doesn't pass the validation tests. 2) There's no "A" record for autodiscover.pinkpil.co.il to direct the test to your CAS. 3) You don't have a SRV record in your DNS for _autodiscover._tcp.pinkpil.co.il How do you want AutoDiscover to work? Should it use pinkpil.co.il, autodiscover.pinkpil.co.il, or _autodiscover.tcp.pinkpil.co.il? --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

i have created new host records (dns entery):

i have created new host records (dns entery):

Hi Rich, Acoording to ManU PhiliP answer i have created new hotst in dns, picture in previous answer thank you :)

Hi Rich, Acoording to ManU PhiliP answer i have created new hotst in dns, picture in previous answer thank you :)

i have created new host records (dns entery):

Hi Rich, Acoording to ManU PhiliP answer i have created new hotst in dns, picture in previous answer thank you :)

Hi Thanks for the update, please Mark As Answer if possible. CheersZi Feng TechNet Community Support

Hi Thanks for the update, please Mark As Answer if possible. CheersZi Feng TechNet Community Support

Hi Thanks for the update, please Mark As Answer if possible. CheersZi Feng TechNet Community Support

On Mon, 25 Jun 2012 08:34:25 +0000, exhange.help wrote: >Acoording to ManU PhiliP answer i have created new hotst in dns, picture in previous answer I'm sorry, but that's not going to work. You must create the necessary DNS resource record in an Internet-facing DNS. If your domainis named "domain" there's no way that anyone on the Internet is going to be able to resolve that to-level-domain. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

On Mon, 25 Jun 2012 08:34:25 +0000, exhange.help wrote: >Acoording to ManU PhiliP answer i have created new hotst in dns, picture in previous answer I'm sorry, but that's not going to work. You must create the necessary DNS resource record in an Internet-facing DNS. If your domainis named "domain" there's no way that anyone on the Internet is going to be able to resolve that to-level-domain. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

On Mon, 25 Jun 2012 08:34:25 +0000, exhange.help wrote: >Acoording to ManU PhiliP answer i have created new hotst in dns, picture in previous answer I'm sorry, but that's not going to work. You must create the necessary DNS resource record in an Internet-facing DNS. If your domainis named "domain" there's no way that anyone on the Internet is going to be able to resolve that to-level-domain. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Hi, If your user need to access Autodiscover from internet, then also needs to add A record in Public DNS. if your user located internally, then only host A record needs to add in Internal DNS. So, could you explain what URL, you have register on Autodiscover service and also on AutodiscoverServiceInternalURI on Client access server using below cmd Get-Autodiscovervirtauldirectory -server <CAS Server name> |fl internal*, External* Get-ClientAccessServer -Identity <CAS Server Name> | fl AutodiscoverServiceInternalUri Set-ClientAccessServer Identity <Server Name> -AutoDiscoverServiceInternalUri: https://<preferred name>.pinkpil.co.il/Autodiscover/Autodiscover.xml or Set-ClientAccessServer Identity <Server Name> -AutoDiscoverServiceInternalUri: https://autodiscover.pinkpil.co.il/Autodiscover/Autodiscover.xml And Also set the internal and exteral URL matching with above URi Also keep in mind that certificate must match the Autodiscover URL on CAS servers then add Host A reord in Internal DNS pointing to URL (autodiscover.pinkpil.co.il or <preferred name>.pinkpil.co.il) and if required externally access, then also on external DNS. Ex:- if Autodiscover URL is https://mail.domain.com/Autodiscover/Autodiscover.xml And internal and external URl on autodiscover virtual directory is :https://mail.domain.com/Autodiscover/Autodiscover.xml Using below shell cmd you could set internal and external URL Set-Autodiscovervirtauldirecoty -identity "CAS name\Autodis*" -InternalURL "https://mail.domain.com/Autodiscover/Autodiscover.xml" -externalURL"https://mail.domain.com/Autodiscover/Autodiscover.xml " And DNS have host record pointing to mail.doamin.com and with alias autodiscover.domain.com Note: For Shell command, you can check microsoft technet. Thanks, Vidyanand Sah

Hi Vidyanand all the scripts works, exclusive of the script: Get-Autodiscovervirtauldirectory -server <CAS Server name> |fl internal*, External* for example: Get-Autodiscovervirtauldirectory -server mbxsvr01 |fl internal*, External* dns:

Hi Vidyanand all the scripts works, exclusive of the script: Get-Autodiscovervirtauldirectory -server <CAS Server name> |fl internal*, External* for example: Get-Autodiscovervirtauldirectory -server mbxsvr01 |fl internal*, External* dns:

Hi Vidyanand all the scripts works, exclusive of the script: Get-Autodiscovervirtauldirectory -server <CAS Server name> |fl internal*, External* for example: Get-Autodiscovervirtauldirectory -server mbxsvr01 |fl internal*, External* dns:

Hi, Below are the correct command Get-AutodiscoverVirtualDirectory -Server <CAS ServerName> |fl internalURL, ExternalURL Get-AutodiscoverVirtualDirectory -Server <CAS ServerName> |fl internal*, External* Set-ClientAccessServer -identity <servername> -AutodiscoverServiceInternalUri https://autodiscover.pinkpil.co.il/Autodiscover/Autodiscover.xml Get-AutodiscoverVirtualDirectory -Server <CAS ServerName> | Set-AutodiscoverVirtualDirectory -InternalURL https://autodiscover.pinkpil.co.il/Autodiscover/Autodiscover.xml -ExternalURL https://autodiscover.pinkpil.co.il/Autodiscover/Autodiscover.xml Make sure CAS Server have Certificate installed with matching the name (autodiscover.pinkpil.co.il). and also check EWS Virtaul dierectory site URL settings Using below shell command Get-WebServicesVirtualDirectory -server <CAS ServerName> |fl internalURL, ExternalURL Get-WebServicesVirtualDirectory -server <CAS ServerName> | Set-WebServicesVirtualDirectory -InternalURL https://<FQDN of CAS Server>/EWS/Exchange.asmx -ExternalURL https://<FQDN of CAS Server>/EWS/Exchange.asmx Note: <FQDN of CAS Server> or custom URL, Also note that certificate must be matching the name with URL. SO you have to Deploy SAN Certificate or Star Certificate on CAS server. Thanks, Vidyanand Sah

Hi All all server deleted from adsi, server reinstalled thank you!!!