e.g. if the system returns email@example.com but this is not in the address policy as valid "used" e-mail address. Then this could be the issue.
If this is the issue test with the primary smtp address or another valid address that is in the e-mail address properties by using that address in the registry key. stated above instead.
Have added firstname.lastname@example.org to the HKLM\Software\WOW6432Node\McAfee\MSME\E2007\ - ODUserID registry key.
It is a valid address - it can send receive mail and is in OD users mailbox e-mail address properties.
This doesn't appear to have made any difference to the On-Demand scan task.
the value for the ODUSerID reg value needs to be set to the upn value for the msmeoduser account. in the properties of the mailbox for that user is where you need to have an smtp address that matches the upn address. that smtp address just needs to be a secondary smtp listing.
so if ad domain is abc.local and primary smtp address is company.com this is how it needs to be setup
ODUserID reg value = email@example.com
smtp addresses for msmeoduser
Primary = firstname.lastname@example.org
secondary = email@example.com
also make sure that the msmeoduser account isn't locked out or disabled in AD.
the other thing that i would do is make sure the ewswrapper dll is registered.
you can do this by opening a cmd prompt and cd to the msme\bin folder
type the following as is -- configurex64.exe RegisterEWSWrapper
the parameter after the .exe is case sensitive. this will update/create a file called MCEWSWrapper.tlb in the bin folder
Have undertaken new installations of MSME 8 through ePO and clean Standalone installs on the Exchange server. Have implemented the registry changes suggested above, yet any form of on-demand scan still 'completes' after 50 seconds or so with same error message - 'On-demand scan task failed due to 'EWSWrapper failure while CoCreateInstance'.
Management are getting pretty fed up and asking me to consider other products.
It would be adviseable then to get a case open with support.. It would be good to have the debug logs ready.
Createa a new local folder ... e.g c:\debugs.
In interface - setting and diagnostics - diagnostics.
Set Log Level "High"
Set Specify location for Debug files"
From Drop down list select "Full Path"
Enter your new folder e.g. C:\Debug.
Run the ODS and as you state it will fail within 50 secs.
Set Diagnostics "Log Level" back to None.
Zip up logs and attach to your case or send to your support representative.
Another thought .... Is the EWSUrl reg populated with correct information detail on your environment... heres description from guide...
This is the URL used to connect to Exchange
web services hosted by CAS server. This value
is populated by powershell script
GetHubTxDetails.ps1 during installation and
also whenever MSME service is restarted.
(Maybe drop a copy of HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\McAfee reg export in with debug logs)
I had the same error under MSME 8.5. I setup a log (per Aidan instruction) and after looking this file RunScheduleX64.txt I found this entry:
EWSWrapper object created
9:29, 09:34:30.9767375, Thread ID: 1, Level: Info, init called usr: MSMEODUser@ourdomain.corp
9:29, 09:34:30.9767375, Thread ID: 1, Level: Info, Number of items to load for each ews call: 10
9:29, 09:34:31.0079883, Thread ID: 1, Level: Info, Making use of default Autodiscover for user : MSMEODUser@ourdomain.corp
9:29, 09:34:33.7736841, Thread ID: 1, Level: Info, AutodiscoverRemoteException Exception: The e-mail address cannot be found.
Then I realize that there are some other entry for ODUserID because I have everything correct under HKLM\Software\WOW6432Node\McAfee\MSME\E2007\ - ODUserID registry key. I did start looking for the same ID in the rest of the MCafee registry entries and I found the problem under HKLM\Software\WOW6432Node\McAfee\MSME\SystemState\. Tehre was another instance of ODUserID that had the wrong email address. After changing it to the actual email (the same one under E2007 entry) on-demand scanning start working without problem.