Quest CPUU / EMWProf and Windows Credential Manager

I ran into an issue on my current project with Quest Client Profile Update Utility (CPUU).  The CPUU / EMWProf was prompting for user or password or it was failing with MAPI_E_FAILONEPROVIDER error.  The error message or result wasn’t consistent. 

 

The CPUU log shows the utility wasn’t getting the correct source and target user name and password from the INI file.  The utility was trying to open target mailbox using source admin account etc.  I even have specified the target domain domain in the Domaincfg section. 

I was using the latest version of the CPUU utility (5.2).   Clearing the credentials on local machine did not help in my situation.  My solution was to disable the Windows Credential Manger using a GPO (Network access:  Do not allow storage of passwords and credentials – Enabled).  You can GPO details in the following screenshot:

 

 

The following is the error message details from CPUU log file:

 

MAPI error.

Error code: 0x8004011d

Description: MAPI_E_FAILONEPROVIDER

Extended error description:

   Component:         Microsoft Exchange Information Store

   Error description: Microsoft Exchange is not available.  Either there are network problems or the Exchange server is down for maintenance.

   Context:           1318

   Low level:         2147746069

MAPI error.

Error code: 0x8004010f

Description: MAPI_E_NOT_FOUND

http://www.amazon.com/dp/1849687447/?tag=packtpubli-20

>Outlook – Cannot move the items to PST

>

digg_url = “http://santhoshsivarajan.blogspot.com/2010/01/outlook-cannot-move-items-to-pst.html”;digg_title = “Outlook – Cannot move the items to PST”;digg_bgcolor = “#FFFFFF”;digg_skin = “normal”;digg_url = undefined;digg_title = undefined;digg_bgcolor = undefined;digg_skin = undefined;

I was at a client site doing migrations using Quest Migration Manager (QMM).  After the EMWProf update, users started complaining that they can’t move any mail items from their mailbox to PST and they were getting the following error message:

The issue was related to a GPO that prevents users from moving/adding more items to the PST file.  Here is the registry configuration info:

HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\PST\PSTDisableGrow

If you configure the PSTDisableGrow value to 1, it will prevent Outlook from creating new items in a PST file.