Skip to main content

Making use of Autodiscovery in VBS and Powershell Scripts

Auto discovery is one of the new features that are trying to alleviate some of the pain of configuring and maintaining Outlook client setting. Once you have managed to overcome the SSL configuration peculiarities you have a nifty little service that you can authenticate against, supply it with your email address and it will inform you about everything you need to know about connecting to exchange using Outlook, OWA, EWS and or any of the other new services Exchange 2007 provides. If you’re a scripter the information the auto discovery service provides can be retrieved via Active Directory but it not that easy and certain not as convenient as doing with one request.

The scripts I’ll talk about in this post are designed to be run from workstation where the Exchange Management Tools aren’t install so they won’t be using any of the Exchange Management Shell cmdlets.

The first thing you need to do if you want to use Auto discovery is query Active Directory for the Service Connection Point. This will give you the URL which you can send your AutoDiscovery Query (okay there is another option which is using autodisovery.domain.com). The SCP for Autodiscovery is located under the server/procotol nodes in the Active directory configuration partition. So to start with you need to use an ADSI query with the following filter (&(objectClass=serviceConnectionPoint) (|(keywords=67661d7F-8FC4-4fa7-BFAC-E1D7794C1F68) (keywords=77378F46-2C66-4aa9-A6A6-3E7A48B19596))). This will return one or more SCP you can then use to make a auto discovery request. If you want to find the closest SCP to the machine that is making the query you can use the Keywords attribute on the ServiceConnectionPoint to return the site name. You could also use a IP table with some metrics to work this out. Once you have the URL for auto discovery you can then send a XML request to the autodiscover service. Of course you will to also authenticate for this to work in a script you can do this in one of two way by hardcoding a username and password into the script file or by using the logged on user credentials the script from the post both make use of the Logged on user credentials.

Thats pretty much it for more information on Auto discovery I would recommend having a read of this if you want to write something in C# that uses autodiscover then check out the Auto discover sample in the Exchange SDK.

I’ve put a download of the scripts here the vbs sample looks like

ScpUrlGuidString = "77378F46-2C66-4aa9-A6A6-3E7A48B19596"
ScpPtrGuidString = "67661d7F-8FC4-4fa7-BFAC-E1D7794C1F68"

set conn = createobject("ADODB.Connection")
set com = createobject("ADODB.Command")
Set iAdRootDSE = GetObject("LDAP://RootDSE")
strNameingContext = iAdRootDSE.Get("configurationNamingContext")
Conn.Provider = "ADsDSOObject"
Conn.Open "ADs Provider"
svcQuery = "<LDAP://CN=Microsoft Exchange,CN=Services," & strNameingContext &
">;(&(objectClass=serviceConnectionPoint)" _
& "(|(keywords=" & ScpPtrGuidString & ")(keywords=" & ScpUrlGuidString & ")));cn,name,serviceBindingInformation,legacyExchangeDN;subtree"
Com.ActiveConnection = Conn
Com.CommandText = svcQuery
Set Rs = Com.Execute
while not rs.eof
wscript.echo rs.fields("cn")
call queryautodiscovery(wscript.arguments(0),rs.fields("serviceBindingInformation").Value)
rs.movenext
wend

sub queryautodiscovery(emailaddress,casAddress)
wscript.echo "Using AutoDisover Address : " & casAddress(0)
autodiscoResponse = "<Autodiscover xmlns=""http://schemas.microsoft.com/exchange/autodiscover/outlook/requestschema/2006"">"
_
& " <Request>" _
& " <EMailAddress>" + emailaddress + "</EMailAddress>" _
& " <AcceptableResponseSchema>http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a</AcceptableResponseSchema>"
_
& " </Request>" _
& "</Autodiscover>"
set req = createobject("MSXML2.ServerXMLHTTP.6.0")
req.Open "Post",casAddress(0) ,False
req.SetOption 2, 13056
req.setRequestHeader "Content-Type", "text/xml"
req.setRequestHeader "Content-Length", len(autodiscoResponse)
req.send autodiscoResponse
wscript.echo req.responsetext
end sub
Labels:

Popular posts from this blog

The MailboxConcurrency limit and using Batching in the Microsoft Graph API

If your getting an error such as Application is over its MailboxConcurrency limit while using the Microsoft Graph API this post may help you understand why. Background   The Mailbox  concurrency limit when your using the Graph API is 4 as per https://docs.microsoft.com/en-us/graph/throttling#outlook-service-limits . This is evaluated for each app ID and mailbox combination so this means you can have different apps running under the same credentials and the poor behavior of one won't cause the other to be throttled. If you compared that to EWS you could have up to 27 concurrent connections but they are shared across all apps on a first come first served basis. Batching Batching in the Graph API is a way of combining multiple requests into a single HTTP request. Batching in the Exchange Mail API's EWS and MAPI has been around for a long time and its common, for email Apps to process large numbers of smaller items for a variety of reasons.  Batching in the Gr...
Read more

Sending a MimeMessage via the Microsoft Graph using the Graph SDK, MimeKit and MSAL

One of the new features added to the Microsoft Graph recently was the ability to create and send Mime Messages (you have been able to get Message as Mime for a while). This is useful in a number of different scenarios especially when trying to create a Message with inline Images which has historically been hard to do with both the Graph and EWS (if you don't use MIME). It also opens up using SMIME for encryption and a more easy migration path for sending using SMTP in some apps. MimeKit is a great open source library for parsing and creating MIME messages so it offers a really easy solution for tackling this issue. The current documentation on Send message via MIME lacks any real sample so I've put together a quick console app that use MSAL, MIME kit and the Graph SDK to send a Message via MIME. As the current Graph SDK also doesn't support sending via MIME either there is a workaround for this in the future my guess is this will be supported.
Read more

Export calendar Items to a CSV file using Microsoft Graph and Powershell

For the last couple of years the most constantly popular post by number of views on this blog has been  Export calendar Items to a CSV file using EWS and Powershell closely followed by the contact exports scripts. It goes to show this is just a perennial issue that exists around Mail servers, I think the first VBS script I wrote to do this type of thing was late 90's against Exchange 5.5 using cdo 1.2. Now it's 2020 and if your running Office365 you should really be using the Microsoft Graph API to do this. So what I've done is create a PowerShell Module (and I made it a one file script for those that are more comfortable with that format) that's a port of the EWS script above that is so popular. This script uses the ADAL library for Modern Authentication (which if you grab the library from the PowerShell gallery will come down with the module). Most EWS properties map one to one with the Graph and the Graph actually provides better information on recurrences then...
Read more
All sample scripts and source code is provided by for illustrative purposes only. All examples are untested in different environments and therefore, I cannot guarantee or imply reliability, serviceability, or function of these programs.

All code contained herein is provided to you "AS IS" without any warranties of any kind. The implied warranties of non-infringement, merchantability and fitness for a particular purpose are expressly disclaimed.