Identifying Unresolved LegacyExchangeDNs via EWS and Powershell

re: Identifying Unresolved LegacyExchangeDNs via EWS and Powershell

Bill Long [Exchange] — Fri, 30 Sep 2011 13:49:03 GMT

Excellent! I took this idea and modified it into a single line that prompts for the password and puts it in the $password variable, so that the rest of the script didn't have to be modified. You could do the same thing with Get-Credential, but I wanted to have a little more control over the dialog, so I used PromptForCredential. It's really no different, though.

I had no idea we stored a plain text password on this credential object. Thanks again!

re: Identifying Unresolved LegacyExchangeDNs via EWS and Powershell

DJ Grijalva — Wed, 28 Sep 2011 19:57:43 GMT

I found another helper for your script. For the credential issue, you would just have to do the following:

$Creds = Get-Credential

$service.Credentials = New-Object Microsoft.Exchange.WebServices.Data.WebCredentials -ArgumentList $Creds.UserName, $Creds.GetNetworkCredential().Password

re: Identifying Unresolved LegacyExchangeDNs via EWS and Powershell

Bill Long [Exchange] — Mon, 19 Sep 2011 16:27:06 GMT

Hey, that actually works! Thanks DJ! I've updated the script.

re: Identifying Unresolved LegacyExchangeDNs via EWS and Powershell

DJ — Fri, 16 Sep 2011 19:32:36 GMT

Have you tried replacing:

$exchService.AutoDiscoverUrl($emailAddress)

with:

$exchService.AutodiscoverUrl($emailAddress, {$true})

to handle the Autodiscover redirect?