Category Archives: 13178

Fix for Exchange ActiveSync Failures After Migration to Exchange 2013

There’s a bug in Exchange 2013 that causes Exchange ActiveSync to fail for newly migrated users from Exchange 2010. It only affects migrated users who already have a mobile device configured, not new users (i.e., test mailboxes). This issue was discussed in the Exchange Server forums back in August 2013.


The issue occurs because the IIS application pools on the CAS 2013 servers do not automatically detect that the mailbox has been moved to Exchange 2013. When the user’s mobile device connects to CAS 2013, CAS 2013 proxies the user back to CAS 2010 which responds with an error saying the mailbox is corrupt or missing. If you run an Exchange ActiveSync test using ExRCA you will see the X-CalculatedBETarget value reported by CAS2013 is still pointing to the Exchange 2010 server. The problem usually resolves itself in 1-8 hours, depending on the Exchange 2013 build.

The workaround is to manually recycle the MSExchangeAutodiscoverAppPool and MSExchangeSyncAppPool application pools in IIS on all CAS2013 servers.

I wrote a PowerShell script for this called Recycle-AppPools.ps1:

#Recycle-AppPools.ps1
#Jeff Guillet, MCM|MCSM|MVP|CISSP
#Use this script to recycle IIS Application Pools to overcome Exchange 2013 SP1 ActiveSync bug for migrated users

#Get all Exchange 2013 CAS servers
$CASServers = Get-ClientAccessServer | where {$_.WorkloadManagementPolicy -ne $null}

#Loop through each CAS2013 and recycle the IIS App Pools
foreach ($CAS in $CASServers) {
  Write-Host “Recycling App Pools on $CAS…”
  $appPool = Get-WmiObject -Authentication PacketPrivacy -Impersonation Impersonate -ComputerName $CAS -namespace “root/MicrosoftIISv2″ -class IIsApplicationPool | Where-Object {$_.Name -eq “W3SVC/AppPools/MSExchangeAutodiscoverAppPool” }
  $appPool.Recycle()
  $appPool = Get-WmiObject -Authentication PacketPrivacy -Impersonation Impersonate -ComputerName $CAS -namespace “root/MicrosoftIISv2″ -class IIsApplicationPool | Where-Object {$_.Name -eq “W3SVC/AppPools/MSExchangeSyncAppPool” }
  $appPool.Recycle()
}

You will need to run the script after an EAS user or batch of users have been migrated. There is no outage associated with recycling the app pools and it recycles very quickly. A fix is scheduled for Exchange 2013 CU5.



Exchange 2013 CU3 upgrade removes the ActiveSync virtual directory ExternalURL

Microsoft released Exchange Server 2013 Cumulative Update 3 on November 25, 2013.  CU3 includes fixes for many customer reported issues, minor product enhancements and previously released security bulletins.  A complete list of customer reported issues resolved in Exchange Server 2013 Cumulative Update 3 can be found in Knowledge Base Article KB 2892464.



Although it’s not listed in the Description of Cumulative Update 3 for Exchange Server 2013, one of the important things that Exchange 2013 CU3 fixes is OWA redirection for OWA 2010.  I discussed this in my article, OWA 2013 CU1 Redirection is Broken for Legacy Mailboxes.



Unfortunately, one important fix did not make it into CU3: Upgrading Exchange 2013 blanks out the ActiveSyncVirtualDirectory ExternalUrl property.  This only affects Exchange 2013 upgrades from RTM through CU2 – it does not affect new installations of Exchange 2013.



Exchange 2013 ActiveSyncVirtualDirectory URL values before CU3



Exchange 2013 ActiveSyncVirtualDirectory URL values after CU3



This problem was actually introduced back in the Exchange 2010 timeframe and has been present since Exchange 2013 CU1.  If you perform a RecoverServer operation in 2010, the operation should reconfigure the recovered server with the existing values stored in Active Directory.  At some point code was introduced that reset the URL values and security configuration of the OWA, ECP and ActiveSync to their default values (InternalURL uses the FQDN of the server and ExternalURL is blank).  Since Exchange 2013 servicing is a build-to-build upgrade it behaves pretty much like a RecoverServer operation and the problem becomes apparent.



The Exchange Team was able to address this behavior for the OWA and ECP virtual directories, but unfortunately did not address it for ActiveSync (it’s still being tracked).  Fixing the issue for OWA and ECP virtual directories was high priority since this affects users’ ability to access ECP and options from Outlook.



ActiveSync, however, only uses the external URL value once when a mobile device is first configured for email.  EAS devices do not periodically check Autodiscover and reconfigure themselves like Outlook does, so if the value is blank devices configured prior to the CU3 upgrade will still work.



This does affect new devices, however.  If the ExternalURL value for the ActiveSync is blank when a user tries to configure a new EAS mail client, the device has no idea how to connect to Exchange.  EAS will then prompt the user for the server name, which they may or may not know.



The fix is simple: After upgrading Exchange Server 2013 to CU3 reconfigure the ActiveSync virtual directory ExternalURL property using the following cmdlet:

Set-ActiveSyncVirtualDirectory -Server <servername> -ExternalUrl https://<external fqdn>/Microsoft-Server-ActiveSync

You may also need to reconfigure security settings for the ActiveSync virtual directory (i.e., if you use user certificates for authentication).  I recommend making note of your ActiveSync virtual directory URLs and security settings prior to the upgrade.



Hopefully, this will be completely addressed in Exchange 2013 SP1 due early 2014.



Fix for Excessive Duplicate Contacts

If you’re running Lync in your environment you may notice that you have multiple duplicate contacts in your contacts list.






This issue also affects your ActiveSync mobile devices, such as the iPhone.






If you open one of these duplicate contacts, you will notice that the Notes field says the contact was added by Lync 2013.






This a caused by a bug in the Lync client, which adds a duplicate contact item every time you have do an IM with this contact.  The bug will be fixed in the next cumulative update (CU) for the Lync 2013 client.  In the meantime, here’s how you can fix it.



The duplicate contacts are stored in a contacts folder called Lync Contacts.  This folder is protected by Outlook so you can’t delete it from there.  You need to delete it from Outlook Web App, which does not treat it as protected.



  • Log into OWA and view your contacts.
  • Right-click the Lync Contacts folder and select Delete.



  • Click Yes to confirm you want to delete the selected folder and move all contents into the Deleted Items folder.  You can then sign out of OWA.
  • From the Outlook client you’ll need to empty your Deleted Items folder to finish getting rid of all the duplicate contacts.  You’ll then be free of them!







Comprehensive Guide on Addressing Exchange Calendaring Issues

Rand Morimoto wrote a great article for Network World about Exchange calendaring issues.  Rand is the president of Convergent Computing, the company I work for.  His article covers lost appointments, duplicate appointments, odd delegate issues, etc.  This article is based on the real-world experience we as a company have gained working with many organizations of all sizes.

I wanted to add a few comments of my own, to follow up on to Rand’s excellent article.

Another factor that can cause calendar issues for delegates is Cached Exchange Mode, which can cause an artificial delay in updating calendar information. For example, the boss (using Entourage, which doesn’t have Cached Mode) may accept or alter the same appointment that the assistant (using Outlook in Cached Mode) accepts or alters. The default Cached Mode settings may cause a delay of up to a minute before the assistant’s calendar item is updated on Exchange. Who wins is anybody’s guess.

By the way, my recommendation is to adjust the Cached Mode latencies to 1 second using Group Policy. There is virtually no network performance impact and it solves a lot of issues, especially “perceived performance” issues.  See http://support.microsoft.com/kb/870926/%20target=.

Regarding BES, RIM is making quite a few changes recently due to inconsistency problems (especially in calendaring). BES 5.0 SP2 is supposed to make huge performance improvements so that BES IOPS are now equal to Outlook (see http://flaphead.com/archive/2010/07/24/bes-5-0-sp2-blackberry-user-exchange-2010-iops-now-equal-to-an-outlook-client.aspx). The rumor is that BES 6.0 will completely re-architect BES to use Exchange Web Services (EWS) rather than MAPI.

That said, BES changes versions as often as we change socks. I find that most orgs are WAY behind on BES versions from the current version, so they can’t take advantage of these improvements. And as with any other technology with massive changes, it will probably introduce a new set of unknown problems.

Being that calendaring issues are 99% due to client issues (Outlook, Entourage, BES, iPhone, etc.), I expect that most of these issues will go away as the clients move toward using EWS. The problems documented in Rand’s article occur because of the way the clients handle calendaring/email objects. If the client software lets Exchange handle these objects using standard EWS APIs, the problems will diminish/disappear.

Trouble with ActiveSync with iOS4 for iPhone

As reported all over the Internet, customers are having trouble with Exchange ActiveSync after upgrading their iPhones to iOS4.  Problems range from not syncing to over utilization of Exchange servers.

Apple has been nearly silent on this issue, choosing to do damage control over it’s poorly designed antenna in the new iPhone 4.

The Microsoft Exchange Team has posted on its blog more information about these issues, which is much more than anything we’ve seen or heard from Apple.  With Microsoft’s assistance, Apple released a fix that changes the timeout value that Exchange ActiveSync connection uses to four minutes, which should be long enough for the vast majority of users.

But take a look at that Apple article.  There’s virtually no technical content or explanation that describes what the new profile does, other than saying it increases the timeout value.  To what?  From what?  What was it in previous iOS versions?

All this demonstrates how the iPhone is not an enterprise ready device, primarily because Apple does not provide enterprise-class support.  Apple could learn a lot from Microsoft.  Honesty and transparency is always the best way to provide support.

How to Securely Deploy iPhones with Exchange ActiveSync – Phase 6 – End-User Deployment of the ActiveSync Profile

This is the seventh and last post in my series, How to Securely Deploy iPhones with Exchange ActiveSync in the Enterprise. To read an overview of the solution click here.  In this phase I will demonstrate the steps and procedures that the end-user will perform to configure their iPhone for ActiveSync.  I will also cover some advanced reverse proxy configurations, such as using Microsoft Threat Management Gateway (TMG), ISA, Tivoli Access Manager (TAM), etc.

As a review, the infrastructure has been built and the necessary software and certificates have been installed and configured.  Members of the ActiveSync Administrators group configure iPhone Configuration Profiles, one per iPhone, which includes the user’s ActiveSync configuration settings and the ActiveSyncUser user certificate.  Each iPhone Configuration Profile (iCP) is married to the iPhone and exported to the EAS share, which is also a website virtual directory on the CAS server.  The iCP is named for the user for which it is intended (i.e., jqsmith.mobileconfig).

In this final phase, the user authenticates to the EAS website using Safari from the iPhone.  The iPhone automatically downloads the iCP that matches the username.

Here are the steps in detail:

The user is instructed to tap Safari on the iPhone and navigate to https://webmail.companyabc.com/eas (where webmail.companyabc.com is the public FQDN for the CAS server).  The user logs into the Secure Website using the user’s AD logon name and password, as shown:


After successfully logging in, the iPhone will download the user-specific ActiveSync Configuration Profile, as shown.


The green Verified indication signifies that the profile was encrypted and signed for this device.

If the user taps More Details on the profile, the details of the configuration profile are displayed showing the ActiveSync server and the email address used in the configuration profile, as shown.  Note that the user cannot tell that a user certificate is embedded in the configuration profile.


Back on the Install Profile screen, tap Install and Install Now to begin installing the profile.

Note that the iPhone only supports one Exchange ActiveSync profile at a time (I sincerely hope this changes in the near future).  If the user already has Exchange ActiveSync configured, the iPhone will display the warning, “Can’t install Profile. Only one Exchange account can be set up at a given time.”  Remove the existing ActiveSync settings and begin the process again.

If the iPhone already has a passcode configured, the user will need to enter it at this time to begin installing the profile.

During installation of the profile the user is prompted for his/her AD password to connect to their mailbox, as shown:


Enter the AD password, tap Return, and then tap Next to complete installation of the profile.  When the profile has been successfully installed, tap Done.  The user can now close Safari.

If a device lock passcode has been configured in the Exchange ActiveSync Policy, the iPhone will display a message that the user must accept the new policy.  It will then prompt the user for a passcode using the complexity requirements specified in the EAS policy.

It may take a few minutes to complete synchronizing the user’s email, calendar, contacts and tasks for the first time.

If at any time in the future the user needs to re-install the ActiveSync Profile on the iPhone (for example, after a hardware reset or software restore), simply follow these steps again.

Removing the ActiveSync Profile
If the user wants to remove the ActiveSync Profile, follow these steps.  Removing the ActiveSync profile also removes the user certificate from the iPhone.

Tap Settings on the iPhone home screen and then tap General.  Scroll to the bottom and tap Profiles.  Tap the profile to remove and then tap Remove.  If the iPhone has a passcode configured, it must be entered to remove the profile.


Reverse Proxy Scenarios
Some environments secure their Client Access Servers from direct Internet communication using Microsoft ISA, Threat Management Gateway (TMG) server, or another reverse proxy solution.

In these scenarios, the public ActiveSync connection and authentication is made at the reverse proxy.  The reverse proxy then proxies the authentication to the internal CAS server(s).  The CAS servers, themselves, act as reverse proxies to the mailbox servers.

With an environment such as this, you need to install the certificate and private key on the reverse proxy server(s).  The reverse proxies need to be configured to require client certificates and use Basic Authentication.  They must then pass the certificate, username, password to the CAS servers to complete the connection.  This diagram should help.


I hope this series helps you with the deployment of iPhones in your Exchange ActiveSync environment.  I welcome your comments.


This concludes my series, How to Securely Deploy iPhones with Exchange ActiveSync in the Enterprise.

Other articles in this series:

How to Securely Deploy iPhones with Exchange ActiveSync – Phase 5 – Creating the Website for iPhone Profile Deployment

This is the sixth post in my series, How to Securely Deploy iPhones with Exchange ActiveSync in the Enterprise. To read an overview of the solution click here.  In this phase, we will create the deployment website that end-users will use to download the appropriate iPhone Configuration Profile created in Phase 4.

Since you’re most likely using Outlook Web Access served up by the CAS servers, these make a natural choice for hosting the website.  I’ll cover how to do this using a single CAS server and then follow up with guidance and best practices for environments with multiple CAS servers.

Add the ASP Role Service to the Web Server
Begin by logging into the CAS server with administrator credentials and opening Server Manager.  Expand Roles and select Web Server (IIS).  Right-click Web Server (IIS) and select Add Role Services.  Under Application Development add the ASP role service, as shown.


Click Next and Install to complete the installation.  No restart is required.

Create the EAS Virtual Directory
Open Internet Information Services (IIS) Manager.  Expand the CAS server name > Sites > Default Web Site.  Right-click Default Web Site and choose Add Virtual Directory.  Enter EAS for the Alias and click the (…) button to browse for the Physical Path.  Navigate to C:\inetpub\wwwroot and click the Make New Folder button.  Name the new folder EAS and click OK twice.


Configure the EAS WebSite Permissions
Right-click the new EAS virtual directory and choose Edit Permissions.  Click the Sharing tab and configure the EAS share with the following share permissions: Add ActiveSync Users (Read) and ActiveSync Admins (Full Control).  Remove Everyone from the share permissions. 

On the Security tab click Advanced and Change Permissions.  Uncheck Include inheritable permissions from this object’s parent, click Add (for Windows Server 2008, click Copy), and click OK twice.  Click Edit and remove the Users (CASname\Users) group.  Add ActiveSync Users (Read & Execute, List Folder Contents, Read) and ActiveSync Admins (Full Control), and click OK twice.

Configure the EAS WebSite Authentication
Select the EAS website and double-click Authentication.  Disable Anonymous Authentication and enable Basic Authentication.  Select Basic Authentication and click Edit in the Actions pane.  Enter the domain name for the Default Domain and click OK.

Configure MIME Handling
MIME handling tells the web server how to handle different file extensions and associates file extensions with applications.

Select the EAS website and double-click MIME Types.  Click Add in the Actions pane.  Enter mobileconfig for the File name extension and application/iphone-configuration for the MIME type, as shown, then click OK.


Create the Default Document for the EAS Website
We now need to create a default ASP document for the folder.  This ASP page will be used to cause the iPhone to automatically download the correct iPhone Configuration Profile.

Download the default.asp page here.  Edit default.asp to replace webmail.companyabc.com in the second to last line with the FQDN of your publicly available CAS server.  Save the file in the EAS folder.  You can now close Internet Information Services (IIS) Manager.

Putting It All Together
Now that we have the EAS share and website configured, it’s simply a matter of exporting the iPhone configuration profiles to the EAS share (as described in Phase 4), using the ActiveSync user’s logon name as the name of the file (for example, jqsmith.mobileconfig). 

You then instruct the user to enter https://webmail.companyabc.com/eas in Safari from the iPhone.  The user will be prompted for authentication to access the website.  After the user enters his/her AD username and password, the iPhone Configuration Profile that matches the logon name will be downloaded to install on the iPhone.  I’ll cover those steps in detail in the final phase.

Special Configuration for Multiple CAS Servers
If your environment has more than one CAS server in a load-balancing solution used for OWA, you need to perform the procedures above for each of those CAS servers.

You will also need to make sure that you copy the encrypted and signed iPhone Configuration Profiles to each CAS server’s EAS share when you export it.  If this pertains to your environment, I recommend using DFS to replicate and distribute the profiles amongst the participating CAS servers.  With DFS you can save the iPhone Configuration Profiles to \\domain\EAS and it will replicate to all the CAS servers automatically.

This completes the configuration of the EAS deployment website.





This concludes Phase 5 of my series, How to Securely Deploy iPhones with Exchange ActiveSync in the Enterprise.  In the last phase I will provide the end-user instructions and procedures.

Other articles in this series:

How to Securely Deploy iPhones with Exchange ActiveSync – Phase 4 – Creating the iPhone Configuration Profile

This is the fifth post in my series, How to Securely Deploy iPhones with Exchange ActiveSync in the Enterprise. To read an overview of the solution click here. In this phase, we will create iPhone Configuration Profiles using Apple’s iPhone Configuration Utility.  I will also show you how to embed the user certificate and private key into the profile and how to marry the profile to a specific iPhone. 

Let’s get started.

First, you will need to download and install the Apple iPhone Configuration Utility (iCU).  The latest version as of this writing is version 2.1.0.163 and is the one I will use here.  The iCU only installs on Windows XP SP3 or Windows Vista SP1 or greater.  It will not install on Windows Server.  It also requires NET 3.5 SP1.

Note: The iCU is not an enterprise class software program.  All the configurations, hardware profiles and configuration profiles are stored locally on the workstation in %USERPROFILE%\Local Settings\Application Data\Apple Computer\MobileDevice folder.  For this reason, I recommend using a single workstation for iPhone management and to backup this folder and child folders to a network location periodically.

Begin the configuration process by logging into the workstation with the credentials used to request and install the user certificate created in Phase 1.  This user has the ActiveSyncUser user certificate stored in his/her personal certificate store.  It will be needed later in this process.

Before the iPhone can be configured it must be activated on the AT&T network.  This is performed using iTunes.  Simply launch iTunes, connect the new iPhone to the computer using the USB cable, and follow the iTunes Setup Assistant.  Once the iPhone is activated you can close iTunes.

Now launch the iPhone Configuration Utility.  The iPhone will automatically be added to the Devices Library in the iCU, as shown below:


In the Devices library, click the iPhone and enter the user’s name and email address to identify the device profile.  Note that most iPhones will have the helpful name “iPhone”, so the Contact info you enter here will help you out later.

Now click the Configuration Profiles library and click the New icon to create a new base configuration profile.  The base configuration profile can be used for configuration settings that cannot be made using the Exchange ActiveSync Policy, such as iPhone Restrictions or VPN settings.  Apple calls these configurations “payloads”.

To create a new base configuration, select the General (Mandatory) setting and enter a Name, Identifier, Organization, and Description, as shown. 


Choose whether the base configuration profile can be removed.  Choices are Always, With Authentication (using a password), or Never.  For base configurations, I recommend With Authentication to prevent end-users from easily removing company restrictions.  You must then supply the Authorization password.  Notice there is no “Save” button anywhere.  Whatever you configure is written immediately to the configuration profile(s).

You can now configure your base configuration settings and restrictions, as shown.  Refer to the iCU help for configuration settings.  If you want to delete a payload from a profile, click the minus sign in the top right corner of the configuration item.


I recommend using Exchange 2007 / 2010 ActiveSync over-the-air policies for any configuration that can be configured using them (for example, device locking duration and passcode complexity).  This will give you the greatest amount of flexibility and will allow you to make changes on the fly.

Now deploy the iPhone Base Profile to the iPhone by clicking the iPhone name under DEVICES on the left pane.  Select the iPhone Base Profile and click Install.


The iPhone will prompt you to install the iPhone Base Profile, as shown below.  Tap Install and the Install Now.  After the profile installs, tap Done.


Back in the iCU, click the Configuration Profiles library.  Click the New icon again to create the ActiveSync Profile.  Configure the General (Mandatory) section as shown:


I recommend setting Security so that the ActiveSync Profile can Always be removed.  This will allow users to remove the EAS profile, which will help later if you ever need to re-deploy the EAS profile.

Now click the Exchange ActiveSync section and configure your ActiveSync settings for the iPhone.  Enter the Account Name, Exchange ActiveSync Host, Domain, User, and Email Address, as shown:


Do not enter the user’s password.  The iPhone will prompt the user for any field you leave blank when it installs the profile.  Going forward, the only items you will need to configure for subsequent ActiveSync profiles are the User and Email Address.

Click the + sign under Authentication Credential Name.  The Personal Certificate Store will open for you to add the ActiveSyncUser user certificate to the Exchange ActiveSync profile, as shown:


Enter the password you entered for the certificate’s private key in Phase 1.  The certificate and private key will be added to the Exchange ActiveSync configuration.  Check Include Authentication Credential Passphrase to include it in the profile, otherwise the device will prompt the user for the passphrase (not good).


You now have a fully configured iPhone ActiveSync Configuration Profile.  All that’s left is to export the ActiveSync Profile so that the user can install it.  You need the user to do this because the profile will prompt for the user’s Active Directory password (something I hope you don’t know).

Ensure that the ActiveSync Profile is selected and click the Export button.  The Export Configuration Profile window will open.  Select Create and sign encrytped configuration profile for each selected device from the dropdown box and select the correct device, as shown below.  Then click Export.  This will “marry” the ActiveSync configuration profile to the selected device, preventing it from being installed on any other iPhone.  This is how we meet the requirement that “only authorized devices can access Activesync”.


Now I need to jump forward a bit.  In the next phase, I will explain how to create the deployment website.  For now, let’s assume that the website already exists and that the UNC path to the share for that website is \\EXCAS1\eas.  Save the configuration profile to that share, naming the profile with the AD user’s logon name (for example, jqsmith.mobileconfig).

Congratulations!  You have now created a unique ActiveSync configuration profile with the embedded ActiveSyncUser user certificate, and encypted and married the profile to a specific iPhone.



This concludes Phase 4 of my series, How to Securely Deploy iPhones with Exchange ActiveSync in the Enterprise.  The next phase will cover how to create the website for end-user iPhone profile deployment.

Other articles in this series:

How to Securely Deploy iPhones with Exchange ActiveSync – Phase 3 – Publishing User Certificates to Active Directory

This is the fourth post in my series, How to Securely Deploy iPhones with Exchange ActiveSync in the Enterprise. To read an overview of the solution click here. In this phase, we will publish the same user certificate to each user object in Active Directory that is a member of the ActiveSync Users security group.

As mentioned earlier, ActiveSync will be configured to require user certificates for authentication.  This means that the user needs a user certificate with the private key and ActiveSync will check this certificate for a matching certificate in Active Directory.  We need to publish the user accounts in Active Directory, as shown below.


When you view the properties of the published certificate, you see that it was issued by the CA (W2K8R2-CA) and that the certification path is valid, since we published the root CA certificate to all machines in the domain using Group Policy in Phase 2.


While this is a fairly simple process to do, I wrestled with different ways of doing it programmatically.  I finally decided to use VBScript to publish the certificate to AD.  I chose VBScript instead of PowerShell because I could not be certain that the ActiveSync Administrator(s) would have PowerShell installed.

The script uses CAPICOM, which is a security technology from Microsoft that allows Microsoft Visual Basic, Visual Basic Script, ASP, and C++ programmers to easily incorporate digital signing and encryption into their application.  To use CAPICOM, you must download and register the CAPICOM.DLL on the computer that runs the script.  The script automatically registers the DLL, as long as it resides in the same network share where the ActiveSync user certificate resides.

First, download CAPICOM and extract the contents to get the CAPICOM.DLL file (we have no need for any of the other files or examples).  Then create a network share that the mobile administrators have access to (for example \\fileserver\iPhone).  Copy the CAPICOM.DLL, the ActiveSyncUser.cer user certificate (exported in Phase 1), and the vbscript below to the share.  You will need to edit the script to reflect the name you used for your ActiveSync Users group in AD, the path to CAPICOM.DLL and the user certificate, and the name of the user certificate if necessary.

Here’s the Publish Mobile Cert.vbs script:

‘======================================================================================================================================
‘Publish Mobile Cert.vbs –
The admin running the script must have rights to modify the user accounts that are members of the ActiveSync Users group in AD.

‘Jeff Guillet
’02/10/2010

‘This script publishes the mobile user certificate into Active Directory for all members of the ActiveSync Users security group

‘Micosoft link for CAPICOM: http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=860EE43A-A843-462F-ABB5-FF88EA5896F6
‘=======================================================================================================================================


On Error Resume Next


‘Configure constants
Const ADS_PROPERTY_UPDATE = 2
Const ADS_PROPERTY_APPEND = 3


‘————————————————————————–
‘Modify the three variables below, as required
‘————————————————————————–
eASUsersGroup = “ActiveSync Users”
pathToFiles = “\\fileserver\iPhone\”
certFile = “ActiveSyncUser.cer”
‘————————————————————————–


msg = “This script publishes the ‘” & certFile & “‘ certificate to all members of” & vbCRLF
msg = msg & “the ‘” & eASUsersGroup & “‘ security group. Do you want to continue?”
r = MsgBox(msg, vbYesNo + vbQuestion, “Publish Mobile Cert”)
If r = vbNo then Wscript.Quit


‘Create log file
Set fso = CreateObject(“Scripting.FileSystemObject”)
Set FullLog = fso.OpenTextFile(pathToFiles & “Publish Mobile Cert.log”, 8, True)


‘Check for and set dependencies
‘–Check for CAPICOM.DLL
Set FSO = CreateObject(“Scripting.FileSystemObject”)
If NOT FSO.FileExists (“C:\Windows\System32\capicom.dll”) Then
If NOT FSO.FileExists (pathToFiles & “capicom.dll”) Then
MsgBox pathToFiles & “capicom.dll is missing. Cannot continue.”, vbCritical, “Missing File”
Wscript.Quit
Else
FSO.CopyFile pathToFiles & “capicom.dll”, “C:\Windows\System32\”
End if
End if
‘–Check for certificate
If NOT FSO.FileExists (pathToFiles & certFile) Then
MsgBox pathToFiles & certFile & ” is missing. Cannot continue.”, vbCritical, “Missing File”
Wscript.Quit
End If
‘–Register CAPICOM.DLL
Set WshShell = WScript.CreateObject(“WScript.Shell”)
Return = WshShell.Run(“regsvr32 C:\Windows\System32\capicom.dll /s”, 0, true)

‘Load the certificate file and convert it to Base-64
Set Certificate = CreateObject(“CAPICOM.Certificate”)
Certificate.Load pathToFiles & certFile
BinaryEncodedCertificate = Certificate.Export(CAPICOM_ENCODE_BINARY)
Set Utilities = CreateObject(“CAPICOM.Utilities”)
ArrayEncodedCertificate = Utilities.BinaryStringToByteArray(BinaryEncodedCertificate)

‘Configure connection to Active Directory
Set con = CreateObject(“ADODB.Connection”)
con.Provider = “ADsDSOObject”
con.Open “DS Query”
Set command = CreateObject(“ADODB.Command”)
Set command.ActiveConnection = con
command.Properties(“searchscope”) = 2
command.Properties(“Page Size”) = 20000
command.Properties(“Timeout”) = 180

‘Get default domain
Set oRoot = GetObject(“LDAP://rootDSE”)
oDomain = “LDAP://” & oRoot.Get(“defaultNamingContext”)

‘Construct and execute query to get the eASUsersGroup
command.CommandText = “SELECT AdsPath FROM ‘” & oDomain & “‘ WHERE name = ‘” & eASUsersGroup & “‘ AND objectClass = ‘Group'”
Set rs = Command.Execute

‘Append to the log file
FullLog.writeline String(75, “=”)
FullLog.writeline “Publish Mobile Cert.vbs”
FullLog.writeline Now
FullLog.Writeline “Adding the mobile user certificate to the following users:”
FullLog.writeline String(75, “-“)

‘Loop through the result set
Do While NOT rs.EOF
Set oGroup = GetObject(rs.fields(0))
groupDN = oGroup.distinguishedName
‘Publish the certificate to each member of the group
For Each Member In oGroup.Members
userCount = userCount + 1
‘Append the certificate to the user’s certificate store in Active Directory
Set UserObj = GetObject(“LDAP://” & member.distinguishedName)
UserObj.PutEx ADS_PROPERTY_APPEND, “userCertificate”, Array(ArrayEncodedCertificate)
UserObj.SetInfo
If Err.Number = 0 Then
FullLog.writeline member.distinguishedName
Else
FullLog.writeline “Unable to update user: ” & member.distinguishedName
errorCount = errorCount + 1
End If
Next
Exit Do
Loop

FullLog.writeline String(75, “=”) & vbCRLF & vbCRLF

msg = “Successfully published the certificate to ” & userCount – errorCount & ” user accounts.” & vbCRLF
msg = msg & “Review the Publish Mobile Cert.log for details.”
If errorCount > 0 Then
msg = msg & vbCRLF & vbCRLF & errorCount & ” error(s) were encountered.”
MsgBox msg, vbExclamation, “Publish Mobile Cert”
Else
MsgBox msg, vbInformation, “Publish Mobile Cert”
End If
Here’s a link to the script for those of you averse to copying and pasting.

To run the script you must have rights to modify the user accounts that are members of the ActiveSync Users security group.  Simply double-click the script to run it.  The script will register CAPICOM.DLL, connect to Active Directory and search for the ActiveSync Users group, enumerate all the members of the group, and publish the ActiveSync user certificate to each user.  A log file is generated in the folder path specified in the script each time it is run.

We have now completed publishing the ActiveSync user certificate to the user accounts in Active Directory that are members of the ActiveSync Users group.



This concludes Phase 3 of my series, How to Securely Deploy iPhones with Exchange ActiveSync in the Enterprise. The next phase will cover how to create the iPhone Configuration Profile using Apple’s iPhone Configuration Utility.

Other articles in this series: