Skip to main content

Modifying Outlook profiles in Outlook 2010 with VBS and Powershell

Outlook profiles can present somewhat of a challenge to any mail administrator regardless of the size of the mail system. One way of looking at Outlook profiles is that they are just a whole collection of registry settings on a machine which is true but the number and compelxity of structures involved means that if you want to write a script that will modify a particular profile for a particular user its not just as simple as modifying a single registry key. In previous versions of Outlook you could generally rely on the GUID "13dbb0c8aa05101a9bb000aa002fc45a" to locate the key where the values for the Exchange settings are located but if you have done any work with Outlook 2010 on windows 7 you will generally find this is nolonger the case and its now more reliable to enumerate all the keys under a particular profile and find a particular setting which will indicate this particular key has the values for the Exchange Setting you want to modify. The one thing that computers are really good at is processing things quickly so if you wanted to for instance modify the cache mode setting within a profile in VBS you could use the following code to locate the default profile

Set WshShell = WScript.CreateObject("WScript.Shell")
strComputer = "."
HKEY_CURRENT_USER = &H80000001
Set oReg = GetObject("winmgmts:\\" & strComputer & "\root\default:StdRegProv")
keypath = "Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles\"

profile = WshShell.RegRead("HKCU\"&keypath&"DefaultProfile")


Then enumerate all the keys under this profile to identify the key that has the cache mode value.

oReg.EnumKey HKEY_CURRENT_USER, (keypath & profile & "\"), arrSubKeys
For Each subkey In arrSubKeys
oReg.EnumValues HKEY_CURRENT_USER, (keypath & profile & "\" & subkey & "\"), arrSubValues
on error resume next
for each ValueKey in arrSubValues
if ValueKey = "00036601" then
oReg.GetBinaryValue HKEY_CURRENT_USER,(keypath & profile & "\" & subkey),"00036601",prProxyValRes
if not IsNull(prProxyValRes) then
if prProxyValRes(0) = "132" then
Wscript.echo "Cache Mode Enabled"
else
Wscript.echo "Cache Mode Disabled"
end if
end if
end if
next
on error goto 0
next

If you want to change the setting instead of just echoing it out the current setting then you would need to include something like

newValue1 = Array(&H84,&H05,&H00,&H00)
oReg.SetBinaryValue HKEY_CURRENT_USER,(keypath & profile & "\" & subkey),"00036601",newValue1


Note the hex value that you put in the second array element can vary depending on whether you want to enable the download public folder or shared folders check boxes.

If you think vbs is for mugs and you want to do this in powershell instead then you would need something like this

$RootKey = "Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles"
$pkProfileskey = [Microsoft.Win32.Registry]::CurrentUser.OpenSubKey($RootKey, $true)
$defProf = $pkProfileskey.GetValue("DefaultProfile")
$pkSubProfilekey = [Microsoft.Win32.Registry]::CurrentUser.OpenSubKey(($RootKey + "\\" + $defProf), $true)
foreach($Valuekey in $pkSubProfilekey.getSubKeyNames()){
$pkSubValueKey = [Microsoft.Win32.Registry]::CurrentUser.OpenSubKey(($RootKey + "\\" + $defProf + "\\" + $Valuekey ), $true)
foreach ($values in $pkSubValueKey.GetValueNames())
{
if ($values -eq "00036601"){
if(($pkSubValueKey.GetValue("00036601"))[0] -eq 132){
"Cache Mode Enabled"}
else{
"Cache Mode Disabled"
}
}
}



}

Popular posts from this blog

Testing and Sending email via SMTP using Opportunistic TLS and oAuth in Office365 with PowerShell

As well as EWS and Remote PowerShell (RPS) other mail protocols POP3, IMAP and SMTP have had OAuth authentication enabled in Exchange Online (Official announcement here ). A while ago I created  this script that used Opportunistic TLS to perform a Telnet style test against a SMTP server using SMTP AUTH. Now that oAuth authentication has been enabled in office365 I've updated this script to be able to use oAuth instead of SMTP Auth to test against Office365. I've also included a function to actually send a Message. Token Acquisition  To Send a Mail using oAuth you first need to get an Access token from Azure AD there are plenty of ways of doing this in PowerShell. You could use a library like MSAL or ADAL (just google your favoured method) or use a library less approach which I've included with this script . Whatever way you do this you need to make sure that your application registration  https://docs.microsoft.com/en-us/azure/active-directory/develop/quickstart-register-

How to test SMTP using Opportunistic TLS with Powershell and grab the public certificate a SMTP server is using

Most email services these day employ Opportunistic TLS when trying to send Messages which means that wherever possible the Messages will be encrypted rather then the plain text legacy of SMTP.  This method was defined in RFC 3207 "SMTP Service Extension for Secure SMTP over Transport Layer Security" and  there's a quite a good explanation of Opportunistic TLS on Wikipedia  https://en.wikipedia.org/wiki/Opportunistic_TLS .  This is used for both Server to Server (eg MTA to MTA) and Client to server (Eg a Message client like Outlook which acts as a MSA) the later being generally Authenticated. Basically it allows you to have a normal plain text SMTP conversation that is then upgraded to TLS using the STARTTLS verb. Not all servers will support this verb so if its not supported then a message is just sent as Plain text. TLS relies on PKI certificates and the administrative issue s that come around certificate management like expired certificates which is why I wrote th

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 Graph is limited to a m
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.