Update 10/4/2007: Since this post has been published, we've updated the Exchange 2007 Autodiscover Service whitepaper to include this information. Please consult the whitepaper for most up-to-date ...
Updated Jul 01, 2019
Version 2.0
Blog Post
Hi Matt,
When I run "Get-ClientAccessServer" it returns our local CAS server internal netbios name. Are you saying that we need to change that from the local server name to autodiscover.domain.com, to resolve this problem? I thought, based upon all documentation I've read, that this had to be set to the local internal name of the server.
Aside from my previous paragraph, I have previously set all internal and external names to the appropriate external names(I.E. x.domain.com.) We have DNS both internal and external responding to the appropriate IP addresses, so this shouldn't be the problem. Somehow the CAS server returns its internal FQDN versus the internal/external name we assigned to all services.
Thanks!
When I run "Get-ClientAccessServer" it returns our local CAS server internal netbios name. Are you saying that we need to change that from the local server name to autodiscover.domain.com, to resolve this problem? I thought, based upon all documentation I've read, that this had to be set to the local internal name of the server.
Aside from my previous paragraph, I have previously set all internal and external names to the appropriate external names(I.E. x.domain.com.) We have DNS both internal and external responding to the appropriate IP addresses, so this shouldn't be the problem. Somehow the CAS server returns its internal FQDN versus the internal/external name we assigned to all services.
Thanks!